Created 03-21-2016 10:55 AM
I have install Oozie with Ambari but I am getting 2 alerts this is m tail of ambari-alerts.log
root@VM-HADOOP-SLAVE2:/var/log/ambari-agent# tail -8 ambari-alerts.log INFO 2016-03-17 17:29:13,985 logger.py:67 - call['test -w /run/user'] {'sudo': True, 'timeout': 5} INFO 2016-03-17 17:29:13,994 logger.py:67 - call returned (0, '') INFO 2016-03-17 17:29:13,994 logger.py:67 - call['test -w /hadoop'] {'sudo': True, 'timeout': 5} INFO 2016-03-17 17:29:14,004 logger.py:67 - call returned (0, '') INFO 2016-03-17 17:29:17,158 logger.py:67 - Execute['export HIVE_CONF_DIR='/usr/hdp/current/hive-metastore/conf/conf.server' ; hive --hiveconf hive.metastore.uris=thriftm-hadoop-slave2.out:9083 --hiveconf hive.metastore.client.connect.retry.delay=1 --hiveconf hive.metastore.failure.retries=1 -hiveconf hive.metastore.connect.retries=1 --hiveconf hive.metastore.client.socket.timeout=14 --hiveconf hive.execution.engine=mr -e 'shotabases;''] {'path': ['/bin/', '/usr/bin/', '/usr/sbin/', '/usr/hdp/current/hive-metastore/bin'], 'user': 'ambari-qa', 'timeout': 30} INFO 2016-03-17 17:29:17,177 logger.py:67 - Execute['! beeline -u 'jdbc:hive2://vm-hadoop-slave2.out:11000/;transportMode=binary' -e '' 2>&1| awk '{print}'|grep -i -e 'Cction refused' -e 'Invalid URL''] {'path': ['/bin/', '/usr/bin/', '/usr/lib/hive/bin/', '/usr/sbin/'], 'user': 'ambari-qa', 'timeout': 30} INFO 2016-03-17 17:29:17,214 logger.py:67 - Execute['source /usr/hdp/current/oozie-server/conf/oozie-env.sh ; oozie admin -oozie http://vm-hadoop-slave2.out:11000/oozie tus'] {'environment': None, 'user': 'oozie'} ERROR 2016-03-17 17:29:17,717 script_alert.py:112 - [Alert][oozie_server_status] Failed with result CRITICAL: ["Execution of 'source /usr/hdp/current/oozie-server/conf/o-env.sh ; oozie admin -oozie http://vm-hadoop-slave2.out:11000/oozie -status' returned 255. Error: IO_ERROR : java.io.IOException: Error while connecting Oozie server. N retries = 1. Exception = Could not authenticate, Authentication failed, status: -1, message: null"] root@VM-HADOOP-SLAVE2:/var/log/ambari-agent#
Can somebody could help me figure out what is the problem?
Created 03-21-2016 10:57 AM
Check your hive url
17:29:17,177 logger.py:67 - Execute['! beeline -u 'jdbc:hive2://vm-hadoop-slave2.out:11000/;transportMode=binary' -e '' 2>&1| awk '{print}'|grep -i -e 'Cction refused' -e 'Invalid URL''] {'path': ['/bin/', '/usr/bin/', '/usr/lib/hive/bin/', '/usr/sbin/'], 'user': 'ambari-qa', 'timeout': 30} INFO 2016-03-17 17:29:17,214 logger.py:67 - Execute['source /usr/hdp/current/oozie-server/conf/oozie-env.sh ;
Created 03-21-2016 10:57 AM
Check your hive url
17:29:17,177 logger.py:67 - Execute['! beeline -u 'jdbc:hive2://vm-hadoop-slave2.out:11000/;transportMode=binary' -e '' 2>&1| awk '{print}'|grep -i -e 'Cction refused' -e 'Invalid URL''] {'path': ['/bin/', '/usr/bin/', '/usr/lib/hive/bin/', '/usr/sbin/'], 'user': 'ambari-qa', 'timeout': 30} INFO 2016-03-17 17:29:17,214 logger.py:67 - Execute['source /usr/hdp/current/oozie-server/conf/oozie-env.sh ;
Created 03-21-2016 04:30 PM
@Rosaura Maria Fran Mongardini Can you check the status of the Oozie server by running the following command:
oozie admin -oozie http://vm-hadoop-slave2.out:11000/oozie -status
If the above command failed. Can you try restarting the oozie from ambari and check the status again?
Created 03-22-2016 01:34 PM
root@VM-HADOOP-SLAVE2:~# oozie admin -oozie http://vm-hadoop-slave2.out:11100/oozie -status System mode: NORMAL
Notice I had to change the port (from 11000 to 11100) as I explained ahead
Created 03-21-2016 08:38 PM
Thanks for your answers, it was a port issue, port 11000 was already busy. I now use 11100 and now everything is fine
Created 03-21-2016 10:42 PM
What is being used by port 11000? We do not use it for anything but Oozie, it could be another instance of Oozie, please dig into the process and kill if necessary.
ps aux | grep oozie
kill -9 ooziepid
Created 03-22-2016 01:31 PM
I changed the default 10000 for hive and used instead 11000 (since 10000 was busy)
root@VM-HADOOP-SLAVE2:~# netstat -anp | grep 10000
tcp 0 0 0.0.0.0:10000 0.0.0.0:* LISTEN 1309/perl udp 0 0 0.0.0.0:10000 0.0.0.0:* 1309/perl
Thats why 11000 was already busy (used by hive) and that's why I was having problems. Know that I change the port to 11100 everything is ok