ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-20020) Ambari-server restart --debug failed
Date Wed, 15 Feb 2017 13:04:41 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-20020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15867789#comment-15867789
] 

Hadoop QA commented on AMBARI-20020:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12852803/AMBARI-20020.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/10585//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/10585//console

This message is automatically generated.

> Ambari-server restart --debug failed
> ------------------------------------
>
>                 Key: AMBARI-20020
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20020
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-20020.patch
>
>
> Artifacts: <http://qelog.hortonworks.com/log/nat-yc-r7-yrhs-ambari-hv-r-upg-19
> /test-logs/ambari-hv-r-upg/ambaritestartifacts/artifacts/screenshots/com.hw.am
> bari.ui.tests.monitoring.admin_page.rolling_express_upgrade.TestRUPrechecksSki
> p/test040_PrerequisitesCheck/_30_1_55_48_Element_has_not_been_found_within_30_
> seconds__/>
>     
>     
>     
>     Sending command [ambari-server restart --debug]
>     [OUTPUT STREAM]
>     Using python  /usr/bin/python
>     Restarting ambari-server
>     Waiting for server stop...
>     Ambari-server failed to stop
>     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.........
>     Unable to determine server PID. Retrying...
>     ......
>     Unable to determine server PID. Retrying...
>     ......
>     Unable to determine server PID. Retrying...
>     DB configs consistency check: no errors and warnings were found.
>     ERROR: Exiting with exit code -1. 
>     REASON: Ambari Server java process died with exitcode 2. Check /var/log/ambari-server/ambari-server.out
for more information.
>     
>     [ERROR STREAM]
>     
> ambari-server.out
>     
>     
>     OpenJDK 64-Bit Server VM warning: ignoring option PermSize=1024m; support was removed
in 8.0
>     OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=1024m; support was
removed in 8.0
>     OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed
in 8.0
>     ERROR: transport error 202: bind failed: Address already in use
>     ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
>     JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [debugInit.c:750]
>     



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message