HDP image failures/warnings in boot.log for VM
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Sahara |
Fix Released
|
Medium
|
Robert Nettleton |
Bug Description
This bug describes a minor issue in the HDP images in sahara-
Some error messages and warnings are occurring in a VM instance based on either of the HDP images (HDP 1.3.2 or HDP 2.0.6).
The warnings are as follows:
"Starting ambari-server
ERROR: Exiting with exit code 1.
REASON: Unable to detect a system user for Ambari Server.
- If this is a new setup, then run the "ambari-server setup" command to create the user
- If this is an upgrade of an existing setup, run the "ambari-server upgrade" command.
Refer to the Ambari documentation for more information on setup and upgrade.
Starting atd: [ OK ]
/etc/rc3.
Starting Hadoop historyserver:[ OK ]
Error: JAVA_HOME is not set and could not be found.
/etc/rc3.
Starting Hadoop nodemanager:[ OK ]
Error: JAVA_HOME is not set and could not be found.
/etc/rc3.
Starting Hadoop proxyserver:[ OK ]
Error: JAVA_HOME is not set and could not be found.
/etc/rc3.
Starting Hadoop resourcemanager:[ OK ]
Error: JAVA_HOME is not set and could not be found."
The ambari-server service starts up upon first boot, and runs into errors, since it has not been setup yet with the "ambari-server setup" command. The setup command is usually run by the HDP plugin during cluster startup. This problem occurs with both versions of HDP in these images.
The other errors are only specific to the HDP 2.0.6 image. Some of the Hadoop 2.x package installs now include automatic startup of a set of Hadoop services. These services attempt to startup during the first boot of the instance. This startup fails, since the Hadoop services have not yet been configured by Ambari.
These errors/warnings are really only a cosmetic issue. Once HDP plugin configures ambari-server, which in turn configures the Hadoop services, these problems do not actually occur during cluster startup/runtime. This issue only occurs upon the first boot of the image.
Even though this is a cosmetic issue, it should be resolved, since these errors can be confusing to users as they try to debug failing cluster startups.
I have a fix for this implemented, and will be submitting a patch soon to resolve this.
Changed in sahara: | |
milestone: | none → juno-1 |
Changed in sahara: | |
importance: | Undecided → Medium |
Changed in sahara: | |
status: | Fix Committed → Fix Released |
Changed in sahara: | |
milestone: | juno-1 → 2014.2 |
More comments about the fix required:
The ambari-server and ambari-agent services will be turned off by default, using the chkconfig command.
The hadoop services listed in these warnings/errors will be turned off by default, using the chkconfig command.
Turning these services off by default will only affect the first boot, and will not modify the behavior of cluster startups.