[JIRA] (JENKINS-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Jon Whitcraft edited a comment on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException For now as a workaround, i've recompiled workflow-durable-task-plugin with [this line|https://github.com/jenkinsci/workflow-durable-task-step-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/steps/durable_task/DurableTaskStep.java#L327] commented out. IMO the logger a few lines up should produce an error instead of fine, and no not taint the job console like it is.I'd be willing to issue a PR to make this change, if [~jglick] agrees. 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Jon Whitcraft commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException For now as a workaround, i've recompiled workflow-durable-task-plugin with this line commented out. IMO the logger a few lines up should produce an error instead of fine, and no taint the job console like it is. I'd be willing to issue a PR to make this change, if Jesse Glick agrees. 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Jon Whitcraft updated an issue Jenkins / JENKINS-42048 Cannot Connect, PID NumberFormatException Change By: Jon Whitcraft Attachment: Screenshot 2017-03-28 17.05.18.png 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Jon Whitcraft commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException Sascha Vujevic Unfortunately there is no way to do that. I pinged Carlos Sanchez about this a few weeks ago and he added the component label but I have not heard anything else. It would be nice to get this fixed. it's really annoying when trying to debug issues. 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Sascha Vujevic commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException Could this logoutput be avoided by setting a loglevel in Jenkins ? The logfile looks not pretty and it's not easy to filter the relevant logoutput. Thank you for your support. 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Martin Sander commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException This also occurs for me when NOT running on kubernetes. 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Carlos Sanchez updated an issue Jenkins / JENKINS-42048 Cannot Connect, PID NumberFormatException Change By: Carlos Sanchez Component/s: kubernetes-plugin 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Jesse Redl commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException Thanks for the clarification, and yes you're correct about the errors being part of 2.8 as per the addition of the above logger. Mar 04, 2017 4:52:27 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep could not check /home/jenkins/workspace/ogies_AA_sre_datadog-events-YUQOU4YVOIDND57J35UZCATDN3QRXKHXSLMS4JYIUCSNEI6IDZGQ java.lang.NumberFormatException: For input string: "" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Integer.parseInt(Integer.java:592) at java.lang.Integer.parseInt(Integer.java:615) at org.jenkinsci.plugins.durabletask.BourneShellScript$ShellController.pid(BourneShellScript.java:183) Caused: java.io.IOException: corrupted content in /home/jenkins/workspace/ogies_AA_sre_datadog-events-YUQOU4YVOIDND57J35UZCATDN3QRXKHXSLMS4JYIUCSNEI6IDZGQ@tmp/durable-35571e92/pid at org.jenkinsci.plugins.durabletask.BourneShellScript$ShellController.pid(BourneShellScript.java:185) at org.jenkinsci.plugins.durabletask.BourneShellScript$ShellController.exitStatus(BourneShellScript.java:197) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution$3.call(DurableTaskStep.java:314) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution$3.call(DurableTaskStep.java:306) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution$4.call(DurableTaskStep.java:359) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Jesse Glick commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException Again the bug probably exists in all versions, it is only printed to the build log as of 2.9. You can add a FINE logger to org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep to verify. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Jesse Redl commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException It looks like the comments have already covered this bug, but when I upgrade to 2.9 I see these same exceptions in our logs. I have downgraded the plugin to version 2.8 and everything is fine. [pylint_test] Cannot contact kubernetes-2035b9ceb44d46db9a42cd8dbc1fa0b7-27af70ee4f39c: java.io.IOException: corrupted content in /home/jenkins/workspace/ogies_AA_sre_datadog-events-YUQOU4YVOIDND57J35UZCATDN3QRXKHXSLMS4JYIUCSNEI6IDZGQ@tmp/durable-05858b77/pid: java.lang.NumberFormatException: For input string: "" Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Jesse Glick commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException It looks like the Kubernetes plugin launcher can't handle any errors in the shell scripts Maybe my warning was right? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title
Juha Tiensyrjä commented on JENKINS-42048
Re: Cannot Connect, PID NumberFormatException
private static String[] getCommands(Launcher.ProcStarter starter) {
List allCommands = new ArrayList();
boolean first = true;
String previous = "";
String previousPrevious = "";
for (String cmd : starter.cmds()) {
if (first && "nohup".equals(cmd)) {
first = false;
continue;
}
if ("sh".equals(previousPrevious) && "-c".equals(previous)) {
cmd = String.format("\"%s\"", cmd);
}
previousPrevious = previous;
previous = cmd;
//I shouldn't been doing that, but clearly the script that is passed to us is wrong?
allCommands.add(cmd.replaceAll("\\$\\$", "\\$"));
}
return allCommands.toArray(new String[allCommands.size()]);
}
That should take care of adding the quotes around the shell command argument, which kind of works. I start to get this error instead:
Executing shell script inside container [debian] of pod [test-f669ba016c06421092b43fbd8b23e3d1-f2d539661013]
Executing command: ps -o pid=
# cd "/home/jenkins/workspace/Playground/test-JENKINS-42048"
ps -o pid=
exit
# # command terminated with non-zero exit code: Error executing in Docker Container: 1Executing shell script inside container [debian] of pod [test-f669ba016c06421092b43fbd8b23e3d1-f2d539661013]
Executing command: ps -o pid= 6
[Pipeline] }
[Pipeline] // container
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // podTemplate
[Pipeline] End of Pipeline
ERROR: script returned exit code -1
Finished: FAILURE
It looks like the Kubernetes plugin launcher can't handle any errors in the shell scripts and instead of returning true/false on the aliveness probe in https://github.com/jenkinsci/durable-task-plugin/blob/e174ce7f11e31da0a29c6d3af8023de48c269654/src/main/java/org/jenkinsci/plugins/durabletask/ProcessLiveness.java#L87 it drops dead. Any good ideas, anyone?
Add Comment
[JIRA] (JENKINS-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Jesse Glick commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException It should not be enclosed in quotes. It is a single argument to sh -c. Maybe the Kubernetes plugin has a buggy Launcher? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Juha Tiensyrjä commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException Great - can it be fixed so that the `cmd` is enclosed in quotes? That should make this problem disappear as then the `echo $$` command should work just fine. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Jesse Glick commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException Yes that is where the script is created which stores its own PID. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Juha Tiensyrjä commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException I tried to do an 'echo $$' in different ways within a container running in Kubernetes: $ sh -c "echo $$" 4118 $ sh -c echo $$ $ sh -c 'echo $$' 4187 So it looks like the shell command which is responsible for creating the PID file doesn't work correctly. Please correct me if I'm wrong, but it looks like this happens in https://github.com/jenkinsci/durable-task-plugin/blob/master/src/main/java/org/jenkinsci/plugins/durabletask/BourneShellScript.java#L119 ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Jesse Glick commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException BTW workflow-durable-task-step 2.9 does add this log message but it is just exposing a problem that was already there, and simply being suppressed unless you were running a sufficiently fine logger. The problem is that this code is seeing a file which is supposed to contain a number once created, whereas it is being created as empty for some reason. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title
Michael Andrews edited a comment on JENKINS-42048
Re: Cannot Connect, PID NumberFormatException
We just upgraded the Kubernetes Plugin to 0.11 and are now seeing this as well. Seems to happen on our shell steps (but not all the shell steps).Here is the pipeline code:{code} query = '\'Reservations[].Instances[].ImageId\''imagesInUse = sh( returnStdout: true, script: """\ aws ec2 describe-instances \ --region ${region} \ --query ${query} \ --output text """.stripIndent() ).trim().split().toUnique()echo "Images in-use:\n${imagesInUse}"{code}...and here is the logging:{code}// Some comments here+ aws ec2 describe-instances --region us-east-1 --query Reservations[].Instances[].ImageId --output textCannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba:
[JIRA] (JENKINS-42048) Cannot Connect, PID NumberFormatException
Title: Message Title
Michael Andrews edited a comment on JENKINS-42048
Re: Cannot Connect, PID NumberFormatException
We just upgraded the Kubernetes Plugin to 0.11 and are now seeing this as well. Seems to happen on our shell steps (but not all the shell steps).Here is the pipeline code:{code :groovy } query = '\'Reservations[].Instances[].ImageId\''imagesInUse = sh( returnStdout: true, script: """\ aws ec2 describe-instances \ --region ${region} \ --query ${query} \ --output text """.stripIndent() ).trim().split().toUnique()echo "Images in-use:\n${imagesInUse}"{code}...and here is the logging:{code}// Some comments here+ aws ec2 describe-instances --region us-east-1 --query Reservations[].Instances[].ImageId --output textCannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba:
[JIRA] (JENKINS-42048) Cannot Connect, PID NumberFormatException
Title: Message Title
Michael Andrews commented on JENKINS-42048
Re: Cannot Connect, PID NumberFormatException
We just upgraded the Kubernetes Plugin to 0.11 and are now seeing this as well. Seems to happened on shell steps. Here is the pipeline code:
Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
query = '\'Reservations[].Instances[].ImageId\''
imagesInUse =
sh(
returnStdout: true,
script: """\
aws ec2 describe-instances \
--region ${region} \
--query ${query} \
--output text
""".stripIndent()
).trim().split().toUnique()
echo "Images in-use:\n${imagesInUse}"
...and here is the logging:
// Some comments here
+ aws ec2 describe-instances --region us-east-1 --query Reservations[].Instances[].ImageId --output text
Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""
Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""
Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""
Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""
Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""
Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""
Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba:
[JIRA] (JENKINS-42048) Cannot Connect, PID NumberFormatException
Title: Message Title
Michael Andrews edited a comment on JENKINS-42048
Re: Cannot Connect, PID NumberFormatException
We just upgraded the Kubernetes Plugin to 0.11 and are now seeing this as well. Seems to happened happen on our shell steps (but not all the shell steps) . Here is the pipeline code: {code:groovy} query = '\'Reservations[].Instances[].ImageId\''imagesInUse = sh( returnStdout: true, script: """\ aws ec2 describe-instances \ --region ${region} \ --query ${query} \ --output text """.stripIndent() ).trim().split().toUnique()echo "Images in-use:\n${imagesInUse}"{code}...and here is the logging:{code}// Some comments here+ aws ec2 describe-instances --region us-east-1 --query Reservations[].Instances[].ImageId --output textCannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact kubernetes-d132fbe56cdf44b589aa03203db4ae55-f2bde129ba: java.io.IOException: corrupted content in /home/jenkins/workspace/ops-maintenance/ops-maintenance-scheduled/clean-up-amis/cleanup-baseline-amis@tmp/durable-fe439038/pid: java.lang.NumberFormatException: For input string: ""Cannot contact
[JIRA] (JENKINS-42048) Cannot Connect, PID NumberFormatException
Title: Message Title
Juha Tiensyrjä commented on JENKINS-42048
Re: Cannot Connect, PID NumberFormatException
I tried that, the problem seems to be the same:
[Pipeline] node
Running on test-55f1b2f811564473b115b8af4962a8ad-1b98a80d910eec in /var/tmp/workspace/Playground/test-JENKINS-42048
[Pipeline] {
[Pipeline] sh
[test-JENKINS-42048] Running shell script
+ echo Foo
Foo
+ sleep 10
[Pipeline] container
[Pipeline] {
[Pipeline] sh
[test-JENKINS-42048] Running shell script
Executing shell script inside container [jnlp] of pod [test-55f1b2f811564473b115b8af4962a8ad-1b98a80d910eec]
Executing command: sh -c echo $$ > '/var/tmp/workspace/Playground/test-JENKINS-42048@tmp/durable-b2162d32/pid'; jsc=durable-51e972f92a0e472b7953c41703e464ca; JENKINS_SERVER_COOKIE=$jsc '/var/tmp/workspace/Playground/test-JENKINS-42048@tmp/durable-b2162d32/script.sh' > '/var/tmp/workspace/Playground/test-JENKINS-42048@tmp/durable-b2162d32/jenkins-log.txt' 2>&1; echo $? > '/var/tmp/workspace/Playground/test-JENKINS-42048@tmp/durable-b2162d32/jenkins-result.txt'
$ cd "/var/tmp/workspace/Playground/test-JENKINS-42048"
sh -c echo $$ > '/var/tmp/workspace/Playground/test-JENKINS-42048@tmp/durable-b2162d32/pid'; jsc=durable-51e972f92a0e472b7953c41703e464ca; JENKINS_SERVER_COOKIE=$jsc '/var/tmp/workspace/Playground/test-JENKINS-42048@tmp/durable-b2162d32/script.sh' > '/var/tmp/workspace/Playground/test-JENKINS-42048@tmp/durable-b2162d32/jenkins-log.txt' 2>&1; echo $? > '/var/tmp/workspace/Playground/test-JENKINS-42048@tmp/durable-b2162d32/jenkins-result.txt'
exit
$ + echo Bar
Bar
+ sleep 10
Cannot contact test-55f1b2f811564473b115b8af4962a8ad-1b98a80d910eec: java.io.IOException: corrupted content in /var/tmp/workspace/Playground/test-JENKINS-42048@tmp/durable-b2162d32/pid: java.lang.NumberFormatException: For input string: ""
...
The container and the directory is the same, only difference is that first I call it directly from within a node block, then I call it from within a container block.
Add Comment
[JIRA] (JENKINS-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Ioannis Canellos commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException Can you set the `workingDir` on the jnlp container and tell me if that makes any difference? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Juha Tiensyrjä commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException I could probably find some time for debugging this week. Just let me know what to do. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Jesse Glick assigned an issue to Unassigned Unless there is some way to reproduce without Kubernetes, or someone using Kubernetes is willing to debug why an empty PID file is being written, I have nothing to go on. Jenkins / JENKINS-42048 Cannot Connect, PID NumberFormatException Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Lars Lawoko edited a comment on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException [~iocanel] Will do, i believe [~jglick] is part of that plugin team?Also if you are in the kubernetes team and have time, could you have a quick look at JENKINS- 42048 40647 , I can confirm that it is still happening with the plugins updated to latest. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Lars Lawoko commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException Ioannis Canellos Will do, i believe Jesse Glick is part of that plugin team? Also if you are in the kubernetes team and have time, could you have a quick look at JENKINS-42048 , I can confirm that it is still happening with the plugins updated to latest. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Lars Lawoko assigned an issue to Jesse Glick Jenkins / JENKINS-42048 Cannot Connect, PID NumberFormatException Change By: Lars Lawoko Assignee: Ioannis Canellos Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Ioannis Canellos commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException Awesome, that's really helpfull! Unfortunately, I can only help regarding the kubernetes-plugin, can you reassign the issue to someone involved with `Pipeline Nodes and Processes Plugin`? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Lars Lawoko edited a comment on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException [~daichirata] Thanks, just tried this and can confirm that Pipeline Nodes and Processes Plugin 2.9 is the issue [~iocanel] He narrowed it down to this plugin / version Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Lars Lawoko commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException Daichi Hirata Thanks, just tried this and can confirm that Pipeline Nodes and Processes Plugin 2.9 is the issue Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Lars Lawoko updated an issue Jenkins / JENKINS-42048 Cannot Connect, PID NumberFormatException Change By: Lars Lawoko Component/s: workflow-durable-task-step-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Daichi Hirata commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException The same kind of problem has occurred in my Jenkins running on GKE. This problem occurred by upgrading Pipeline Nodes and Processes Plugin from 2.8 to 2.9. I am confirming that this problem temporarily resolves by downgrading that plugin from 2.9 to 2.8. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title
Lars Lawoko edited a comment on JENKINS-42048
Re: Cannot Connect, PID NumberFormatException
For more context we are running on the Google container engine (hosted k8), The weird thing is that it seems to be working right, i.e the pipeline builds, even with the constant exception.The exception starts once the gradle shell is run:{code}[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Build & run unit tests)[Pipeline] withEnv[Pipeline] {[Pipeline] sh00:01:05.567 [Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A] Running shell script00:01:05.572 Executing shell script inside container [gcloud-jdk7] of pod [kubernetes-9f544f8d984342c8bfa152fd3134608b-d1fdf7ba230b9]00:01:05.653 Executing command: sh -c echo $$ > '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/pid'; jsc=durable-ca85172bfb8670e4c44f30557e14af18; JENKINS_SERVER_COOKIE=$jsc '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/script.sh' > '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/jenkins-log.txt' 2>&1; echo $? > '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/jenkins-result.txt' 00:01:05.694 # cd /home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A00:01:05.694 sh -c echo $$ > '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/pid'; jsc=durable-ca85172bfb8670e4c44f30557e14af18; JENKINS_SERVER_COOKIE=$jsc '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/script.sh' > '/home/jenkins/workspace/Robusta_robusta_develop-6E# PNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/jenkins-log.txt' 2>&1; echo $? > '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/jenkins-result.txt' 00:01:05.694 exit00:01:05.909 + ./gradlew --stacktrace --parallel buildUnitTest00:01:05.909 Downloading https://services.gradle.org/distributions/gradle-3.3-all.zip00:01:05.995 Cannot contact kubernetes-9f544f8d984342c8bfa152fd3134608b-d1fdf7ba230b9: java.io.IOException: corrupted content in /home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/pid: java.lang.NumberFormatException: For input string: ""{code}Our jenkinsfile is pretty massive, but here is the core (has been edited):{code} podTemplate(label: 'JavaPod', containers: [containerTemplate(name: 'gcloud-jdk7',image: 'gcr.io/pc-infrastructure/robusta-jenkins-gcloud-jdk7',ttyEnabled: true,args: 'cat',command: '/bin/sh -c',alwaysPullImage: true,workingDir: '/home/jenkins',resourceRequestCpu: '2',resourceRequestMemory: '8Gi',resourceLimitCpu: '5',resourceLimitMemory: '9Gi',),containerTemplate(name: 'jnlp',image: 'jenkinsci/jnlp-slave:alpine',args: '${computer.jnlpmac} ${computer.name}',resourceRequestCpu: '100m',resourceRequestMemory: '500Mi',resourceLimitCpu: '500m',resourceLimitMemory: '1Gi',)]) { node('JavaPod') {container('gcloud-jdk7') {timeout(30) {
[JIRA] (JENKINS-42048) Cannot Connect, PID NumberFormatException
Title: Message Title
Lars Lawoko commented on JENKINS-42048
Re: Cannot Connect, PID NumberFormatException
For more context we are running on the Google container engine (hosted k8), The weird thing is that it seems to be working right, i.e the pipeline builds, even with the constant exception. The exception starts once the gradle shell is run:
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Build & run unit tests)
[Pipeline] withEnv
[Pipeline] {
[Pipeline] sh
00:01:05.567 [Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A] Running shell script
00:01:05.572 Executing shell script inside container [gcloud-jdk7] of pod [kubernetes-9f544f8d984342c8bfa152fd3134608b-d1fdf7ba230b9]
00:01:05.653 Executing command: sh -c echo $$ > '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/pid'; jsc=durable-ca85172bfb8670e4c44f30557e14af18; JENKINS_SERVER_COOKIE=$jsc '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/script.sh' > '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/jenkins-log.txt' 2>&1; echo $? > '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/jenkins-result.txt'
00:01:05.694 # cd /home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A
00:01:05.694 sh -c echo $$ > '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/pid'; jsc=durable-ca85172bfb8670e4c44f30557e14af18; JENKINS_SERVER_COOKIE=$jsc '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/script.sh' > '/home/jenkins/workspace/Robusta_robusta_develop-6E# PNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/jenkins-log.txt' 2>&1; echo $? > '/home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/jenkins-result.txt'
00:01:05.694 exit
00:01:05.909 + ./gradlew --stacktrace --parallel buildUnitTest
00:01:05.909 Downloading https://services.gradle.org/distributions/gradle-3.3-all.zip
00:01:05.995 Cannot contact kubernetes-9f544f8d984342c8bfa152fd3134608b-d1fdf7ba230b9: java.io.IOException: corrupted content in /home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-aa4bf913/pid: java.lang.NumberFormatException: For input string: ""
Our jenkinsfile is pretty massive, but here is the core (has been edited):
node('JavaPod') {
container('gcloud-jdk7') {
timeout(30) { //assume something is wrong if it takes an half an hour
stage('checkout source') {
checkout scm
}
switch (env.BRANCH_NAME) {
case 'develop':
buildUnitTest()
[JIRA] (JENKINS-42048) Cannot Connect, PID NumberFormatException
Title: Message Title
J Knurek commented on JENKINS-42048
Re: Cannot Connect, PID NumberFormatException
I'm experiencing the same recurring error message the slave is using the golang docker image, and the pipeline is setup like this:
podTemplate(label: 'jenkpod', containers: [
containerTemplate(name: 'golang', image: 'golang:1.8', ttyEnabled: true, command: 'cat')
]) {
node ('jenkpod') { container('golang') {
stage('Pre-Build') {
checkout scm
sh 'make get'
}
} }
}
the events for the slave pod:
Events:
FirstSeen LastSeen Count FromSubObjectPath Type Reason Message
- - - -- ---
13m 13m 1 {default-scheduler } Normal Scheduled Successfully assigned kubernetes-f1e4a27973a941c2af08bebbc74cc080-10bf4e8527c4 to gke-jenkins
13m 13m 1 {kubelet gke-jenkins} spec.containers{golang} Normal Pulled Container image "golang:1.8" already present on machine
13m 13m 1 {kubelet gke-jenkins} spec.containers{golang} Normal Created Created container with docker id 97e4b71e323e; Security:[seccomp=unconfined]
13m 13m 1 {kubelet gke-jenkins} spec.containers{golang} Normal Started Started container with docker id 97e4b71e323e
13m 13m 1 {kubelet gke-jenkins} spec.containers{jnlp} Normal Pulled Container image "jenkinsci/jnlp-slave:alpine" already present on machine
13m 13m 1 {kubelet gke-jenkins} spec.containers{jnlp} Normal Created Created container with docker id 628623d03379; Security:[seccomp=unconfined]
13m 13m 1 {kubelet gke-jenkins} spec.containers{jnlp} Normal Started Started container with docker id 628623d03379
Add Comment
[JIRA] (JENKINS-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Ioannis Canellos commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException It seems that you pod is created but for some reason can't read the pid, which is something I've never seen before. Can you please tell us how your pipeline looks like and maybe get us the output of `kubectl describe` for the kubernetes-ef39fe82c8a541be84bd780e4d7c1ddb-ce4d47fc96bfc pod? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Lars Lawoko created an issue Jenkins / JENKINS-42048 Cannot Connect, PID NumberFormatException Issue Type: Bug Assignee: Ioannis Canellos Components: kubernetes-pipeline-plugin, workflow-api-plugin Created: 2017/Feb/15 5:03 AM Environment: Jenkins 2.32.2 Priority: Minor Reporter: Lars Lawoko I tried to narrow this bug down, but there isn't much information. We just upgraded to all newest plugins, but unfortunately we upgraded a lot at once, so no idea which one. This is spamming out logs every few seconds: 00:19:42.695 Cannot contact kubernetes-ef39fe82c8a541be84bd780e4d7c1ddb-ce4d47fc96bfc: java.io.IOException: corrupted content in /home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-96fa79b7/pid: java.lang.NumberFormatException: For input string: "" 00:19:57.758 Cannot contact kubernetes-ef39fe82c8a541be84bd780e4d7c1ddb-ce4d47fc96bfc: java.io.IOException: corrupted content in /home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-96fa79b7/pid: java.lang.NumberFormatException: For input string: "" 00:20:12.769 Cannot contact kubernetes-ef39fe82c8a541be84bd780e4d7c1ddb-ce4d47fc96bfc: java.io.IOException: corrupted content in /home/jenkins/workspace/Robusta_robusta_develop-6EPNQBJK5BYEXOJV6L45MMZZGUIP7WO4Y6EGRUYNFFMRC7B2GL3A@tmp/durable-96fa79b7/pid: java.lang.NumberFormatException: For input string: ""
