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

Observium tries to open munin graphs from the wrong path

Details

    • Bug
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Web Interface
    • None

    Description

      Hi.

      after updating observium to 23.9.13005 it seems to be the web interface tries to open the munin graphs from the wrong path.

      the rrd's are saved under the hostname but the web interface tries to open it directly from the rrd path.

      E.g.: 

      real path: /opt/observium/rrd/10.242.0.9/munin_ping_10.242.0.10_ping.rrd

      web interface tries to open: /opt/observium/rrd/munin_ping_10.242.0.10_ping.rrd

      Error Messages says: No such file or directory.

      How we can fix this issue?

       

      BR. Torsten

      Attachments

        Activity

          [OBS-4624] Observium tries to open munin graphs from the wrong path

          Please, can you reopen this issue?

          twilms Torsten Wilms added a comment - Please, can you reopen this issue?

          Sorry, but we using 13018. it is not fixed

          twilms Torsten Wilms added a comment - Sorry, but we using 13018. it is not fixed

          Should be fixed in r13018.

          landy Mike Stupalov added a comment - Should be fixed in r13018.

          /opt/observium/rrd/10.242.0.9/munin_ping_10.242.0.10_ping.rrd

          twilms Torsten Wilms added a comment - /opt/observium/rrd/10.242.0.9/munin_ping_10.242.0.10_ping.rrd

          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
            twilms Torsten Wilms
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: