[JIRA] (JENKINS-49958) random jenkins IO failure
Title: Message Title Jeff Thompson closed an issue as Cannot Reproduce Closing for lack of response providing sufficient reproduction or diagnostic information. Jenkins / JENKINS-49958 random jenkins IO failure Change By: Jeff Thompson Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-49958) random jenkins IO failure
Title: Message Title Jeff Thompson commented on JENKINS-49958 Re: random jenkins IO failure You can also read about agent logging here: https://github.com/jenkinsci/remoting/blob/master/docs/logging.md . In summary, if you add a java.util.logging properties file and then reference it via the `-loggingConfig` parameter to the agent. For example something like this: `-loggingConfig jenkins-logging.properties`. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-49958) random jenkins IO failure
Title: Message Title Oleg Nenashev commented on JENKINS-49958 Re: random jenkins IO failure yacoub hossain https://speakerdeck.com/onenashev/day-of-jenkins-2017-dealing-with-agent-connectivity-issues?slide=51 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-49958) random jenkins IO failure
Title: Message Title yacoub hossain commented on JENKINS-49958 Re: random jenkins IO failure Oleg Nenashev, okay but how do i find it (i assume you meant logs) on the agent? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-49958) random jenkins IO failure
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49958 random jenkins IO failure Change By: Oleg Nenashev Component/s: remoting Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-49958) random jenkins IO failure
Title: Message Title Oleg Nenashev commented on JENKINS-49958 Re: random jenkins IO failure yacoub hossain It needs a long from the agent side as well. Cannot diagnose without it Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-49958) random jenkins IO failure
Title: Message Title Adam Zovits assigned an issue to Unassigned Jenkins / JENKINS-49958 random jenkins IO failure Change By: Adam Zovits Assignee: Kohsuke Kawaguchi Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-49958) random jenkins IO failure
Title: Message Title yacoub hossain assigned an issue to Kohsuke Kawaguchi wasn't sure who to assign to Jenkins / JENKINS-49958 random jenkins IO failure Change By: yacoub hossain Assignee: Kohsuke Kawaguchi Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-49958) random jenkins IO failure
Title: Message Title yacoub hossain created an issue Jenkins / JENKINS-49958 random jenkins IO failure Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-03-06 18:13 Environment: Jenkins Master 2.89.4 windows host, issue happens on os x slave Priority: Blocker Reporter: yacoub hossain i get these random failures, seeming due to IO issues and seemingly coonfined to OS X machines. Here is an example stack; (I checked, and the file it seems to be complaining about "/Users/asm_qa/jf/workspace/dr64@tmp/secretFiles/f7e1d980-45c5-4350-b77c-a697c022f422" does exist on that slave.) please HELP! java.nio.channels.ClosedChannelException at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:179) at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:721) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) Caused: hudson.remoting.ChannelClosedException: Remote call on JNLP4-connect connection from camac1.ads.autodesk.com/10.146.47.76:49613 failed. The channel is closing down or has closed down at hudson.remoting.Channel.call(Channel.java:901) at hudson.FilePath.act(FilePath.java:986) Caused: java.io.IOException: remote file operation failed: /Users/asm_qa/jf/workspace/dr64@tmp/secretFiles/f7e1d980-45c5-4350-b77c-a697c022f422 at hudson.remoting.Channel@4df50645:JNLP4-connect connection from camac1.ads.autodesk.com/10.146.47.76:49613 at hudson.FilePath.act(FilePath.java:993) at hudson.FilePath.act(FilePath.java:975) at hudson.FilePath.deleteRecursive(FilePath.java:1177) at org.jenkinsci.plugins.credentialsbinding.impl.UnbindableDir$UnbinderImpl.unbind(UnbindableDir.java:84) at org.jenkinsci.plugins.cr
