-
Bug
-
Resolution: Fixed
-
Major
-
Master : Redhat 5
Slave Node : Win7 x64
-
Powered by SuggestiMate -
Jenkins 2.248
We used to be able to launch the slave node successfully, but it did not work since we upgraded the jenkins to latest version (1.449)
It doesn't dump any exception to the console, but I captured the output:
Connecting to 192.168.160.62 Checking if Java exists java full version "1.7.0-b147" Installing the Jenkins slave service Copying jenkins-slave.exe Copying slave.jar Copying jenkins-slave.xml Registering the service ERROR: Failed to create a service: Status Invalid Service Account ...
[JENKINS-12660] Fail to start the windows service when trying to launch agent node
Have the same issue as well as stated above, master is 1.450, slave a Windows Server 2008 R2 x64.
I had the same issue but was able to resolve it by using <Computer Name>\<User name>
The same issue. Master is 1.451, slave - Windows Server 2003.
changed to master/slave component as it is not related to the slave-setup plugin.
So what I did was add the Machine-Name part to the user names:
Launch method: Let Jenkins control this Windows slave as a Windows service
Administrator user name: .\Administrator
Password: ***
Host:
Run service as: Log on using a different account
User name: .\Builder
Password: ***
I'm getting a similar problem with Jenkins 1.451 and 2008 R2
However, I'm trying to use a managed Service Account under the domain.
Prefixing the username with "computername\" resolves this issue for me.
That has worked for me as well, thanks! - added "computername\" before Administrator user name as Tom mentioned and set 'Run service as' to be "Use Administrator account given above".
Adding ".\" before the username worked for me. Using '.\' is the same as using the local domain. If you type in .\ before the username, that will instruct it that you are logging onto the local computer.
Facing same issue with following configuration:
Java Version: 1.7.0-25
Slave : Windows 2008 R2-64Bit
But the approach ".\Username" is not solving problem in my case.
In system events found error saying logon failure due to incorrect username or password even though provided correct credentials.
JNLP agent connected from /10.192.60.191 <===[JENKINS REMOTING CAPACITY]===>Slave.jar version: 2.22 This is a Windows slave Copied maven-agent.jar Copied maven3-agent.jar Copied maven3-interceptor.jar Copied maven-interceptor.jar Copied maven2.1-interceptor.jar Copied plexus-classworld.jar Copied classworlds.jar Slave successfully connected and online ERROR: Connection terminated java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:185) at java.io.BufferedInputStream.fill(BufferedInputStream.java:235) at java.io.BufferedInputStream.read(BufferedInputStream.java:254) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2265) at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2558) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2568) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1314) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
Its is mostly a documentation bug.
WinSW should explicitly mention that user name should be specified along with its domain
Alternatively, if the user name does not contain a backslash,prefix with .\
Still actual, I'd guess. Will verify it and cross-post a bug to WinSW if it still exists
Still actual!!!
[2017-03-07 21:49:25] [windows-slaves] Starting the service ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
java.lang.reflect.UndeclaredThrowableException
at com.sun.proxy.$Proxy56.start(Unknown Source) at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:340) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:261) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.jinterop.JInteropInvocationHandler.invoke(JInteropInvocationHandler.java:140) ... 8 more Caused by: org.jinterop.dcom.common.JIException: Service Logon Failure at org.jvnet.hudson.wmi.Win32Service$Implementation.start(Win32Service.java:149) ... 13 more
Managed to make this occur, not sure if this helps debug / resolve the issue. On a windows 10 slave that was working, I turned on auto logon so my admin user would logon automatically at boot time. Once I did this the same issue above started happening. To which .\username and hostname\username could not rectify the issue. I also disabled auto login and the problem still persists. I will likely build the slave up from scratch again.
Server: Jenkins:lts docker image, ver 2.73.2, jdk8+
Client Windows 10, jdk8+
[ts-syd-01] Starting Virtual Machine... [ts-syd-01] VM already powered on [ts-syd-01] Waiting for VMTools [ts-syd-01] VM Tools are running [ts-syd-01] Finished wait for VMTools [ts-syd-01] Waiting for 10 seconds before asking hudson.os.windows.ManagedWindowsServiceLauncher@6b5f20e to launch slave. [ts-syd-01] Asking ManagedWindowsServiceLauncher to launch slave. [2018-01-31 07:34:34] [windows-slaves] Connecting to 10.7.65.217 Checking if Java exists java -version returned 1.8.0. [2018-01-31 07:34:42] [windows-slaves] Copying jenkins-slave.xml [2018-01-31 07:34:42] [windows-slaves] Copying slave.jar [2018-01-31 07:34:42] [windows-slaves] Starting the service [ts-syd-01] EXCEPTION while starting VM java.lang.reflect.UndeclaredThrowableException java.lang.reflect.UndeclaredThrowableException at com.sun.proxy.$Proxy94.start(Unknown Source) at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:342) at hudson.slaves.DelegatingComputerLauncher.launch(DelegatingComputerLauncher.java:64) at org.jenkinsci.plugins.vSphereCloudLauncher.launch(vSphereCloudLauncher.java:248) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:262) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.jinterop.JInteropInvocationHandler.invoke(JInteropInvocationHandler.java:140) ... 10 more Caused by: org.jinterop.dcom.common.JIException: Service Logon Failure at org.jvnet.hudson.wmi.Win32Service$Implementation.start(Win32Service.java:149) ... 15 more ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins org.jinterop.dcom.common.JIException: Service Logon Failure at org.jvnet.hudson.wmi.Win32Service$Implementation.start(Win32Service.java:149) Caused: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.jinterop.JInteropInvocationHandler.invoke(JInteropInvocationHandler.java:140) Caused: java.lang.reflect.UndeclaredThrowableException at com.sun.proxy.$Proxy94.start(Unknown Source) at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:342) at hudson.slaves.DelegatingComputerLauncher.launch(DelegatingComputerLauncher.java:64) at org.jenkinsci.plugins.vSphereCloudLauncher.launch(vSphereCloudLauncher.java:248) Caused: java.lang.RuntimeException at org.jenkinsci.plugins.vSphereCloudLauncher.launch(vSphereCloudLauncher.java:268) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:262) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)
phopkins101 not sure they are the same. You one looks like a bug in vSphere Cloud Plugin
Manually setting the log on credentials within the service itself directly on the Win 7 box fixed it for me. Used the same creds, but when doing it manually Windows grants the Service Logon right to the user.
This issue was resolved by nextturn in Windows Service Wrapper 2.7.0: https://github.com/winsw/winsw/releases/tag/v2.7.0 . This version was integrated into Jenkins 2.248.
Had the same today installing a Windows Server 2008 R2 x64 node using the local admin account.
However, I added another node with the same OS to the same Master successfully this morning too but with a domain account.
Master is 1.444