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

Duplicate (empty) sensors reported for certain devices

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Discovery
    • None

    Description

      Using 21.11.11767

      I've been trying to figure out why I have '4 alerts' listed for statuses but clicking the alerts shows me nothing and I think I've got a lead - if I click 'statuses' and then inverse sort by event, I can see four sensors listed with no status or event (two devices, a powersupply and fan sensor for each).

      If I look at the status indicators for each device, I cans ee the relevant statuses listed twice; one entry is OK, the other is blank. I tried re-discovering the device and watched the output and the duplicate blank status is shown there too. If I look at the graphs for the empy sensors it looks like they have previously logged some data.

      Attachments

        Activity

          [OBS-3952] Duplicate (empty) sensors reported for certain devices
          kingtrw Tom King added a comment -

          Amazing, so quick! Thanks very much - my status dashboard line is now clear

          kingtrw Tom King added a comment - Amazing, so quick! Thanks very much - my status dashboard line is now clear

          Fixed in r11777 (rolling updates).

          Duplicate (incorrect) entries will deleted after update and rediscovery device.

          landy Mike Stupalov added a comment - Fixed in r11777 (rolling updates). Duplicate (incorrect) entries will deleted after update and rediscovery device.

          General questions and device support can be discussed in our Discord channel, click here to join.


          Please make and attach additional information about the device:

          • full snmp dump from device:

            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

            If device not support SNMP version 2c, replace -v2c with -v1.

          • If you have problems with discovery or poller processes, please do and attach these debugs:

            ./discovery.php -d -h <device>
            ./poller.php -d -h <device>

          • additionally attach device and/or vendor specific MIB files

          This comment is added automatically.

          bot Observium Bot added a comment - General questions and device support can be discussed in our Discord channel, click here to join . Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files This comment is added automatically.

          People

            landy Mike Stupalov
            kingtrw Tom King
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: