[JIRA] (JENKINS-52125) jenkins master: Cannot contact <slave name>: java.lang.InterruptedException without heavy load or obvious network issue

3,012 views
Skip to first unread message

zichuan.zou@viavisolutions.com (JIRA)

unread,
Jun 21, 2018, 5:39:04 PM6/21/18
to jenkinsc...@googlegroups.com
z z created an issue
 
Jenkins / Bug JENKINS-52125
jenkins master: Cannot contact <slave name>: java.lang.InterruptedException without heavy load or obvious network issue
Issue Type: Bug Bug
Assignee: Oleg Nenashev
Components: _unsorted
Created: 2018-06-21 21:38
Environment: Jenkins master: Jenkins ver. 2.107.3, Debian 3.16.43-2 (this instance running in a docker container, and this docker container is running in a VM on physical machine) also seen on a previous version of Jenkins, 2.65(not very sure)

All Linux(Both slaves and master).
Priority: Major Major
Reporter: z z

This error, Cannot contact <slave name>: java.lang.InterruptedException,

  • no other messages, just one line.
  • happen most often during network I/O intense process like downloading.. also seen during shell script running, building software and tarring files, git merge... while other metrics like cpu usage, memory usage and disk usage are pretty normal/stable, not high load.
  • This error will/will not lead the job to fail. 
  • This message will show in build logs and it happens on many slaves, some of the slaves are VMs on server, some of them are physical server.
  • many affected jobs have parallel branches.
  • network seems working well.
  • also it might be correlated to, (shown in slave's log on master machine, this one does not happen often, but at least one time it synced with the error in question): 
    • INFO: Failed to synchronize IO streams on the channel hudson.remoting.Channel@762efe5d:channel java.lang.InterruptedException     at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:172) at hudson.remoting.Channel.call(Channel.java:951) at hudson.remoting.Channel.syncIO(Channel.java:1679) at hudson.Launcher$RemoteLaunchCallable$1.join(Launcher.java:1315) at sun.reflect.GeneratedMethodAccessor164.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:927) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:901) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:850) at hudson.remoting.UserRequest.perform(UserRequest.java:210) at hudson.remoting.UserRequest.perform(UserRequest.java:53) at hudson.remoting.Request$2.run(Request.java:364) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 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 Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

o.v.nenashev@gmail.com (JIRA)

unread,
Jun 21, 2018, 5:50:02 PM6/21/18
to jenkinsc...@googlegroups.com

o.v.nenashev@gmail.com (JIRA)

unread,
Jun 21, 2018, 5:50:03 PM6/21/18
to jenkinsc...@googlegroups.com

wynet321@163.com (JIRA)

unread,
Jun 29, 2018, 2:44:02 AM6/29/18
to jenkinsc...@googlegroups.com
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

venkat.emadi@gmail.com (JIRA)

unread,
Jul 3, 2018, 1:06:02 AM7/3/18
to jenkinsc...@googlegroups.com

I too see this issue : Cannot contact <machine>: java.lang.InterruptedException. 
When this error encountered, job hangs at this state. 

No other error messages are shown in console log.

There is no network/ssh/hardware issue from slave machine. Since slave machine is online in Jenkins Master and reachable.

venkat.emadi@gmail.com (JIRA)

unread,
Jul 4, 2018, 6:03:02 AM7/4/18
to jenkinsc...@googlegroups.com

jthompson@cloudbees.com (JIRA)

unread,
Sep 24, 2018, 4:37:02 PM9/24/18
to jenkinsc...@googlegroups.com
Jeff Thompson commented on Bug JENKINS-52125
 
Re: jenkins master: Cannot contact <slave name>: java.lang.InterruptedException without heavy load or obvious network issue

Unfortunately, there is not enough information provided to be able to diagnose or reproduce this problem. If you can determine more information about how to isolate or characterize it, we could look into it in more detail. 

This presentation contains further information on diagnosing Remoting connectivity issues. You might be able to find some information in there useful for your troubleshooting exercise. https://speakerdeck.com/onenashev/day-of-jenkins-2017-dealing-with-agent-connectivity-issues

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

jthompson@cloudbees.com (JIRA)

unread,
Oct 29, 2018, 6:10:03 PM10/29/18
to jenkinsc...@googlegroups.com
Jeff Thompson closed an issue as Cannot Reproduce
 

As there hasn't been any response on this for a long time, there is insufficient information to reproduce, and responses were provided to the submitter I'm going to close this out.

Change By: Jeff Thompson
Status: Open Closed
Resolution: Cannot Reproduce

mailriteshm@gmail.com (JIRA)

unread,
Nov 7, 2018, 5:04:02 AM11/7/18
to jenkinsc...@googlegroups.com
ritesh mahendrakar commented on Bug JENKINS-52125
 
Re: jenkins master: Cannot contact <slave name>: java.lang.InterruptedException without heavy load or obvious network issue

I get this error only when I start the Jenkins as a Service and run a pipeline job which transfers data between Master and Slave.

The same job works fine when I Enable / Launch the save using client.

I am using Jenkins 2.138.2

tiendungitd@gmail.com (JIRA)

unread,
Jun 4, 2019, 3:42:02 AM6/4/19
to jenkinsc...@googlegroups.com

I got the same issue in version 2.164.2. I think the build job produce a heavy load, sometimes it also encounter the error 

The forked VM terminated without properly saying goodbye. VM crash or System.exit called

tiendungitd@gmail.com (JIRA)

unread,
Jun 4, 2019, 3:43:02 AM6/4/19
to jenkinsc...@googlegroups.com
Dennis Tran edited a comment on Bug JENKINS-52125
I got the same issue in version 2.164.2. I think the build job produce a heavy load, sometimes it also encounter encountered the error 
{code:java}
The forked VM terminated without properly saying goodbye. VM crash or System.exit called{code}

jthompson@cloudbees.com (JIRA)

unread,
Jun 11, 2019, 4:52:02 PM6/11/19
to jenkinsc...@googlegroups.com

I've seen something like what Dennis Tran reports a few times associated with an OutOfMemoryError. It can take a bit of digging to actually see the errors in these cases. Because the channel or VM fails, the errors may not reach the logs.

Reply all
Reply to author
Forward
0 new messages