[
https://issues.jenkins-ci.org/browse/JENKINS-8740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159301#comment-159301
]
Nick Sieger commented on JENKINS-8740:
--------------------------------------
We're running 1.449 at this time and haven't seen this issue for a while, so I
think it's safe to call it closed.
> Log file filling up disk with connection reset and broken pipe errors
> ---------------------------------------------------------------------
>
> Key: JENKINS-8740
> URL: https://issues.jenkins-ci.org/browse/JENKINS-8740
> Project: Jenkins
> Issue Type: Bug
> Components: master-slave
> Affects Versions: current
> Environment: http://ci.jruby.org/
> Jenkins 1.396
> Linux ip-10-251-193-235 2.6.18-xenU-ec2-v1.0 #2 SMP Tue Feb 19 10:51:53 EST
> 2008 i686 Dual-Core AMD Opteron(tm) Processor 2218 HE AuthenticAMD GNU/Linux
> Java 1.6.0_11-b03
> Reporter: Nick Sieger
> Priority: Critical
> Attachments: ci.jruby.org-jenkins-node.log,
> ci.jruby.org-jenkins-node2.log
>
>
> I have ci.jruby.org running a recent Jenkins build with a master and 3 remote
> nodes started by JNLP. After a while the nodes get disconnected, and the
> master's log starts filling up with these stack traces:
> {noformat}
> Feb 7, 2011 12:22:00 PM hudson.remoting.ProxyOutputStream$Chunk$1 run
> WARNING: Failed to write to stream
> winstone.ClientSocketException: Failed to write to client
> at winstone.ClientOutputStream.write(ClientOutputStream.java:41)
> at winstone.WinstoneOutputStream.commit(WinstoneOutputStream.java:181)
> at winstone.WinstoneOutputStream.commit(WinstoneOutputStream.java:119)
> at winstone.WinstoneOutputStream.write(WinstoneOutputStream.java:112)
> at java.io.OutputStream.write(OutputStream.java:58)
> at
> hudson.remoting.ProxyOutputStream$Chunk$1.run(ProxyOutputStream.java:185)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: java.net.SocketException: Connection reset
> at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:96)
> at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
> at winstone.ClientOutputStream.write(ClientOutputStream.java:39)
> ... 11 more
> Feb 7, 2011 12:22:00 PM hudson.remoting.ProxyOutputStream$Chunk$1 run
> WARNING: Failed to write to stream
> winstone.ClientSocketException: Failed to write to client
> at winstone.ClientOutputStream.write(ClientOutputStream.java:41)
> at winstone.WinstoneOutputStream.commit(WinstoneOutputStream.java:181)
> at winstone.WinstoneOutputStream.commit(WinstoneOutputStream.java:119)
> at winstone.WinstoneOutputStream.write(WinstoneOutputStream.java:112)
> at java.io.OutputStream.write(OutputStream.java:58)
> at
> hudson.remoting.ProxyOutputStream$Chunk$1.run(ProxyOutputStream.java:185)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: java.net.SocketException: Broken pipe
> at java.net.SocketOutputStream.socketWrite0(Native Method)
> at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
> at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
> at winstone.ClientOutputStream.write(ClientOutputStream.java:39)
> ... 11 more
> {noformat}
> I can provide a login to the Jenkins instance on ci.jruby.org if desired.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
