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

Unexpected exception occurred while performing online-node command

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • core
    • None

      Multiple issues with launching well-known good jobs on slave nodes have been occurring intermittently (<50%.) Downgrading from Jenkins version 2.164.1 to 2.150.3 unfortunately does not appear to resolve the issue. Specifically:

      • Jobs failing due to "ERROR: Unexpected exception occurred while performing online-node command. java.net.SocketTimeoutException: Read timed out"
      • Jobs failing due to "ERROR: (job name) aborted." with no record of any user abort or reason for abort
      • Jobs failing due to "FATAL: command execution failed java.nio.channels.ClosedChannelException"

      This was reproduced over the course of multiple days and randomly started about a week ago. No workaround was found for this issue, and a downgrade was unable to resolve the issue. 

      Notepad documents containing the entirety of each of these errors from our job output have been attached, but if any other logs are needed, please let me know.

      These jobs provide a variety of functions, mostly in the way of running simple batch commands, disconnecting the node, then reconnecting only after a ping response fails for a time, then succeeds. The output provided should provide more information. 

       

          [JENKINS-56767] Unexpected exception occurred while performing online-node command

          Chance Davies created issue -
          Chance Davies made changes -
          Description Original: Multiple issues with launching well-known good jobs on slave nodes have been occurring after updating from Jenkins version 2.150.3 to 2.164.1. Specifically:
           * Jobs failing due to "{color:#de350b}ERROR: Unexpected exception occurred while performing online-node command. java.net.SocketTimeoutException: Read timed out{color}"
           * Jobs failing due to "{color:#de350b}ERROR: (job name) aborted.{color}" with no record of any user abort or reason for abort
           * Jobs failing due to "{color:#de350b}FATAL: command execution failed java.nio.channels.ClosedChannelException{color}"

          This was reproduced over the course of multiple days, and finally ceased only when the Jenkins version was downgraded to our previous version (2.150.3.)

          Notepad documents containing the entirety of each of these errors from our job output have been attached, but if any other logs are needed, please let me know.

          These jobs provide a variety of functions, mostly in the way of running simple batch commands, disconnecting the node, then reconnecting only after a ping response fails for a time, then succeeds. The output provided should provide more information. 

           
          New: Multiple issues with launching well-known good jobs on slave nodes have been occurring after updating from Jenkins version 2.150.3 to 2.164.1. Specifically:
           * Jobs failing due to "{color:#de350b}ERROR: Unexpected exception occurred while performing online-node command. java.net.SocketTimeoutException: Read timed out{color}"
           * Jobs failing due to "{color:#de350b}ERROR: (job name) aborted.{color}" with no record of any user abort or reason for abort
           * Jobs failing due to "{color:#de350b}FATAL: command execution failed java.nio.channels.ClosedChannelException{color}"

          This was reproduced over the course of multiple days, and finally ceased only when the Jenkins version was downgraded to our previous version (2.150.3.) No workaround was found for this issue, and only this downgrade was able to resolve our issues. 

          Notepad documents containing the entirety of each of these errors from our job output have been attached, but if any other logs are needed, please let me know.

          These jobs provide a variety of functions, mostly in the way of running simple batch commands, disconnecting the node, then reconnecting only after a ping response fails for a time, then succeeds. The output provided should provide more information. 

           
          Chance Davies made changes -
          Description Original: Multiple issues with launching well-known good jobs on slave nodes have been occurring after updating from Jenkins version 2.150.3 to 2.164.1. Specifically:
           * Jobs failing due to "{color:#de350b}ERROR: Unexpected exception occurred while performing online-node command. java.net.SocketTimeoutException: Read timed out{color}"
           * Jobs failing due to "{color:#de350b}ERROR: (job name) aborted.{color}" with no record of any user abort or reason for abort
           * Jobs failing due to "{color:#de350b}FATAL: command execution failed java.nio.channels.ClosedChannelException{color}"

          This was reproduced over the course of multiple days, and finally ceased only when the Jenkins version was downgraded to our previous version (2.150.3.) No workaround was found for this issue, and only this downgrade was able to resolve our issues. 

          Notepad documents containing the entirety of each of these errors from our job output have been attached, but if any other logs are needed, please let me know.

          These jobs provide a variety of functions, mostly in the way of running simple batch commands, disconnecting the node, then reconnecting only after a ping response fails for a time, then succeeds. The output provided should provide more information. 

           
          New: Multiple issues with launching well-known good jobs on slave nodes have been occurring. Downgrading from Jenkins version 2.150.3 to 2.164.1. Specifically:
           * Jobs failing due to "{color:#de350b}ERROR: Unexpected exception occurred while performing online-node command. java.net.SocketTimeoutException: Read timed out{color}"
           * Jobs failing due to "{color:#de350b}ERROR: (job name) aborted.{color}" with no record of any user abort or reason for abort
           * Jobs failing due to "{color:#de350b}FATAL: command execution failed java.nio.channels.ClosedChannelException{color}"

          This was reproduced over the course of multiple days, and finally ceased only when the Jenkins version was downgraded to our previous version (2.150.3.) No workaround was found for this issue, and only this downgrade was able to resolve our issues. 

          Notepad documents containing the entirety of each of these errors from our job output have been attached, but if any other logs are needed, please let me know.

          These jobs provide a variety of functions, mostly in the way of running simple batch commands, disconnecting the node, then reconnecting only after a ping response fails for a time, then succeeds. The output provided should provide more information. 

           
          Chance Davies made changes -
          Description Original: Multiple issues with launching well-known good jobs on slave nodes have been occurring. Downgrading from Jenkins version 2.150.3 to 2.164.1. Specifically:
           * Jobs failing due to "{color:#de350b}ERROR: Unexpected exception occurred while performing online-node command. java.net.SocketTimeoutException: Read timed out{color}"
           * Jobs failing due to "{color:#de350b}ERROR: (job name) aborted.{color}" with no record of any user abort or reason for abort
           * Jobs failing due to "{color:#de350b}FATAL: command execution failed java.nio.channels.ClosedChannelException{color}"

          This was reproduced over the course of multiple days, and finally ceased only when the Jenkins version was downgraded to our previous version (2.150.3.) No workaround was found for this issue, and only this downgrade was able to resolve our issues. 

          Notepad documents containing the entirety of each of these errors from our job output have been attached, but if any other logs are needed, please let me know.

          These jobs provide a variety of functions, mostly in the way of running simple batch commands, disconnecting the node, then reconnecting only after a ping response fails for a time, then succeeds. The output provided should provide more information. 

           
          New: Multiple issues with launching well-known good jobs on slave nodes have been occurring. Downgrading from Jenkins version 2.164.1 to 2.150.3 unfortunately does not appear to resolve the issue. Specifically:
           * Jobs failing due to "{color:#de350b}ERROR: Unexpected exception occurred while performing online-node command. java.net.SocketTimeoutException: Read timed out{color}"
           * Jobs failing due to "{color:#de350b}ERROR: (job name) aborted.{color}" with no record of any user abort or reason for abort
           * Jobs failing due to "{color:#de350b}FATAL: command execution failed java.nio.channels.ClosedChannelException{color}"

          This was reproduced over the course of multiple days and randomly started about a week ago. No workaround was found for this issue, and a downgrade was unable to resolve our issues. 

          Notepad documents containing the entirety of each of these errors from our job output have been attached, but if any other logs are needed, please let me know.

          These jobs provide a variety of functions, mostly in the way of running simple batch commands, disconnecting the node, then reconnecting only after a ping response fails for a time, then succeeds. The output provided should provide more information. 

           
          Chance Davies made changes -
          Description Original: Multiple issues with launching well-known good jobs on slave nodes have been occurring. Downgrading from Jenkins version 2.164.1 to 2.150.3 unfortunately does not appear to resolve the issue. Specifically:
           * Jobs failing due to "{color:#de350b}ERROR: Unexpected exception occurred while performing online-node command. java.net.SocketTimeoutException: Read timed out{color}"
           * Jobs failing due to "{color:#de350b}ERROR: (job name) aborted.{color}" with no record of any user abort or reason for abort
           * Jobs failing due to "{color:#de350b}FATAL: command execution failed java.nio.channels.ClosedChannelException{color}"

          This was reproduced over the course of multiple days and randomly started about a week ago. No workaround was found for this issue, and a downgrade was unable to resolve our issues. 

          Notepad documents containing the entirety of each of these errors from our job output have been attached, but if any other logs are needed, please let me know.

          These jobs provide a variety of functions, mostly in the way of running simple batch commands, disconnecting the node, then reconnecting only after a ping response fails for a time, then succeeds. The output provided should provide more information. 

           
          New: Multiple issues with launching well-known good jobs on slave nodes have been occurring intermittently (<50%.) Downgrading from Jenkins version 2.164.1 to 2.150.3 unfortunately does not appear to resolve the issue. Specifically:
           * Jobs failing due to "{color:#de350b}ERROR: Unexpected exception occurred while performing online-node command. java.net.SocketTimeoutException: Read timed out{color}"
           * Jobs failing due to "{color:#de350b}ERROR: (job name) aborted.{color}" with no record of any user abort or reason for abort
           * Jobs failing due to "{color:#de350b}FATAL: command execution failed java.nio.channels.ClosedChannelException{color}"

          This was reproduced over the course of multiple days and randomly started about a week ago. No workaround was found for this issue, and a downgrade was unable to resolve the issue. 

          Notepad documents containing the entirety of each of these errors from our job output have been attached, but if any other logs are needed, please let me know.

          These jobs provide a variety of functions, mostly in the way of running simple batch commands, disconnecting the node, then reconnecting only after a ping response fails for a time, then succeeds. The output provided should provide more information. 

           
          Chance Davies made changes -
          Attachment Original: Unexpected exception occurred while performing online-node command.txt [ 46564 ]
          Chance Davies made changes -
          Attachment Original: Job Randomly Aborted.txt [ 46566 ]
          Chance Davies made changes -
          Attachment Original: java.nio.channels.ClosedChannelException.txt [ 46565 ]

          Chance Davies added a comment -

          Please note: My company has recommended I remove the logs which were originally attached to this bug. I can still provide specifics and logs which do not contain system names or IPs upon request. 

          Chance Davies added a comment - Please note: My company has recommended I remove the logs which were originally attached to this bug. I can still provide specifics and logs which do not contain system names or IPs upon request. 
          Thomas de Grenier de Latour made changes -
          Link New: This issue relates to JENKINS-61103 [ JENKINS-61103 ]

            Unassigned Unassigned
            cdavies Chance Davies
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: