CODEWITHSUNDEEP
windows-servicesjenkins
Ice
Ice

Reputation: 303

Jenkins - Service fail to start on Windows 7

When I try manually to start Jenkins from "Computer Management" I got an error 1053: "Error 1053: The service did not respond to the start or control request in a timely fashion."

I try to start from CMD with: jenkins.exe start and I get an error: enter image description here

The system was working some 2 weeks ago, I don't know what happened.

Upvotes: 2

Views: 10183

Answers (4)

Dan Narsavage
Dan Narsavage

Reputation: 377

TL;DR:

If you're not getting any logs, maybe try running jenkins.exe at a command prompt and see if it provides something useful there.

Funny story:

I was having other issues with the Jenkins Windows service that required some changes to jenkins.xml and other places. I made those changes and the service started successfully. Yay! But while googling for that solution, I discovered some other changes I could make to jenkins.xml, so I made them. And for good measure added a couple comments regarding the changes. Then the Jenkins Windows service wouldn't start again. And suddenly there was NOTHING new in the logs at all. Undid the configuration changes I had just made, and still got nothing. Spent the rest of the day googling & tinkering unsuccessfully. Then I thought, "Hmm, why not just run jenkins.exe at a command prompt & see what happens." Did that, and . . .

The configuration file cound not be loaded. An XML comment cannot contain '--', and '-' cannot be the last character. Line 36, position 148.

Good. Grief.

Upvotes: 2

Chetan
Chetan

Reputation: 734

I faced same error 1053. The jenkinsservice was not able to start. I noticed that port 8080 was already taken by other windows application service. So i changed the port to other number in jenkins.xml in jenkins installation folder. Now the jenkins service is up and running.

Upvotes: 0

Ice
Ice

Reputation: 303

I found the problem, my server works very slow, probably because Windows. Windows can not start the Jenkins service in 30 seconds.

Solution:

The Service Control Manager will generate an event if a service does not respond within the defined timeout period (the default timeout period is 30000 milliseconds). To resolve this problem, use the Registry Editor to change the default timeout value for all services.

  1. In the Registry Editor, click the registry subkey HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
  2. In the details pane, locate the ServicesPipeTimeout entry, right-click that entry and then select Modify.Note: If the ServicesPipeTimeout entry does not exist, you must create it by selecting New on the Edit menu, followed by the DWORD Value, then typing ServicesPipeTimeout, and clicking Enter.
  3. Click Decimal, enter the new timeout value in milliseconds (I prefer 120000), and then click OK.
  4. Restart the computer.

Upvotes: 3

Stuart Whelan
Stuart Whelan

Reputation: 385

Use task manager to check that there is not a hung instance of the service that is holding the listening TCP port open.

Are you using port 80, 8080 or something else?

Is it possible that IIS is installed on the machine and is stopping Jenkins from using the listening port?

Upvotes: 0

Related Questions