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

Eaton UPS - still not displaying proper info

Details

    • Vendor Bug
    • Resolution: Incomplete
    • Major
    • None
    • Professional Edition
    • Default
    • None

    Description

      Hello again,

       

      some time ago (https://jira.observium.org/browse/OBS-4383) we've reported issues with Eaton UPSes and lately we've updated our OBS to version 23.2.12520 (stable). 

      With latest updates some of the parameters of the UPS started showing properly, but still the Output of voltage, frequency and load doesn't show any reasonable data.

       

      Do let us know if you want to make the snmpwalks again.

       

      Attachments

        1. image-2023-03-27-14-55-55-360.png
          image-2023-03-27-14-55-55-360.png
          166 kB
        2. image-2023-04-18-13-29-13-297.png
          image-2023-04-18-13-29-13-297.png
          124 kB
        3. image-2023-04-18-13-32-00-085.png
          image-2023-04-18-13-32-00-085.png
          169 kB
        4. image-2023-04-18-13-33-19-469.png
          image-2023-04-18-13-33-19-469.png
          169 kB
        5. image-2023-04-25-09-57-11-267.png
          image-2023-04-25-09-57-11-267.png
          148 kB
        6. ups.thane.bom.eix.poller
          66 kB
        7. ups.thane.bom.eix-1.poller
          67 kB

        Issue Links

          Activity

            [OBS-4458] Eaton UPS - still not displaying proper info

            It's really very strange situation.. seems I can't fix it by debug outputs, probably trouble exist on your local system.

            Can you provide temporary access to your observium host?
            Ie with tmate (https://tmate.io/).

            You can write me directly by mail mike@observium.org or in our official Discord channel (user @landy).

            landy Mike Stupalov added a comment - It's really very strange situation.. seems I can't fix it by debug outputs, probably trouble exist on your local system. Can you provide temporary access to your observium host? Ie with tmate ( https://tmate.io/ ). You can write me directly by mail mike@observium.org or in our official Discord channel (user @landy ).

            The above command exits with status 0 and no output is displayed. Will try to update with the latest SVN stable branch and if the issue still persist will let you know

             

            ymarinov Yavor Marinov added a comment - The above command exits with status 0 and no output is displayed. Will try to update with the latest SVN stable branch and if the issue still persist will let you know  

            show please svn status of observium dir:

            svn status /opt/observium

            Issue was alredy fixed, but seems your install still use old code, by unknown reason.

            Additionally I changed same part by different way (really nothing changed) in r12743.

            landy Mike Stupalov added a comment - show please svn status of observium dir: svn status /opt/observium Issue was alredy fixed, but seems your install still use old code, by unknown reason. Additionally I changed same part by different way (really nothing changed) in r12743.

            Here is the latest request of discovery.

            ymarinov Yavor Marinov added a comment - Here is the latest request of discovery.

            Make debug discovery one time again please.

            ./discovery.php -dd -m sensors -h <device>

            landy Mike Stupalov added a comment - Make debug discovery one time again please. ./discovery.php -dd -m sensors -h <device>

            I not sure how, but I see that your device still not rediscovered!
            Oids for this sensors still not updated.

            Run device rediscovery.
            And check if you have crontab entry for discovery all devices..

            landy Mike Stupalov added a comment - I not sure how, but I see that your device still not rediscovered! Oids for this sensors still not updated. Run device rediscovery. And check if you have crontab entry for discovery all devices..

            Attaching the output of poller.php -r -d -m sensors -h and fresh screenshot of the webui status of this UPS

             

            ymarinov Yavor Marinov added a comment - Attaching the output of poller.php -r -d -m sensors -h and fresh screenshot of the webui status of this UPS  

            this debug is failed:

             o Device status        Device hostname is not resolved

            landy Mike Stupalov added a comment - this debug is failed: o Device status Device hostname is not resolved

            Attaching the poller with params -r -d -m sensors -h DEVICE

             

             

            ymarinov Yavor Marinov added a comment - Attaching the poller with params -r -d -m sensors -h DEVICE    

            Hello and sorry for the late reply.

            No matter that we re-discovered the Eaton UPS and made the poller changes as you asked we couldn't find any difference - in fact now Observium gives a lot less information about the device. Also again it's detected as PowerWalker UPS instead of Eaton.

             

             

            In our "production" environment where we didn't update to the latest svn stable branch the same UPS is displaying the following information in WebUI

            ymarinov Yavor Marinov added a comment - Hello and sorry for the late reply. No matter that we re-discovered the Eaton UPS and made the poller changes as you asked we couldn't find any difference - in fact now Observium gives a lot less information about the device. Also again it's detected as PowerWalker UPS instead of Eaton.     In our "production" environment where we didn't update to the latest svn stable branch the same UPS is displaying the following information in WebUI

            And be sure, that you rediscovered device after upgrade!
            In previous ticked we fixed discovery this sensors, but need device rediscovery.
            This is done automatically if you have cron with "discovery all"

            ./discovery.php -h <device>

            landy Mike Stupalov added a comment - And be sure, that you rediscovered device after upgrade! In previous ticked we fixed discovery this sensors, but need device rediscovery. This is done automatically if you have cron with "discovery all" ./discovery.php -h <device>

            People

              landy Mike Stupalov
              ymarinov Yavor Marinov
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: