• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • Build Failure Analyzer 1.19.0
      Jenkins ver. 2.73.1
      CentOS Linux release 7.3.1611 (Core)
      OpenJDK Runtime Environment (build 1.8.0_141-b16)

      The "I/O error writing PNG file!" (see attachment) happens on a pilot Jenkins instance with only a single job, which runs few times a day. It's an instance with very low activity.

      The issue happened twice in the recent weeks (Dec 06, 2017 2:14:47 PM and Dec 20, 2017 5:40:02 PM). It is also to notice that no build was running when the issue was detected (in fact, not a single build was executed on 20.12).

      I couldn't find a pattern that points me to any scheduled automated activities from the Jenkins Master itself, except that both happened on a Wednesday...

      This ticket has been raised against the BFA plugin because it happened while creating a png related to it. But since it was not directly trigger by a build that runs the BFA, I can't say whether this could have been triggered by the Master itself in order the serve the plugin.

      Also, it cannot be detected in the Jenkins interface. Besides the Master's log giving me an exception, I can't find any other anomaly.

          [JENKINS-48721] I/O error writing PNG file

          I just noticed that clicking on the Jenkins Global Configuration and immediately interrupting the page load (for instance, by clicking another link) causes a java.nio.channels.ClosedChannelException to occur. (oleg_nenashev, not sure if that's a bug).

          So, I could also think that the I/O operation of the BFA plugin was interrupted by a similar interactive pattern. That would assume though that the graphs are dynamically generated on page request...

          Rafael Rezende added a comment - I just noticed that clicking on the Jenkins Global Configuration and immediately interrupting the page load (for instance, by clicking another link) causes a java.nio.channels.ClosedChannelException to occur. ( oleg_nenashev , not sure if that's a bug). So, I could also think that the I/O operation of the BFA plugin was interrupted by a similar interactive pattern. That would assume though that the graphs are dynamically generated on page request...

          Oleg Nenashev added a comment -

          It is either a bug or infra issue. Generally it means that the HTTPs session has been interrupted IIUC.

          Caused by: java.nio.channels.ClosedChannelException
                  at org.eclipse.jetty.util.IteratingCallback.close(IteratingCallback.java:427)
                  at org.eclipse.jetty.server.HttpConnection.onClose(HttpConnection.java:491)
                  at org.eclipse.jetty.io.ssl.SslConnection.onClose(SslConnection.java:244)
                  at org.eclipse.jetty.io.SelectorManager.connectionClosed(SelectorManager.java:310)
                  at org.eclipse.jetty.io.ManagedSelector.lambda$destroyEndPoint$0(ManagedSelector.java:437)
                  ... 8 more
          

          Will recategorize to the core. olamy maybe there are something known in Jetty

          Oleg Nenashev added a comment - It is either a bug or infra issue. Generally it means that the HTTPs session has been interrupted IIUC. Caused by: java.nio.channels.ClosedChannelException at org.eclipse.jetty.util.IteratingCallback.close(IteratingCallback.java:427) at org.eclipse.jetty.server.HttpConnection.onClose(HttpConnection.java:491) at org.eclipse.jetty.io.ssl.SslConnection.onClose(SslConnection.java:244) at org.eclipse.jetty.io.SelectorManager.connectionClosed(SelectorManager.java:310) at org.eclipse.jetty.io.ManagedSelector.lambda$destroyEndPoint$0(ManagedSelector.java:437) ... 8 more Will recategorize to the core. olamy maybe there are something known in Jetty

          Sorin Sbarnea added a comment - - edited

          We got a very similar error after upgrading our Jenkins from 2.73 LTS to 2.89 LTS.

          See log at https://gist.github.com/ssbarnea/aec8ea4500c1103c2611bea556a81c31

          Any idea what is causing it and if there is a workaround? For the moment we disabled the graph generation inside BFA config. Looking at the trace I have reasons to believe that is not a BFA bug.

          Sorin Sbarnea added a comment - - edited We got a very similar error after upgrading our Jenkins from 2.73 LTS to 2.89 LTS. See log at  https://gist.github.com/ssbarnea/aec8ea4500c1103c2611bea556a81c31 Any idea what is causing it and if there is a workaround? For the moment we disabled the graph generation inside BFA config. Looking at the trace I have reasons to believe that is not a BFA bug.

            t_westling Tomas Westling
            rafaelrezend Rafael Rezende
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: