You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

General Troubleshooting

Ambari Server: Check /var/log/ambari-server/ambari-server.[log|out] for errors.
Ambari Agent: Check /var/log/ambari-agent/ambari-agent.[log|out] for errors.
Note that if Ambari Agent has any output in /var/log/ambari-agent/ambari-agent.out, it is indicative of a significant problem with the agent.

Services fail to start up

  • HDFS: Check log files under /var/log/hadoop/hdfs
  • MapReduce: Check log files under /var/log/hadoop/mapred

Nagios alerts don't show up in Ambari Web

  • Run "service httpd restart" on the Nagios Server host.

Install Wizard fails during Install phase

  • Click on the Retry button. In most cases, this will solve install failures due to package install problems due to intermittent software repository availability.

Installing a new cluster on top of an existing cluster

When installing a Hadoop cluster via Ambari on hosts that already have Hadoop bits installed (including an existing cluster deployed via Ambari), perform the following:

  • Stop all the services on all the nodes(including ganglia and nagios)
  • It is also a good practice to delete the rpms from all nodes.

search for the rpms:
rpm -qa | grep ganglia
rpm -qa | grep oozie
rpm -qa | grep sqoop
rpm -qa | grep pig
rpm -qa | grep nagios
rpm -qa | grep hadoop

and remove them :
rpm -e <package name>

  • No labels