You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/09/01 09:08:20 UTC
[jira] [Commented] (AMBARI-18294) Ambari Server Start/Stop fails on
Centos 7.1+
[ https://issues.apache.org/jira/browse/AMBARI-18294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15454839#comment-15454839 ]
Hadoop QA commented on AMBARI-18294:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12826587/AMBARI-18294.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/8548//console
This message is automatically generated.
> Ambari Server Start/Stop fails on Centos 7.1+
> ---------------------------------------------
>
> Key: AMBARI-18294
> URL: https://issues.apache.org/jira/browse/AMBARI-18294
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.4.1
>
> Attachments: AMBARI-18294.patch
>
>
> Brand new install on Centos 7.2
> Ambari Server 'setup' completed successfully.
> [root@c7001 ~]# ambari-server start
> Using python /usr/bin/python
> Starting ambari-server
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> No errors were found.
> Ambari database consistency check finished
> 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....................
> Ambari Server 'start' completed successfully.
> [root@c7001 ~]# cat /var/run/ambari-server/ambari-server.pid
> 12302
> 12303
> [root@c7001 ~]# ps aux | grep AmbariServer
> root 12302 0.0 0.0 113116 644 pts/0 S 20:42 0:00 /bin/sh -c ulimit -n 10000 ; /usr/jdk64/jdk1.8.0_77/bin/java -server -XX:NewRatio=3 -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit -XX:CMSInitiatingOccupancyFraction=60 -XX:+CMSClassUnloadingEnabled -Dsun.zip.disableMemoryMapping=true -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.security.auth.useSubjectCredsOnly=false -cp '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/postgresql-jdbc.jar' org.apache.ambari.server.controller.AmbariServer > /var/log/ambari-server/ambari-server.out 2>&1 || echo $? > /var/run/ambari-server/ambari-server.exitcode &
> root 12303 87.7 14.8 4377224 431856 pts/0 Sl 20:42 0:29 /usr/jdk64/jdk1.8.0_77/bin/java -server -XX:NewRatio=3 -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit -XX:CMSInitiatingOccupancyFraction=60 -XX:+CMSClassUnloadingEnabled -Dsun.zip.disableMemoryMapping=true -Xms512m -Xmx2048m -XX:MaxPermSize=128m -Djava.security.auth.login.config=/etc/ambari-server/conf/krb5JAASLogin.conf -Djava.security.krb5.conf=/etc/krb5.conf -Djavax.security.auth.useSubjectCredsOnly=false -cp /etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/postgresql-jdbc.jar org.apache.ambari.server.controller.AmbariServer
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)