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

EATON UPS very strange port name/broken web interface

Details

    • Vendor Bug
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Web Interface
    • ubuntu 22.04

    Description

      Hi,

      Im facing strange issue after updating (svn update) observium yesturday.

      Port names are very strange for two devices. Tried to remove and add again, but still im getting same result.

      I have 2 UPS with same model, and both getting the simillar port name/description/glitch

      Attachments

        Activity

          [OBS-4399] EATON UPS very strange port name/broken web interface
          moonboylv Ivo added a comment -

          These are ups'es too!

          That was fast answer, thanks Mike!

          moonboylv Ivo added a comment - These are ups'es too! That was fast answer, thanks Mike!
          landy Mike Stupalov added a comment -

          I not know how this can be related with observium update, because this is common Eaton devices memory leak issue.
          (Same issue known for UPSes).

          I added fix for ports name in r12511.
          (It will generated from port type).

          landy Mike Stupalov added a comment - I not know how this can be related with observium update, because this is common Eaton devices memory leak issue. (Same issue known for UPSes). I added fix for ports name in r12511. (It will generated from port type).
          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.

          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
            moonboylv Ivo
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: