[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
Daniel Beck updated JENKINS-13253 Slave connection reset issues since 1.456 Change By: Daniel Beck (01/Sep/14 2:43 PM) Labels: remoting 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.
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
Anne Stellingwerf commented on JENKINS-13253 Slave connection reset issues since 1.456 Did anyone ever realize this issue is almost only occurring on Windows?: Over the past 10 days, I faced this issue on 57 occasions, exclusively on Windows slaves. Cees Bos mentioned he saw the issue once on Linux, but all other comments are mentioning Windows slaves. @Bipin Jethwani: Could you elaborate on your solution direction? What did you do to fix it? 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.
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
Bipin Jethwani commented on JENKINS-13253 Slave connection reset issues since 1.456 Anne, It was a network cable issue. When we reached out to that machine and tried simple ping it was erratic. And finally replacing the network cable fixed it. It's running perfectly fine since then. -Bipin 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.
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
Daniel Beck commented on JENKINS-13253 Slave connection reset issues since 1.456 Did anyone rule out the local network being unstable or incapable of holding connections for long periods of time? 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.
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
Bipin Jethwani commented on JENKINS-13253 Slave connection reset issues since 1.456 It was indeed a network issue. It's resolved for me. 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.
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
Bipin Jethwani commented on JENKINS-13253 Slave connection reset issues since 1.456 We are using Jenkins ver. 1.546 The slave is Win 7 machine and we are facing the same connection reset issue. Is there a solution or workaround available? 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.
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
Bipin Jethwani edited a comment on JENKINS-13253 Slave connection reset issues since 1.456 We are using Jenkins ver. 1.546 The slave is Win 7 machine and we are facing the same connection reset issue. Is there a solution or workaround available? Slave.jar version: 2.33 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.
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
Xin Huang edited a comment on JENKINS-13253 Slave connection reset issues since 1.456 Our team is facing the connection reset issue, too. We've tried various version of Jenkins, ranging from 1.4xx to 1.6xx, but the issue seems somewhat random: Before the issue happens, the slave works well. However, several slaves are just don't work. Tried re-create slave VMs, doesn't help much. Newly created slave would suffer the issue after working well for 1 or 2 days. Build lasts from several minutes to hours, usually connection reset happens 1~2 hours after build starts, (long-lasting jobs) but slave is not offline. What's wired, one of our master/slaves never suffered from such issue. It's using 1.469 Change new server to this version doesn't help. We are using Windows 7 Enterprise 64bit on LAN, all slaves are hosted on vSphere. Slaves are connected via web start/install as service. Edit: It turns out we have made a silly mistake. Previously we are using Windows Server 2003/2008, which doesn't have Power Option set to "sleep every 30 min", which is the default option of Windows 7. We found the power option issue by examine all system events at time when socket timeout happened on each master/slave. 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.
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
sharon xia commented on JENKINS-13253 Slave connection reset issues since 1.456 I think this might be caused by the slave node configuration. I used another Win 7 machine and installed the whole process and this issue is gone. 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.
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
Xin Huang commented on JENKINS-13253 Slave connection reset issues since 1.456 Our team is facing the connection reset issue, too. We've tried various version of Jenkins, ranging from 1.4xx to 1.6xx, but the issue seems somewhat random: Before the issue happens, the slave works well. However, several slaves are just don't work. Tried re-create slave VMs, doesn't help much. Newly created slave would suffer the issue after working well for 1 or 2 days. Build lasts from several minutes to hours, usually connection reset happens 1~2 hours after build starts, (long-lasting jobs) but slave is not offline. What's wired, one of our master/slaves never suffered from such issue. It's using 1.469 Change new server to this version doesn't help. We are using Windows 7 Enterprise 64bit on LAN, all slaves are hosted on vSphere. Slaves are connected via web start/install as service. 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.
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
Brian Smith commented on JENKINS-13253 Slave connection reset issues since 1.456 Seeing what looks like the same thing using 1.532.2 - seems fairly random so far. If I manage to figure out any sort of pattern I will post again. Windows Server Windows Nodes all on the same local corporate network Jobs are Freestyle with Windows batch files being used. 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.
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
Brian Smith edited a comment on JENKINS-13253 Slave connection reset issues since 1.456 Seeing what looks like the same thing using 1.532.2 - seems fairly random so far. If I manage to figure out any sort of pattern I will post again. Windows Server Windows Nodes all on the same local corporate network Jobs are Freestyle with Windows batch files being used. FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:722) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:167) at $Proxy42.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:925) at hudson.Launcher$ProcStarter.join(Launcher.java:360) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:91) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:60) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:566) at hudson.model.Run.execute(Run.java:1665) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:246) Caused by: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:782) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.net.SocketException: Connection reset 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:77) at java.io.ObjectInputStream$PeekInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) 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.
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
Doug Henderson commented on JENKINS-13253 Slave connection reset issues since 1.456 Hi, I'm using Jenkins 1.532.2 and am seeing the same error... but maybe slightly different? You tell me - quite happy to dump logs and the like (will look at the docs and add another comment later). Our primary Jenkins master is running on a Google VM, with the slaves running on other Google VM's and connected/registered via swarm plugin. We use REST API to launch jobs and monitor output - so while we seem similar problem, its also sorta the same The REST API returns the error mentioned so many times above... pretty stack trace output partially into the build. HOWEVER, once the API has returned the error text, our app stops polling for console output. At that point the SAME build seems to start logging again in the normal Jenkins build console... and when you add the initial logging retrieved via REST and the new logging that started upon failure, we see the build actually did complete. (REST log + Console log = Entire log) Doug As mentioned above, I'll try to get some official logs and attach them later. 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.
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
Doug Henderson edited a comment on JENKINS-13253 Slave connection reset issues since 1.456 Hi, I'm using Jenkins 1.532.2 and am seeing the same error... but maybe slightly different? You tell me - quite happy to dump logs and the like (will look at the docs and add another comment later). Our primary Jenkins master is running on a Google VM, with the slaves running on other Google VM's and connected/registered via swarm plugin. We use REST API to launch jobs and monitor output - so while we seem similar problem, its also sorta the same The REST API returns the error mentioned so many times above... pretty stack trace output partially into the build. HOWEVER, once the API has returned the error text, our app stops polling for console output. At that point the SAME build seems to start logging again in the normal Jenkins build console... and when you add the initial logging retrieved via REST and the new logging that started upon failure, we see the build actually did complete. (REST log + Console log = Entire log) Doug As mentioned above, I'll try to get some official logs and attach them later. ADDITIONAL: The job in question was a build that used the MavenPlugin to execute. When I changed to a freestyle build with a cmd-line step of "mvn ." the problem no longer occurred. 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.
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
sharon xia commented on JENKINS-13253 Slave connection reset issues since 1.456 I saw this issue on 1.532.2. The slave is Win 7 machine. I have a automation test running on it which supposed to last for more than 10 hours. The reset exception will 100% happen after running a while(several minutes after test start, or 1 hour or two after test starts). However, similar job could run successfully without such exception on either linux or win server 2008. FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset 16:43:49 hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset 16:43:49 at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) 16:43:49 at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) 16:43:49 at hudson.remoting.Request.call(Request.java:174) 16:43:49 at hudson.remoting.Channel.call(Channel.java:722) 16:43:49 at hudson.Launcher$RemoteLauncher.kill(Launcher.java:887) 16:43:49 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:589) 16:43:49 at hudson.model.Run.execute(Run.java:1665) 16:43:49 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 16:43:49 at hudson.model.ResourceController.execute(ResourceController.java:88) 16:43:49 at hudson.model.Executor.run(Executor.java:246) 16:43:49 Caused by: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset 16:43:49 at hudson.remoting.Request.abort(Request.java:299) 16:43:49 at hudson.remoting.Channel.terminate(Channel.java:782) 16:43:49 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) 16:43:49 Caused by: java.net.SocketException: Connection reset 16:43:49 at java.net.SocketInputStream.read(Unknown Source) 16:43:49 at java.io.BufferedInputStream.fill(Unknown Source) 16:43:49 at java.io.BufferedInputStream.read(Unknown Source) 16:43:49 at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:77) 16:43:49 at java.io.ObjectInputStream$PeekInputStream.peek(Unknown Source) 16:43:49 at java.io.ObjectInputStream$BlockDataInputStream.peek(Unknown Source) 16:43:49 at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source) 16:43:49 at java.io.ObjectInputStream.readObject0(Unknown Source) 16:43:49 at java.io.ObjectInputStream.readObject(Unknown Source) 16:43:49 at hudson.remoting.Command.readFrom(Command.java:92) 16:43:49 at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71) 16:43:49 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) 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.
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
vbier commented on JENKINS-13253 Slave connection reset issues since 1.456 As of today, we also have this problem. Builds have not run for a while, and the only thing we changed in the meantime was moving the master installation from a physical server to a virtual machine. We have been running 1.509.4, and after the error appeared I upgraded to 1.532.1, but this did not change anything. I enabled log level FINE for hudson.remoting, but that does not really give any obvious additional information. I include it here in case you can figure out anything from it: Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,38) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,38) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,628) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,628) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,155) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,155) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,2) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,2) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
vbier edited a comment on JENKINS-13253 Slave connection reset issues since 1.456 As of today, we also have this problem. Builds have not run for a while, and the only thing we changed in the meantime was moving the master installation from a physical server to a virtual machine. We have been running 1.509.4, and after the error appeared I upgraded to 1.532.1, but this did not change anything. I enabled log level FINE for hudson.remoting, but that does not really give any obvious additional information. I include it here in case you can figure out anything from it: Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,38) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,38) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,628) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,628) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,155) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,155) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,2) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,2) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
vbier edited a comment on JENKINS-13253 Slave connection reset issues since 1.456 As of today, we also have this problem. Builds have not run for a while, and the only thing we changed in the meantime was moving the master installation from a physical server to a virtual machine. We have been running 1.509.4, and after the error appeared I upgraded to 1.532.1, but this did not change anything. I enabled log level FINE for hudson.remoting, but that does not really give any obvious additional information. I include it here in case you can figure out anything from it: Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,38) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,38) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,628) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,628) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,155) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,155) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,2) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,2) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
vbier edited a comment on JENKINS-13253 Slave connection reset issues since 1.456 As of today, we also have this problem. Builds have not run for a while, and the only thing we changed in the meantime was moving the master installation from a physical server to a virtual machine. We have been running 1.509.4, and after the error appeared I upgraded to 1.532.1, but this did not change anything. I enabled log level FINE for hudson.remoting, but that does not really give any obvious additional information. I include it here in case you can figure out anything from it: Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,38) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,38) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,628) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,628) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,155) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,155) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,2) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,2) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
vbier edited a comment on JENKINS-13253 Slave connection reset issues since 1.456 As of today, we also have this problem. Builds have not run for a while, and the only thing we changed in the meantime was moving the master installation from a physical server to a virtual machine. We have been running 1.509.4, and after the error appeared I upgraded to 1.532.1, but this did not change anything. I enabled log level FINE for hudson.remoting, but that does not really give any obvious additional information. I include it here in case you can figure out anything from it: Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,38) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,38) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,628) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,628) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,155) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,155) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,2) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,2) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
vbier edited a comment on JENKINS-13253 Slave connection reset issues since 1.456 As of today, we also have this problem. Builds have not run for a while, and the only thing we changed in the meantime was moving the master installation from a physical server to a virtual machine. We have been running 1.509.4, and after the error appeared I upgraded to 1.532.1, but this did not change anything. I enabled log level FINE for hudson.remoting, but that does not really give any obvious additional information. I include it here in case you can figure out anything from it: Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,38) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,38) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,628) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,628) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,155) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,155) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,2) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,2) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
Wendy Wen commented on JENKINS-13253 Slave connection reset issues since 1.456 Our team face the same issue, which happen frequently. Here is the log: E:\Head-Build-Job-Workspaceexit 0 FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:722) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:887) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:589) at hudson.model.Run.execute(Run.java:1678) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:782) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.net.SocketException: Connection reset 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:77) at java.io.ObjectInputStream$PeekInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) 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/groups/opt_out.
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
Jay Spang commented on JENKINS-13253 Slave connection reset issues since 1.456 I'm also seeing this same issue. Master: Jenkins 1.537 (Win2012) Slave: Win7 using JNLP It doesn't afflict just one slave. I have a pool of 10 identical slaves and I would guess that I get this error maybe 2-3 times a day across different slaves (causing jobs to fail ). 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/groups/opt_out.
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
chikigai commented on JENKINS-13253 Slave connection reset issues since 1.456 I am getting random job failures very frequently due to this. I have a master running Jenkins 1.538 on WinXP and 3 Windows7 slave machines connected via launch method "Windows slave as a Windows Service" all disconnecting with the same issue. Never had this issue when the slave machines were WinXP and master was running 1.528. Is anyone aware of a past version where this issue does not occur? 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/groups/opt_out.
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
Nicholas Lun commented on JENKINS-13253 Slave connection reset issues since 1.456 Is there any update to this issue? All I can tell from the stacktrace is that at the end of the build, Jenkins requests that the slave kill the remaining processes. But, before it can do so it receives a response that the Connection was terminated due to some failure during a read operation(can't see the reason behind the failure in the stacktrace). Doesn't this seem like some kind of race condition where the slave is trying to finish up and kill the remaining processes while the master terminates the connection before the slave can finish? 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/groups/opt_out.
