[Puppet Users] Failed to retrieve current state of resource error on one module

2010-06-17 Thread Aaron Blew
I'm getting the following errors in the module I'm writing to maintain my snmpd configurations (this is a mis of verbose and normal errors): err: //snmp/File[/etc/sysconfig/snmpd.options]: Failed to retrieve current state of resource: Could not retrieve information from source(s) puppet:///snmp/sn

[Puppet Users] Re: Failed to retrieve current state of resource error on one module

2010-06-18 Thread Aaron Blew
To follow up, I had absolutely been looking at the problem for too long. The filenames were snmpd.conf and snmpd.options, so I was just missing the d. -Aaron On Thu, Jun 17, 2010 at 4:44 PM, Aaron Blew wrote: > I'm getting the following errors in the module I'm writing to mainta

[Puppet Users] Interesting "Bad Certificate" Problem

2010-07-01 Thread Aaron Blew
All, I'm having an interesting certificate problem with a host I provisioned today. The host was provisioned and puppet was installed as part of the post-os provisioning process. After I signed the certificate I see the following on the client side: [r...@client ~]# puppetd --verbose --no-daemon

[Puppet Users] Re: Cannot get puppetlabs-haproxy to do what I want

2013-03-24 Thread Aaron Blew
I'm running into this issue as well, but I can't figure out what James changed in order to get his setup working. Here's what I'm calling from within one of my modules: #Node 1 - Load balancer: #... class { "haproxy": } haproxy::listen { "beanstalk00":ipaddress => $::ipaddress