Luke Kanies wrote:
> You've almost assuredly come across some kind of internal race
Wheeee!
> condition, albeit one I've not seen before. We've refactored all of
> this code in 0.25 (thankfully), but the 0.24 code paths for getting
> checksum and content information around was, um, horrible.
What I find really odd is why the checksum value and the content checksum
value come out to two different values, in a situation where there shouldn't
be any changes.
> The confusing thing is why you're getting this on some hosts but not
> others. Maybe try removing or editing the state file, to remove the
> stored info about the ntp.conf?
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.
--
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
-~----------~----~----~----~------~----~------~--~---
