Skip to content
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

snmpd starts on each puppet run #252

Closed
3c2b2ff5 opened this issue Sep 27, 2021 · 1 comment
Closed

snmpd starts on each puppet run #252

3c2b2ff5 opened this issue Sep 27, 2021 · 1 comment

Comments

@3c2b2ff5
Copy link

Hi,

I am running keepalived with snmp support to be able to monitor the state of my vrrp instances, snmpd is running on the keepalived VM's and the monitoring host. On each puppet run on the monitoring host I get the following:

Notice: /Stage[main]/Snmp/Service[snmpd]/ensure: ensure changed 'stopped' to 'running' (corrective)
Info: /Stage[main]/Snmp/Service[snmpd]: Unscheduling refresh on Service[snmpd]

Here are my simple manifests:
$ cat manifests/snmpd.pp

#class sprd_snmp
class sprd_snmp::snmpd {

  create_resources('class', { 'snmp' => lookup("${module_name}::snmpd", Hash, hash, {}) })

}

$ cat manifests/client.pp

#class sprd_snmp
class sprd_snmp::client {

  create_resources('class', { 'snmp::client' => lookup("${module_name}::client", Hash, hash, {}) })

}

snmpd.pp is included to the keepalived hosts and client.pp to the monitoring host.

Can I stop this behavior? I actually need snmpd to be running on the keepalived VM's only?

Thanks

@3c2b2ff5
Copy link
Author

I forked client.pp

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant