Details

    • Bug
    • Resolution: Fixed
    • Minor
    • None
    • Enterprise Edition
    • Alerting
    • Version: Observium 25.5.14009 (stable)
      Browser: Microsoft Edge for Business, Version 136.0.3240.76 (Official build) (64-bit)

    Description

      Version: Observium 25.5.14009 (stable)

      On the properties page for a device, example here:

      The power for Slot 11 got set wrong automatically. When I change the value in the field and press save in the bottom of the page I get this message:

      If i reload the page, no changes are made.

      If i change alerts from Yes to No and save, the changes are saved.

      I've inspected the payload and i see the json in the payload contains the updated value, but the server does not seem to accept the change.

      Best regards,
      Emil Kristensen

       

      Attachments

        Activity

          [OBS-5031] Sensor limit not updated

          When changing sensor limits on this page, make sure to also enable the ‘Custom’ flag.
          This should also be done automatically when editing limits, but it was broken.

          Fixed in r14019.
          Not in stable yet, will be released soon.

          landy Mike Stupalov added a comment - When changing sensor limits on this page, make sure to also enable the ‘Custom’ flag. This should also be done automatically when editing limits, but it was broken. Fixed in r14019. Not in stable yet, will be released soon.

          I can give you this, but I have no issues with pooling data. I want to change the sensor limits in observium. 

          Please confirm if you still need this.

          emik Emil Kristensen added a comment - I can give you this, but I have no issues with pooling data. I want to change the sensor limits in observium.  Please confirm if you still need this.

          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
            emik Emil Kristensen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: