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

Polling error sometimes (needs reboot)

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: scripttrigger-plugin
    • Labels:
      None
    • Environment:
    • Similar Issues:

      Description

      We get the following error at the bottom of the scripttrigger log:

      [ERROR] - Polling error...

      With no evidence that it tried to run the script. The Polling error happens every time afterwards until Jenkins is restarted. I haven't seen any logs describing what the error is or why it's happening.

      We've rebooted our server so that we can continue working. This problem is not reproducible. It has happened 3 times in the past 6 months (the last 2 times were within the last two weeks). When you're ready to work on it, we will keep the problem around when it happens again for debugging purposes.

        Attachments

          Activity

          Hide
          de396889 Blaine Young added a comment - - edited

          It happened again this morning. Here's the script trigger output:

          Polling started on Nov 18, 2014 9:03:29 AM
          Polling for the job InstallAndRunAllTests
          Looking nodes where the poll can be run.
          Looking for a candidate node to run the poll.
          Looking for a node with no predefined label.
          Trying to poll with the last built on node.
          
          Polling on master.
          The expected script execution code is 1
          Evaluating the script: 
          
          #!/bin/bash
          
          # Get the bldinfo file from all E-Boxes
          NONCONSISTENT=false
          boxes=(
             alpha
             beta
             charlie
             kilo
             lima
             mike
             november
             papa
             quebec
             romeo
             sierra
             )
          firstBox=${boxes[0]}
          for box in ${boxes[@]}; do
             scp user@$box:/usr/oec/bldinfo /tmp/bldinfo-$box
             if ! diff /tmp/bldinfo-$firstBox /tmp/bldinfo-$box; then
                NONCONSISTENT=true
                echo "Nonconsistent builds exist between $firstBox and $box" >&2
                break
             fi
          done
          
          DAILY_BUILD_ROOT=/dailyBuild/release
          NEWEST_BUILD_INFO="$(find "$DAILY_BUILD_ROOT" -maxdepth 3 -name bldinfo -exec ls -lt {} + | head -n 1 | awk '{ print $9 }')"
          
          if diff /tmp/bldinfo-$firstBox $NEWEST_BUILD_INFO && [ "$NONCONSISTENT" != "true" ]; then
             exit 0  # Nothing to do
          else
             exit 1  # Let's do something
          fi
          
          for box in ${boxes[@]}; do
             rm /tmp/bldinfo-$box
          done
          [ERROR] - Polling error...
          [ERROR] - Error message: 95
          

          Any insight or help?

          Since I've received no reply about someone working on this, I'll clear it and let you know if it happens again.

          Show
          de396889 Blaine Young added a comment - - edited It happened again this morning. Here's the script trigger output: Polling started on Nov 18, 2014 9:03:29 AM Polling for the job InstallAndRunAllTests Looking nodes where the poll can be run. Looking for a candidate node to run the poll. Looking for a node with no predefined label. Trying to poll with the last built on node. Polling on master. The expected script execution code is 1 Evaluating the script: #!/bin/bash # Get the bldinfo file from all E-Boxes NONCONSISTENT=false boxes=( alpha beta charlie kilo lima mike november papa quebec romeo sierra ) firstBox=${boxes[0]} for box in ${boxes[@]}; do scp user@$box:/usr/oec/bldinfo /tmp/bldinfo-$box if ! diff /tmp/bldinfo-$firstBox /tmp/bldinfo-$box; then NONCONSISTENT=true echo "Nonconsistent builds exist between $firstBox and $box" >&2 break fi done DAILY_BUILD_ROOT=/dailyBuild/release NEWEST_BUILD_INFO="$(find "$DAILY_BUILD_ROOT" -maxdepth 3 -name bldinfo -exec ls -lt {} + | head -n 1 | awk '{ print $9 }')" if diff /tmp/bldinfo-$firstBox $NEWEST_BUILD_INFO && [ "$NONCONSISTENT" != "true" ]; then exit 0 # Nothing to do else exit 1 # Let's do something fi for box in ${boxes[@]}; do rm /tmp/bldinfo-$box done [ERROR] - Polling error... [ERROR] - Error message: 95 Any insight or help? Since I've received no reply about someone working on this, I'll clear it and let you know if it happens again.
          Hide
          de396889 Blaine Young added a comment -

          We manually triggered the build process rather than restarting Jenkins. The manual trigger seems to have reset the polling error because the next time the polling worked and started the build.

          Show
          de396889 Blaine Young added a comment - We manually triggered the build process rather than restarting Jenkins. The manual trigger seems to have reset the polling error because the next time the polling worked and started the build.

            People

            • Assignee:
              gbois Gregory Boissinot
              Reporter:
              de396889 Blaine Young
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: