Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

TIP: when you get a message in job log user [Dr. Who] is not authorized to view the log

avatar
Master Mentor

here's the message

355-error-message.png

here's a quick fix, replace root with the user executing the job

356-correction.png

1 ACCEPTED SOLUTION

avatar
Expert Contributor

This should help:

PROBLEM Customer unable to see logs via Resource Manager UI due to incorrect permissions for the default user dr.who.

RESOLUTION Customer changed the following property in core-site.xml to resolve the issue. Other values such as hdfs or mapred also resolve the issue. If the cluster is managed by Ambari, this should be added in Ambari > HDFS > Configurations >Advanced core-site > Add Property

hadoop.http.staticuser.user=yarn

View solution in original post

14 REPLIES 14

avatar

Which Ambari version did you use to install the cluster?

Ambari fixed the issue in its 2.1.1 version, see AMBARI-12415. The issue was with the setting of property "yarn.admin.acl" value.

avatar
Master Mentor

this is in Sandbox 2.3.2

avatar
Expert Contributor

Hi Artem,

You have steps to repro? I run a tez job and don't get the behavior.

Regards,

Robert

avatar

@rmolina@hortonworks.com same here sandbox 2.3.2. it's easy to reproduce, it happens to all applications created by spark-shell, spark-submit or zeppelin

avatar
Master Mentor

not just spark, mapreduce as well. I ran an oozie job that executes a pig script in mapreduce mode and it prompted that message

avatar

@rmolina@hortonworks.com I was just able to confirm this behavior on the latest 2.3.2 sandbox when you go to Resource Manager UI , you get the same error message [Dr.Who]

avatar
Expert Contributor

This should help:

PROBLEM Customer unable to see logs via Resource Manager UI due to incorrect permissions for the default user dr.who.

RESOLUTION Customer changed the following property in core-site.xml to resolve the issue. Other values such as hdfs or mapred also resolve the issue. If the cluster is managed by Ambari, this should be added in Ambari > HDFS > Configurations >Advanced core-site > Add Property

hadoop.http.staticuser.user=yarn

avatar
Master Mentor

Just tested this, it does work, can we set this by default in the future Sandbox releases?

avatar
Super Collaborator

Applied the suggested parameter on our env cluster, and it works!

Thanks!

https://community.hortonworks.com/questions/43331/user-drwho-is-not-authorized-to-view-the-logs.html