Knowing uptime is a security flaw, therefore this is a very very
important OpenBSD security feature.
:D
adam.
Mike Stupalov via observium wrote on 13/11/2023 10:14:
Heh,
it's funny. Seems as this is an openbsd snmpd issue.
It's report 3 different Uptimes:
1. SNMPv2-MIB::sysUpTime.0 = 1:0:58:32.85 (Timeticks converted
1:0:58:32.85 -> 89912)
2. HOST-RESOURCES-MIB::hrSystemUptime.0 = 7:10:54:04.27 (Timeticks
converted 7:10:54:04.27 -> 644044)
3. SNMP-FRAMEWORK-MIB::snmpEngineTime.0 = 1699608841
We always take 3 values and choose the maximum of them.
But seems as OpenBSD report just current unixtime in snmpEngineTime.
This is incorrect.
I added workaround for this case in r13160.
Bryan Fields wrote on 10.11.2023 12:42:
On 11/10/23 3:43 AM, Mike Stupalov wrote:
I've captured the output here:http://keekles.org/OpenBSD.txt
I didn't see an option to kill the escape codes for color though.
That file ok, but this is not debug output.. you must run commands with
-d flag as I written!
With debug I can see required snmp outputs.. (or errors)
Sorry, I know how frustrating that is, it was an oversight and I
appreciate the help.
I've run both these commands:
su observium -c '/opt/observium/discovery.php -d -h 52'
>>/root/OpenBSD-debug.txt
su observium -c '/opt/observium/poller.php -d -h 52'
>>/root/OpenBSD-debug.txt
The output is here:
http://keekles.org/OpenBSD-debug.txt
Thank you,
--
Mike Stupalov,
Discord channel: https://discord.gg/GjpNXKWm8W
Observium Limited, https://observium.org
_______________________________________________
observium mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
observium mailing list -- [email protected]
To unsubscribe send an email to [email protected]
