Hello,
I'm posting this because I noticed another user is having similar difficulty in starting the SNMP service. I want to avoid the perception of "No Repro" syndrome from support members. I've had this issue ever since I embarked on the Protectli FW4B/OPNsense journey in mid-2019. An authoritative person ("...mail", I believe) tried to assist me in the early days but the suggestion to start the service explicitly from the Dashboard screen never worked. I haven't had much luck with Netgear MIBs and therefore this SNMP anomaly is not a handicap for me but if it helps others in reproducible diagnostics, I'll do whatever suggestions that are relayed to me and are practical for me.
During the boot process, I noticed ~4 lines of text stating:
- SNMP service could not be started
- Conf file should be checked
As a
newbie with OPNsense (even though I've been operating it for over two years) I am ignorant on how to check for the corresponding SNMP config file. Thanks for your understanding.
Kind regards.[/list]
Hello,
are there any new findings about the problem ?
My net-smnp starts after a reboot of the OPNSense (according to the dashboard it is running) but it does not deliver SNMP data for monitoring.
A restart via the dashboard does not bring any change, I have to disable the service myself and then enable it, then it runs again.
The error already runs through several software versions up to the current 22.1.9.
I have already considered to restart the net-snmp via cron-job regularly.
best regards
Thomas
I have just installed os-net-snmp on OPNsense 22.4.2-amd64 and it is running.
( @baqwas : have you tried to deinstall and reinstall os-net-snmp ? )
I will try to restart the firewall next weekend
I still got these issues.
44 days ago (after an update?) our snmp-server said our OpnSense went down (which it wasn't).
So I noticed i also can't start Net-SNMP (if i leave listen IP's empty or not).
Does anyone have a sollution?