You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@oozie.apache.org by The Trainer <tr...@gmail.com> on 2013/05/29 13:19:29 UTC

E0901: Namenode [pofmv1145] not allowed, not in Oozies whitelist

Hi Shouvanik Haldar,

You might be havig hdfs:// as prefix in your Job Tracker URL.

Yesterday I had the similar issue and found that my Job Tracker URL has
above said prefix. Once I removed it worked.

Also check in OOzie UI - System Info page - Job Tracker Whitelist property.
I found out my Job Tracker Host name with 8021 port number does exists but
still I got below error. This error I got before removing the hdfs:// After
removal it worked.

Mohammad Islam <mi...@yahoo.com>SubjectRe: Oozie 2.3.2 - Long running
coordinators - purge service not deleting historical actionsDateWed, 29 May
2013 08:53:15 GMT

Hi ,
No never used talented.

Is there any value for property
(oozie.service.HadoopAccessorService.nameNode.whitelist) in
conf/ooze-site.xml?

Regards,
Mohammad


________________________________
 From: "shouvanik.haldar@accenture.com" <sh...@accenture.com>
To: user@oozie.apache.org
Sent: Tuesday, May 28, 2013 10:45 PM
Subject: RE: Oozie 2.3.2 - Long running coordinators - purge service
not deleting historical
actions


Has anyone ever faced a problem like below

[2013-05-28 14:25:01]Deploying job to Hadoop...
[2013-05-28 14:32:50]Deployment complete!
[2013-05-28 14:33:01]Error submitting workflow job to Oozie.
[2013-05-28 14:33:01]Please check if the "Job tracker end point" and
"Oozie end point" are
valid!
[2013-05-28 14:33:01]E0901. E0901: Namenode [pofmv1145] not allowed,
not in Oozies whitelist


Has anybody used OOZIE with Talend?

Regards,
Shouvanik

RE: E0901: Namenode [pofmv1145] not allowed, not in Oozies whitelist

Posted by sh...@accenture.com.
Thanks!

Regards,
Shouvanik

-----Original Message-----
From: The Trainer [mailto:training.my.hobby@gmail.com]
Sent: Wednesday, May 29, 2013 4:49 PM
To: user@oozie.apache.org
Subject: E0901: Namenode [pofmv1145] not allowed, not in Oozies whitelist

Hi Shouvanik Haldar,

You might be havig hdfs:// as prefix in your Job Tracker URL.

Yesterday I had the similar issue and found that my Job Tracker URL has above said prefix. Once I removed it worked.

Also check in OOzie UI - System Info page - Job Tracker Whitelist property.
I found out my Job Tracker Host name with 8021 port number does exists but still I got below error. This error I got before removing the hdfs:// After removal it worked.

Mohammad Islam <mi...@yahoo.com>SubjectRe: Oozie 2.3.2 - Long running coordinators - purge service not deleting historical actionsDateWed, 29 May
2013 08:53:15 GMT

Hi ,
No never used talented.

Is there any value for property
(oozie.service.HadoopAccessorService.nameNode.whitelist) in conf/ooze-site.xml?

Regards,
Mohammad


________________________________
 From: "shouvanik.haldar@accenture.com" <sh...@accenture.com>
To: user@oozie.apache.org
Sent: Tuesday, May 28, 2013 10:45 PM
Subject: RE: Oozie 2.3.2 - Long running coordinators - purge service not deleting historical actions


Has anyone ever faced a problem like below

[2013-05-28 14:25:01]Deploying job to Hadoop...
[2013-05-28 14:32:50]Deployment complete!
[2013-05-28 14:33:01]Error submitting workflow job to Oozie.
[2013-05-28 14:33:01]Please check if the "Job tracker end point" and "Oozie end point" are valid!
[2013-05-28 14:33:01]E0901. E0901: Namenode [pofmv1145] not allowed, not in Oozies whitelist


Has anybody used OOZIE with Talend?

Regards,
Shouvanik

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited.

Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.

______________________________________________________________________________________

www.accenture.com


RE: E0901: Namenode [pofmv1145] not allowed, not in Oozies whitelist

Posted by sh...@accenture.com.
The previous problem got resolved. Issue with ports of Hadoop Jobtracker and namenode.

Now, I have a simple job. (non big-data, just displaying message). But I am getting the below error

[2013-05-30 16:57:24]Deploying job to Hadoop...
[2013-05-30 16:58:12]Deployment complete!
[2013-05-30 16:58:23]Job is running ...
[2013-05-30 16:58:40]Job killed!
[2013-05-30 16:58:41]Main class [demo.test_job_0_1.test_job], exit code [1]
[2013-05-30 16:58:41]Job failed, error message[Main class [demo.test_job_0_1.test_job], exit code [1]]


Any idea. Please help

Regards,
Shouvanik


-----Original Message-----
From: The Trainer [mailto:training.my.hobby@gmail.com]
Sent: Wednesday, May 29, 2013 4:49 PM
To: user@oozie.apache.org
Subject: E0901: Namenode [pofmv1145] not allowed, not in Oozies whitelist

Hi Shouvanik Haldar,

You might be havig hdfs:// as prefix in your Job Tracker URL.

Yesterday I had the similar issue and found that my Job Tracker URL has above said prefix. Once I removed it worked.

Also check in OOzie UI - System Info page - Job Tracker Whitelist property.
I found out my Job Tracker Host name with 8021 port number does exists but still I got below error. This error I got before removing the hdfs:// After removal it worked.

Mohammad Islam <mi...@yahoo.com>SubjectRe: Oozie 2.3.2 - Long running coordinators - purge service not deleting historical actionsDateWed, 29 May
2013 08:53:15 GMT

Hi ,
No never used talented.

Is there any value for property
(oozie.service.HadoopAccessorService.nameNode.whitelist) in conf/ooze-site.xml?

Regards,
Mohammad


________________________________
 From: "shouvanik.haldar@accenture.com" <sh...@accenture.com>
To: user@oozie.apache.org
Sent: Tuesday, May 28, 2013 10:45 PM
Subject: RE: Oozie 2.3.2 - Long running coordinators - purge service not deleting historical actions


Has anyone ever faced a problem like below

[2013-05-28 14:25:01]Deploying job to Hadoop...
[2013-05-28 14:32:50]Deployment complete!
[2013-05-28 14:33:01]Error submitting workflow job to Oozie.
[2013-05-28 14:33:01]Please check if the "Job tracker end point" and "Oozie end point" are valid!
[2013-05-28 14:33:01]E0901. E0901: Namenode [pofmv1145] not allowed, not in Oozies whitelist


Has anybody used OOZIE with Talend?

Regards,
Shouvanik

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited.

Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.

______________________________________________________________________________________

www.accenture.com