Uploaded image for project: 'Ambari'
  1. Ambari
  2. AMBARI-20020

Ambari-server restart --debug failed

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.5.0
    • None
    • None

    Description

      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]

      Attachments

        1. AMBARI-20020.patch
          1.0 kB
          Andrew Onischuk

        Issue Links

          Activity

            People

              aonishuk Andrew Onischuk
              Dtarasyuk Denis Tarasyuk
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: