# Troubleshooting


See the following sections for troubleshooting solutions.

## Logging


EMR Serverless uses Spark resources profiles to split job execution. EMR Serverless uses the user profile to run the code you supplied, while the system profile enforces Lake Formation policies. You can access the logs for the tasks ran as the user profile.

For more information about debugging Lake Formation-enabled jobs, refer to [Debugging jobs](emr-serverless-lf-enable-debugging.html).

## Live UI and Spark History Server


The Live UI and the Spark History Server have all Spark events generated from the user profile and redacted events generated from the system driver.

You can see all of the tasks from the user and system drivers in the **Executors** tab. However, log links are available only for the user profile. Also, some information is redacted from Live UI, such as the number of output records.

## Job failed with insufficient Lake Formation permissions


Make sure that your job runtime role has the permissions to run SELECT and DESCRIBE on the table that you are accessing.

## Job with RDD execution failed


EMR Serverless currently doesn't support resilient distributed dataset (RDD) operations on Lake Formation-enabled jobs.

## Unable to access data files in Amazon S3


Make sure you have registered the location of the data lake in Lake Formation.

## Security validation exception


EMR Serverless detected a security validation error. Contact Amazon support for assistance.

## Sharing Amazon Glue Data Catalog and tables across accounts


You can share databases and tables across accounts and still use Lake Formation. For more information, refer to [Cross-account data sharing in Lake Formation](https://docs.amazonaws.cn/lake-formation/latest/dg/cross-account-permissions.html) and [How do I share Amazon Glue Data Catalog and tables cross-account using Amazon Lake Formation?](https://repost.aws/knowledge-center/glue-lake-formation-cross-account).