OPNsense Forum
Archive => 18.1 Legacy Series => Topic started by: poodad on May 06, 2018, 08:11:49 pm
-
After updating to 18.1.7 I noticed that I was not getting snmp data from opnsense. Looking at the dashboard, I could see that the snmp service was stopped. Attempts to start didn't work.
Looking in the log, I could see this error:
snmpd[24875]: error in config file
snmpd[24875]: in file /var/etc/snmpd.conf line 11
Looking at line 11 in that file shows this line:
begemotSnmpdPortStatus..161 = 1
Editing the file to remove the extra "." and starting the service from the GUI resulted in the same error. Looking at the file, I can see the bad line has been added back.
The temp workaround is to edit the file, removing the extra ".", than starting the bsnmpd service with:
/etc/rc.d/bsnmpd onestart
EDIT: It looks like much more breaks as well. It appears the UCD-SNMP-MIB (1.3.6.1.4.1.2021) MIB is no longer working., even though the "UCD" option is checked in the SNMP configuration.
-
You have a misplaced interface in your SNMP GUI config, one that doesn't exist anymore.
Cheers,
Franco
-
And how would one track that down and fix it?
-
Under Services: SNMP check the values for "Bind Interface" at the bottom.
Cheers,
Franco
-
Hi,
same problem here after updating to 18.1.7_1. The snmpd doesn't start if the interface is set to "all" in the GUI, or another virtual (i.e. CARP) interface, it starts only if it's bound to a real interface. The workaround suggested by poodad works for me at the moment. But it would be nice to use it as on 18.1.6, we used the CARP IP at the lan interface to monitor it from remote net.
Regards,
Siegfried
-
I've fixed strange behaviour in the code, but to be honest sooner or later the current SNMP plugin will not receive any more maintenance due to its age and need for replacement (net-snmp plugin will be coming sooner or later).
https://github.com/opnsense/plugins/commit/8f7e89fc1
Cheers,
Franco