Jenkins service started and then stopped

5,332 views
Skip to first unread message

Bryan

unread,
Apr 12, 2011, 11:57:58 AM4/12/11
to Jenkins Users
I installed using the Windows installer and was very impressed by how
simple it was, everything worked flawlessly out of the box.

This morning the service has stopped and will not restart. When I try
to start the service manually I get the following message:

"The Jenkins service on Local Computer started and then stopped. Some
services stop automatically if they have no work to do, for example,
the Performance Logs and Alerts service."

The Windows XP machine that this is running on is scheduled to reboot
every morning at 3am. Not sure if this is relevant since Jenkins
survived several nightly reboots without issue.

In the jenkins.wrapper.log I found the following command:

C:\Program Files\Jenkins\jre\bin\java -Xrs -Xmx256m -
Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "C:
\Program Files\Jenkins\jenkins.war" --httpPort=8080

If I execute this manually, Jenkins is served up on port 8080.

What can I do to run the Windows service?

Manuel Doninger

unread,
Apr 12, 2011, 12:05:03 PM4/12/11
to jenkins...@googlegroups.com
Are there any other errors in jenkins.out.log or jenkins.err.log?

Manuel

Bryan

unread,
Apr 12, 2011, 12:24:45 PM4/12/11
to Jenkins Users
> Are there any other errors in jenkins.out.log or jenkins.err.log?

No errors.

Martijn Baay

unread,
Apr 12, 2011, 2:11:36 PM4/12/11
to jenkins...@googlegroups.com
Last place to look might be the windows event viewer. Does any error show up there?

Bryan

unread,
Apr 12, 2011, 2:46:26 PM4/12/11
to Jenkins Users
On Apr 12, 2:11 pm, Martijn Baay <martijn.b...@gmail.com> wrote:
> Last place to look might be the windows event viewer. Does any error show up
> there?

I'm not seeing anything related to the Jenkins service in any of the
Event Viewer logs.

cdm

unread,
Apr 13, 2011, 4:08:30 AM4/13/11
to Jenkins Users
I'm not (yet) familiar with the windows installer but I had a similar
experience with running Jenkins on Tomcat as a service with a 1.6 jdk.
That issue was caused by the service wrapper depending on msvcr71.dll,
which was available on the classpath in the 1.5 jdk but not so with
the 1.6 jdk.
I solved that problem by copying the jre/bin/new_plugin/msvcr71.dll to
the tomcat/bin directory.
Copying the dll file to the windows/system32 directory also worked.
Hope this helps.

Bryan

unread,
Apr 13, 2011, 9:18:02 AM4/13/11
to Jenkins Users
On Apr 13, 4:08 am, cdm <c.de.mei...@gmail.com> wrote:
> I solved that problem by copying the jre/bin/new_plugin/msvcr71.dll to
> the tomcat/bin directory.
> Copying the dll file to the windows/system32 directory also worked.
> Hope this helps.

I've got an abundance of copies of msvcr71.dll including one in windows
\system32 and Jenkins\jre\bin where my java.exe runs from.

Bryan

unread,
Apr 13, 2011, 9:28:08 AM4/13/11
to Jenkins Users
Thank you all for your ideas so far, it's great to have things to
investigate when you're completely stumped.

I tried uninstalling the service and creating a new service using sc
to run the java command that I originally listed but Windows
apparently times out waiting for it to start.

KP

unread,
May 18, 2011, 10:42:36 AM5/18/11
to Jenkins Users
I had similar issues... nothing to see in the normal log, event log,
etc... Re-installing, etc, nothing helped.

Then I also checked jenkins.wrapper.log , turned out the Windows Event
Log was full, so apparently that's why the service didn't start. After
clearing the logs/increasing/whatever you want, the service started
again.

Craig

unread,
May 8, 2014, 8:15:35 AM5/8/14
to jenkins...@googlegroups.com
Thanks KP this was a problem for me and clearing the Windows Event Logs allowed Jenkins to start.
Interestingly nothing at all was written to any of the logfiles.

Craig

unread,
Oct 21, 2014, 10:12:49 AM10/21/14
to jenkins...@googlegroups.com
I've had the issue several times now and it's always resolved by clearing the logs.
Today I tried a different fix and set the Event Log to 'Overwrite as Needed' (it was set to overwrite older than 7 days).
This has resolved the issue without clearing the log, so it could be a permanent fix.
Note that I'm using XP, I daresay that the Event Log in Win7 is very different.

Craig
Reply all
Reply to author
Forward
0 new messages