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

Jenkins master throwing java.io.IOException when running pipeline in swarm client

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • swarm-plugin
    • Master:
      Jenkins Version : 2.32.2
      Running on Windows Server 2012 R2
      Pipeline: Nodes and Processes 2.10 (works fine in 2.8)

      Client:
      Swarm Client 3.3 on AIX 7.1 / JDK 8

      Im trying to run a pipeline job in an agent which is using swarm client. The job runs fine but im getting a lot of error messages in the log like below:

      Cannot contact tst_db2: java.io.IOException: Remote call on Channel to /XX.XX.XX.XXX failed
      

      (actual IP address replaced with XX)

      In my observation the master is throwing this errors while waiting for the script that is running in the client. Again, the pipeline job run perfectly except that im getting this error on the pipeline logs.

      Below is my pipeline script:

      pipeline {
          agent none
          stages {
              stage('Recreate DB') {
                  agent { label 'tst_db2'}
                  steps {
                      checkout([$class: 'SubversionSCM', 
                        additionalCredentials: [], 
                        excludedCommitMessages: '', 
                        excludedRegions: '', 
                        excludedRevprop: '', 
                        excludedUsers: '', 
                        filterChangelog: false, 
                        ignoreDirPropChanges: false, 
                        includedRegions: '', 
                        locations: [[credentialsId: 'a84f7197-929a-437e-9aac-ca09fcd4c63a', 
                                     depthOption: 'infinity', 
                                     ignoreExternalsOption: true, 
                                     local: '', 
                                     remote: 'svn://XXXXX/XXX/tags/CR/Rebuild_VCRDWD01']], 
                        workspaceUpdater: [$class: 'CheckoutUpdater']])  
      
                       sh 'Rebuild_VCRDWD01/recreate_db.sh'
                  }
              }       
          }
      }   
      

      Is there anyway we can get rid of this errors?

          [JENKINS-42428] Jenkins master throwing java.io.IOException when running pipeline in swarm client

          Marlon Cenita created issue -

          Joe Fowler added a comment - - edited

          Interesting, I am getting a very similar error on my pipeline jobs:

          Cannot contact SERVER_ABC: java.io.IOException: Remote call on SERVER_ABC failed.

          I have 2 different Jenkins Masters failing to 2 different agents.

          As noted, the builds execute fine. It is as though some polling is occurring

          Joe Fowler added a comment - - edited Interesting, I am getting a very similar error on my pipeline jobs: Cannot contact SERVER_ABC: java.io.IOException: Remote call on SERVER_ABC failed. I have 2 different Jenkins Masters failing to 2 different agents. As noted, the builds execute fine. It is as though some polling is occurring

          Brad Donovan added a comment -

          We started seeing the same issue a week or so ago. It doesn't cause the builds to fail but it certainly makes the console message noisy. Also add that it only happens on our linux slave, windows does not throw the same error.

          This got me checking the plugins and i noticed this change was made to the "ssh slaves plugin" : https://github.com/jenkinsci/ssh-slaves-plugin/pull/41

          We tried reverting to the previous version of the plugin but it didn't resolve the issue.

          Brad Donovan added a comment - We started seeing the same issue a week or so ago. It doesn't cause the builds to fail but it certainly makes the console message noisy. Also add that it only happens on our linux slave, windows does not throw the same error. This got me checking the plugins and i noticed this change was made to the "ssh slaves plugin" : https://github.com/jenkinsci/ssh-slaves-plugin/pull/41 We tried reverting to the previous version of the plugin but it didn't resolve the issue.

          Joe Fowler added a comment -

          Joe Fowler added a comment - This is probably the same as  https://issues.jenkins-ci.org/browse/JENKINS-42405

          Joe Fowler added a comment -

          This is actually quite ugly when trying to sort through the logs.   Is there a way to filter and ignore these messages?

          Joe Fowler added a comment - This is actually quite ugly when trying to sort through the logs.   Is there a way to filter and ignore these messages?

          Brent Laster added a comment -

          I'm seeing the same thing after recent plugin upgrades.  Even seems to happen in the very simplest test case where you have a Linux slave on the same system as a master (no swarm involved).

          Brent Laster added a comment - I'm seeing the same thing after recent plugin upgrades.  Even seems to happen in the very simplest test case where you have a Linux slave on the same system as a master (no swarm involved).

          Downgrade of plugin "Pipeline: Nodes and Processes" from v.2.9 to v.2.8 has fixed this problem (at least in my environment)

          Ivan Prokhorov added a comment - Downgrade of plugin "Pipeline: Nodes and Processes" from v.2.9 to v.2.8 has fixed this problem (at least in my environment)

          Brent Laster added a comment -

          Thanks ivanpro, I was able to get rid of the problem as well by backleveling my 2.10 version of Pipeline: Nodes and Processes to 2.8.  Unfortunately there are a number of other plugins I have installed dependent on 2.10 that I'm not keen on backleveling so guess I'm going to have to live with this as an annoyance until there's an official fix.  Hopefully that will be soon.

          Brent Laster added a comment - Thanks ivanpro , I was able to get rid of the problem as well by backleveling my 2.10 version of Pipeline: Nodes and Processes to 2.8.  Unfortunately there are a number of other plugins I have installed dependent on 2.10 that I'm not keen on backleveling so guess I'm going to have to live with this as an annoyance until there's an official fix.  Hopefully that will be soon.

          It's polluting our logs, too. Please fix soon.

          Mathias Rühle added a comment - It's polluting our logs, too. Please fix soon.
          Oleg Nenashev made changes -
          Labels Original: jenkins pipeline swarm New: jenkins pipeline regression swarm

            Unassigned Unassigned
            mcenita Marlon Cenita
            Votes:
            15 Vote for this issue
            Watchers:
            26 Start watching this issue

              Created:
              Updated: