• Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • core
    • None

      Starting from around 2.463 (Java 17 update) we are unable to tail jenkins job execution logs properly as we get 'Failed to fetch more data. The page might no longer exist or you no longer have permission to see it.' all the time. 

       

      This issue affects:

      1. pipeline job logs
      2. freestyle job logs
      3. worker node logs

      Details:

      1. Jenkins version: 2.467
      2. Master node details:
        1. Ubuntu 22.04 LTS
        2. JDK 17.0.10 (Azul Zulu, also tested on Bellsoft's Liberica and Oracle's OpenJDK, same results)
      3. Worker node details:
        1. JDK 11/17/21 on worker nodes (Bellsoft's Liberica version, installed via sdkman,  default java package used connectivity to the host)

       

      Master-node runtime: J

          [JENKINS-73428] Unable to follow output of jenkins job

          Mark Waite added a comment -

          I can't duplicate the problem as described, though I am not sure that I've understood what you mean by "tail Jenkins job execution logs". Can you provide more details to describe what you mean when you say "tail Jenkins job execution logs"?

          Steps I tried:

          1. Install Jenkins 2.467 with Pipeline plugins
          2. Configure a freestyle job that iterates hundreds of times over a loop that prints a message and sleeps for 3 seconds
          3. Run the freestyle job and confirm that the web browser correctly shows the continuing arrival of new messages
          4. From the file system, use tail -f to read the build log that is written to the disc, confirming that it can continues to show output
          5. Used wget to read the build log from the build URL

          All those steps behaved as expected.

          Mark Waite added a comment - I can't duplicate the problem as described, though I am not sure that I've understood what you mean by "tail Jenkins job execution logs". Can you provide more details to describe what you mean when you say "tail Jenkins job execution logs"? Steps I tried: Install Jenkins 2.467 with Pipeline plugins Configure a freestyle job that iterates hundreds of times over a loop that prints a message and sleeps for 3 seconds Run the freestyle job and confirm that the web browser correctly shows the continuing arrival of new messages From the file system, use tail -f to read the build log that is written to the disc, confirming that it can continues to show output Used wget to read the build log from the build URL All those steps behaved as expected.

          Aleksei Grigorov added a comment - - edited

          markewaite, I probably used the wrong wording to describe the issue, sorry.

          Whenever we open a page in jenkins that tries to fetch latest logs (simplest example is job's console output) spinner would appear at the bottom of the page indicating that new output is getting fetched from the server:

          But after a second or two it fails and shows this error message instead:

          New output that's generated by the job won't be visible until we manually refresh the page. I've tried reverting back to v2.466 and still have same issue.

          It seems that this is transient issue related to having too many JSESSIONID cookies as when I open same page in a different browser or in incognito mode in same browser this problem doesn't happen anymore):

          Aleksei Grigorov added a comment - - edited markewaite , I probably used the wrong wording to describe the issue, sorry. Whenever we open a page in jenkins that tries to fetch latest logs (simplest example is job's console output) spinner would appear at the bottom of the page indicating that new output is getting fetched from the server: But after a second or two it fails and shows this error message instead: New output that's generated by the job won't be visible until we manually refresh the page. I've tried reverting back to v2.466 and still have same issue. It seems that this is transient issue related to having too many JSESSIONID cookies as when I open same page in a different browser or in incognito mode in same browser this problem doesn't happen anymore):

            Unassigned Unassigned
            ktannenberg Aleksei Grigorov
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: