Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-36065

ci.lsst.codes gives 502 Bad Gateway

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: jenkins
    • Labels:
      None
    • Story Points:
      0.5
    • Team:
      SQuaRE
    • Urgent?:
      No

      Description

      ci.lsst.codes is not responding properly.  It appears to be accepting connections but not responding to https://ci.lsst.codes/blue/organizations/jenkins.  I eventually get a 502 Bad Gateway response.  Is this a problem with ingress or with the service?  I don't believe I have credentials to look at the service itself, running on AWS.

        Attachments

          Activity

          Hide
          athornton Adam Thornton added a comment -

          I logged onto jenkins-master (vagrant, SSH key in 1password), became root via sudo, restarted nginx, that didn't help, restarted Jenkins, that fixed it.

           

          That's a much more linear narrative than the actual set of events, but it's fairly true.

          Show
          athornton Adam Thornton added a comment - I logged onto jenkins-master (vagrant, SSH key in 1password), became root via sudo, restarted nginx, that didn't help, restarted Jenkins, that fixed it.   That's a much more linear narrative than the actual set of events, but it's fairly true.
          Hide
          athornton Adam Thornton added a comment -

          Rebooting the VM would have worked too.

          Show
          athornton Adam Thornton added a comment - Rebooting the VM would have worked too.
          Hide
          tjenness Tim Jenness added a comment - - edited

          The page is up but no jobs are running:

          There are no nodes with the label ‘jenkins-manager’

          eg https://ci.lsst.codes/blue/organizations/jenkins/stack-os-matrix/detail/stack-os-matrix/37234/pipeline/

          Show
          tjenness Tim Jenness added a comment - - edited The page is up but no jobs are running: There are no nodes with the label ‘jenkins-manager’ eg https://ci.lsst.codes/blue/organizations/jenkins/stack-os-matrix/detail/stack-os-matrix/37234/pipeline/
          Hide
          ktl Kian-Tat Lim added a comment -

          Fixed by adding the jenkins-manager label to the primary executor.

          Show
          ktl Kian-Tat Lim added a comment - Fixed by adding the jenkins-manager label to the primary executor.

            People

            Assignee:
            athornton Adam Thornton
            Reporter:
            ktl Kian-Tat Lim
            Watchers:
            Adam Thornton, Kian-Tat Lim, Tim Jenness
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Jenkins

                No builds found.