Details
-
Vendor Bug
-
Resolution: Fixed
-
Minor
-
None
-
Professional Edition
-
None
Description
Observium Professional 22.5.12014
I have an AVTech Roomalert 32 that's up to date with vendor firmware (3.3.1). It has 6 temp/humidity probes conncected on ports 1-6 and two temp probes connected on 7-8. It also has an internal temp/humidity sensor. These are all reporting correctly according to the device's built in monitoring interface.
Experiencing following issues:
- Obs does not know about software version
- Obs is aware of temp/humidity sensors 1 through 6, but is only drawing graphs for a couple of them. In the graph legends the value data for the missing entries is listed as 'NaN'.
- Obs is not aware of sensors 7-8 at all.
I've filed this as vendor bug as I'm toelrably certain they're not doing SNMP right, but if you could check I'd be very grateful.
Attachments
Activity
Obs does not know about software version
This is (probably) firmware issue, previously the version information was in sysDescr.
old example:
SNMPv2-MIB::sysDescr.0 = STRING: Room Alert 32E v3.0.2
|
your snmpdump:
SNMPv2-MIB::sysDescr.0 = STRING: sproomalertoeg3
|
not possible be fixed in our side.
Obs is aware of temp/humidity sensors 1 through 6, but is only drawing graphs for a couple of them. In the graph legends the value data for the missing entries is listed as 'NaN'.
you have rrd file(s) permission troubles on server (for this host rrddir). See rrd command error:
RRD CMD[update sproomalertoeg3.ddns.eng.ox.ac.uk/sensor-temperature-ROOMALERT32E-MIB-digital-sen2-5-0.rrd N:21 --daemon unix:/var/run/rrdcached.sock]
|
|
|
RRD STDOUT[ERROR: rrdcached@unix:/var/run/rrdcached.sock: Cannot read/write /opt/observium/rrd/sproomalertoeg3.ddns.eng.ox.ac.uk/sensor-temperature-ROOMALERT32E-MIB-digital-sen2-5-0.rrd: Permission denied]
|
Check fix files permissions in rrd dir /opt/observium/rrd/sproomalertoeg3.ddns.eng.ox.ac.uk
Obs is not aware of sensors 7-8 at all.
This fixed in r12017.
Trying to attach relevant files but getting Jira error
File "snmpwalk.txt" was not uploaded
An error occured while attaching snmpwalk.txt: Could not save attachment data from stream.
will keep trying!
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.snmpwalksnmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalkIf 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.
Awesome, thanks! No idea how the rrd permissions got out of whack but they seem happy now.