Slave Won't Run Under Configured User
Locked
 
|
Issue:
The problem I'm facing is the Jenkins slave is running as Window's "Default User," despite being configured to run as a Domain Admin on our network. Because it doesn't have the proper execution, modify, or write permissions, the result is build failures from SVN, Maven, Jboss related builds, etc. How do I resolve this? Jenkins Set-up Details: I'm using Windows Server 2003 on both Jenkins machines. One is the master the other is the slave. They both run as window services under the same Administrator account. This is configured both in the Jenkins UI and in the Window Services. BTW I'm using Jenkins ver. 1.409.1
Justin
|
Re: Slave Won't Run Under Configured User
|
Hi,
I had a similar problem recently: the way I solved it was to configure a login with userid / password of administrator (middle tab when you define the services) for the service in order for it to run properly. Hope it helps didier On Jun 22, 6:51 pm, CMSeeker <[hidden email]> wrote: > Issue: > The problem I'm facing is the Jenkins slave is running as Window's "Default > User," despite being configured to run as a Domain Admin on our network. > Because it doesn't have the proper execution, modify, or write permissions, > the result is build failures from SVN, Maven, Jboss related builds, etc. > How do I resolve this? > > Jenkins Set-up Details: > I'm using Windows Server 2003 on both Jenkins machines. One is the master > the other is the slave. They both run as window services under the same > Administrator account. This is configured both in the Jenkins UI and in the > Window Services. BTW I'm using Jenkins ver. 1.409.1 > > ----- > Justin > -- > View this message in context:http://jenkins.361315.n4.nabble.com/Slave-Won-t-Run-Under-Configured-... > Sent from the Jenkins users mailing list archive at Nabble.com. |
|
|
Didier, I tried that and unfortunately it did not work.
Justin
|
|
|
Has anyone else had this issue?
Issue: The problem I'm facing is the Jenkins slave is running as Window's "Default User," despite being configured to run as a Domain Admin on our network. Because it doesn't have the proper execution, modify, or write permissions, the result is build failures from SVN, Maven, Jboss related builds, etc. How do I resolve this? Jenkins Set-up Details: I'm using Windows Server 2003 on both Jenkins machines. One is the master the other is the slave. They both run as window services under the same Administrator account. This is configured both in the Jenkins UI and in the Window Services. BTW I'm using Jenkins ver. 1.409.1
Justin
|
|
|
That's odd, I am successfully running the slave under a specific user. I went into the windows services mmc addin and specified the login to use, then restarted the system. I too am using win2k3. On Jun 28, 2011 7:55 AM, "CMSeeker" <[hidden email]> wrote:
> Has anyone else had this issue? > > Issue: > The problem I'm facing is the Jenkins slave is running as Window's "Default > User," despite being configured to run as a Domain Admin on our network. > Because it doesn't have the proper execution, modify, or write permissions, > the result is build failures from SVN, Maven, Jboss related builds, etc. > How do I resolve this? > > Jenkins Set-up Details: > I'm using Windows Server 2003 on both Jenkins machines. One is the master > the other is the slave. They both run as window services under the same > Administrator account. This is configured both in the Jenkins UI and in the > Window Services. BTW I'm using Jenkins ver. 1.409.1 > > ----- > Justin > -- > View this message in context: http://jenkins.361315.n4.nabble.com/Slave-Won-t-Run-Under-Configured-User-tp3617555p3630564.html > Sent from the Jenkins users mailing list archive at Nabble.com. |
|
|
Suggesting a restart? I'll give it a shot.
Justin
|
|
|
You definitely need to restart the service once you've made the change to the login, the login doesn't take effect until the service restarts, I've found that if you try and manually restart the slave service, it messes with the communication with Jenkins, so restarting the machine is the easier route.
On Tue, Jun 28, 2011 at 8:49 AM, CMSeeker <[hidden email]> wrote: Suggesting a restart? I'll give it a shot. -- slide-o-blog http://slide-o-blog.blogspot.com/ |
Re: Slave Won't Run Under Configured User
|
|
If you're running with letting Jenkins handle the Windows service you should also be able to disconnect/relaunch the slave to restart the service.
Richard.
On Wed, Jun 29, 2011 at 3:55 AM, Slide <[hidden email]> wrote: You definitely need to restart the service once you've made the change to the login, the login doesn't take effect until the service restarts, I've found that if you try and manually restart the slave service, it messes with the communication with Jenkins, so restarting the machine is the easier route. |
«
Return to Jenkins users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |