Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-42048

Cannot Connect, PID NumberFormatException

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      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: ""
      

      Add information from comments:

      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.

      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.

      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.

        Attachments

          Issue Links

            Activity

            Hide
            jredl Jesse Redl added a comment -

            This is not be a solution for everyone, however this log noise seems to only happen when you have a pod template with more than one container running. I was working around another issue (https://issues.jenkins-ci.org/browse/JENKINS-40825) and by only having one container running (named jnlp) the log noise was also gone.

             

            Show
            jredl Jesse Redl added a comment - This is not be a solution for everyone, however this log noise seems to only happen when you have a pod template with more than one container running. I was working around another issue ( https://issues.jenkins-ci.org/browse/JENKINS-40825 ) and by only having one container running (named jnlp) the log noise was also gone.  
            Hide
            jglick Jesse Glick added a comment -

            workflow-durable-task-step PR 37 will reduce noise without addressing the underlying bug, probably somewhere in the Kubernetes plugin.

            Show
            jglick Jesse Glick added a comment - workflow-durable-task-step PR 37 will reduce noise without addressing the underlying bug, probably somewhere in the Kubernetes plugin.
            Hide
            killdash9 Michael Andrews added a comment -

            Jesse Redl Definitely not a solution for us. But good to know. Hopefully this will help Carlos Sanchez or Ioannis Canellos implement a fix. In the mean time, we did pull the workflow-durable-task-step PR 37 and merged it into a local build. It did lessen the number of time the message is logged. Hoping this issue is addressed soon.

            Show
            killdash9 Michael Andrews added a comment - Jesse Redl Definitely not a solution for us. But good to know. Hopefully this will help Carlos Sanchez or Ioannis Canellos implement a fix. In the mean time, we did pull the workflow-durable-task-step PR 37 and merged it into a local build. It did lessen the number of time the message is logged. Hoping this issue is addressed soon.
            Hide
            jglick Jesse Glick added a comment -

            we did pull the workflow-durable-task-step PR 37 and merged it into a local build

            Just update to 2.11.

            Show
            jglick Jesse Glick added a comment - we did pull the workflow-durable-task-step PR 37 and merged it into a local build Just update to 2.11.
            Show
            csanchez Carlos Sanchez added a comment - PR at  https://github.com/jenkinsci/kubernetes-plugin/pull/157  

              People

              • Assignee:
                csanchez Carlos Sanchez
                Reporter:
                larslawoko Lars Lawoko
              • Votes:
                19 Vote for this issue
                Watchers:
                36 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: