Unbound-control and SNMP extend

[Headless1919]

Hello team,

I have a somewhat left-field use case. I am making use of LibreNMS and their application monitoring for Unbound (https://docs.librenms.org/Extensions/Applications/#unbound) which requires unbound-control to be running as well as an SNMP extend for their script to pull the stats via SNMP.

My questions are as follows:

• Is there a way, or preferred way, to get unbound-control to run at boot? Currently I need to SSH in every time and issue "unbound-control start"
• Can we get a custon SNMP extend functionality, similar to what has been provided for Unbound? The configuration in the file is not persistent and must be reapplied after reboot

Everything works under normal circumstances but a reboot for whatever reason necessitates logging in and starting the process, followed by adding the extend back into the SNMP file again.

[heyheyheyhey]

Same problem.  My search brought me here.

unbound-control isnt a service to run, but is enabled with unbound configuration in opnsense.

I learned you have to specify the unbound configuration.

Code: [Select]

unbound-control -c /var/unbound/unbound.conf stats
Returns results.  Just need to figure out how to get the extend configuration to persist through a reboot in the snmp configuration.

[Headless1919]

Thanks for your post, after some digging I agree with you. If I log in now and issue unbound-controls status, the service is not running - but my polling is still working correctly. It would seem that it is not something I manually need to start at boot to make things work.

Persistence, as you mention, is now the problem. Does anyone else have any ideas, or can we get some insight from the development team?

[Headless1919]

Bump - still looking for an elegant solution to this. Any solution or input from anyone else?

[Headless1919]

Bump - still no closer to a solution, any help will be appreciated.