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

Failed to execute command Pipe.Flush

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Labels:
      None
    • Environment:
      Running Jenkins in Docker on version 2.138.2.

      Running the Jenkins Slave Docker container using remoting version 3.27
    • Similar Issues:
    • Released As:
      workflow-api 2.33

      Description

      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
      

        Attachments

          Issue Links

            Activity

            Hide
            jglick Jesse Glick added a comment -

            the job which always gave the error message was not able to show logging for the steps it executed

            Unlike the stack trace reported in the original description, which is merely log noise as far as I know, failure to actually show log output would be a real bug. What step is involved? If sh, are you running an up-to-date durable-task & workflow-durable-task-step?

            Show
            jglick Jesse Glick added a comment - the job which always gave the error message was not able to show logging for the steps it executed Unlike the stack trace reported in the original description, which is merely log noise as far as I know, failure to actually show log output would be a real bug. What step is involved? If sh , are you running an up-to-date durable-task & workflow-durable-task-step ?
            Hide
            jglick Jesse Glick added a comment -

            Laurens Leeuwis if you are able to reproduce the Failed to execute command Pipe.Flush error, please try installing this build via Plugin Manager » Advanced. This plugin patch ought to try to flush a collected stream before its delegate is finalized. I also filed a separate fix for Remoting which would avoid the error in any event, but that could take much longer to appear in core builds.

            As an aside, my comment of 2018-11-13 can be disregarded: I found (and offered a fix for) a buglet in Remoting that it sometimes printed a message suggesting that it was about to display an explanatory stack trace, even if there was no further stack trace to display.

            Show
            jglick Jesse Glick added a comment - Laurens Leeuwis if you are able to reproduce the Failed to execute command Pipe.Flush error, please try installing this build via Plugin Manager » Advanced . This plugin patch ought to try to flush a collected stream before its delegate is finalized. I also filed a separate fix for Remoting which would avoid the error in any event, but that could take much longer to appear in core builds. As an aside, my comment of 2018-11-13 can be disregarded: I found (and offered a fix for) a buglet in Remoting that it sometimes printed a message suggesting that it was about to display an explanatory stack trace, even if there was no further stack trace to display.
            Hide
            l55s Laurens Leeuwis added a comment - - edited

            Jesse Glick Using the patched version of the workflow-api did make the Pipe.Flush(-1) log disappear! Great

            failure to actually show log output would be a real bug. What step is involved? If sh, are you running an up-to-date durable-task & workflow-durable-task-step?

            We still don't see some logging in blue ocean using the patched version of workflow-api (we do see the logging in the 'normal' Jenkins views). We are making extensive use of sh steps. We're using durable-task v1.27 and workflow-durable-task-step v2.26. I think it might not be related to this Pipe.Flush(-1) issue after all. I found that we're running an ancient version of blueocean (v1.0.0-b23). Might be best to ignore this for now.

             

            Show
            l55s Laurens Leeuwis added a comment - - edited Jesse Glick Using the patched version of the workflow-api  did make the Pipe.Flush(-1)  log disappear! Great failure to actually show log output would be a real bug. What step is involved? If  sh , are you running an up-to-date  durable-task  &  workflow-durable-task-step ? We still don't see some logging in blue ocean using the patched version of workflow-api (we do see the logging in the 'normal' Jenkins views). We are making extensive use of sh steps. We're using durable-task v1.27 and workflow-durable-task-step v2.26. I think it might not be related to this Pipe.Flush(-1) issue after all. I found that we're running an ancient version of blueocean (v1.0.0-b23). Might be best to ignore this for now.  
            Hide
            jglick Jesse Glick added a comment -

            Laurens Leeuwis you might be seeing an issue we suspect exists in Blue Ocean: individual step logs truncate output after >10k lines of text. Or it might be some unrelated issue. At any rate, if the log output is present in the classic UI then I doubt flush-related bugs would be the culprit.

            Show
            jglick Jesse Glick added a comment - Laurens Leeuwis you might be seeing an issue we suspect exists in Blue Ocean: individual step logs truncate output after >10k lines of text. Or it might be some unrelated issue. At any rate, if the log output is present in the classic UI then I doubt flush -related bugs would be the culprit.
            Hide
            dnusbaum Devin Nusbaum added a comment -

            This error was fixed in version 2.33 of the Pipeline API plugin.

            Show
            dnusbaum Devin Nusbaum added a comment - This error was fixed in version 2.33 of the Pipeline API plugin.

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: