Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
All solutions
    • All solutions for Yandex Data Processing
    • Yandex Data Processing cluster is in the `UNKNOWN` status right after it has been created
    • Resolving the error of access to S3 buckets from a Yandex Data Processing 1.4 cluster
    • No logs in YARN Resource Manager Web UI after running jobs

In this article:

  • Issue description
  • Solution
  1. Yandex Data Processing
  2. No logs in YARN Resource Manager Web UI after running jobs

No logs in the YARN Resource Manager web UI after running jobs

Written by
Yandex Cloud
Updated at December 17, 2025
  • Issue description
  • Solution

Issue descriptionIssue description

You cannot view logs for a completed job in the YARN Resource Manager web UI of your Yandex Data Processing cluster; however, you see the logs when running a job. When trying to view logs, you get this message:

Failed redirect for container_....

Failed while trying to construct the redirect url to the log server. Log Server url may not be configured
Local Logs:
java.lang.Exception: Unknown container. Container either has not started or has already completed or doesn't belong to this node at all.

SolutionSolution

Log aggregation is enabled on clusters by default. After a container completes its jobs, its logs are transferred to HDFS. The YARN UI only displays logs when they are placed directly in the node file system. We can suggest a few workarounds:

  • Get logs from HDFS using this command:

    sudo -u hdfs hadoop fs -ls /var/log/yarn/
    
  • Get logs via the YARN CLI:

    yarn logs -applicationId
    
  • Configure log export to S3:

    yc dataproc cluster update <id_cluster> \
          --property "yarn:yarn.nodemanager.remote-app-log-dir=s3a://<bucket>/yarn-logs/"
          --property "yarn:yarn.log-aggregation.retain-seconds=-1"
    

Warning

The --property option will reset all component properties that were not explicitly provided, to their default values. To save the properties you updated, list them in your request along with the ones you want to update.

Enable log aggregation to view logs for an application that has ended in the UI. You can do this using the following CLI command:

yc dataproc cluster update your_cluster --property yarn:yarn.log-aggregation-enable=false

Was the article helpful?

Previous
Resolving the error of access to S3 buckets from a Yandex Data Processing 1.4 cluster
Next
All solutions for DataSphere
© 2025 Direct Cursus Technology L.L.C.