No such file or directory errors about puppet-snmp HOT 10 CLOSED

@blackknight36 What versions of Puppet, Puppet server, and OS are we dealing with? Which version of the razorsedge/snmp module?

from puppet-snmp.

@razorsedge We're running puppetserver 2.7.2 with puppet-agent 1.9.10 on CentOS 7.2. I've also seen this error on Fedora based systems. I believe the issue is that the snmp::client class attempts to create a config file before the /etc/snmp directory exists. This directory is provided by the net-snmp package so it may be possible to fix this by adding a package requirement on the file resource.

from puppet-snmp.

@blackknight36 Odd. I'm looking at the latest code and the File['snmp.conf'] is using a require as long as you are not on Suse. Either the $req is not getting set, or maybe Puppet 4 has issues with package aliases.

from puppet-snmp.

I'll have to set up a VM and run some more tests. The error only occurs on the first puppet run, once the /etc/snmp directory is created the error goes away.

from puppet-snmp.

I believe I see the issue. $req is set to require the snmp-client package which does not create the /etc/snmp directory. /etc/snmp is provided by the net-snmp package on redhat based systems as shown by the rpm command.

username@dev27:/etc/snmp$ rpm -qf .
net-snmp-5.7.3-13.fc25.x86_64

$req should most likely be changed to $snmp::params::package_name since that is the correct package which manages the directory.

from puppet-snmp.

I've submitted PR #98 which should fix this on Redhat and Fedora based systems.

from puppet-snmp.

I'm seeing this too. Since the PR has been merged, is there an ETA for when this can hit the forge?

from puppet-snmp.

I hope to get this pushed to the Forge by this weekend.

from puppet-snmp.

Closed by #98

from puppet-snmp.

3.8.0 has been pushed to the Forge.

from puppet-snmp.