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

status.lsst.codes ssllabs check broken

    Details

      Description

      The nagios check-ssl-qualys.rb plugin has been broken for 63 days now. It appears that the v2 api is gone and v3 has replaced it. Eg.,

      https://api.ssllabs.com/api/v3/info
      https://github.com/ssllabs/ssllabs-scan/blob/master/ssllabs-api-docs-v3.md

        Attachments

          Issue Links

            Activity

            Hide
            jhoblitt Joshua Hoblitt added a comment -
            Show
            jhoblitt Joshua Hoblitt added a comment - Reported upstream on the plugin as https://github.com/sensu-plugins/sensu-plugins-ssl/issues/33
            Hide
            jhoblitt Joshua Hoblitt added a comment -

            A permanent fix has been PR'd upstream: https://github.com/sensu-plugins/sensu-plugins-ssl/pull/34

            Show
            jhoblitt Joshua Hoblitt added a comment - A permanent fix has been PR'd upstream: https://github.com/sensu-plugins/sensu-plugins-ssl/pull/34
            Hide
            jhoblitt Joshua Hoblitt added a comment - - edited

            So it appears that the v2 api is working but requests are often taking over 2 minutes now (this is also happening with v3. However, I don't think it will hurt to leave the switch to the v3 API in place.

            I have pushed the nagios service check timeout up to 240s. This has gotten all of the checks passing except for

            • sw.lsstcorp.org, which seems to be broken and is no longer properly redirecting to to https://eups.lsst.codes – this results in the ssllabs check hitting the 240s timeout
            • git-lfs.lsst.codes is now successfully being checked but is obtaining an F rating.
            Show
            jhoblitt Joshua Hoblitt added a comment - - edited So it appears that the v2 api is working but requests are often taking over 2 minutes now (this is also happening with v3 . However, I don't think it will hurt to leave the switch to the v3 API in place. I have pushed the nagios service check timeout up to 240s. This has gotten all of the checks passing except for sw.lsstcorp.org, which seems to be broken and is no longer properly redirecting to to https://eups.lsst.codes – this results in the ssllabs check hitting the 240s timeout git-lfs.lsst.codes is now successfully being checked but is obtaining an F rating.
            Hide
            jhoblitt Joshua Hoblitt added a comment -

            I'm going to leave this ticket open until the related issues are resolved and then enable ssllabs check notifications under it.

            Show
            jhoblitt Joshua Hoblitt added a comment - I'm going to leave this ticket open until the related issues are resolved and then enable ssllabs check notifications under it.
            Hide
            jhoblitt Joshua Hoblitt added a comment -

            Notifications for ssllabs checks have been renabled and the timeout further increased to 300s in an attempt to prevent errors.

            The ssllab check for git-lfs.lsst.codes has been acknowledged to prevent noise.

            Show
            jhoblitt Joshua Hoblitt added a comment - Notifications for ssllabs checks have been renabled and the timeout further increased to 300s in an attempt to prevent errors. The ssllab check for git-lfs.lsst.codes has been acknowledged to prevent noise.

              People

              • Assignee:
                jhoblitt Joshua Hoblitt
                Reporter:
                jhoblitt Joshua Hoblitt
                Watchers:
                Adam Thornton, Joshua Hoblitt
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: