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

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-19000:
-
Reporter: Anusha Bilgi  (was: Andrew Onischuk)

> 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: Anusha Bilgi
>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.15#6346)

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

[Andrew Onischuk (JIRA)]

 [ 
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)

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

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-19000:
-
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.

> 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)

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

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-19000:
-
Description: (was: After enabling WireEncyption For HDFS, ambari server 
goes down, I tried
restart again, it came up. but all hosts in HEARTBEAT_LOST state.

cluster: 

logs:  


Steps test executes to enable swebHDFS:  


)

> 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
>
>




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

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

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-19000:
-
Attachment: AMBARI-19000.patch

> 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
>
>
> After enabling WireEncyption For HDFS, ambari server goes down, I tried
> restart again, it came up. but all hosts in HEARTBEAT_LOST state.
> cluster: 
> logs:  
>  /ambari-stackviews-we/artifacts/screenshots/com.hw.ambari.view.conf.ViewConfig
> uration/UndefinedMethod/_25_5_54_37_Element_has_not_been_found_within_60_secon
> ds__/logs/>
> Steps test executes to enable swebHDFS:  
>  /src/test/java/com/hw/ambari/view/conf/ViewConfiguration.java#L101>



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

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

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-19000:
-
Status: Patch Available  (was: Open)

> 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
>
>
> After enabling WireEncyption For HDFS, ambari server goes down, I tried
> restart again, it came up. but all hosts in HEARTBEAT_LOST state.
> cluster: 
> logs:  
>  /ambari-stackviews-we/artifacts/screenshots/com.hw.ambari.view.conf.ViewConfig
> uration/UndefinedMethod/_25_5_54_37_Element_has_not_been_found_within_60_secon
> ds__/logs/>
> Steps test executes to enable swebHDFS:  
>  /src/test/java/com/hw/ambari/view/conf/ViewConfiguration.java#L101>



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