Description
If you specify an incorrect oozie url (e.g. its quite common for users to type http://localhost:11000 instead of http://localhost:11000/oozie) on a secure cluster (kerberos) and oozie hasn't already cached the delegation token (in ~/.oozie-auth-token), the oozie client gives a nasty NPE error:
$ rm ~/.oozie-auth-token $ kinit ... $ oozie admin -status -oozie http://localhost:11000 java.lang.NullPointerException at java.io.Writer.write(Writer.java:140) at org.apache.oozie.client.AuthOozieClient.writeAuthToken(AuthOozieClient.java:182) at org.apache.oozie.client.AuthOozieClient.createConnection(AuthOozieClient.java:137) at org.apache.oozie.client.OozieClient.validateWSVersion(OozieClient.java:243) at org.apache.oozie.client.OozieClient.createURL(OozieClient.java:344) at org.apache.oozie.client.OozieClient.access$000(OozieClient.java:76) at org.apache.oozie.client.OozieClient$ClientCallable.call(OozieClient.java:410) at org.apache.oozie.client.OozieClient.getSystemMode(OozieClient.java:1299) at org.apache.oozie.cli.OozieCLI.adminCommand(OozieCLI.java:1323) at org.apache.oozie.cli.OozieCLI.processCommand(OozieCLI.java:499) at org.apache.oozie.cli.OozieCLI.run(OozieCLI.java:466) at org.apache.oozie.cli.OozieCLI.main(OozieCLI.java:176) null
Once Oozie writes the auth token (because you used the correct url), if you then give an incorrect url, it will return a more appropriate 404 error:
$ sudo -u oozie oozie admin -status -oozie http://localhost:11000/oozie $ ls ~/.oozie-auth-token /home/rkanter/.oozie-auth-token $ sudo -u oozie oozie admin -status -oozie http://localhost:11000 Error: HTTP error code: 404 : Not Found
Attachments
Attachments
Issue Links
- is related to
-
OOZIE-1010 Oozie CLI throws an NPE with Hadoop trunk with simple auth
- Resolved
- relates to
-
HADOOP-10078 KerberosAuthenticator always does SPNEGO
- Closed