Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-26883

SEVERE: Restarting VM as requested by username

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • CentOS 6.6 x86_64, jenkins-1.580.3-1.1.noarch, java-1.7.0-openjdk-1.7.0.75-2.5.4.0.el6_6.x86_64

      While managing modules, I am offered a "restart" button, but when I click it, it logs this message:

      Feb 10, 2015 10:00:46 AM jenkins.model.Jenkins$23 run
      SEVERE: Restarting VM as requested by username
      

      The "log level" should be changed to "INFO" or "NOTICE" rather than "SEVERE" as SEVERE should be reserved for "really bad things" such as crashes or something that is actually severe

      ~tommy

          [JENKINS-26883] SEVERE: Restarting VM as requested by username

          Oleg Nenashev added a comment -

          No strong opinion. SEVERE is intentional to make it visible in system logs, but I admit it may confuse external monitoring systems

          Oleg Nenashev added a comment - No strong opinion. SEVERE is intentional to make it visible in system logs, but I admit it may confuse external monitoring systems

          Niels Kristian Jensen added a comment - - edited

          I see this issue at every single restart, safeRestart or not. It seems to be related to the connected slaves:

          aug. 10, 2017 1:00:08 PM jenkins.model.Jenkins$26 run
          INFO: Restart in 10 seconds
          aug. 10, 2017 1:00:18 PM jenkins.model.Jenkins$26 run
          SEVERE: Restarting VM as requested by nkj
          aug. 10, 2017 1:00:18 PM jenkins.model.Jenkins cleanUp
          INFO: Stopping Jenkins
          aug. 10, 2017 1:00:18 PM jenkins.model.Jenkins$21 onAttained
          INFO: Started termination
          aug. 10, 2017 1:00:18 PM jenkins.model.Jenkins$21 onAttained
          INFO: Completed termination
          aug. 10, 2017 1:00:18 PM jenkins.model.Jenkins _cleanUpDisconnectComputers
          INFO: Starting node disconnection
          aug. 10, 2017 1:00:18 PM jenkins.slaves.DefaultJnlpSlaveReceiver channelClosed
          WARNING: safe-restart thread for EAC3 Win10 (dtdkcphpw200044) terminated
          java.nio.channels.ClosedChannelException

          environment: Windows 2008 server, slaves are Jnlp connected windows 10 and SSH connected Linux. Jenkins version 2.73. Please NOTE: I run the Jenkins service as an Active Directory user, not a local system account.

          The result is that Jenkins stops, but never restarts:

          INFO: Waiting for node disconnection completion
          aug. 10, 2017 1:00:20 PM jenkins.model.Jenkins cleanUp
          INFO: Jenkins stopped

          If I look at the service state using "Services", Jenkins appear to be running. A "Restart the service" brings it back up.

          Niels Kristian Jensen added a comment - - edited I see this issue at every single restart, safeRestart or not. It seems to be related to the connected slaves: aug. 10, 2017 1:00:08 PM jenkins.model.Jenkins$26 run INFO: Restart in 10 seconds aug. 10, 2017 1:00:18 PM jenkins.model.Jenkins$26 run SEVERE: Restarting VM as requested by nkj aug. 10, 2017 1:00:18 PM jenkins.model.Jenkins cleanUp INFO: Stopping Jenkins aug. 10, 2017 1:00:18 PM jenkins.model.Jenkins$21 onAttained INFO: Started termination aug. 10, 2017 1:00:18 PM jenkins.model.Jenkins$21 onAttained INFO: Completed termination aug. 10, 2017 1:00:18 PM jenkins.model.Jenkins _cleanUpDisconnectComputers INFO: Starting node disconnection aug. 10, 2017 1:00:18 PM jenkins.slaves.DefaultJnlpSlaveReceiver channelClosed WARNING: safe-restart thread for EAC3 Win10 (dtdkcphpw200044) terminated java.nio.channels.ClosedChannelException environment: Windows 2008 server, slaves are Jnlp connected windows 10 and SSH connected Linux. Jenkins version 2.73. Please NOTE: I run the Jenkins service as an Active Directory user, not a local system account. The result is that Jenkins stops, but never restarts: INFO: Waiting for node disconnection completion aug. 10, 2017 1:00:20 PM jenkins.model.Jenkins cleanUp INFO: Jenkins stopped If I look at the service state using "Services", Jenkins appear to be running. A "Restart the service" brings it back up.

          Oleg Nenashev added a comment -

          nkjensen Seems you are trying to report a defect to a logging improvement request

          Oleg Nenashev added a comment - nkjensen Seems you are trying to report a defect to a logging improvement request

          Daniel Beck added a comment -

          nkjensen Unrelated to the issue here, which is just about the log level of the restart message (i.e. it saying "SEVERE" instead of "INFO" in the fourth of the log messages you quote).

          Daniel Beck added a comment - nkjensen Unrelated to the issue here, which is just about the log level of the restart message (i.e. it saying "SEVERE" instead of "INFO" in the fourth of the log messages you quote).

          You are right, both of you. I'll try to locate an existing defect as similar as possible to the one I am trying to work around.

          Niels Kristian Jensen added a comment - You are right, both of you. I'll try to locate an existing defect as similar as possible to the one I am trying to work around.

          Oleg Nenashev added a comment -

          you are welcome. Make sure you use the "winsw" label.

          Oleg Nenashev added a comment - you are welcome. Make sure you use the "winsw" label.

          I have re-opened https://issues.jenkins-ci.org/browse/JENKINS-24238 since it looks very similar. 40305 also look similar.

          Niels Kristian Jensen added a comment - I have re-opened https://issues.jenkins-ci.org/browse/JENKINS-24238 since it looks very similar. 40305 also look similar.

          I just started to work on this ticket.

          Victor Martinez added a comment - I just started to work on this ticket.

          I'll close this ticket as duplicated by JENKINS-53282.  There is already a PR for that particular Jira and therefore I'd prefer to close this ticket on benefits of the other one. Please feel free to reopen it in case you think that ticket is not related with this one.

           

          Thanks

          Victor Martinez added a comment - I'll close this ticket as duplicated by  JENKINS-53282 .  There is already a PR for that particular Jira and therefore I'd prefer to close this ticket on benefits of the other one. Please feel free to reopen it in case you think that ticket is not related with this one.   Thanks

            v2v Victor Martinez
            tommythekid Tommy McNeely
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: