Reply
Highlighted
New Contributor
Posts: 4
Registered: ‎10-26-2016

Oozie Error

Hi ,  Am using CDH5.8.3  ,

I have started oozie service from cloudera manager . While submiting workflow  and running any of oozie admin commands  , am getting the following error ,

 

Error: IO_ERROR : java.io.IOException: Error while connecting Oozie server. No of retries = 1. Exception = Could not authenticate, Authentication failed, status: 302, message: Found

 

proxyuser host and group are '*' by default . Still issue is there. 

Cloudera Employee
Posts: 267
Registered: ‎03-23-2015

Re: Oozie Error

Hi,

 

I believe that those errors were from client output, can you also paste the error from the Oozie server log? Do you have Kerberos enabled? Did you mean that all Oozie commands fail with the same error?

New Contributor
Posts: 4
Registered: ‎10-26-2016

Re: Oozie Error

Kerberos is not enabled. All oozie commands fails with this error . Logs have only the following entries ,


2017-01-02 13:05:54,632 INFO org.apache.oozie.service.PauseTransitService: SERVER[server] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[-] ACTION[-] Acquired lock for [org.apache.oozie.service.PauseTransitService]
2017-01-02 13:05:54,639 INFO org.apache.oozie.service.PauseTransitService: SERVER[server] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[-] ACTION[-] Released lock for [org.apache.oozie.service.PauseTransitService]
2017-01-02 13:06:39,624 INFO org.apache.oozie.service.StatusTransitService$StatusTransitRunnable: SERVER[server] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[-] ACTION[-] Acquired lock for [org.apache.oozie.service.StatusTransitService]
2017-01-02 13:06:39,625 INFO org.apache.oozie.service.StatusTransitService$StatusTransitRunnable: SERVER[server] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[-] ACTION[-] Running coordinator status service from last instance time = 2017-01-02T12:05Z
2017-01-02 13:06:39,627 INFO org.apache.oozie.service.StatusTransitService$StatusTransitRunnable: SERVER[server] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[-] ACTION[-] Running bundle status service from last instance

Contributor
Posts: 66
Registered: ‎01-19-2017

Re: Oozie Error

Hi,

 

     did you find solution for the above problem?

 

 

Thanks & Regards,

J.Ganesh Kumar.

New Contributor
Posts: 3
Registered: ‎11-13-2017

Re: Oozie Error

Hi,

 

We have the same issue here:

[user@server tmp]$ klist
Ticket cache: FILE:/tmp/krb5cc_1221406138_rBzFRx
Default principal: user@CORP.SOMECORP.HU

Valid starting Expires Service principal
04/06/2018 09:01:20 04/06/2018 19:01:20 krbtgt/CORP.SOMECORP.HU@CORP.SOMECORP.HU
renew until 04/07/2018 09:01:20
[user@server tmp]$ oozie admin -oozie http://localhost:11001/oozie -status
Connection exception has occurred [ java.net.SocketException Connection reset ]. Trying after 1 sec. Retry count = 1
Connection exception has occurred [ java.net.SocketException Connection reset ]. Trying after 2 sec. Retry count = 2
^C[user@server tmp]oozie admin -oozie http://localhost:11000/oozie -status
Error: IO_ERROR : java.io.IOException: Error while connecting Oozie server. No of retries = 1. Exception = Could not authenticate, Authentication failed, URL: http://localhost:11000/oozie/versions?server.name=user, status: 302, message: Found

 

We would really appreciate some insight on this! Thank you

Cloudera Employee
Posts: 267
Registered: ‎03-23-2015

Re: Oozie Error

Hi,

You used the wrong Oozie URL, once the cluster is kerberized, you need to use the Oozie URL that matches with the kerberos principal. So please update the URL from :

http://localhost:11000/oozie

To:

http://<oozie-url>:11000/oozie

Let me know if that helps.
Announcements