Monitoring Chronyd still produces errors

[cbfa]

Hello All,

Still can’t get chronyd to work. Everything seems to be configured correctly according to this

How to enable Chrony monitoring?

It looks like support was added for Chrony (an alternative to ntpd) a while ago, in this PR: But there’s no documentation about how to implement it. I presume a script has to be dropped somewhere and then snmpd.conf needs an edit similar to nginx or OS Updates monitoring…?

I get the following errors:

Application: chronyd, app_id=22SNMP[‘/usr/bin/snmpget’ ‘-v1’ ‘-c’ ‘COMMUNITY’ ‘-Oqv’ ‘-m’ ‘NET-SNMP-EXTEND-MIB’ ‘-M’ ‘/opt/librenms/mibs’ ‘-t’ ‘2’ ‘udp:HOSTNAME:161’ ‘nsExtendOutputFull.7.99.104.114.111.110.121.100’]

Exitcode: 2

Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: NET-SNMP-EXTEND-MIB::nsExtendOutputFull.“chronyd”

Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: NET-SNMP-EXTEND-MIB::nsExtendOutputFull.“chronyd”

chronyd:-2:Empty return from snmp_get.

Any help you are able to provide is greatly appreciated.

[Houtek]

Hi,
do you have
extend chronyd /etc/snmp/chrony
in your snmpd.conf and this file https://raw.githubusercontent.com/librenms/librenms-agent/master/snmp/chrony in place?
It needs to be executable, otherwise, it won’t work.

[cbfa]

Yes, I do. When I run the script locally it works and gets the output.
I am running it on ubuntu not sure if there is anything more that could be done.

Not sure how to go about troubleshooting these type of errors.

Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: NET-SNMP-EXTEND-MIB::nsExtendOutputFull.“chronyd”