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 <f...@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+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to