Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-3728

Alert checkers died, shows null device ID

Details

    • Bug
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Alerting
    • None

    Description

      The device ID is not recognized in alert checkers. Eg. Alert checker for port shows the corresponding port but device is null and checkers have stopped processing.

      Running 21.4.11253 on fresh Ubuntu 20.04.2 install via automated install script.

      Suspected DB corruption on production server but fresh install is doing the same thing.

      Attachments

        Activity

          [OBS-3728] Alert checkers died, shows null device ID

          Aha, this took a bit of fiddling to work out. It should be fixed now!

          There's a new db update for discovery.php -u that'll pop device_ids onto rows that don't have them.

          adama Adam Armstrong added a comment - Aha, this took a bit of fiddling to work out. It should be fixed now! There's a new db update for discovery.php -u that'll pop device_ids onto rows that don't have them.
          nturnet William Hanson added a comment - - edited

          Additional Update:

          If you manually run: /opt/observium/housekeeping.php -yrptb

          Once completed, housekeeping removes the Entity Association Ruleset all together from the Port type alert checker.

          [db.log] [housekeeping.log] [observium.log]

          0 errors

          nturnet William Hanson added a comment - - edited Additional Update: If you manually run:  /opt/observium/housekeeping.php -yrptb Once completed, housekeeping removes the Entity Association Ruleset  all together from the Port  type alert checker. [db.log] [housekeeping.log]   [observium.log] 0 errors
          nturnet William Hanson added a comment - - edited

          Attempted to switch to rolling trunk with 21.4.11258 now active. Update included revised SQL script, ran afterwards

          ./discovery.php -u

          Same result. I've also deleted and recreated the checker but no such luck.

          The issue seems to directly affect alert checkers configured for "port" checks. Adversely, an alert checker to simply check for down devices appears to work.

          nturnet William Hanson added a comment - - edited Attempted to switch to rolling trunk with 21.4.11258 now active. Update included revised SQL script, ran afterwards ./discovery.php -u Same result. I've also deleted and recreated the checker but no such luck. The issue seems to directly affect alert checkers configured for "port" checks. Adversely, an alert checker to simply check for down devices appears to work.

          People

            adama Adam Armstrong
            nturnet William Hanson
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: