Reputation: 2497
The command :
oozie job -oozie http://localhost:8080/oozie -config /home/hadoop/Desktop/Cloudera/oozie-2.3.0-cdh3u1/examples/apps/no-op/job.properties -run
Error message:
Error: IO_ERROR : java.net.ConnectException: Connection refused
Upvotes: 3
Views: 9733
Reputation: 2095
If you are not an Admin make sure you are invoking the oozie client from the correct node. Use localhost
only if you are connecting the client from the machine where the oozie server is running. If you are a developer like me who is connecting from an edge node make sure you are exporting the correct URL of oozie the server.
I had a similar problem in my cluster(CDH 5.3.6) running on AWS. I was trying to export the OOZIE_URL just with the host name and port like below
[user@ip-10-241-1-164 ~]$ export OOZIE_URL=http://10.241.1.164:11000/oozie
but it was throwing the same error. It did not like the host name. Finally I have navigated to the Oozie section (find the steps at the end) in Hue and found the oozie.servers value
oozie.servers
value ip-10-241-1-111.ec2.internal=http://ip-10-241-1-111.ec2.internal:11000/oozie
copied the value and changed the export command like this
[user@ip-10-241-1-164 ~]$ export OOZIE_URL=http://ip-10-241-1-111.ec2.internal:11000/oozie
and that has fixed my issue.
How to find the oozie.servers value:
Upvotes: 0
Reputation: 1
It took me 2 days to fix this error. In my case I had 4 Nodes. Oozie was configured in Node 4. But I kept on running the command to name-node which was N1 or hive server which was N3. So make sure you are running command against Oozie server.
Upvotes: 0
Reputation: 2497
Finally I configured the oozie
Steps
Add this line in core-site.xml in hadoop conf
hadoop.proxyuser.xxx.hosts * hadoop.proxyuser.xxx.groups *
Here, xxx - User name
Save the conf file and run the code
oozie job -oozie http://localhost:11000/oozie -config /home/hadoop/Desktop/Cloudera/oozie-2.3.0-cdh3u1/examples/apps/no-op/job.properties -run
Upvotes: 3