[AMBARI-19000] Ambari-server fails to restart with --debug if it is already running

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.5.0
• Assignee: Andrew Onischuk
• Reporter: Anusha Bilgi
• Created: 28/Nov/16 16:24
• Updated: 20/Mar/17 21:58
• Resolved: 30/Nov/16 15:07

Description

Using python /usr/bin/python
Restarting ambari-server
Ambari Server stopped
Ambari Server running with administrator privileges.
Organizing resource files at /var/lib/ambari-server/resources...
Ambari database consistency check started...
Server PID at: /var/run/ambari-server/ambari-server.pid
Server out at: /var/log/ambari-server/ambari-server.out
Server log at: /var/log/ambari-server/ambari-server.log
Waiting for server start.........
DB configs consistency check: no errors and warnings were found.
ERROR: Exiting with exit code -1.
REASON: Ambari Server java process died with exitcode 134. Check /var/log/ambari-server/ambari-server.out for more information.

Issue Links

• is duplicated by: AMBARI-19021 Ambari server java process died with exit code 134 after setting up Ambari kerberos JAAS configuration
• links to: ReviewBoard