I'm interested, and I may have a co-worker or two interested as well.
Thanks!
- Jeff
On 02/07/2012 09:04 PM, Dan Bode wrote:
Hi Austin Puppet Users,
I will be in the area in a few weeks and I would like to try to get some
of the local users together to talk Puppet and have a few beers.
Curio
I don't think you should be specifying the "files" part of the source path:
Try:
source => puppet:///modules/ntp/ntp.conf.debian
- Jeff
On 06/20/2011 06:12 PM, Craig White wrote:
I don't know if it is or isn't being included but the -d -e were certainly
useful bits...
err: /Stage[main]/Ntp
We're a Debian shop, with our own internal repository for controlling
packages. We use the unattended-upgrades package to perform upgrades and
use puppet to instantiate the whole process using a variant of the
recipe at the bottom of this page:
http://reductivelabs.com/trac/puppet/wiki/Recipes
We had this issue while we were using webrick and ended up with the
following in cron running every 15 minutes:
if [ `/usr/bin/puppetlast |grep -v puppetlast |sort -n -k 4 |head -n
1|awk '{print \$4}'` -ge 15 ]; then /etc/init.d/puppetmaster restart ;fi
- Jeff
On 09/22/2009 02:38 PM, Pete Eme
Something like the following should work:
exec { subscribe-echo:
command => "/usr/bin/apt-get -q -q update && touch
/home/test ",
logoutput => false,
refreshonly => true,
subscribe => file["/etc/apt/sources.list"]
We have had this happening occasionally (approx. 1 out of ~120 VMs,
every other week or so) on our OpenVZ VMs as well.
We're running Debian Etch, and over the past week upgraded to 0.24.5-3,
so I'm keeping an eye on things to see if that resolved it for us.
- Jeff
Paul Lathrop wrote:
> On Mon
My WEBrick's masterhttp.log file was telling a slightly different story:
[2009-05-21 11:41:22] ERROR OpenSSL::SSL::SSLError: sslv3 alert bad
certificate
/usr/lib/ruby/1.8/openssl/ssl.rb:122:in `accept'
As it turned out, in my /etc/puppet/manifest/site.pp file the filebucket
configurat
Pretty sure I ran across this same issue. Try pulling the :: out of the
variable name. e.g. %{environment}
- Jeff
On 05/08/2014 11:21 AM, Israel Calvete wrote:
Yes, hiera file is in /etc/puppet/hiera.yaml
On Thursday, May 8, 2014 6:15:34 PM UTC+2, Brendan O'Bra wrote:
Where is your hiera
We're using eyaml in our masterless setup as well. We've got our
hiera.yaml in /etc/puppet, so we don't need to specify the
--hiera_config with puppet apply.
True that distributing the private key(s) was an interesting issue to solve.
- Jeff
On 03/11/2015 08:30 AM, Alessandro Franceschi wrote:
s setup?
Thanks for the reply.
Heinz
On Wednesday, March 11, 2015 at 9:43:02 AM UTC-4, jeff Adams wrote:
We're using eyaml in our masterless setup as well. We've got our
hiera.yaml in /etc/puppet, so we don't need to specify the
--hiera_config with puppet apply.
We've settled on a git repo per module, then using r10k (thinking about
moving to librarian-puppet) to pull modules from git onto our nodes.
This happens in the wrapper script that we run out of cron that also
executes the puppet apply.
The advantage here is that if you happen to "break" puppet,
11 matches
Mail list logo
