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

Failed to execute command Pipe.Flush

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • None
    • Running Jenkins in Docker on version 2.138.2.

      Running the Jenkins Slave Docker container using remoting version 3.27
    • workflow-api 2.33

      Seeing this in my logs but for the most part everything seems to be working fine. I am sort of unclear on whether my Jenkins master is compatible with this agent version so that may be the problem.

       

      SEVERE: This command is created here
      Nov 10, 2018 3:58:44 PM hudson.remoting.Channel$1 handle
      SEVERE: Failed to execute command Pipe.Flush(-1) (channel Jenkins Agent (i-03788ba5fec517424))
      java.util.concurrent.ExecutionException: Invalid object ID -1 iota=263
      	at hudson.remoting.ExportTable.diagnoseInvalidObjectId(ExportTable.java:478)
      	at hudson.remoting.ExportTable.get(ExportTable.java:397)
      	at hudson.remoting.Channel.getExportedObject(Channel.java:780)
      	at hudson.remoting.ProxyOutputStream$Flush.execute(ProxyOutputStream.java:307)
      	at hudson.remoting.Channel$1.handle(Channel.java:565)
      	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:87)
      Caused by: java.lang.Exception: Object appears to be deallocated at lease before Sat Nov 10 15:38:16 UTC 2018
      	at hudson.remoting.ExportTable.diagnoseInvalidObjectId(ExportTable.java:474)
      	... 5 more
      Nov 10, 2018 3:58:44 PM hudson.remoting.Channel$1 handle
      SEVERE: This command is created here
      

            jglick Jesse Glick
            awiddersheim Andrew Widdersheim
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: