Puppet users - May 2009 - Dealing with connection issues with puppet master...

Hi all,

Over the weekend, I had an issue with Puppet not being able to
communicate with its master...
Basically, Puppet went somewhat nuts once it couldn''t communicate,
with the following
things happening:

 - It started using a cached version - Obviously can shut this off
with usecacheonfailure=false in
   puppet.conf...
 - The tagmail reports started spamming the mail server - to the tune
of 1000+ messages every
    few minutes. I''ve temporarily disabled tagmail, as this
"feature"
of reports is not overly useful...
 - node YAML files on puppet master get corrupted...

The bigger issue is the second one... I like what tagmail does, and it
is a useful option when it behaves...
However it appears that it thinks that the reporting function has
failed somehow, so reattempts
it, then gets stuck repeating the reporting section until someone
comes along and kills it... It seems
to re-run all reports - not just the tagmail one...

Has anyone else seen this? What have people done to stop it going
nuts? Am using 0.24.8, by
the way...

The other issue I saw was that the node yaml file on the master seems
to get corrupted sometimes,
and when it does, Puppet doesn''t handle it very well... Solution is to
manually delete the file so that it
will refresh. Can puppet refresh the YAML file automatically if it
detects a problem with the node facts?
Will submit a bugreport for this one...

thanks,

Greg
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---