Windows 2008 Server

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Windows 2008 Server

Daniel Barbato
Hi,

I'm trying to get Jenkins installed as a service on a Vanilla Windows
2008 SP1 server. I can't seem to get it to run as a service and am
looking for any ideas to help get it going.

I've performed the following steps:

 * Installed java 64 bit
 * Started Jenkins with java -jar jenkins.war (I've also tried doing
this with the web start)
 * Gone to Manage Jenkins and set it to run as a Windows Service.
 * Told Jenkins to restart itself as a service.

At this point, Jenkins dies and doesn't come back up.

When I try and manually start Jenkins I get error 1053 (service took
too long to start). I can't spot any log files or other information.

The Wiki page I'm told to check if it doesn't come up doesn't exist
(the hudson equivalent does exist but doesn't provide any clues) and
Googling hasn't provided much support either.

Any ideas or suggestions welcome, I'd also be curious to hear from
anyone who has got it working on this O/S (or a windows 2003 server).

Many Thanks

Dan
Reply | Threaded
Open this post in threaded view
|

Re: Windows 2008 Server

James Nord
I have it working on a 2k3 server (x86) - as a slave (1.399).
I have a user account explicitly for Jenkins to use that has logon as
a service right and has admin privs (blame MS for that one as we need
to build msi packages and that needs admin rights).
After Jenkins installed the slave I went into the service.msc snapin
and changed the user from Administrator to my Jenkins user.

Not sure it helps you - but it does work on 2k3 as a slave when
running as a service.

/James

On Mar 2, 10:19 pm, Daniel B <[hidden email]> wrote:

> Hi,
>
> I'm trying to get Jenkins installed as a service on a Vanilla Windows
> 2008 SP1 server. I can't seem to get it to run as a service and am
> looking for any ideas to help get it going.
>
> I've performed the following steps:
>
>  * Installed java 64 bit
>  * Started Jenkins with java -jar jenkins.war (I've also tried doing
> this with the web start)
>  * Gone to Manage Jenkins and set it to run as a Windows Service.
>  * Told Jenkins to restart itself as a service.
>
> At this point, Jenkins dies and doesn't come back up.
>
> When I try and manually start Jenkins I get error 1053 (service took
> too long to start). I can't spot any log files or other information.
>
> The Wiki page I'm told to check if it doesn't come up doesn't exist
> (the hudson equivalent does exist but doesn't provide any clues) and
> Googling hasn't provided much support either.
>
> Any ideas or suggestions welcome, I'd also be curious to hear from
> anyone who has got it working on this O/S (or a windows 2003 server).
>
> Many Thanks
>
> Dan
Reply | Threaded
Open this post in threaded view
|

Re: Windows 2008 Server

Daniel Barbato
Hi James,

What are you running your Hudson Master on?

Dan

On 2 March 2011 22:40, teilo <[hidden email]> wrote:

> I have it working on a 2k3 server (x86) - as a slave (1.399).
> I have a user account explicitly for Jenkins to use that has logon as
> a service right and has admin privs (blame MS for that one as we need
> to build msi packages and that needs admin rights).
> After Jenkins installed the slave I went into the service.msc snapin
> and changed the user from Administrator to my Jenkins user.
>
> Not sure it helps you - but it does work on 2k3 as a slave when
> running as a service.
>
> /James
>
> On Mar 2, 10:19 pm, Daniel B <[hidden email]> wrote:
>> Hi,
>>
>> I'm trying to get Jenkins installed as a service on a Vanilla Windows
>> 2008 SP1 server. I can't seem to get it to run as a service and am
>> looking for any ideas to help get it going.
>>
>> I've performed the following steps:
>>
>>  * Installed java 64 bit
>>  * Started Jenkins with java -jar jenkins.war (I've also tried doing
>> this with the web start)
>>  * Gone to Manage Jenkins and set it to run as a Windows Service.
>>  * Told Jenkins to restart itself as a service.
>>
>> At this point, Jenkins dies and doesn't come back up.
>>
>> When I try and manually start Jenkins I get error 1053 (service took
>> too long to start). I can't spot any log files or other information.
>>
>> The Wiki page I'm told to check if it doesn't come up doesn't exist
>> (the hudson equivalent does exist but doesn't provide any clues) and
>> Googling hasn't provided much support either.
>>
>> Any ideas or suggestions welcome, I'd also be curious to hear from
>> anyone who has got it working on this O/S (or a windows 2003 server).
>>
>> Many Thanks
>>
>> Dan
Reply | Threaded
Open this post in threaded view
|

Re: Windows 2008 Server

James Nord
Cent os 64bit with a 64 bit jdk

On Mar 2, 11:12 pm, Daniel Barbato <[hidden email]> wrote:

> Hi James,
>
> What are you running your Hudson Master on?
>
> Dan
>
> On 2 March 2011 22:40, teilo <[hidden email]> wrote:
>
>
>
> > I have it working on a 2k3 server (x86) - as a slave (1.399).
> > I have a user account explicitly for Jenkins to use that has logon as
> > a service right and has admin privs (blame MS for that one as we need
> > to build msi packages and that needs admin rights).
> > After Jenkins installed the slave I went into the service.msc snapin
> > and changed the user from Administrator to my Jenkins user.
>
> > Not sure it helps you - but it does work on 2k3 as a slave when
> > running as a service.
>
> > /James
>
> > On Mar 2, 10:19 pm, Daniel B <[hidden email]> wrote:
> >> Hi,
>
> >> I'm trying to get Jenkins installed as a service on a Vanilla Windows
> >> 2008 SP1 server. I can't seem to get it to run as a service and am
> >> looking for any ideas to help get it going.
>
> >> I've performed the following steps:
>
> >>  * Installed java 64 bit
> >>  * Started Jenkins with java -jar jenkins.war (I've also tried doing
> >> this with the web start)
> >>  * Gone to Manage Jenkins and set it to run as a Windows Service.
> >>  * Told Jenkins to restart itself as a service.
>
> >> At this point, Jenkins dies and doesn't come back up.
>
> >> When I try and manually start Jenkins I get error 1053 (service took
> >> too long to start). I can't spot any log files or other information.
>
> >> The Wiki page I'm told to check if it doesn't come up doesn't exist
> >> (the hudson equivalent does exist but doesn't provide any clues) and
> >> Googling hasn't provided much support either.
>
> >> Any ideas or suggestions welcome, I'd also be curious to hear from
> >> anyone who has got it working on this O/S (or a windows 2003 server).
>
> >> Many Thanks
>
> >> Dan
Reply | Threaded
Open this post in threaded view
|

Re: Windows 2008 Server

Richard Bywater
In reply to this post by James Nord
I'm seeing a similar thing when trying to start a slave on 2008.
Basically the Jenkins-slave.exe starts and then it dies off before the
java process is started.

This was working back on 1.372 but stopped when we went to 1.396 :(. I
do notice that some of the slave code got changed for the windows
stuff so don't know if it is that change that broke it or not...

Richard.

On Thursday, March 3, 2011, teilo <[hidden email]> wrote:

> I have it working on a 2k3 server (x86) - as a slave (1.399).
> I have a user account explicitly for Jenkins to use that has logon as
> a service right and has admin privs (blame MS for that one as we need
> to build msi packages and that needs admin rights).
> After Jenkins installed the slave I went into the service.msc snapin
> and changed the user from Administrator to my Jenkins user.
>
> Not sure it helps you - but it does work on 2k3 as a slave when
> running as a service.
>
> /James
>
> On Mar 2, 10:19 pm, Daniel B <[hidden email]> wrote:
>> Hi,
>>
>> I'm trying to get Jenkins installed as a service on a Vanilla Windows
>> 2008 SP1 server. I can't seem to get it to run as a service and am
>> looking for any ideas to help get it going.
>>
>> I've performed the following steps:
>>
>>  * Installed java 64 bit
>>  * Started Jenkins with java -jar jenkins.war (I've also tried doing
>> this with the web start)
>>  * Gone to Manage Jenkins and set it to run as a Windows Service.
>>  * Told Jenkins to restart itself as a service.
>>
>> At this point, Jenkins dies and doesn't come back up.
>>
>> When I try and manually start Jenkins I get error 1053 (service took
>> too long to start). I can't spot any log files or other information.
>>
>> The Wiki page I'm told to check if it doesn't come up doesn't exist
>> (the hudson equivalent does exist but doesn't provide any clues) and
>> Googling hasn't provided much support either.
>>
>> Any ideas or suggestions welcome, I'd also be curious to hear from
>> anyone who has got it working on this O/S (or a windows 2003 server).
>>
>> Many Thanks
>>
>> Dan
Reply | Threaded
Open this post in threaded view
|

Re: Windows 2008 Server

cforce-2
We run jenkins on windows srv 2008 as war on tomcat without issues

2011/3/3 Richard Bywater <[hidden email]>:

> I'm seeing a similar thing when trying to start a slave on 2008.
> Basically the Jenkins-slave.exe starts and then it dies off before the
> java process is started.
>
> This was working back on 1.372 but stopped when we went to 1.396 :(. I
> do notice that some of the slave code got changed for the windows
> stuff so don't know if it is that change that broke it or not...
>
> Richard.
>
> On Thursday, March 3, 2011, teilo <[hidden email]> wrote:
>> I have it working on a 2k3 server (x86) - as a slave (1.399).
>> I have a user account explicitly for Jenkins to use that has logon as
>> a service right and has admin privs (blame MS for that one as we need
>> to build msi packages and that needs admin rights).
>> After Jenkins installed the slave I went into the service.msc snapin
>> and changed the user from Administrator to my Jenkins user.
>>
>> Not sure it helps you - but it does work on 2k3 as a slave when
>> running as a service.
>>
>> /James
>>
>> On Mar 2, 10:19 pm, Daniel B <[hidden email]> wrote:
>>> Hi,
>>>
>>> I'm trying to get Jenkins installed as a service on a Vanilla Windows
>>> 2008 SP1 server. I can't seem to get it to run as a service and am
>>> looking for any ideas to help get it going.
>>>
>>> I've performed the following steps:
>>>
>>>  * Installed java 64 bit
>>>  * Started Jenkins with java -jar jenkins.war (I've also tried doing
>>> this with the web start)
>>>  * Gone to Manage Jenkins and set it to run as a Windows Service.
>>>  * Told Jenkins to restart itself as a service.
>>>
>>> At this point, Jenkins dies and doesn't come back up.
>>>
>>> When I try and manually start Jenkins I get error 1053 (service took
>>> too long to start). I can't spot any log files or other information.
>>>
>>> The Wiki page I'm told to check if it doesn't come up doesn't exist
>>> (the hudson equivalent does exist but doesn't provide any clues) and
>>> Googling hasn't provided much support either.
>>>
>>> Any ideas or suggestions welcome, I'd also be curious to hear from
>>> anyone who has got it working on this O/S (or a windows 2003 server).
>>>
>>> Many Thanks
>>>
>>> Dan
>
Reply | Threaded
Open this post in threaded view
|

Re: Windows 2008 Server

Richard Bywater
FYI I think I might have found the reason behind my issue at least.

It seems that jenkins-slave.exe is digitally signed whereas the old hudson-slave.exe wasn't. Unfortunately on my machine I don't have the correct root certs loaded and so it appears that the exe is trying to talk to the internet to verify the exe. Being behind a firewalled network means that this isn't possible and so the service startup times out due to what appears to be a long SYN timeout on Windows 2008.

In the end I ended up copying an old hudson-slave.exe over the top of the jenkins-slave.exe and this worked perfectly.

Maybe that will help others?  In the meantime, can we possibly remove the code signing from jenkins-slave.exe - does it really need it?

Cheers
Richard.

On Fri, Mar 4, 2011 at 7:22 AM, Fabi <[hidden email]> wrote:
We run jenkins on windows srv 2008 as war on tomcat without issues

2011/3/3 Richard Bywater <[hidden email]>:
> I'm seeing a similar thing when trying to start a slave on 2008.
> Basically the Jenkins-slave.exe starts and then it dies off before the
> java process is started.
>
> This was working back on 1.372 but stopped when we went to 1.396 :(. I
> do notice that some of the slave code got changed for the windows
> stuff so don't know if it is that change that broke it or not...
>
> Richard.
>
> On Thursday, March 3, 2011, teilo <[hidden email]> wrote:
>> I have it working on a 2k3 server (x86) - as a slave (1.399).
>> I have a user account explicitly for Jenkins to use that has logon as
>> a service right and has admin privs (blame MS for that one as we need
>> to build msi packages and that needs admin rights).
>> After Jenkins installed the slave I went into the service.msc snapin
>> and changed the user from Administrator to my Jenkins user.
>>
>> Not sure it helps you - but it does work on 2k3 as a slave when
>> running as a service.
>>
>> /James
>>
>> On Mar 2, 10:19 pm, Daniel B <[hidden email]> wrote:
>>> Hi,
>>>
>>> I'm trying to get Jenkins installed as a service on a Vanilla Windows
>>> 2008 SP1 server. I can't seem to get it to run as a service and am
>>> looking for any ideas to help get it going.
>>>
>>> I've performed the following steps:
>>>
>>>  * Installed java 64 bit
>>>  * Started Jenkins with java -jar jenkins.war (I've also tried doing
>>> this with the web start)
>>>  * Gone to Manage Jenkins and set it to run as a Windows Service.
>>>  * Told Jenkins to restart itself as a service.
>>>
>>> At this point, Jenkins dies and doesn't come back up.
>>>
>>> When I try and manually start Jenkins I get error 1053 (service took
>>> too long to start). I can't spot any log files or other information.
>>>
>>> The Wiki page I'm told to check if it doesn't come up doesn't exist
>>> (the hudson equivalent does exist but doesn't provide any clues) and
>>> Googling hasn't provided much support either.
>>>
>>> Any ideas or suggestions welcome, I'd also be curious to hear from
>>> anyone who has got it working on this O/S (or a windows 2003 server).
>>>
>>> Many Thanks
>>>
>>> Dan
>

Reply | Threaded
Open this post in threaded view
|

Re: Windows 2008 Server

Les Mikesell
On 3/10/11 8:47 PM, Richard Bywater wrote:
> FYI I think I might have found the reason behind my issue at least.
>
> It seems that jenkins-slave.exe is digitally signed whereas the old
> hudson-slave.exe wasn't. Unfortunately on my machine I don't have the correct
> root certs loaded and so it appears that the exe is trying to talk to the
> internet to verify the exe. Being behind a firewalled network means that this
> isn't possible and so the service startup times out due to what appears to be a
> long SYN timeout on Windows 2008.

I'm not positive about this, but I think if your firewall did a 'deny' (with
ICMP response) rather than 'drop' of the outbound traffic this connection
attempt would fail immediately instead of having to wait for a timeout.

--
   Les Mikesell
    [hidden email]