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

Sporadically Receive ERR_EMPTY_RESPONSE When Saving Configuration

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: _unsorted
    • Labels:
      None
    • Environment:
    • Similar Issues:

      Description

      We receive an ERR_EMPTY_RESPONSE when attempting to save the configuration of Freestyle Jobs, Pipeline Jobs, and Global Security Configuration. In most cases we can refresh the browser and the 'configSubmit' operation will be processed successfully, though not in 100% of cases. The issue does not occur persistently, but approximately 1 in ever 3 attempts results in the error response. I attempted to roll back any plugins that were installed during the last 2 weeks but with no success. I checked iptables and the AWS NSG for my EC2 instance but nothing appears to be incorrect or has any errors to report.

        Attachments

          Activity

          Hide
          jdh Joe Hartley added a comment -

          That's odd, I don't have parameterized-trigger plugin installed.

          Where is the use of parentheses () a problem?

          Show
          jdh Joe Hartley added a comment - That's odd, I don't have parameterized-trigger plugin installed. Where is the use of parentheses () a problem?
          Hide
          hubertus Hubertus added a comment -

          Update (issue seems to be resolved for me): After some tests today, I figured out that a combination of:
          a) Using "Parameterized Trigger" plugin version 2.41 AND
          b) Using special characters - in my case parentheses ()
          leads to the problem
          Downgrading "Parameterized Trigger" plugin to version 2.40 OR prevent parentheses resolves the problem.

          Show
          hubertus Hubertus added a comment - Update (issue seems to be resolved for me): After some tests today, I figured out that a combination of: a) Using "Parameterized Trigger" plugin version 2.41 AND b) Using special characters - in my case parentheses () leads to the problem Downgrading "Parameterized Trigger" plugin to version 2.40 OR prevent parentheses resolves the problem.
          Hide
          jdh Joe Hartley added a comment -

          I'm seeing the same issue after updating from 2.277.1 to 2.289.1 and updating all plugins to latest. 

          Show
          jdh Joe Hartley added a comment - I'm seeing the same issue after updating from 2.277.1 to 2.289.1 and updating all plugins to latest. 
          Hide
          hubertus Hubertus added a comment -

          Have the same problem today after updating Jenkins from 2.277.1 to 2.2.89.1 incl. update of all plug-ins. Roll back to previous Jenkins version and plug-ins resolve the problem. 

          But the reason isn't known at the moment.

          Show
          hubertus Hubertus added a comment - Have the same problem today after updating Jenkins from 2.277.1 to 2.2.89.1 incl. update of all plug-ins. Roll back to previous Jenkins version and plug-ins resolve the problem.  But the reason isn't known at the moment.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            djarvey David
            Votes:
            3 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated: