[JIRA] (JENKINS-59683) Jenkins EC2 nodes fail to launch

31 views
Skip to first unread message

gunter@grodotzki.co.za (JIRA)

unread,
Oct 7, 2019, 5:03:03 AM10/7/19
to jenkinsc...@googlegroups.com
Gunter Grodotzki created an issue
 
Jenkins / Bug JENKINS-59683
Jenkins EC2 nodes fail to launch
Issue Type: Bug Bug
Assignee: FABRIZIO MANFREDI
Components: ec2-plugin
Created: 2019-10-07 09:02
Priority: Blocker Blocker
Reporter: Gunter Grodotzki 
ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
java.lang.NullPointerException
	at java.lang.ProcessEnvironment.validateValue(ProcessEnvironment.java:120)
	at java.lang.ProcessEnvironment.access$400(ProcessEnvironment.java:61)
	at java.lang.ProcessEnvironment$Value.valueOf(ProcessEnvironment.java:203)
	at java.lang.ProcessEnvironment$StringEnvironment.put(ProcessEnvironment.java:243)
	at java.lang.ProcessEnvironment$StringEnvironment.put(ProcessEnvironment.java:221)
	at hudson.slaves.CommandLauncher.launch(CommandLauncher.java:130)
	at hudson.plugins.ec2.ssh.EC2UnixLauncher.launchScript(EC2UnixLauncher.java:253)
	at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48)
	at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:297)
	at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
	at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71)
	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)

when I manually log and use the same command it works?

 

 
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

gunter@grodotzki.co.za (JIRA)

unread,
Oct 7, 2019, 5:05:02 AM10/7/19
to jenkinsc...@googlegroups.com
Gunter Grodotzki updated an issue
Change By: Gunter Grodotzki
{noformat}

ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
java.lang.NullPointerException
at java.lang.ProcessEnvironment.validateValue(ProcessEnvironment.java:120)
at java.lang.ProcessEnvironment.access$400(ProcessEnvironment.java:61)
at java.lang.ProcessEnvironment$Value.valueOf(ProcessEnvironment.java:203)
at java.lang.ProcessEnvironment$StringEnvironment.put(ProcessEnvironment.java:243)
at java.lang.ProcessEnvironment$StringEnvironment.put(ProcessEnvironment.java:221)
at hudson.slaves.CommandLauncher.launch(CommandLauncher.java:130)
at hudson.plugins.ec2.ssh.EC2UnixLauncher.launchScript(EC2UnixLauncher.java:253)
at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:297)
at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71)
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){noformat}

when I manually log and use the same command it works?

Switching to java-connection instead of native ssh makes it work again.  

 

gunter@grodotzki.co.za (JIRA)

unread,
Oct 7, 2019, 5:07:02 AM10/7/19
to jenkinsc...@googlegroups.com
Gunter Grodotzki updated an issue
Change By: Gunter Grodotzki
Environment: Jenkins ver. 2.190.1
ec2: 1.46.1

gunter@grodotzki.co.za (JIRA)

unread,
Oct 7, 2019, 5:23:02 AM10/7/19
to jenkinsc...@googlegroups.com
Gunter Grodotzki updated an issue
Change By: Gunter Grodotzki
Component/s: configuration-as-code-plugin

gunter@grodotzki.co.za (JIRA)

unread,
Oct 7, 2019, 5:24:02 AM10/7/19
to jenkinsc...@googlegroups.com
Gunter Grodotzki updated an issue
{noformat}
ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
java.lang.NullPointerException
at java.lang.ProcessEnvironment.validateValue(ProcessEnvironment.java:120)
at java.lang.ProcessEnvironment.access$400(ProcessEnvironment.java:61)
at java.lang.ProcessEnvironment$Value.valueOf(ProcessEnvironment.java:203)
at java.lang.ProcessEnvironment$StringEnvironment.put(ProcessEnvironment.java:243)
at java.lang.ProcessEnvironment$StringEnvironment.put(ProcessEnvironment.java:221)
at hudson.slaves.CommandLauncher.launch(CommandLauncher.java:130)
at hudson.plugins.ec2.ssh.EC2UnixLauncher.launchScript(EC2UnixLauncher.java:253)
at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:297)
at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71)
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){noformat}
 

on non-native-ssh:

 
{noformat}
INFO: Launching remoting agent (via Trilead SSH2 Connection):  java  -jar /tmp/remoting.jar -workDir /tmp
<===[JENKINS REMOTING CAPACITY]===>Remoting version: 3.33
This is a Unix agent

ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
java.lang.NullPointerException
at hudson.Util.isRelativePath(Util.java:351)
at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:649)
at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:435)
at hudson.plugins.ec2.ssh.EC2UnixLauncher.launchScript(EC2UnixLauncher.java:263)

at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:297)
at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71)
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)
ERROR: Connection terminated
java.io.EOFException
at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2681)
at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3156)
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:862)
at java.io.ObjectInputStream.<init>(ObjectInputStream.java:358)
at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:49)
at hudson.remoting.Command.readFrom(Command.java:140)
at hudson.remoting.Command.readFrom(Command.java:126)
at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36)
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)
Caused: java.io.IOException: Unexpected termination of the channel
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77){noformat}
This seems to be related to the "configuration-as-code-plugin" - when I manually log and use save the same command jenkins config via web-ui (without changing anything) it works . Seems like a setting is not properly being set ?

Switching to java-connection instead of native ssh makes it work again.  

 

 

gunter@grodotzki.co.za (JIRA)

unread,
Oct 7, 2019, 5:26:03 AM10/7/19
to jenkinsc...@googlegroups.com
Gunter Grodotzki updated an issue
Change By: Gunter Grodotzki
Environment:
Jenkins ver. 2.190.1
ec2: 1.46.1
configuration-as-code-plugin: 1.31

gunter@grodotzki.co.za (JIRA)

unread,
Oct 7, 2019, 6:33:03 AM10/7/19
to jenkinsc...@googlegroups.com
Gunter Grodotzki commented on Bug JENKINS-59683
 
Re: Jenkins EC2 nodes fail to launch

sorted, I had to explicitly set "remoteFS" via configuration-as-code. Via webinterface I can leave it empty and it will automatically use the homedir, with CasC that does not seem to be supported

gunter@grodotzki.co.za (JIRA)

unread,
Oct 7, 2019, 6:35:02 AM10/7/19
to jenkinsc...@googlegroups.com
Change By: Gunter Grodotzki
Status: Open Fixed but Unreleased
Resolution: Not A Defect
Reply all
Reply to author
Forward
0 new messages