[JIRA] [remoting] (JENKINS-23852) slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed"
Title: Message Title James Femia commented on JENKINS-23852 Re: slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed" We are having the same issue, already running slave.jar as a scheduled task on login so the suggested workaround does not help us Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23852) slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed"
Title: Message Title James Femia edited a comment on JENKINS-23852 Re: slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed" We are having the same issue with slaves running on Win10 in VMWare , already running slave.jar as a scheduled task on login so the suggested workaround does not help us Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23852) slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed"
Title: Message Title Dario Griffo commented on JENKINS-23852 Re: slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed" Florian Doersch Arnt Witteveen I have been running again builds for 4 hours without any disconnection. My "fix": stop using the slave windows service and run this as a scheduled task running a bat file. First I downloaded the slave.jar and slave-agent.jnlp into an empty folder (C:\Jenkins). Created the following .bat in that folder cd C:\Jenkins java -jar slave.jar -jnlpUrl http:/MY_JENKINS_URL/computer/MY_SLAVE_NAME/slave-agent.jnlp -secret MYSECRET That last line is the one in the agent page Create a scheduled task to run at startup with same credentials as the uninstall windows slave service. So far, no disconnections, when I used to have them every 4~5 minutes. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23852) slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed"
Title: Message Title Dario Griffo commented on JENKINS-23852 Re: slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed" Same issue for me. Below some log from the slave. I can get small builds to end fine (less than 2 minutes), but we are running automation tests running in this box (fixed job) and takes ~30 minutes. This started last week, without any changes in the boxes, no updates, no infrastructure changes. The build has been working fine for 2 months. Master: Windows 2012 64-bit R2 Datacenter Slave: Windows 7 64-bit Enterprise Slave log (all look the same) INFO: Trying protocol: JNLP2-connect Jan 18, 2016 12:49:34 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connected Jan 18, 2016 12:59:54 PM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel channel java.net.SocketException: Software caused connection abort: recv failed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82) at hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:72) at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103) at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Jan 18, 2016 12:59:54 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Terminated Jan 18, 2016 1:00:04 PM jenkins.slaves.restarter.JnlpSlaveRestarterInstaller$2$1 onReconnect INFO: Restarting slave via jenkins.slaves.restarter.WinswSlaveRestarter@c2400d Jan 18, 2016 1:00:06 PM hudson.remoting.jnlp.Main createEngine INFO: Setting up slave: vostro-470-002 Jan 18, 2016 1:00:06 PM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode. Jan 18, 2016 1:00:06 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among http://168.0.0.228:7542/ Jan 18, 2016 1:00:06 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking Jan 18, 2016 1:00:06 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to ci.teamhours.com:50081 Jan 18, 2016 1:00:06 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Trying protocol: JNLP2-connect Jan 18, 2016 1:00:06 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connected Add Comment
[JIRA] [remoting] (JENKINS-23852) slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed"
Title: Message Title Moshe Zvi commented on JENKINS-23852 Re: slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed" +1 Florian Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23852) slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed"
Title: Message Title Florian Doersch commented on JENKINS-23852 Re: slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed" we're having the same issue with 1.638 and "real" (not virtualized) hosts Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23852) slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed"
Title: Message Title Jay Kah commented on JENKINS-23852 Re: slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed" We are having the same issue on Jenkins ver. 1.634 on Ubuntu Trusty. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23852) slave builds repeatedly broken by hudson.remoting.ChannelClosedException: channel is already closed
Title: Message Title Ed Mangual commented on JENKINS-23852 Re: slave builds repeatedly broken by hudson.remoting.ChannelClosedException: channel is already closed I have the same issues with frequent disconnects with Jenkins Master/Slaves VMs hosted on ESX with VMotion enabled. This is common in IT organizations nowadays. What are we doing to get a permanent solution to this issue? Daniel Serodio Can you tell us if disabling VMotion helped? In the meantime I will have my ops team disable vmotion as well. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23852) slave builds repeatedly broken by hudson.remoting.ChannelClosedException: channel is already closed
Title: Message Title Daniel Serodio commented on JENKINS-23852 Re: slave builds repeatedly broken by hudson.remoting.ChannelClosedException: channel is already closed Ed Mangual unfortunately, I found out that VMotion was already disabled. I did find out that our corporate firewall closes connections if the connection is idle, but from what I understand of Jenkins remoting I think the ping thread should prevent the connection from idling. Still investigating. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23852) slave builds repeatedly broken by hudson.remoting.ChannelClosedException: channel is already closed
Title: Message Title Arnt Witteveen commented on JENKINS-23852 Re: slave builds repeatedly broken by hudson.remoting.ChannelClosedException: channel is already closed At the time this first occurred, in my case we had only 1 slave, so that means that at least for me that was probably not the cause if I understand correctly? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23852) slave builds repeatedly broken by hudson.remoting.ChannelClosedException: channel is already closed
Title: Message Title stephenconnolly commented on JENKINS-23852 Re: slave builds repeatedly broken by hudson.remoting.ChannelClosedException: channel is already closed By any chance are you provisioning and de-provisioning other unrelated slaves? I ask as a slave disconnect, if incorrectly timed and unlucky enough can cause NioChannelHub to livelock (JENKINS-25218) trying to process the channel termination for the disconnected slave until the ping thread kills that channel and breaks the livelock. Disabling the ping threads on the slave and the master should either provide an alternative workaround or confirm that this issue is JENKINS-25218 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23852) slave builds repeatedly broken by hudson.remoting.ChannelClosedException: channel is already closed
Title: Message Title stephenconnolly commented on JENKINS-23852 Re: slave builds repeatedly broken by hudson.remoting.ChannelClosedException: channel is already closed Arnt Witteveen correct if you have one and only one slave and you are not using one of the cloud providers and you are not using a retention strategy that disconnects when idle then this issue is not JENKINS-25218. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23852) slave builds repeatedly broken by hudson.remoting.ChannelClosedException: channel is already closed
Title: Message Title Daniel Serodio commented on JENKINS-23852 Re: slave builds repeatedly broken by hudson.remoting.ChannelClosedException: channel is already closed Thanks Arnt Witteveen, this is exactly our setup. As a workaround, I've asked our ops team do disable VMotion for these VMs Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23852) slave builds repeatedly broken by hudson.remoting.ChannelClosedException: channel is already closed
Title: Message Title Arnt Witteveen commented on JENKINS-23852 Re: slave builds repeatedly broken by hudson.remoting.ChannelClosedException: channel is already closed Meanwhile, we have found another cause of these disconnects, which may help in reproducing it (if you happen to have this setup available) : this happens when the slave is on a VMWare ESXi virtual machine, and you have multiple hosts (physical machines running VMWare ESX) available, and you have set up VMotion with DRS: at the moment the current slave VM host gets overloaded (e.g. because it starts a build!) the load is rebalanced over the hosts, and the slave VM may move to another host. This movement should be transparent but seems to cause this issue (I'm not sure why, it might be a timeout, it might be the fact that the physical network card that receives the traffic changes, or something else still). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23852) slave builds repeatedly broken by hudson.remoting.ChannelClosedException: channel is already closed
Michael M commented on JENKINS-23852 slave builds repeatedly broken by hudson.remoting.ChannelClosedException: channel is already closed Just wanted to follow up. We see this issue a few times a week, and are confident that there isn't technically a network outage at all as other nodes and jobs stay connected through this error. It most frequently happens for us at the end of a job, once as far as I'm concerned everything is complete. Can attach more logs of the error if that is helpful. Running Jenkins 1.583 on Windows 7. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
