your puppet client is hung, which is why the kick
isn't working. So the problem isn't the kick, it's the client state.
On Jan 2, 2012, at 7:51 AM, Pavel Weber wrote:
I have exactly the same problem you described. Have you got the
solution for this? I didn't find any reply for
Hi Mario,
I have exactly the same problem you described. Have you got the solution
for this? I didn't find any reply for your question. What we found that
there is the puppetdlock file in directory: /var/lib/puppet/state on
the host. If the file is there then it shows the message while runn
|Hi,
After many attempts we found that the value of path variable in the fileserver.conf has
to end up with "files". Actually I didn't find any place
where this is explicitly documented. Why it is important to have the "files" ending and
not just arbitrary directory name? Another thing is "moun
Hi All,
I've started with Puppet recently. So maybe it is a simple problem, but
could not find out up to now the solution. I just want to print out the
debug/log message in client report.
The only way I found is to use notify for this purpose like:
class repo {
notify {"The log message":}
