Could you try putting * in each of the proxy configuration lines to verify it isn't an issue with user/machine name resolution?
<property> <name>hadoop.proxyuser.oozie.hosts</name> <value>*</value> </property> <property> <name>hadoop.proxyuser.oozie.groups</name> <value>*</value> </property> ~Matt -----Original Message----- From: Suresh S [mailto:[email protected]] Sent: Wednesday, November 30, 2011 11:12 AM To: [email protected] Subject: AuthorizationException on running a oozie job Hi**** I am using Hadoop version: 0.20.203, and yahoo Oozie version: 3.0.2. Successfully ran the oozie, able to see the oozie webconsole,**** ** ** Able to run the hadoop job successfully, but When I am trying to run the example job of oozie, ** I get the below exception:**** ** ** org.apache.oozie.service.AuthorizationException: E0902: Exception occured: [java.net.ConnectException: Call to localhost/127.0.0.1:54310 failed on connection exception: java.net.ConnectException: Connection refused]**** at org.apache.oozie.service.AuthorizationService.authorizeForApp(AuthorizationService.java:320)**** at org.apache.oozie.servlet.BaseJobServlet.checkAuthorizationForApp(BaseJobServlet.java:185)**** at org.apache.oozie.servlet.BaseJobsServlet.doPost(BaseJobsServlet.java:89)**** at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)**** at org.apache.oozie.servlet.JsonRestServlet.service(JsonRestServlet.java:281)**** at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)**** at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)**** at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)**** at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)**** at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)**** at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)**** at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)**** at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)**** at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)**** at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)**** at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)**** at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)**** at java.lang.Thread.run(Thread.java:679)**** ** ** $ bin/oozie job -config /home/oozie/oozie_ex/examples/apps/map-reduce/job.properties -run**** Error: E0902 : E0902: Exception occured: [java.net.ConnectException: Call to localhost/127.0.0.1:54310 failed on connection exception: java.net.ConnectException: Connection refused]**** ** ** port 54310 is running fine.**** root@ZETA23089:~# netstat -nltp**** Active Internet connections (only servers)**** Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name**** tcp6 0 0 10.105.165.8:54310 :::* LISTEN 13214/java**** tcp6 0 0 10.105.165.8:54311 :::* LISTEN 13553/java**** ** ** my job.properties file is correctly pointing to NN/JT:**** nameNode=hdfs://localhost:54310**** jobTracker=localhost:54311**** queueName=default**** examplesRoot=examples**** ** ** oozie.wf.application.path=${nameNode}/user/${user.name}/${examplesRoot}/apps/map-reduce**** outputDir=map-reduce**** ** ** The proxy entries in core-site.xml,**** Core-site.xml:**** <property>**** <name>hadoop.proxyuser.oozie.hosts</name>**** <value>localhost</value>**** </property>**** <property>**** <name>hadoop.proxyuser.oozie.groups</name>**** <value>oozie</value>**** </property> hadn't changed the default oozie-site.xml Thanks.**** Suresh S This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited. All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto, including its subsidiaries. The recipient of this e-mail is solely responsible for checking for the presence of "Viruses" or other "Malware". Monsanto, along with its subsidiaries, accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment. The information contained in this email may be subject to the export control laws and regulations of the United States, potentially including but not limited to the Export Administration Regulations (EAR) and sanctions regulations issued by the U.S. Department of Treasury, Office of Foreign Asset Controls (OFAC). As a recipient of this information you are obligated to comply with all applicable U.S. export laws and regulations.
