Recently, through no obvious change that I can find, I started getting these
messages on each puppet run on two hosts:
Sat May 16 16:52:17 -0400 2009
//Node[fedora.wpi.edu]/ntp_client/File[/etc/ntp.conf]/checksum (notice):
checksum changed ''{md5}cf294ce81a023d1cda9bbaa7ac359c2c'' to
''{md5}8bca22fcbc96b285185621d23d82b1f4''
Sat May 16 16:52:17 -0400 2009
//Node[fedora.wpi.edu]/ntp_client/File[/etc/ntp.conf] (notice): Filebucketed
to backups with sum 8bca22fcbc96b285185621d23d82b1f4
Sat May 16 16:52:17 -0400 2009
//Node[fedora.wpi.edu]/ntp_client/File[/etc/ntp.conf]/content (notice):
content changed ''{md5}8bca22fcbc96b285185621d23d82b1f4'' to
''{md5}cf294ce81a023d1cda9bbaa7ac359c2c''
Sat May 16 16:52:18 -0400 2009 //Node[fedora.wpi.edu]/ntp_base/Service[ntpd]
(notice): Triggering ''refresh'' from 2 dependencies
So first the checksum changes from A to B, then the file contents change from
B to A. Each of these changes then triggers a refresh on the service that
subscribes to the file.
The systems are both running CentOS 5.3, with puppet 0.24.8, though I have
other systems with same OS and puppet version that are including the same
class, but not showing the same oddity.
I''ve included the relevant puppet classes below; the nodes in question
include
the ntp_client class. Does anyone have any idea about what the heck might be
going on?
class ntp_base {
package { ntp:
ensure => installed
}
service { ntpd:
enable => true,
ensure => running,
require => [Package[ntp],
File["/etc/ntp.conf"],
File["/etc/ntp/step-tickers"]]
}
}
class ntp_client inherits ntp_base {
file { "/etc/ntp.conf":
ensure => file,
owner => root,
group => root,
mode => 644,
content => "restrict default ignore
restrict 127.0.0.1
driftfile /var/lib/ntp/drift
broadcastdelay 0.008
authenticate yes
keys /etc/ntp/keys
restrict 130.215.144.33 nomodify notrap noquery
restrict 130.215.32.18 nomodify notrap noquery
restrict 130.215.39.18 nomodify notrap noquery
server 130.215.144.33
server 130.215.32.18
server 130.215.39.18
",
require => Package[ntp],
notify => Service[ntpd]
}
file { "/etc/ntp/step-tickers":
ensure => file,
owner => root,
group => root, mode => 644,
content => "130.215.144.33
130.215.32.18
130.215.39.18
",
require => Package[ntp]
}
}
--
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
That does seem weird. It almost seems like you have 2 file resources somehow managing the same file. Maybe inspecting the graphs (--graph makes dot files) will help? Can you do a run with --debug and see if we can''t get diffs for the intermediate change? On Sat, May 16, 2009 at 3:29 PM, Frank Sweetser <fs@wpi.edu> wrote:> > > Recently, through no obvious change that I can find, I started getting > these > messages on each puppet run on two hosts: > > Sat May 16 16:52:17 -0400 2009 > //Node[fedora.wpi.edu]/ntp_client/File[/etc/ntp.conf]/checksum (notice): > checksum changed ''{md5}cf294ce81a023d1cda9bbaa7ac359c2c'' to > ''{md5}8bca22fcbc96b285185621d23d82b1f4'' > > Sat May 16 16:52:17 -0400 2009 > //Node[fedora.wpi.edu]/ntp_client/File[/etc/ntp.conf] (notice): > Filebucketed > to backups with sum 8bca22fcbc96b285185621d23d82b1f4 > > Sat May 16 16:52:17 -0400 2009 > //Node[fedora.wpi.edu]/ntp_client/File[/etc/ntp.conf]/content (notice): > content changed ''{md5}8bca22fcbc96b285185621d23d82b1f4'' to > ''{md5}cf294ce81a023d1cda9bbaa7ac359c2c'' > > Sat May 16 16:52:18 -0400 2009 //Node[fedora.wpi.edu > ]/ntp_base/Service[ntpd] > (notice): Triggering ''refresh'' from 2 dependencies > > So first the checksum changes from A to B, then the file contents change > from > B to A. Each of these changes then triggers a refresh on the service that > subscribes to the file. > > The systems are both running CentOS 5.3, with puppet 0.24.8, though I have > other systems with same OS and puppet version that are including the same > class, but not showing the same oddity. > > I''ve included the relevant puppet classes below; the nodes in question > include > the ntp_client class. Does anyone have any idea about what the heck might > be > going on? > > class ntp_base { > > package { ntp: > ensure => installed > } > > service { ntpd: > enable => true, > ensure => running, > require => [Package[ntp], > File["/etc/ntp.conf"], > File["/etc/ntp/step-tickers"]] > } > > } > > class ntp_client inherits ntp_base { > > file { "/etc/ntp.conf": > ensure => file, > owner => root, > group => root, > mode => 644, > content => "restrict default ignore > restrict 127.0.0.1 > driftfile /var/lib/ntp/drift > broadcastdelay 0.008 > authenticate yes > keys /etc/ntp/keys > restrict 130.215.144.33 nomodify notrap noquery > restrict 130.215.32.18 nomodify notrap noquery > restrict 130.215.39.18 nomodify notrap noquery > server 130.215.144.33 > server 130.215.32.18 > server 130.215.39.18 > ", > require => Package[ntp], > notify => Service[ntpd] > } > > file { "/etc/ntp/step-tickers": > ensure => file, > owner => root, > group => root, mode => 644, > content => "130.215.144.33 > 130.215.32.18 > 130.215.39.18 > ", > require => Package[ntp] > } > } > > > -- > 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On May 16, 2009, at 4:29 PM, Frank Sweetser wrote:> > > Recently, through no obvious change that I can find, I started > getting these > messages on each puppet run on two hosts: > > Sat May 16 16:52:17 -0400 2009 > //Node[fedora.wpi.edu]/ntp_client/File[/etc/ntp.conf]/checksum > (notice): > checksum changed ''{md5}cf294ce81a023d1cda9bbaa7ac359c2c'' to > ''{md5}8bca22fcbc96b285185621d23d82b1f4'' > > Sat May 16 16:52:17 -0400 2009 > //Node[fedora.wpi.edu]/ntp_client/File[/etc/ntp.conf] (notice): > Filebucketed > to backups with sum 8bca22fcbc96b285185621d23d82b1f4 > > Sat May 16 16:52:17 -0400 2009 > //Node[fedora.wpi.edu]/ntp_client/File[/etc/ntp.conf]/content > (notice): > content changed ''{md5}8bca22fcbc96b285185621d23d82b1f4'' to > ''{md5}cf294ce81a023d1cda9bbaa7ac359c2c'' > > Sat May 16 16:52:18 -0400 2009 //Node[fedora.wpi.edu]/ntp_base/ > Service[ntpd] > (notice): Triggering ''refresh'' from 2 dependencies > > So first the checksum changes from A to B, then the file contents > change from > B to A. Each of these changes then triggers a refresh on the > service that > subscribes to the file.You''ve almost assuredly come across some kind of internal race 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. 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? -- Happiness is not achieved by the conscious pursuit of happiness; it is generally the by-product of other activities. -- Aldous Huxley --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Luke Kanies wrote:> You''ve almost assuredly come across some kind of internal raceWheeee!> 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---