[ https://issues.apache.org/jira/browse/AMBARI-19021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aravindan Vijayan resolved AMBARI-19021. ---------------------------------------- Resolution: Duplicate Assignee: Robert Levas > Ambari server java process died with exit code 134 after setting up Ambari > kerberos JAAS configuration > ------------------------------------------------------------------------------------------------------ > > Key: AMBARI-19021 > URL: https://issues.apache.org/jira/browse/AMBARI-19021 > Project: Ambari > Issue Type: Bug > Affects Versions: 2.5.0 > Reporter: Vivek Rathod > Assignee: Robert Levas > Fix For: 2.5.0 > > > Ambari server java process died with exit code 134 after setting up Ambari > kerberos JAAS configuration. While enabling SPNEGO Authentication, after > setting up JAAS configuration, ambari server restart failed with exitcode 134. > On performing the ambari server setup and start manually on the same cluster, > everything went through fine and the ambari server is now running on the > cluster. This may be an intermittent issue. > {noformat} > 2016-11-29 06:12:51,092 DEBUG > com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence(): > Sending commands to host : > 2016-11-29 06:12:51,092 DEBUG > com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence(): > Sending command [ambari-server setup-security] > 2016-11-29 06:12:51,093 DEBUG > com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence(): > Sending command [3] > 2016-11-29 06:12:51,093 DEBUG > com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence(): > Sending command [ambari-qa-...@example.com] > 2016-11-29 06:12:51,093 DEBUG > com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence(): > Sending command [/etc/security/keytabs/smokeuser.headless.keytab] > 2016-11-29 06:12:51,795 DEBUG > com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence(): > [OUTPUT STREAM] > Using python /usr/bin/python > Security setup options... > =========================================================================== > Choose one of the following options: > [1] Enable HTTPS for Ambari server. > [2] Encrypt passwords stored in ambari.properties file. > [3] Setup Ambari kerberos JAAS configuration. > [4] Setup truststore. > [5] Import certificate to truststore. > =========================================================================== > Enter choice, (1-5): Setting up Ambari kerberos JAAS configuration to access > secured Hadoop daemons... > Enter ambari server's kerberos principal name (amb...@example.com): Enter > keytab path for ambari server's kerberos principal: Ambari Server > 'setup-security' completed successfully. > [ERROR STREAM] > [EXIT CODE] > 0 > 2016-11-29 06:12:51,796 INFO > com.hw.ambari.ui.tests.console.TestConfigureHTTPSpnegoAuthentication.changeKRB5_JAASLOGIN_CONF(): > [Finished] > 2016-11-29 06:12:51,797 INFO > com.hw.ambari.ui.util.cluster_managers.AmbariManager.getStartAmbariServerCommand(): > Trying to restart Ambari server ... > 2016-11-29 06:12:51,798 DEBUG > com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence(): > Sending commands to host : > 2016-11-29 06:12:51,798 DEBUG > com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence(): > Sending command [ambari-server restart --debug] > 2016-11-29 06:12:52,700 DEBUG > com.hw.ambari.ui.util.cluster_managers.ProcessData.buildOutputAndErrorStreamData(): > sh: line 1: 419471 Aborted /usr/jdk64/jdk1.8.0_77/bin/java > -server -XX:NewRatio=2 -XX:+UseConcMarkSweepGC -Xms512m -Xmx2048m > -XX:MaxPermSize=128m > -Djava.security.auth.login.config=$ROOT/etc/ambari-server/conf/krb5JAASLogin.conf > -Djava.security.krb5.conf=/etc/krb5.conf -Djavax.securit > 2016-11-29 06:12:52,701 DEBUG > com.hw.ambari.ui.util.cluster_managers.ProcessData.buildOutputAndErrorStreamData(): > y.auth.useSubjectCredsOnly=false -Xdebug > -Xrunjdwp:transport=dt_socket,address=5005,server=y,suspend=n -cp > /etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/mysql-connector-java.jar > org.apache.ambari.server.controller.AmbariServer > > /var/log/ambari-server/ambari-server.out 2>&1 > 2016-11-29 06:13:03,521 DEBUG > com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence(): > [OUTPUT STREAM] > 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. > [ERROR STREAM] > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)