Frank Sweetser wrote:
> Purging out the client state did indeed fix the glitch on one of the
> problematic systems. I made a copy of /var/lib/puppet from when the
> problem was occurring, and have another system still generating the
> problem, so let me know if you want any of it gathered up for debugging
> purposes.
Well, I seem to have spoken too soon. After a while, puppet went back to the
same behavior. I took a look at the graph files, as suggested by Andrew, and
didn't find anything obviously wrong, but that doesn't mean much as I wouldn't
be completely sure what to look for anyway.
Any other suggestions?
--
Frank Sweetser fs at wpi.edu | For every problem, there is a solution that
WPI Senior Network Engineer | is simple, elegant, and wrong. - HL Mencken
GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC
--~--~---------~--~----~------------~-------~--~----~
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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
