\\
On May 9, 2014 3:13 PM, wrote:
> Today's topic summary
>
> Group: http://groups.google.com/group/puppet-users/topics
>
>- Error 400 on SERVER: no 'environments' in
>{:root_environment=>#@name=:"*root*", @manifest="/usr/share/puppet/rack/puppetmasterd",
>@modulepath=[]> <#145e
Hi All!
I want to grant spetial permissions on some core files. So it would be nice
to use something like
file { "/var/lib/monitorium/core*" :
mode => 0644,
}
But that obviously doesn't work. Any people with the same problem i've
googled used some workarounds like managing dire
Unfortunately no. It uses cached catalog only if puppet master returns
error code. If it is completely unavaliable agent just does nothing.
Logs contain something like
>>>
2013-02-13T18:02:09.416421+04:00 distbuilder-b puppet-agent[1432]: Puppet
--listen / kick is deprecated. See
http://links.pu
Hi All!
I do manage some hosts with puppet and it's pretty great.
But among those hosts htere are some boxes that are sometimes taken away
from my network, used for demonstrations somewhere outside and return back.
And I want puppet to manage those hosts even when they are away and alone.
And of
