New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
systemd daemon-reload restarts snmpd #244
Comments
What is the Linux distribution involved? Do you have commercial support? |
I am running Debian 10 with 5.10.0-0.bpo.3-amd64 Kernel. I am afraid we don't have a commercial support! |
Does the problem occur when you execute |
It happens when |
@3c2b2ff5 do you have an example puppet report/output that we can see which resources are involved? The only real connection between systemd and snmpd i identfied at a quick look is https://github.com/voxpupuli/puppet-snmp/blob/master/manifests/init.pp#L460-L463 or if snmpd config changes. It would also be helpful if you can tell us your used versions of the modules (and/or update them to the lastest once if not already done) |
I modified
|
Well I can update some modules at the next schedule, we need to coordinate this first. But for now the module versions are:
|
You're at the latest version of this module so I think you'll have to get the module modified for your use case, or submit a PR. |
Thank you very much @ubellavance |
How can I get it modified? |
You can wait until someone does, or try to find a puppet consultant that will do the PR for you. |
OK, sure thanks |
This an other incident I had yesterday:
|
I believe this is now fixed with 6.0.0. I hope so at least. |
Hi,
I am seeing a strange behavior of snmpd. When ever
systemctl daemon-reload
is triggered, snmpd is restarted.I am running keepalived with snmp support to be able to monitor the state of my vrrp instances, but when snmpd is restarted, keepalived needs a restart as well, otherwise the connection to AgentX is lost.
How is this connected to systemd? could it be that the agent socket is managed by systemd? How can I avoid this behavior?
Thank you very much
The text was updated successfully, but these errors were encountered: