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

no graphs, ports on one of the devices after upgrade

Details

    • Help
    • Resolution: Not A Bug
    • Major
    • None
    • None
    • Discovery, Graphs
    • None

    Description

      It seems that after the upgrade (Observium itself and also Debian from 9 to 10) one of the device is not displaying the ports tab (it's empty), nor any graphs, logs etc.

       

      It only shows the eventlog. And that all the data was deleted...

       

      Is there a way to recover all the data?

      Attachments

        Activity

          [OBS-4829] no graphs, ports on one of the devices after upgrade

          Yes, removing this value helped indeed. Really don't know how this value got there. The only thing I could correlate is the upgrade I've done recently. Thank you for your support.

          mkac Marcin Kaczynski added a comment - Yes, removing this value helped indeed. Really don't know how this value got there. The only thing I could correlate is the upgrade I've done recently. Thank you for your support.
          landy Mike Stupalov added a comment - - edited

          You have set SNMP Max Repetition on device edit page as '80',
          but really device not support this value.

          I've seen previous reports of problems on this platform (probably after firmware updates).
          Reduce (or remove) this value as small as possible.

          Example of error in your debug

          ifOperStatus Device-specific maxrep 80.
           
          CMD[/usr/bin/snmpbulkwalk -Cr'80' -t '2' -r '5' -v2c -c 'my-sensitive-data' -Pud -OQUs -m IF-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'nat1-war91.inwep.wan':'161' ifOperStatus]
           
          CMD EXITCODE[2]
          CMD RUNTIME[0.0274s]
          STDOUT[
          ifOperStatus = No Such Object available on this agent at this OID
          ]
          STDERR[
          Error in packet.
          Reason: (tooBig) Response message would have been too large.
          ]
          

          landy Mike Stupalov added a comment - - edited You have set SNMP Max Repetition on device edit page as '80', but really device not support this value. I've seen previous reports of problems on this platform (probably after firmware updates). Reduce (or remove) this value as small as possible. Example of error in your debug ifOperStatus Device-specific maxrep 80.   CMD[/usr/bin/snmpbulkwalk -Cr'80' -t '2' -r '5' -v2c -c 'my-sensitive-data' -Pud -OQUs -m IF-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'nat1-war91.inwep.wan':'161' ifOperStatus]   CMD EXITCODE[2] CMD RUNTIME[0.0274s] STDOUT[ ifOperStatus = No Such Object available on this agent at this OID ] STDERR[ Error in packet. Reason: (tooBig) Response message would have been too large. ]

          Attaching output. All the sensitive data (community string and neighbours section) I have replaced with string my-sensitive-data

          discovery.txt

          mkac Marcin Kaczynski added a comment - Attaching output. All the sensitive data (community string and neighbours section) I have replaced with string my-sensitive-data discovery.txt

          run a debugged discovery on the device : 

          ./discovery.php -h <device_id> -dd

          The output will probably explain what's happening.

          adama Adam Armstrong added a comment - run a debugged discovery on the device :  ./discovery.php -h <device_id> -dd The output will probably explain what's happening.

          People

            landy Mike Stupalov
            mkac Marcin Kaczynski
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: