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

hudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel@6b5d6424:JNLP4-connect connection from IP"n.n.n.n/n.n.nn":49060": failed. The channel is closing down or has closed down

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: kubernetes-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.222.4 and kubernetes Plugin - 1.24.1
    • Similar Issues:

      Description

      Occasionally we are getting into this JNLP4 connection issue.

      09:37:45 2021-05-21 09:37:42 ** INFO: Generated python modules listing.
      10:57:18 Cannot contact oscs-oci-scan-hfht2-gkp6f: hudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel@6b5d6424:JNLP4-connect connection from n.n.n.n/n.n.n.n:49060": Remote call on JNLP4-connect connection from n.n.n.n/n.n.n.n:49060 failed. The channel is closing down or has closed down
      11:07:48 Created Pod: oscs-oci-scan-728nr-pl5hv in namespace jenkins
      11:07:48 Created Pod: oscs-oci-scan-728nr-jqg9p in namespace jenkins
      ..
      ..
      ..
      07:36:08 Created Pod: oscs-oci-scan-728nr-lvl4r in namespace jenkins
      07:44:08 Created Pod: oscs-oci-scan-728nr-zb039 in namespace jenkins
      07:45:59 Cancelling nested steps due to timeout
      07:45:59 Could not connect to oscs-oci-scan-hfht2-gkp6f to send interrupt signal to process

        Attachments

          Activity

          Hide
          akmjenkins ASHOK MOHANTY added a comment - - edited

          Seems, It tries to communicate and/or trying to resume into another pod. And then finally it failed after 20+Hrs.
          i) Can we do something to avoid this connection issue. !! OR
          ii) Once it struck this JNLP4 connection issue, it should failed the pipeline immediately. It shouldn't run/try for 20+ Hrs.??

          Show
          akmjenkins ASHOK MOHANTY added a comment - - edited Seems, It tries to communicate and/or trying to resume into another pod. And then finally it failed after 20+Hrs. i) Can we do something to avoid this connection issue. !! OR ii) Once it struck this JNLP4 connection issue, it should failed the pipeline immediately. It shouldn't run/try for 20+ Hrs.??
          Hide
          akmjenkins ASHOK MOHANTY added a comment -

          May be related to - JENKINS-59705 , JENKINS-52922
          Will this be any help : "-Dhudson.slaves.ChannelPinger.pingInterval=2" !?

          Show
          akmjenkins ASHOK MOHANTY added a comment - May be related to - JENKINS-59705 , JENKINS-52922 Will this be any help : "-Dhudson.slaves.ChannelPinger.pingInterval=2" !?
          Hide
          akmjenkins ASHOK MOHANTY added a comment -

          Any update on this one !!? Any additional information required here..

          And/OR can you please point me to some alternate/workaround solution..!!

          Any idea if the upgrading Kub-plugin will help (reduce the connection issue) !!

          Show
          akmjenkins ASHOK MOHANTY added a comment - Any update on this one !!? Any additional information required here.. And/OR can you please point me to some alternate/workaround solution..!! Any idea if the upgrading Kub-plugin will help (reduce the connection issue) !!

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            akmjenkins ASHOK MOHANTY
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: