ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Onischuk (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-19000) Ambari-server fails to restart with --debug if it is already running
Date Wed, 30 Nov 2016 15:07:58 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-19000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Onischuk updated AMBARI-19000:
-------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2.5

> Ambari-server fails to restart with --debug if it is already running
> --------------------------------------------------------------------
>
>                 Key: AMBARI-19000
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19000
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-19000.patch
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message