Details

    • Help
    • Resolution: Not A Bug
    • Minor
    • None
    • CE-21.10
    • Poller
    • Ubuntu 20.04 / 22.04

    Description

      First of all, sorry if this is the wrong place to post this.

      This has nothing to do with Observium, but rather with the clients it monitors.

      I am hoping that someone has a solution to this problem.

      We have a handfull Ubuntu clients that we are trying to monitor via SNMP v3.

      They are mostly Ubuntu 20.04 LTS which uses NET-SNMP 5.8.

      The problem is that the SNMPD service dies pretty quickly after we have setup the monitoring...

      We have of cause googled the problem, and it seems to be a know issue which should have been solved in a later release (which is not yet released on Ubuntu 20.04 (or 22.04))

      If anyone has fixed this issue, please share the knowledge  

      For now we have setup a cron that restarts the service every hour (which some times isn't enough)...

      Attachments

        Activity

          [OBS-4251] SNMP v3 Client dies on Ubuntu...

          This is completely not Observium issue, you should use Ubuntu (and/or Net-Snmp) issue trackers.

          I can only suggest to use SNMP v2 (instead v3) if there is known issue with v3 snmp.

          landy Mike Stupalov added a comment - This is completely not Observium issue, you should use Ubuntu (and/or Net-Snmp) issue trackers. I can only suggest to use SNMP v2 (instead v3) if there is known issue with v3 snmp.

          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
            Beardmann Heino Walther
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: