Details

    • Bug
    • Resolution: Fixed
    • Major
    • None
    • None
    • Discovery
    • None

    Description

      Once i upgraded to version 13803 from version 13759 and i tried to run manual discovery or poll i got errors that the devices doesnt exist in observium db.
      Once i reverted to version 13759 everything is back to normal.
      After the upgrade to 13803 i ran ./discovery.php -u and no updates were made, the same after reverting to version 13759

      Attachments

        Activity

          [OBS-4950] Database issue with version 13803
          Shama Tarek added a comment -

          Thanks
          When is the release date for this version?

          Shama Tarek added a comment - Thanks When is the release date for this version?

          Fixed in r13805.

          But you should prefer device_id number here and do not use IP address as hostname.

          landy Mike Stupalov added a comment - Fixed in r13805. But you should prefer device_id number here and do not use IP address as hostname.
          Shama Tarek added a comment -

          For example:

          ERROR: Device with hostname '10.41.155.58' does not exist in observium db.

          You can see in the screenshot that i reverted to version 13759 and its started working again.

          Shama Tarek added a comment - For example: ERROR: Device with hostname '10.41.155.58' does not exist in observium db. You can see in the screenshot that i reverted to version 13759 and its started working again.

          please show your manual discovery commands (and error output).

          landy Mike Stupalov added a comment - please show your manual discovery commands (and error output).
          Shama Tarek added a comment -

          Thats what i am running now and it seem to be working fine

          Shama Tarek added a comment - Thats what i am running now and it seem to be working fine

          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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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
            Shama Tarek
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: