[JIRA] (JENKINS-55625) ec2 agent launching broken in 1.42

acrewdson@gmail.com (JIRA)

unread,

Jan 16, 2019, 11:08:02 AM1/16/19

to jenkinsc...@googlegroups.com

Andrew C created an issue

Jenkins /

JENKINS-55625

ec2 agent launching broken in 1.42

Issue Type:	Bug
Assignee:	FABRIZIO MANFREDI
Components:	ec2-plugin
Created:	2019-01-16 16:07
Environment:	Jenkins 2.150.1
Priority:	Minor
Reporter:	Andrew C

Upgraded to ec2 plugin 1.42 today (Jenkins 2.150.1) and it broke ec2 agent launching. Downgrading to 1.42 fixed the problem. Here's the exception and stack trace below. Let me know if I can provide more information and thanks for taking a look.

 
                                                                <===[JENKINS REMOTING CAPACITY]===>Remoting version: 3.27
This is a Unix agent
ERROR: Connection terminated
ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
java.io.EOFException
    at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2680)
    at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3155)
    at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:861)
    at java.io.ObjectInputStream.<init>(ObjectInputStream.java:357)
    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)java.lang.NullPointerException
    at hudson.Util.isRelativePath(Util.java:555)
    at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:642)
    at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:432)
    at hudson.plugins.ec2.ssh.EC2UnixLauncher.launchScript(EC2UnixLauncher.java:217)
    at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48)
    at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294)
    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)

 
                                                            

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

acrewdson@gmail.com (JIRA)

unread,

Jan 16, 2019, 11:09:02 AM1/16/19

to jenkinsc...@googlegroups.com

Andrew C updated an issue

Jenkins /

JENKINS-55625

ec2 agent launching broken in 1.42

Change By:	Andrew C

Upgraded to ec2 plugin 1.42 today (Jenkins 2.150.1) and it broke ec2 agent launching. Downgrading to 1.42 fixed the problem. Here's the exception and stack trace below. Let me know if I can provide more information and thanks for taking a look.

{code:java}

{code}

Add Comment

acrewdson@gmail.com (JIRA)

unread,

Jan 16, 2019, 11:10:35 AM1/16/19

to jenkinsc...@googlegroups.com

Andrew C updated an issue

Jenkins /

JENKINS-55625

ec2 agent launching broken in 1.42

Change By:	Andrew C

Upgraded to ec2 plugin 1.42 today (Jenkins 2.150.1) and it broke ec2 agent launching. Downgrading to 1.42 fixed the problem. Here's the exception and stack trace below.

We are attempting to launch Linux m4large instances with an init script.

fabrizio.manfredi@gmail.com (JIRA)

unread,

Jan 16, 2019, 11:25:02 AM1/16/19

to jenkinsc...@googlegroups.com

FABRIZIO MANFREDI commented on

JENKINS-55625

Re: ec2 agent launching broken in 1.42

Which version of the plugin has been used before the upgrade ?

Are specify in the configuration the path of the java or working dir other things ?

Did you restart the jenkins without any change in the configuration ? in this case can you re try the plugin, but before the use to save the configuration (without any changes ) ?