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

Windows "services" shows Jenkins as not running.. but it is.

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Fixed
    • core
    • Windows 2012, Jenkins 1.553, Java 1.7.0-45

    Description

      My Jenkins webserver is running on a Windows 2012 VM. It's been working fine and is still running fine after upgrading from 1.552 to 1.553. But after upgrading to 1.553, the 'services' tool in Windows tells me that Jenkins is not running. But it is running – it's running fine. I can refresh webpages, launch jobs, etc, from web browsers.

      But for the "Jenkins" service, the status is blank, where normally it would say: "running". I've closed the tool and relaunched it, hit F5 to refresh, etc. Jenkins is working fine, but the service tool from Microsoft doesn't say it's running.

      This worked in 1.552.

      Attachments

        Issue Links

          Activity

            belpk K P added a comment -

            Your java.exe (running jenkins) probably isn't running as a child of jenkins.exe anymore. You can very this in ProcessExplorer (sysinternals).

            When jenkins upgrades, I've noticed that it happens that the jenkins.exe (= Windows service) somehow "loses" control over the jenkins java.exe. In that case you have to kill the java.exe Process, and then just restart the service.

            belpk K P added a comment - Your java.exe (running jenkins) probably isn't running as a child of jenkins.exe anymore. You can very this in ProcessExplorer (sysinternals). When jenkins upgrades, I've noticed that it happens that the jenkins.exe (= Windows service) somehow "loses" control over the jenkins java.exe. In that case you have to kill the java.exe Process, and then just restart the service.
            danielbeck Daniel Beck added a comment -

            User mentions web interface working, so it's about master, not any windows slave services.

            danielbeck Daniel Beck added a comment - User mentions web interface working, so it's about master, not any windows slave services.
            oleg_nenashev Oleg Nenashev added a comment -

            It's possible that Jenkins master also runs away. Ideally requires some diagnostics on the winsw side

            oleg_nenashev Oleg Nenashev added a comment - It's possible that Jenkins master also runs away. Ideally requires some diagnostics on the winsw side
            krogan mark mann added a comment -

            Jenkins master is on 2.32.1
            Master and slaves running Win2012
            The symptoms sound very familiar to a problem where we've had a jenkins slave up.... then we reboot the windows server (slave).
            When the server returns and the slave is automatically started, it hangs around for about 30secs then terminates connection which kills our job.
            We've also witnessed the hosting windows service winsw 1.17 (which auto upgrades to 1.18) bombs out but leaves the java process running.
            The java process is still keeping the slave active to the master for an indiscriminate amount of time (anywhere between 20secs to 2hrs) before eventually dying of its own accord, with no fresh jobs sent or interaction with the windows service.

            krogan mark mann added a comment - Jenkins master is on 2.32.1 Master and slaves running Win2012 The symptoms sound very familiar to a problem where we've had a jenkins slave up.... then we reboot the windows server (slave). When the server returns and the slave is automatically started, it hangs around for about 30secs then terminates connection which kills our job. We've also witnessed the hosting windows service winsw 1.17 (which auto upgrades to 1.18) bombs out but leaves the java process running. The java process is still keeping the slave active to the master for an indiscriminate amount of time (anywhere between 20secs to 2hrs) before eventually dying of its own accord, with no fresh jobs sent or interaction with the windows service.
            oleg_nenashev Oleg Nenashev added a comment -

            Should be fixed by the Runaway process killer which is provided in Jenkins 2.50+ (See JENKINS-39231)

            oleg_nenashev Oleg Nenashev added a comment - Should be fixed by the Runaway process killer which is provided in Jenkins 2.50+ (See JENKINS-39231 )
            oleg_nenashev Oleg Nenashev added a comment -

            Starting from 2.50, the Runaway process killer is enabled by default for new installations of Jenkins as Windows services

            oleg_nenashev Oleg Nenashev added a comment - Starting from 2.50, the Runaway process killer is enabled by default for new installations of Jenkins as Windows services

            People

              oleg_nenashev Oleg Nenashev
              borisivan boris ivan
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: