Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hadoop >> mail # user >> RE: Oozie workflow error - renewing token issue

Copy link to this message
Re: Oozie workflow error - renewing token issue
The token renewer needs to be the job tracker principal.  I think oozie had "mr token" hardcoded at one point, but later changed it to use a conf setting.

The rest of the log looks very odd - ie. it looks like security is off, but it can't be.  It's trying to renew hdfs tokens issued for the "hdfs" superuser.  Are you running your job as hdfs?  With security enabled, the container executor won't run jobs for hdfs…  It's also trying to renew as "mapred (auth:SIMPLE)".  SIMPLE means that security is disabled, which doesn't make sense since tokens require kerberos.

The cannot find renewer class for MAPREDUCE_DELEGATION_TOKEN is also odd because it did subsequently try to renew the token.


On Jan 30, 2013, at 2:14 PM, Alejandro Abdelnur wrote:


[Moving thread to user@oozie.a.o, BCCing common-user@hadoop.a.o]

* What version of Oozie are you using?
* Is the cluster a secure setup (Kerberos enabled)?
* Would you mind posting the complete launcher logs?


On Wed, Jan 30, 2013 at 6:14 AM, Corbett Martin <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:
Thanks for the tip.

The sqoop command listed in the stdout log file is:

The following information is from the sterr and stdout log files.

/var/log/hadoop-0.20-mapreduce/userlogs/job_201301231648_0029/attempt_201301231648_0029_m_000000_0 # more stderr
No such sqoop tool: sqoop. See 'sqoop help'.
Intercepting System.exit(1)
Failing Oozie Launcher, Main class [org.apache.oozie.action.hadoop.SqoopMain], exit code [1]
/var/log/hadoop-0.20-mapreduce/userlogs/job_201301231648_0029/attempt_201301231648_0029_m_000000_0 # more stdout
>>> Invoking Sqoop command line now >>>

1598 [main] WARN  org.apache.sqoop.tool.SqoopTool  - $SQOOP_CONF_DIR has not been set in the environment. Cannot check for additional configuration.
Intercepting System.exit(1)

<<< Invocation of Main class completed <<<

Failing Oozie Launcher, Main class [org.apache.oozie.action.hadoop.SqoopMain], exit code [1]

Oozie Launcher failed, finishing Hadoop job gracefully

Oozie Launcher ends
~Corbett Martin
Software Architect
AbsoluteAR Accounts Receivable Services - An NHIN Solution

-----Original Message-----
From: Harsh J [mailto:[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>]
Sent: Tuesday, January 29, 2013 10:11 PM
Subject: Re: Oozie workflow error - renewing token issue

The job that Oozie launches for your action, which you are observing is failing, does its own logs (task logs) show any errors?

On Wed, Jan 30, 2013 at 4:59 AM, Corbett Martin <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:
> Oozie question
> I'm trying to run an Oozie workflow (sqoop action) from the Hue
> console and it fails every time.  No exception in the oozie log but I
> see this in the Job Tracker log file.
> Two primary issues seem to be
> 1.   Client mapred tries to renew a token with renewer specified as mr token
> And
> 2.   Cannot find class for token kind MAPREDUCE_DELEGATION_TOKEN
> Any ideas how to get past this?
> Full Stacktrace:
> 2013-01-29 17:11:28,860 INFO
> org.apache.hadoop.security.token.delegation.AbstractDelegationTokenSecretManager:
> Creating password for identifier: owner=hdfs, renewer=mr token,

Harsh J

This message and its contents (to include attachments) are the property of National Health Systems, Inc. and may contain confidential and proprietary information. This email and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed. You are hereby notified that any unauthorized disclosure, copying, or distribution of this message, or the taking of any unauthorized action based on information contained herein is strictly prohibited. Unauthorized use of information contained herein may subject you to civil and criminal prosecution and penalties. If you are not the intended recipient, you should delete this message immediately and notify the sender immediately by telephone or by replying to this transmission.