Digant C Kasundra
2009-Dec-03 22:31 UTC
[Puppet Users] Timestamps need to be in sync on all puppetmasters?
Hey guys, We''re using multiple puppetmasters and I could have sworn I had uncovered an issue once where if a file had a different timestamp on two puppetmasters, clients would keep replacing the file depending on which puppetmaster they talked to because the clients thought the files were changing. But I''ve been unable to reproduce this problem. Is this only an issue in certain situations? We''re not using the checksum parameter to tell file resources to use timestamps and the type references seems to indicate that the default is md5 but I could have sworn I uncovered the aforementioned issue before but cannot for the life of me replicate it now. Anyone else know what I''m talking about? -- Digant C Kasundra <digant@stanford.edu> Technical Lead, ITS Unix Systems and Applications, Stanford University -- 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.
Tony G.
2009-Dec-04 03:43 UTC
Re: [Puppet Users] Timestamps need to be in sync on all puppetmasters?
I''ve see this very often but not sure if this is the issue you are
describing:
Dec 4 03:36:19 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib]/checksum) checksum changed ''{mtime}Fri Oct
30
11:05:32 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:50 +0000
2009''
Dec 4 03:36:20 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet]/checksum) checksum changed
''{mtime}Fri
Oct 30 11:05:33 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:50
+0000 2009''
Dec 4 03:36:21 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/type]/checksum) checksum changed
''{mtime}Fri Oct 30 11:05:49 -0700 2009'' to
''{mtime}Fri Oct 30 18:05:50 +0000
2009''
Dec 4 03:36:24 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/parser]/checksum) checksum changed
''{mtime}Fri Oct 30 11:05:50 -0700 2009'' to
''{mtime}Fri Oct 30 18:05:50 +0000
2009''
Dec 4 03:36:29 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/parser/functions]/checksum) checksum
changed ''{mtime}Fri Oct 30 11:05:50 -0700 2009'' to
''{mtime}Fri Oct 30
18:05:50 +0000 2009''
Dec 4 03:36:29 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider]/checksum) checksum changed
''{mtime}Fri Oct 30 11:05:33 -0700 2009'' to
''{mtime}Fri Oct 30 18:05:48 +0000
2009''
Dec 4 03:36:36 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/package]/checksum) checksum
changed ''{mtime}Fri Oct 30 11:05:35 -0700 2009'' to
''{mtime}Fri Oct 30
18:05:48 +0000 2009''
Dec 4 03:37:00 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/sysctl]/checksum) checksum
changed ''{mtime}Fri Oct 30 11:05:48 -0700 2009'' to
''{mtime}Fri Oct 30
18:05:49 +0000 2009''
Dec 4 03:37:01 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/volumegroup]/checksum) checksum
changed ''{mtime}Fri Oct 30 11:05:34 -0700 2009'' to
''{mtime}Fri Oct 30
18:05:35 +0000 2009''
Dec 4 03:37:06 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/logicalvolume]/checksum) checksum
changed ''{mtime}Fri Oct 30 11:05:33 -0700 2009'' to
''{mtime}Fri Oct 30
18:05:34 +0000 2009''
Dec 4 03:37:07 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/physicalvolume]/checksum)
checksum changed ''{mtime}Fri Oct 30 11:05:34 -0700 2009'' to
''{mtime}Fri Oct
30 18:05:34 +0000 2009''
Dec 4 03:37:15 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/facter]/checksum) checksum changed
''{mtime}Fri
Oct 30 11:05:50 -0700 2009'' to ''{mtime}Tue Nov 03 08:00:05
+0000 2009''
Dec 4 03:37:33 puppetclient puppetd[16163]: Starting catalog run
Dec 4 03:39:46 puppetclient puppetd[16163]: Finished catalog run in 133.44
seconds
I''ve not been able to look on what is causing it, I belive
it''s coming
after we change the environment the puppetclient is pointing to, although we
use the same puppetmaster to use different environments(dev, prod).
Thoughts?
Thanks
On Thu, Dec 3, 2009 at 2:31 PM, Digant C Kasundra
<digant@stanford.edu>wrote:
> Hey guys,
>
> We''re using multiple puppetmasters and I could have sworn I had
uncovered
> an issue once where if a file had a different timestamp on two
> puppetmasters, clients would keep replacing the file depending on which
> puppetmaster they talked to because the clients thought the files were
> changing. But I''ve been unable to reproduce this problem. Is
this only an
> issue in certain situations? We''re not using the checksum
parameter to tell
> file resources to use timestamps and the type references seems to indicate
> that the default is md5 but I could have sworn I uncovered the
> aforementioned issue before but cannot for the life of me replicate it now.
> Anyone else know what I''m talking about?
>
>
> --
> Digant C Kasundra <digant@stanford.edu>
> Technical Lead, ITS Unix Systems and Applications, Stanford University
>
> --
>
> 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<puppet-users%2Bunsubscribe@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
>
--
Tony
--
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.
Digant C Kasundra
2009-Dec-08 20:43 UTC
Re: [Puppet Users] Timestamps need to be in sync on all puppetmasters?
This is similar to what I''m talking about. It looks like this resource is specifically using modified time as the "checksum." Is this something you''ve configured or is this a default of those directories as something internal to puppet. ----- "Tony G." <tonysk8@gmail.com> wrote:> I''ve see this very often but not sure if this is the issue you are > describing: > > Dec 4 03:36:19 puppetclient puppetd[16163]: > (/File[/var/lib/puppet/lib]/checksum) checksum changed ''{mtime}Fri Oct > 30 11:05:32 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:50 +0000 2009'' > Dec 4 03:36:20 puppetclient puppetd[16163]: > (/File[/var/lib/puppet/lib/puppet]/checksum) checksum changed > ''{mtime}Fri Oct 30 11:05:33 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:50 > +0000 2009'' > Dec 4 03:36:21 puppetclient puppetd[16163]: > (/File[/var/lib/puppet/lib/puppet/type]/checksum) checksum changed > ''{mtime}Fri Oct 30 11:05:49 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:50 > +0000 2009'' > Dec 4 03:36:24 puppetclient puppetd[16163]: > (/File[/var/lib/puppet/lib/puppet/parser]/checksum) checksum changed > ''{mtime}Fri Oct 30 11:05:50 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:50 > +0000 2009'' > Dec 4 03:36:29 puppetclient puppetd[16163]: > (/File[/var/lib/puppet/lib/puppet/parser/functions]/checksum) checksum > changed ''{mtime}Fri Oct 30 11:05:50 -0700 2009'' to ''{mtime}Fri Oct 30 > 18:05:50 +0000 2009'' > Dec 4 03:36:29 puppetclient puppetd[16163]: > (/File[/var/lib/puppet/lib/puppet/provider]/checksum) checksum changed > ''{mtime}Fri Oct 30 11:05:33 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:48 > +0000 2009'' > Dec 4 03:36:36 puppetclient puppetd[16163]: > (/File[/var/lib/puppet/lib/puppet/provider/package]/checksum) checksum > changed ''{mtime}Fri Oct 30 11:05:35 -0700 2009'' to ''{mtime}Fri Oct 30 > 18:05:48 +0000 2009'' > Dec 4 03:37:00 puppetclient puppetd[16163]: > (/File[/var/lib/puppet/lib/puppet/provider/sysctl]/checksum) checksum > changed ''{mtime}Fri Oct 30 11:05:48 -0700 2009'' to ''{mtime}Fri Oct 30 > 18:05:49 +0000 2009'' > Dec 4 03:37:01 puppetclient puppetd[16163]: > (/File[/var/lib/puppet/lib/puppet/provider/volumegroup]/checksum) > checksum changed ''{mtime}Fri Oct 30 11:05:34 -0700 2009'' to > ''{mtime}Fri Oct 30 18:05:35 +0000 2009'' > Dec 4 03:37:06 puppetclient puppetd[16163]: > (/File[/var/lib/puppet/lib/puppet/provider/logicalvolume]/checksum) > checksum changed ''{mtime}Fri Oct 30 11:05:33 -0700 2009'' to > ''{mtime}Fri Oct 30 18:05:34 +0000 2009'' > Dec 4 03:37:07 puppetclient puppetd[16163]: > (/File[/var/lib/puppet/lib/puppet/provider/physicalvolume]/checksum) > checksum changed ''{mtime}Fri Oct 30 11:05:34 -0700 2009'' to > ''{mtime}Fri Oct 30 18:05:34 +0000 2009'' > Dec 4 03:37:15 puppetclient puppetd[16163]: > (/File[/var/lib/puppet/lib/facter]/checksum) checksum changed > ''{mtime}Fri Oct 30 11:05:50 -0700 2009'' to ''{mtime}Tue Nov 03 08:00:05 > +0000 2009'' > Dec 4 03:37:33 puppetclient puppetd[16163]: Starting catalog run > Dec 4 03:39:46 puppetclient puppetd[16163]: Finished catalog run in > 133.44 seconds > > I''ve not been able to look on what is causing it, I belive it''s coming > after we change the environment the puppetclient is pointing to, > although we use the same puppetmaster to use different > environments(dev, prod). > > Thoughts? > > Thanks > > > On Thu, Dec 3, 2009 at 2:31 PM, Digant C Kasundra < > digant@stanford.edu > wrote: > > > Hey guys, > > We''re using multiple puppetmasters and I could have sworn I had > uncovered an issue once where if a file had a different timestamp on > two puppetmasters, clients would keep replacing the file depending on > which puppetmaster they talked to because the clients thought the > files were changing. But I''ve been unable to reproduce this problem. > Is this only an issue in certain situations? We''re not using the > checksum parameter to tell file resources to use timestamps and the > type references seems to indicate that the default is md5 but I could > have sworn I uncovered the aforementioned issue before but cannot for > the life of me replicate it now. Anyone else know what I''m talking > about? > > > -- > Digant C Kasundra < digant@stanford.edu > > Technical Lead, ITS Unix Systems and Applications, Stanford University > > -- > > 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 . > > > > > > -- > Tony > > > > > -- 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.-- Digant C Kasundra <digant@stanford.edu> Technical Lead, ITS Unix Systems and Applications, Stanford University -- 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.
Silviu Paragina
2009-Dec-08 21:50 UTC
Re: [Puppet Users] Timestamps need to be in sync on all puppetmasters?
The log you posted looks like a bad date/time timezone conversion, are all the clients/puppetmasters on the same timezone? Notice that the dates are actually identical but one is in utc the other US eastern (I think). Silviu On 08.12.2009 22:43, Digant C Kasundra wrote:> This is similar to what I''m talking about. It looks like this resource is specifically using modified time as the "checksum." Is this something you''ve configured or is this a default of those directories as something internal to puppet. > > ----- "Tony G."<tonysk8@gmail.com> wrote: > > >> I''ve see this very often but not sure if this is the issue you are >> describing: >> >> Dec 4 03:36:19 puppetclient puppetd[16163]: >> (/File[/var/lib/puppet/lib]/checksum) checksum changed ''{mtime}Fri Oct >> 30 11:05:32 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:50 +0000 2009'' >> Dec 4 03:36:20 puppetclient puppetd[16163]: >> (/File[/var/lib/puppet/lib/puppet]/checksum) checksum changed >> ''{mtime}Fri Oct 30 11:05:33 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:50 >> +0000 2009'' >> Dec 4 03:36:21 puppetclient puppetd[16163]: >> (/File[/var/lib/puppet/lib/puppet/type]/checksum) checksum changed >> ''{mtime}Fri Oct 30 11:05:49 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:50 >> +0000 2009'' >> Dec 4 03:36:24 puppetclient puppetd[16163]: >> (/File[/var/lib/puppet/lib/puppet/parser]/checksum) checksum changed >> ''{mtime}Fri Oct 30 11:05:50 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:50 >> +0000 2009'' >> Dec 4 03:36:29 puppetclient puppetd[16163]: >> (/File[/var/lib/puppet/lib/puppet/parser/functions]/checksum) checksum >> changed ''{mtime}Fri Oct 30 11:05:50 -0700 2009'' to ''{mtime}Fri Oct 30 >> 18:05:50 +0000 2009'' >> Dec 4 03:36:29 puppetclient puppetd[16163]: >> (/File[/var/lib/puppet/lib/puppet/provider]/checksum) checksum changed >> ''{mtime}Fri Oct 30 11:05:33 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:48 >> +0000 2009'' >> Dec 4 03:36:36 puppetclient puppetd[16163]: >> (/File[/var/lib/puppet/lib/puppet/provider/package]/checksum) checksum >> changed ''{mtime}Fri Oct 30 11:05:35 -0700 2009'' to ''{mtime}Fri Oct 30 >> 18:05:48 +0000 2009'' >> Dec 4 03:37:00 puppetclient puppetd[16163]: >> (/File[/var/lib/puppet/lib/puppet/provider/sysctl]/checksum) checksum >> changed ''{mtime}Fri Oct 30 11:05:48 -0700 2009'' to ''{mtime}Fri Oct 30 >> 18:05:49 +0000 2009'' >> Dec 4 03:37:01 puppetclient puppetd[16163]: >> (/File[/var/lib/puppet/lib/puppet/provider/volumegroup]/checksum) >> checksum changed ''{mtime}Fri Oct 30 11:05:34 -0700 2009'' to >> ''{mtime}Fri Oct 30 18:05:35 +0000 2009'' >> Dec 4 03:37:06 puppetclient puppetd[16163]: >> (/File[/var/lib/puppet/lib/puppet/provider/logicalvolume]/checksum) >> checksum changed ''{mtime}Fri Oct 30 11:05:33 -0700 2009'' to >> ''{mtime}Fri Oct 30 18:05:34 +0000 2009'' >> Dec 4 03:37:07 puppetclient puppetd[16163]: >> (/File[/var/lib/puppet/lib/puppet/provider/physicalvolume]/checksum) >> checksum changed ''{mtime}Fri Oct 30 11:05:34 -0700 2009'' to >> ''{mtime}Fri Oct 30 18:05:34 +0000 2009'' >> Dec 4 03:37:15 puppetclient puppetd[16163]: >> (/File[/var/lib/puppet/lib/facter]/checksum) checksum changed >> ''{mtime}Fri Oct 30 11:05:50 -0700 2009'' to ''{mtime}Tue Nov 03 08:00:05 >> +0000 2009'' >> Dec 4 03:37:33 puppetclient puppetd[16163]: Starting catalog run >> Dec 4 03:39:46 puppetclient puppetd[16163]: Finished catalog run in >> 133.44 seconds >> >> I''ve not been able to look on what is causing it, I belive it''s coming >> after we change the environment the puppetclient is pointing to, >> although we use the same puppetmaster to use different >> environments(dev, prod). >> >> Thoughts? >> >> Thanks >> >> >> On Thu, Dec 3, 2009 at 2:31 PM, Digant C Kasundra< >> digant@stanford.edu> wrote: >> >> >> Hey guys, >> >> We''re using multiple puppetmasters and I could have sworn I had >> uncovered an issue once where if a file had a different timestamp on >> two puppetmasters, clients would keep replacing the file depending on >> which puppetmaster they talked to because the clients thought the >> files were changing. But I''ve been unable to reproduce this problem. >> Is this only an issue in certain situations? We''re not using the >> checksum parameter to tell file resources to use timestamps and the >> type references seems to indicate that the default is md5 but I could >> have sworn I uncovered the aforementioned issue before but cannot for >> the life of me replicate it now. Anyone else know what I''m talking >> about? >> >> >> -- >> Digant C Kasundra< digant@stanford.edu> >> Technical Lead, ITS Unix Systems and Applications, Stanford University >> >> -- >> >> 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 . >> >> >> >> >> >> -- >> Tony >> >> >> >> >> -- 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. >> >-- 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.
Tony G.
2009-Dec-09 01:21 UTC
Re: [Puppet Users] Timestamps need to be in sync on all puppetmasters?
Hi, They are supposed to have GMT: puppetmaster: $ date Wed Dec 9 00:59:02 *GMT* 2009 puppetclient: $ date Wed Dec 9 00:58:59 *GMT* 2009 But digging more I found this: puppetmaster: $ cat /etc/sysconfig/clock *ZONE="GMT"* *UTC=false* ARC=false puppetclient: $ cat /etc/sysconfig/clock *ZONE="US/Pacific"* *UTC=true* ARC=false But the timezone file in */etc/localtime* is the same on them: md5sum /usr/share/zoneinfo/* 2>/dev/null|grep $(md5sum /etc/localtime|cut -d" " -f1) fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT0 fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT-0 fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT+0 fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/Greenwich Could the /etc/sysconfig/clock file cause this? Thanks! On Tue, Dec 8, 2009 at 1:50 PM, Silviu Paragina <silviu@paragina.ro> wrote:> The log you posted looks like a bad date/time timezone conversion, are > all the clients/puppetmasters on the same timezone? > Notice that the dates are actually identical but one is in utc the other > US eastern (I think). > > > Silviu > > On 08.12.2009 22:43, Digant C Kasundra wrote: > > This is similar to what I''m talking about. It looks like this resource > is specifically using modified time as the "checksum." Is this something > you''ve configured or is this a default of those directories as something > internal to puppet. > > > > ----- "Tony G."<tonysk8@gmail.com> wrote: > > > > > >> I''ve see this very often but not sure if this is the issue you are > >> describing: > >> > >> Dec 4 03:36:19 puppetclient puppetd[16163]: > >> (/File[/var/lib/puppet/lib]/checksum) checksum changed ''{mtime}Fri Oct > >> 30 11:05:32 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:50 +0000 2009'' > >> Dec 4 03:36:20 puppetclient puppetd[16163]: > >> (/File[/var/lib/puppet/lib/puppet]/checksum) checksum changed > >> ''{mtime}Fri Oct 30 11:05:33 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:50 > >> +0000 2009'' > >> Dec 4 03:36:21 puppetclient puppetd[16163]: > >> (/File[/var/lib/puppet/lib/puppet/type]/checksum) checksum changed > >> ''{mtime}Fri Oct 30 11:05:49 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:50 > >> +0000 2009'' > >> Dec 4 03:36:24 puppetclient puppetd[16163]: > >> (/File[/var/lib/puppet/lib/puppet/parser]/checksum) checksum changed > >> ''{mtime}Fri Oct 30 11:05:50 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:50 > >> +0000 2009'' > >> Dec 4 03:36:29 puppetclient puppetd[16163]: > >> (/File[/var/lib/puppet/lib/puppet/parser/functions]/checksum) checksum > >> changed ''{mtime}Fri Oct 30 11:05:50 -0700 2009'' to ''{mtime}Fri Oct 30 > >> 18:05:50 +0000 2009'' > >> Dec 4 03:36:29 puppetclient puppetd[16163]: > >> (/File[/var/lib/puppet/lib/puppet/provider]/checksum) checksum changed > >> ''{mtime}Fri Oct 30 11:05:33 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:48 > >> +0000 2009'' > >> Dec 4 03:36:36 puppetclient puppetd[16163]: > >> (/File[/var/lib/puppet/lib/puppet/provider/package]/checksum) checksum > >> changed ''{mtime}Fri Oct 30 11:05:35 -0700 2009'' to ''{mtime}Fri Oct 30 > >> 18:05:48 +0000 2009'' > >> Dec 4 03:37:00 puppetclient puppetd[16163]: > >> (/File[/var/lib/puppet/lib/puppet/provider/sysctl]/checksum) checksum > >> changed ''{mtime}Fri Oct 30 11:05:48 -0700 2009'' to ''{mtime}Fri Oct 30 > >> 18:05:49 +0000 2009'' > >> Dec 4 03:37:01 puppetclient puppetd[16163]: > >> (/File[/var/lib/puppet/lib/puppet/provider/volumegroup]/checksum) > >> checksum changed ''{mtime}Fri Oct 30 11:05:34 -0700 2009'' to > >> ''{mtime}Fri Oct 30 18:05:35 +0000 2009'' > >> Dec 4 03:37:06 puppetclient puppetd[16163]: > >> (/File[/var/lib/puppet/lib/puppet/provider/logicalvolume]/checksum) > >> checksum changed ''{mtime}Fri Oct 30 11:05:33 -0700 2009'' to > >> ''{mtime}Fri Oct 30 18:05:34 +0000 2009'' > >> Dec 4 03:37:07 puppetclient puppetd[16163]: > >> (/File[/var/lib/puppet/lib/puppet/provider/physicalvolume]/checksum) > >> checksum changed ''{mtime}Fri Oct 30 11:05:34 -0700 2009'' to > >> ''{mtime}Fri Oct 30 18:05:34 +0000 2009'' > >> Dec 4 03:37:15 puppetclient puppetd[16163]: > >> (/File[/var/lib/puppet/lib/facter]/checksum) checksum changed > >> ''{mtime}Fri Oct 30 11:05:50 -0700 2009'' to ''{mtime}Tue Nov 03 08:00:05 > >> +0000 2009'' > >> Dec 4 03:37:33 puppetclient puppetd[16163]: Starting catalog run > >> Dec 4 03:39:46 puppetclient puppetd[16163]: Finished catalog run in > >> 133.44 seconds > >> > >> I''ve not been able to look on what is causing it, I belive it''s coming > >> after we change the environment the puppetclient is pointing to, > >> although we use the same puppetmaster to use different > >> environments(dev, prod). > >> > >> Thoughts? > >> > >> Thanks > >> > >> > >> On Thu, Dec 3, 2009 at 2:31 PM, Digant C Kasundra< > >> digant@stanford.edu> wrote: > >> > >> > >> Hey guys, > >> > >> We''re using multiple puppetmasters and I could have sworn I had > >> uncovered an issue once where if a file had a different timestamp on > >> two puppetmasters, clients would keep replacing the file depending on > >> which puppetmaster they talked to because the clients thought the > >> files were changing. But I''ve been unable to reproduce this problem. > >> Is this only an issue in certain situations? We''re not using the > >> checksum parameter to tell file resources to use timestamps and the > >> type references seems to indicate that the default is md5 but I could > >> have sworn I uncovered the aforementioned issue before but cannot for > >> the life of me replicate it now. Anyone else know what I''m talking > >> about? > >> > >> > >> -- > >> Digant C Kasundra< digant@stanford.edu> > >> Technical Lead, ITS Unix Systems and Applications, Stanford University > >> > >> -- > >> > >> 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<puppet-users%2Bunsubscribe@googlegroups.com>. > >> For more options, visit this group at > >> http://groups.google.com/group/puppet-users?hl=en . > >> > >> > >> > >> > >> > >> -- > >> Tony > >> > >> > >> > >> > >> -- 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<puppet-users%2Bunsubscribe@googlegroups.com> > . > >> For more options, visit this group at > >> http://groups.google.com/group/puppet-users?hl=en. > >> > > > > -- > > 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<puppet-users%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > >-- Tony -- 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.
Steven VanDevender
2009-Dec-09 01:38 UTC
Re: [Puppet Users] Timestamps need to be in sync on all puppetmasters?
Tony G. writes: > They are supposed to have GMT: In these modern times UTC is generally a better universal standard than GMT. > But the timezone file in */etc/localtime* is the same on them: > md5sum /usr/share/zoneinfo/* 2>/dev/null|grep $(md5sum /etc/localtime|cut > -d" " -f1) > fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT > fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT0 > fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT-0 > fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT+0 > fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/Greenwich > > Could the /etc/sysconfig/clock file cause this? UNIX time is based on the number of seconds since January 1, 1970 00:00 UTC. This is converted to local time for display based on the TZ environment variable, with /etc/localtime specifying the default local time conversions rule (and usually a copy or link to a corresponding rule file in /usr/share/zoneinfo). /etc/sysconfig/clock has only to do with management of the hardware clock. The ZONE setting in combination with the UTC boolean determine whether the hardware clock is treated as local time or UTC when the hardware clock is set from the UNIX clock during shutdown. For most server configurations it is advisable to manage the hardware clock in UTC (UTC=true). In particular this can avoid some problems with reboots around daylight savings time changes introducing 1 hour offsets. -- 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.
Silviu Paragina
2009-Dec-09 01:51 UTC
Re: [Puppet Users] Timestamps need to be in sync on all puppetmasters?
Try this ruby -e ''puts Time.at(0)'' In case ruby treats timezones different from how it should (how I think it should actually) Silviu On 09.12.2009 03:21, Tony G. wrote:> Hi, > > They are supposed to have GMT: > puppetmaster: > $ date > Wed Dec 9 00:59:02 *GMT* 2009 > puppetclient: > $ date > Wed Dec 9 00:58:59 *GMT* 2009 > > But digging more I found this: > puppetmaster: > $ cat /etc/sysconfig/clock > *ZONE="GMT"* > *UTC=false* > ARC=false > > puppetclient: > $ cat /etc/sysconfig/clock > *ZONE="US/Pacific"* > *UTC=true* > ARC=false > > > But the timezone file in //etc/localtime/ is the same on them: > md5sum /usr/share/zoneinfo/* 2>/dev/null|grep $(md5sum > /etc/localtime|cut -d" " -f1) > fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT > fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT0 > fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT-0 > fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT+0 > fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/Greenwich > > Could the /etc/sysconfig/clock file cause this? > > Thanks! > > On Tue, Dec 8, 2009 at 1:50 PM, Silviu Paragina <silviu@paragina.ro > <mailto:silviu@paragina.ro>> wrote: > > The log you posted looks like a bad date/time timezone conversion, are > all the clients/puppetmasters on the same timezone? > Notice that the dates are actually identical but one is in utc the > other > US eastern (I think). > > > Silviu > > On 08.12.2009 22:43, Digant C Kasundra wrote: > > This is similar to what I''m talking about. It looks like this > resource is specifically using modified time as the "checksum." > Is this something you''ve configured or is this a default of those > directories as something internal to puppet. > > > > ----- "Tony G."<tonysk8@gmail.com <mailto:tonysk8@gmail.com>> > wrote: > > > > > >> I''ve see this very often but not sure if this is the issue you are > >> describing: > >> > >> Dec 4 03:36:19 puppetclient puppetd[16163]: > >> (/File[/var/lib/puppet/lib]/checksum) checksum changed > ''{mtime}Fri Oct > >> 30 11:05:32 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:50 +0000 2009'' > >> Dec 4 03:36:20 puppetclient puppetd[16163]: > >> (/File[/var/lib/puppet/lib/puppet]/checksum) checksum changed > >> ''{mtime}Fri Oct 30 11:05:33 -0700 2009'' to ''{mtime}Fri Oct 30 > 18:05:50 > >> +0000 2009'' > >> Dec 4 03:36:21 puppetclient puppetd[16163]: > >> (/File[/var/lib/puppet/lib/puppet/type]/checksum) checksum changed > >> ''{mtime}Fri Oct 30 11:05:49 -0700 2009'' to ''{mtime}Fri Oct 30 > 18:05:50 > >> +0000 2009'' > >> Dec 4 03:36:24 puppetclient puppetd[16163]: > >> (/File[/var/lib/puppet/lib/puppet/parser]/checksum) checksum > changed > >> ''{mtime}Fri Oct 30 11:05:50 -0700 2009'' to ''{mtime}Fri Oct 30 > 18:05:50 > >> +0000 2009'' > >> Dec 4 03:36:29 puppetclient puppetd[16163]: > >> (/File[/var/lib/puppet/lib/puppet/parser/functions]/checksum) > checksum > >> changed ''{mtime}Fri Oct 30 11:05:50 -0700 2009'' to ''{mtime}Fri > Oct 30 > >> 18:05:50 +0000 2009'' > >> Dec 4 03:36:29 puppetclient puppetd[16163]: > >> (/File[/var/lib/puppet/lib/puppet/provider]/checksum) checksum > changed > >> ''{mtime}Fri Oct 30 11:05:33 -0700 2009'' to ''{mtime}Fri Oct 30 > 18:05:48 > >> +0000 2009'' > >> Dec 4 03:36:36 puppetclient puppetd[16163]: > >> (/File[/var/lib/puppet/lib/puppet/provider/package]/checksum) > checksum > >> changed ''{mtime}Fri Oct 30 11:05:35 -0700 2009'' to ''{mtime}Fri > Oct 30 > >> 18:05:48 +0000 2009'' > >> Dec 4 03:37:00 puppetclient puppetd[16163]: > >> (/File[/var/lib/puppet/lib/puppet/provider/sysctl]/checksum) > checksum > >> changed ''{mtime}Fri Oct 30 11:05:48 -0700 2009'' to ''{mtime}Fri > Oct 30 > >> 18:05:49 +0000 2009'' > >> Dec 4 03:37:01 puppetclient puppetd[16163]: > >> (/File[/var/lib/puppet/lib/puppet/provider/volumegroup]/checksum) > >> checksum changed ''{mtime}Fri Oct 30 11:05:34 -0700 2009'' to > >> ''{mtime}Fri Oct 30 18:05:35 +0000 2009'' > >> Dec 4 03:37:06 puppetclient puppetd[16163]: > >> (/File[/var/lib/puppet/lib/puppet/provider/logicalvolume]/checksum) > >> checksum changed ''{mtime}Fri Oct 30 11:05:33 -0700 2009'' to > >> ''{mtime}Fri Oct 30 18:05:34 +0000 2009'' > >> Dec 4 03:37:07 puppetclient puppetd[16163]: > >> > (/File[/var/lib/puppet/lib/puppet/provider/physicalvolume]/checksum) > >> checksum changed ''{mtime}Fri Oct 30 11:05:34 -0700 2009'' to > >> ''{mtime}Fri Oct 30 18:05:34 +0000 2009'' > >> Dec 4 03:37:15 puppetclient puppetd[16163]: > >> (/File[/var/lib/puppet/lib/facter]/checksum) checksum changed > >> ''{mtime}Fri Oct 30 11:05:50 -0700 2009'' to ''{mtime}Tue Nov 03 > 08:00:05 > >> +0000 2009'' > >> Dec 4 03:37:33 puppetclient puppetd[16163]: Starting catalog run > >> Dec 4 03:39:46 puppetclient puppetd[16163]: Finished catalog run in > >> 133.44 seconds > >> > >> I''ve not been able to look on what is causing it, I belive it''s > coming > >> after we change the environment the puppetclient is pointing to, > >> although we use the same puppetmaster to use different > >> environments(dev, prod). > >> > >> Thoughts? > >> > >> Thanks > >> > >> > >> On Thu, Dec 3, 2009 at 2:31 PM, Digant C Kasundra< > >> digant@stanford.edu <mailto:digant@stanford.edu>> wrote: > >> > >> > >> Hey guys, > >> > >> We''re using multiple puppetmasters and I could have sworn I had > >> uncovered an issue once where if a file had a different > timestamp on > >> two puppetmasters, clients would keep replacing the file > depending on > >> which puppetmaster they talked to because the clients thought the > >> files were changing. But I''ve been unable to reproduce this > problem. > >> Is this only an issue in certain situations? We''re not using the > >> checksum parameter to tell file resources to use timestamps and the > >> type references seems to indicate that the default is md5 but I > could > >> have sworn I uncovered the aforementioned issue before but > cannot for > >> the life of me replicate it now. Anyone else know what I''m talking > >> about? > >> > >> > >> -- > >> Digant C Kasundra< digant@stanford.edu > <mailto:digant@stanford.edu>> > >> Technical Lead, ITS Unix Systems and Applications, Stanford > University > >> > >> -- > >> > >> 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 <mailto:puppet-users@googlegroups.com> . > >> To unsubscribe from this group, send email to > >> puppet-users+unsubscribe@googlegroups.com > <mailto:puppet-users%2Bunsubscribe@googlegroups.com> . > >> For more options, visit this group at > >> http://groups.google.com/group/puppet-users?hl=en . > >> > >> > >> > >> > >> > >> -- > >> Tony > >> > >> > >> > >> > >> -- 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 <mailto:puppet-users@googlegroups.com>. > >> To unsubscribe from this group, send email to > >> puppet-users+unsubscribe@googlegroups.com > <mailto:puppet-users%2Bunsubscribe@googlegroups.com>. > >> For more options, visit this group at > >> http://groups.google.com/group/puppet-users?hl=en. > >> > > > > -- > > 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 > <mailto:puppet-users@googlegroups.com>. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com > <mailto:puppet-users%2Bunsubscribe@googlegroups.com>. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > > > > > -- > Tony > > -- > > 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.-- 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.
Ohad Levy
2009-Dec-09 01:53 UTC
Re: [Puppet Users] Timestamps need to be in sync on all puppetmasters?
if you want utc, you should use: ruby -e ''puts Time.at(0).utc'' cheers, Ohad On Wed, Dec 9, 2009 at 9:51 AM, Silviu Paragina <silviu@paragina.ro> wrote:> Try this > ruby -e ''puts Time.at(0)'' > In case ruby treats timezones different from how it should (how I think it > should actually) > > > Silviu > > > On 09.12.2009 03:21, Tony G. wrote: > > Hi, > > They are supposed to have GMT: > puppetmaster: > $ date > Wed Dec 9 00:59:02 *GMT* 2009 > puppetclient: > $ date > Wed Dec 9 00:58:59 *GMT* 2009 > > But digging more I found this: > puppetmaster: > $ cat /etc/sysconfig/clock > *ZONE="GMT"* > *UTC=false* > ARC=false > > puppetclient: > $ cat /etc/sysconfig/clock > *ZONE="US/Pacific"* > *UTC=true* > ARC=false > > > But the timezone file in */etc/localtime* is the same on them: > md5sum /usr/share/zoneinfo/* 2>/dev/null|grep $(md5sum /etc/localtime|cut > -d" " -f1) > fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT > fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT0 > fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT-0 > fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT+0 > fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/Greenwich > > Could the /etc/sysconfig/clock file cause this? > > Thanks! > > On Tue, Dec 8, 2009 at 1:50 PM, Silviu Paragina <silviu@paragina.ro>wrote: > >> The log you posted looks like a bad date/time timezone conversion, are >> all the clients/puppetmasters on the same timezone? >> Notice that the dates are actually identical but one is in utc the other >> US eastern (I think). >> >> >> Silviu >> >> On 08.12.2009 22:43, Digant C Kasundra wrote: >> > This is similar to what I''m talking about. It looks like this resource >> is specifically using modified time as the "checksum." Is this something >> you''ve configured or is this a default of those directories as something >> internal to puppet. >> > >> > ----- "Tony G."<tonysk8@gmail.com> wrote: >> > >> > >> >> I''ve see this very often but not sure if this is the issue you are >> >> describing: >> >> >> >> Dec 4 03:36:19 puppetclient puppetd[16163]: >> >> (/File[/var/lib/puppet/lib]/checksum) checksum changed ''{mtime}Fri Oct >> >> 30 11:05:32 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:50 +0000 2009'' >> >> Dec 4 03:36:20 puppetclient puppetd[16163]: >> >> (/File[/var/lib/puppet/lib/puppet]/checksum) checksum changed >> >> ''{mtime}Fri Oct 30 11:05:33 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:50 >> >> +0000 2009'' >> >> Dec 4 03:36:21 puppetclient puppetd[16163]: >> >> (/File[/var/lib/puppet/lib/puppet/type]/checksum) checksum changed >> >> ''{mtime}Fri Oct 30 11:05:49 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:50 >> >> +0000 2009'' >> >> Dec 4 03:36:24 puppetclient puppetd[16163]: >> >> (/File[/var/lib/puppet/lib/puppet/parser]/checksum) checksum changed >> >> ''{mtime}Fri Oct 30 11:05:50 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:50 >> >> +0000 2009'' >> >> Dec 4 03:36:29 puppetclient puppetd[16163]: >> >> (/File[/var/lib/puppet/lib/puppet/parser/functions]/checksum) checksum >> >> changed ''{mtime}Fri Oct 30 11:05:50 -0700 2009'' to ''{mtime}Fri Oct 30 >> >> 18:05:50 +0000 2009'' >> >> Dec 4 03:36:29 puppetclient puppetd[16163]: >> >> (/File[/var/lib/puppet/lib/puppet/provider]/checksum) checksum changed >> >> ''{mtime}Fri Oct 30 11:05:33 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:48 >> >> +0000 2009'' >> >> Dec 4 03:36:36 puppetclient puppetd[16163]: >> >> (/File[/var/lib/puppet/lib/puppet/provider/package]/checksum) checksum >> >> changed ''{mtime}Fri Oct 30 11:05:35 -0700 2009'' to ''{mtime}Fri Oct 30 >> >> 18:05:48 +0000 2009'' >> >> Dec 4 03:37:00 puppetclient puppetd[16163]: >> >> (/File[/var/lib/puppet/lib/puppet/provider/sysctl]/checksum) checksum >> >> changed ''{mtime}Fri Oct 30 11:05:48 -0700 2009'' to ''{mtime}Fri Oct 30 >> >> 18:05:49 +0000 2009'' >> >> Dec 4 03:37:01 puppetclient puppetd[16163]: >> >> (/File[/var/lib/puppet/lib/puppet/provider/volumegroup]/checksum) >> >> checksum changed ''{mtime}Fri Oct 30 11:05:34 -0700 2009'' to >> >> ''{mtime}Fri Oct 30 18:05:35 +0000 2009'' >> >> Dec 4 03:37:06 puppetclient puppetd[16163]: >> >> (/File[/var/lib/puppet/lib/puppet/provider/logicalvolume]/checksum) >> >> checksum changed ''{mtime}Fri Oct 30 11:05:33 -0700 2009'' to >> >> ''{mtime}Fri Oct 30 18:05:34 +0000 2009'' >> >> Dec 4 03:37:07 puppetclient puppetd[16163]: >> >> (/File[/var/lib/puppet/lib/puppet/provider/physicalvolume]/checksum) >> >> checksum changed ''{mtime}Fri Oct 30 11:05:34 -0700 2009'' to >> >> ''{mtime}Fri Oct 30 18:05:34 +0000 2009'' >> >> Dec 4 03:37:15 puppetclient puppetd[16163]: >> >> (/File[/var/lib/puppet/lib/facter]/checksum) checksum changed >> >> ''{mtime}Fri Oct 30 11:05:50 -0700 2009'' to ''{mtime}Tue Nov 03 08:00:05 >> >> +0000 2009'' >> >> Dec 4 03:37:33 puppetclient puppetd[16163]: Starting catalog run >> >> Dec 4 03:39:46 puppetclient puppetd[16163]: Finished catalog run in >> >> 133.44 seconds >> >> >> >> I''ve not been able to look on what is causing it, I belive it''s coming >> >> after we change the environment the puppetclient is pointing to, >> >> although we use the same puppetmaster to use different >> >> environments(dev, prod). >> >> >> >> Thoughts? >> >> >> >> Thanks >> >> >> >> >> >> On Thu, Dec 3, 2009 at 2:31 PM, Digant C Kasundra< >> >> digant@stanford.edu> wrote: >> >> >> >> >> >> Hey guys, >> >> >> >> We''re using multiple puppetmasters and I could have sworn I had >> >> uncovered an issue once where if a file had a different timestamp on >> >> two puppetmasters, clients would keep replacing the file depending on >> >> which puppetmaster they talked to because the clients thought the >> >> files were changing. But I''ve been unable to reproduce this problem. >> >> Is this only an issue in certain situations? We''re not using the >> >> checksum parameter to tell file resources to use timestamps and the >> >> type references seems to indicate that the default is md5 but I could >> >> have sworn I uncovered the aforementioned issue before but cannot for >> >> the life of me replicate it now. Anyone else know what I''m talking >> >> about? >> >> >> >> >> >> -- >> >> Digant C Kasundra< digant@stanford.edu> >> >> Technical Lead, ITS Unix Systems and Applications, Stanford University >> >> >> >> -- >> >> >> >> 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<puppet-users%2Bunsubscribe@googlegroups.com>. >> >> For more options, visit this group at >> >> http://groups.google.com/group/puppet-users?hl=en . >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> Tony >> >> >> >> >> >> >> >> >> >> -- 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<puppet-users%2Bunsubscribe@googlegroups.com> >> . >> >> For more options, visit this group at >> >> http://groups.google.com/group/puppet-users?hl=en. >> >> >> > >> >> -- >> >> 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<puppet-users%2Bunsubscribe@googlegroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en. >> >> >> > > > -- > Tony > > -- > 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. > > > -- > 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<puppet-users%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. >-- 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.
Silviu Paragina
2009-Dec-09 01:59 UTC
Re: [Puppet Users] Timestamps need to be in sync on all puppetmasters?
The output should give a clue if the timezone is wrong for ruby on the client/server machine. If I use utc it will discard that info so it is: ruby -e ''puts Time.at(0)'' and if all things are sane it should output Thu Jan 01 00:00:00 +000 1970 (without +something or -something) Not sure how much it can help, since there are a lot of other components that could change the standard behavior depending on setup (apache/nginx/passenger/mongrel etc) Silviu On 09.12.2009 03:53, Ohad Levy wrote:> if you want utc, you should use: > > ruby -e ''puts Time.at(0).utc'' > > cheers, > Ohad > > > On Wed, Dec 9, 2009 at 9:51 AM, Silviu Paragina <silviu@paragina.ro > <mailto:silviu@paragina.ro>> wrote: > > Try this > ruby -e ''puts Time.at(0)'' > In case ruby treats timezones different from how it should (how I > think it should actually) > > > Silviu > > > On 09.12.2009 03:21, Tony G. wrote: >> Hi, >> >> They are supposed to have GMT: >> puppetmaster: >> $ date >> Wed Dec 9 00:59:02 *GMT* 2009 >> puppetclient: >> $ date >> Wed Dec 9 00:58:59 *GMT* 2009 >> >> But digging more I found this: >> puppetmaster: >> $ cat /etc/sysconfig/clock >> *ZONE="GMT"* >> *UTC=false* >> ARC=false >> >> puppetclient: >> $ cat /etc/sysconfig/clock >> *ZONE="US/Pacific"* >> *UTC=true* >> ARC=false >> >> >> But the timezone file in //etc/localtime/ is the same on them: >> md5sum /usr/share/zoneinfo/* 2>/dev/null|grep $(md5sum >> /etc/localtime|cut -d" " -f1) >> fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT >> fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT0 >> fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT-0 >> fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT+0 >> fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/Greenwich >> >> Could the /etc/sysconfig/clock file cause this? >> >> Thanks! >> >> On Tue, Dec 8, 2009 at 1:50 PM, Silviu Paragina >> <silviu@paragina.ro <mailto:silviu@paragina.ro>> wrote: >> >> The log you posted looks like a bad date/time timezone >> conversion, are >> all the clients/puppetmasters on the same timezone? >> Notice that the dates are actually identical but one is in >> utc the other >> US eastern (I think). >> >> >> Silviu >> >> On 08.12.2009 22:43, Digant C Kasundra wrote: >> > This is similar to what I''m talking about. It looks like >> this resource is specifically using modified time as the >> "checksum." Is this something you''ve configured or is this a >> default of those directories as something internal to puppet. >> > >> > ----- "Tony G."<tonysk8@gmail.com >> <mailto:tonysk8@gmail.com>> wrote: >> > >> > >> >> I''ve see this very often but not sure if this is the issue >> you are >> >> describing: >> >> >> >> Dec 4 03:36:19 puppetclient puppetd[16163]: >> >> (/File[/var/lib/puppet/lib]/checksum) checksum changed >> ''{mtime}Fri Oct >> >> 30 11:05:32 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:50 >> +0000 2009'' >> >> Dec 4 03:36:20 puppetclient puppetd[16163]: >> >> (/File[/var/lib/puppet/lib/puppet]/checksum) checksum changed >> >> ''{mtime}Fri Oct 30 11:05:33 -0700 2009'' to ''{mtime}Fri Oct >> 30 18:05:50 >> >> +0000 2009'' >> >> Dec 4 03:36:21 puppetclient puppetd[16163]: >> >> (/File[/var/lib/puppet/lib/puppet/type]/checksum) checksum >> changed >> >> ''{mtime}Fri Oct 30 11:05:49 -0700 2009'' to ''{mtime}Fri Oct >> 30 18:05:50 >> >> +0000 2009'' >> >> Dec 4 03:36:24 puppetclient puppetd[16163]: >> >> (/File[/var/lib/puppet/lib/puppet/parser]/checksum) >> checksum changed >> >> ''{mtime}Fri Oct 30 11:05:50 -0700 2009'' to ''{mtime}Fri Oct >> 30 18:05:50 >> >> +0000 2009'' >> >> Dec 4 03:36:29 puppetclient puppetd[16163]: >> >> >> (/File[/var/lib/puppet/lib/puppet/parser/functions]/checksum) >> checksum >> >> changed ''{mtime}Fri Oct 30 11:05:50 -0700 2009'' to >> ''{mtime}Fri Oct 30 >> >> 18:05:50 +0000 2009'' >> >> Dec 4 03:36:29 puppetclient puppetd[16163]: >> >> (/File[/var/lib/puppet/lib/puppet/provider]/checksum) >> checksum changed >> >> ''{mtime}Fri Oct 30 11:05:33 -0700 2009'' to ''{mtime}Fri Oct >> 30 18:05:48 >> >> +0000 2009'' >> >> Dec 4 03:36:36 puppetclient puppetd[16163]: >> >> >> (/File[/var/lib/puppet/lib/puppet/provider/package]/checksum) >> checksum >> >> changed ''{mtime}Fri Oct 30 11:05:35 -0700 2009'' to >> ''{mtime}Fri Oct 30 >> >> 18:05:48 +0000 2009'' >> >> Dec 4 03:37:00 puppetclient puppetd[16163]: >> >> >> (/File[/var/lib/puppet/lib/puppet/provider/sysctl]/checksum) >> checksum >> >> changed ''{mtime}Fri Oct 30 11:05:48 -0700 2009'' to >> ''{mtime}Fri Oct 30 >> >> 18:05:49 +0000 2009'' >> >> Dec 4 03:37:01 puppetclient puppetd[16163]: >> >> >> (/File[/var/lib/puppet/lib/puppet/provider/volumegroup]/checksum) >> >> checksum changed ''{mtime}Fri Oct 30 11:05:34 -0700 2009'' to >> >> ''{mtime}Fri Oct 30 18:05:35 +0000 2009'' >> >> Dec 4 03:37:06 puppetclient puppetd[16163]: >> >> >> (/File[/var/lib/puppet/lib/puppet/provider/logicalvolume]/checksum) >> >> checksum changed ''{mtime}Fri Oct 30 11:05:33 -0700 2009'' to >> >> ''{mtime}Fri Oct 30 18:05:34 +0000 2009'' >> >> Dec 4 03:37:07 puppetclient puppetd[16163]: >> >> >> (/File[/var/lib/puppet/lib/puppet/provider/physicalvolume]/checksum) >> >> checksum changed ''{mtime}Fri Oct 30 11:05:34 -0700 2009'' to >> >> ''{mtime}Fri Oct 30 18:05:34 +0000 2009'' >> >> Dec 4 03:37:15 puppetclient puppetd[16163]: >> >> (/File[/var/lib/puppet/lib/facter]/checksum) checksum changed >> >> ''{mtime}Fri Oct 30 11:05:50 -0700 2009'' to ''{mtime}Tue Nov >> 03 08:00:05 >> >> +0000 2009'' >> >> Dec 4 03:37:33 puppetclient puppetd[16163]: Starting >> catalog run >> >> Dec 4 03:39:46 puppetclient puppetd[16163]: Finished >> catalog run in >> >> 133.44 seconds >> >> >> >> I''ve not been able to look on what is causing it, I belive >> it''s coming >> >> after we change the environment the puppetclient is >> pointing to, >> >> although we use the same puppetmaster to use different >> >> environments(dev, prod). >> >> >> >> Thoughts? >> >> >> >> Thanks >> >> >> >> >> >> On Thu, Dec 3, 2009 at 2:31 PM, Digant C Kasundra< >> >> digant@stanford.edu <mailto:digant@stanford.edu>> wrote: >> >> >> >> >> >> Hey guys, >> >> >> >> We''re using multiple puppetmasters and I could have sworn >> I had >> >> uncovered an issue once where if a file had a different >> timestamp on >> >> two puppetmasters, clients would keep replacing the file >> depending on >> >> which puppetmaster they talked to because the clients >> thought the >> >> files were changing. But I''ve been unable to reproduce >> this problem. >> >> Is this only an issue in certain situations? We''re not >> using the >> >> checksum parameter to tell file resources to use >> timestamps and the >> >> type references seems to indicate that the default is md5 >> but I could >> >> have sworn I uncovered the aforementioned issue before but >> cannot for >> >> the life of me replicate it now. Anyone else know what I''m >> talking >> >> about? >> >> >> >> >> >> -- >> >> Digant C Kasundra< digant@stanford.edu >> <mailto:digant@stanford.edu>> >> >> Technical Lead, ITS Unix Systems and Applications, >> Stanford University >> >> >> >> -- >> >> >> >> 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 >> <mailto:puppet-users@googlegroups.com> . >> >> To unsubscribe from this group, send email to >> >> puppet-users+unsubscribe@googlegroups.com >> <mailto:puppet-users%2Bunsubscribe@googlegroups.com> . >> >> For more options, visit this group at >> >> http://groups.google.com/group/puppet-users?hl=en . >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> Tony >> >> >> >> >> >> >> >> >> >> -- 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 >> <mailto:puppet-users@googlegroups.com>. >> >> To unsubscribe from this group, send email to >> >> puppet-users+unsubscribe@googlegroups.com >> <mailto:puppet-users%2Bunsubscribe@googlegroups.com>. >> >> For more options, visit this group at >> >> http://groups.google.com/group/puppet-users?hl=en. >> >> >> > >> >> -- >> >> 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 >> <mailto:puppet-users@googlegroups.com>. >> To unsubscribe from this group, send email to >> puppet-users+unsubscribe@googlegroups.com >> <mailto:puppet-users%2Bunsubscribe@googlegroups.com>. >> For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en. >> >> >> >> >> >> -- >> Tony >> >> -- >> >> 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 <mailto:puppet-users@googlegroups.com>. >> To unsubscribe from this group, send email to >> puppet-users+unsubscribe@googlegroups.com >> <mailto:puppet-users+unsubscribe@googlegroups.com>. >> For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en. > > -- > > 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 > <mailto:puppet-users@googlegroups.com>. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com > <mailto:puppet-users%2Bunsubscribe@googlegroups.com>. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > > -- > > 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.-- 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.
Tony G.
2009-Dec-09 02:07 UTC
Re: [Puppet Users] Timestamps need to be in sync on all puppetmasters?
The output is the same on both: puppetmaster: $ ruby -e ''puts Time.at(0)'' Thu Jan 01 00:00:00 +0000 1970 puppetclient: ruby -e ''puts Time.at(0)'' Thu Jan 01 00:00:00 +0000 1970 Then sometime else might be causing the checksum output. Thanks for the other suggestions and explanations. On Tue, Dec 8, 2009 at 5:59 PM, Silviu Paragina <silviu@paragina.ro> wrote:> The output should give a clue if the timezone is wrong for ruby on the > client/server machine. If I use utc it will discard that info so it is: > ruby -e ''puts Time.at(0)'' > and if all things are sane it should output > Thu Jan 01 00:00:00 +000 1970 (without +something or -something) > Not sure how much it can help, since there are a lot of other components > that could change the standard behavior depending on setup > (apache/nginx/passenger/mongrel etc) > > > Silviu > > > On 09.12.2009 03:53, Ohad Levy wrote: > > if you want utc, you should use: > > ruby -e ''puts Time.at(0).utc'' > > cheers, > Ohad > > > On Wed, Dec 9, 2009 at 9:51 AM, Silviu Paragina <silviu@paragina.ro>wrote: > >> Try this >> ruby -e ''puts Time.at(0)'' >> In case ruby treats timezones different from how it should (how I think it >> should actually) >> >> >> Silviu >> >> >> On 09.12.2009 03:21, Tony G. wrote: >> >> Hi, >> >> They are supposed to have GMT: >> puppetmaster: >> $ date >> Wed Dec 9 00:59:02 *GMT* 2009 >> puppetclient: >> $ date >> Wed Dec 9 00:58:59 *GMT* 2009 >> >> But digging more I found this: >> puppetmaster: >> $ cat /etc/sysconfig/clock >> *ZONE="GMT"* >> *UTC=false* >> ARC=false >> >> puppetclient: >> $ cat /etc/sysconfig/clock >> *ZONE="US/Pacific"* >> *UTC=true* >> ARC=false >> >> >> But the timezone file in */etc/localtime* is the same on them: >> md5sum /usr/share/zoneinfo/* 2>/dev/null|grep $(md5sum /etc/localtime|cut >> -d" " -f1) >> fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT >> fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT0 >> fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT-0 >> fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT+0 >> fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/Greenwich >> >> Could the /etc/sysconfig/clock file cause this? >> >> Thanks! >> >> On Tue, Dec 8, 2009 at 1:50 PM, Silviu Paragina <silviu@paragina.ro>wrote: >> >>> The log you posted looks like a bad date/time timezone conversion, are >>> all the clients/puppetmasters on the same timezone? >>> Notice that the dates are actually identical but one is in utc the other >>> US eastern (I think). >>> >>> >>> Silviu >>> >>> On 08.12.2009 22:43, Digant C Kasundra wrote: >>> > This is similar to what I''m talking about. It looks like this resource >>> is specifically using modified time as the "checksum." Is this something >>> you''ve configured or is this a default of those directories as something >>> internal to puppet. >>> > >>> > ----- "Tony G."<tonysk8@gmail.com> wrote: >>> > >>> > >>> >> I''ve see this very often but not sure if this is the issue you are >>> >> describing: >>> >> >>> >> Dec 4 03:36:19 puppetclient puppetd[16163]: >>> >> (/File[/var/lib/puppet/lib]/checksum) checksum changed ''{mtime}Fri Oct >>> >> 30 11:05:32 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:50 +0000 2009'' >>> >> Dec 4 03:36:20 puppetclient puppetd[16163]: >>> >> (/File[/var/lib/puppet/lib/puppet]/checksum) checksum changed >>> >> ''{mtime}Fri Oct 30 11:05:33 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:50 >>> >> +0000 2009'' >>> >> Dec 4 03:36:21 puppetclient puppetd[16163]: >>> >> (/File[/var/lib/puppet/lib/puppet/type]/checksum) checksum changed >>> >> ''{mtime}Fri Oct 30 11:05:49 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:50 >>> >> +0000 2009'' >>> >> Dec 4 03:36:24 puppetclient puppetd[16163]: >>> >> (/File[/var/lib/puppet/lib/puppet/parser]/checksum) checksum changed >>> >> ''{mtime}Fri Oct 30 11:05:50 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:50 >>> >> +0000 2009'' >>> >> Dec 4 03:36:29 puppetclient puppetd[16163]: >>> >> (/File[/var/lib/puppet/lib/puppet/parser/functions]/checksum) checksum >>> >> changed ''{mtime}Fri Oct 30 11:05:50 -0700 2009'' to ''{mtime}Fri Oct 30 >>> >> 18:05:50 +0000 2009'' >>> >> Dec 4 03:36:29 puppetclient puppetd[16163]: >>> >> (/File[/var/lib/puppet/lib/puppet/provider]/checksum) checksum changed >>> >> ''{mtime}Fri Oct 30 11:05:33 -0700 2009'' to ''{mtime}Fri Oct 30 18:05:48 >>> >> +0000 2009'' >>> >> Dec 4 03:36:36 puppetclient puppetd[16163]: >>> >> (/File[/var/lib/puppet/lib/puppet/provider/package]/checksum) checksum >>> >> changed ''{mtime}Fri Oct 30 11:05:35 -0700 2009'' to ''{mtime}Fri Oct 30 >>> >> 18:05:48 +0000 2009'' >>> >> Dec 4 03:37:00 puppetclient puppetd[16163]: >>> >> (/File[/var/lib/puppet/lib/puppet/provider/sysctl]/checksum) checksum >>> >> changed ''{mtime}Fri Oct 30 11:05:48 -0700 2009'' to ''{mtime}Fri Oct 30 >>> >> 18:05:49 +0000 2009'' >>> >> Dec 4 03:37:01 puppetclient puppetd[16163]: >>> >> (/File[/var/lib/puppet/lib/puppet/provider/volumegroup]/checksum) >>> >> checksum changed ''{mtime}Fri Oct 30 11:05:34 -0700 2009'' to >>> >> ''{mtime}Fri Oct 30 18:05:35 +0000 2009'' >>> >> Dec 4 03:37:06 puppetclient puppetd[16163]: >>> >> (/File[/var/lib/puppet/lib/puppet/provider/logicalvolume]/checksum) >>> >> checksum changed ''{mtime}Fri Oct 30 11:05:33 -0700 2009'' to >>> >> ''{mtime}Fri Oct 30 18:05:34 +0000 2009'' >>> >> Dec 4 03:37:07 puppetclient puppetd[16163]: >>> >> (/File[/var/lib/puppet/lib/puppet/provider/physicalvolume]/checksum) >>> >> checksum changed ''{mtime}Fri Oct 30 11:05:34 -0700 2009'' to >>> >> ''{mtime}Fri Oct 30 18:05:34 +0000 2009'' >>> >> Dec 4 03:37:15 puppetclient puppetd[16163]: >>> >> (/File[/var/lib/puppet/lib/facter]/checksum) checksum changed >>> >> ''{mtime}Fri Oct 30 11:05:50 -0700 2009'' to ''{mtime}Tue Nov 03 08:00:05 >>> >> +0000 2009'' >>> >> Dec 4 03:37:33 puppetclient puppetd[16163]: Starting catalog run >>> >> Dec 4 03:39:46 puppetclient puppetd[16163]: Finished catalog run in >>> >> 133.44 seconds >>> >> >>> >> I''ve not been able to look on what is causing it, I belive it''s coming >>> >> after we change the environment the puppetclient is pointing to, >>> >> although we use the same puppetmaster to use different >>> >> environments(dev, prod). >>> >> >>> >> Thoughts? >>> >> >>> >> Thanks >>> >> >>> >> >>> >> On Thu, Dec 3, 2009 at 2:31 PM, Digant C Kasundra< >>> >> digant@stanford.edu> wrote: >>> >> >>> >> >>> >> Hey guys, >>> >> >>> >> We''re using multiple puppetmasters and I could have sworn I had >>> >> uncovered an issue once where if a file had a different timestamp on >>> >> two puppetmasters, clients would keep replacing the file depending on >>> >> which puppetmaster they talked to because the clients thought the >>> >> files were changing. But I''ve been unable to reproduce this problem. >>> >> Is this only an issue in certain situations? We''re not using the >>> >> checksum parameter to tell file resources to use timestamps and the >>> >> type references seems to indicate that the default is md5 but I could >>> >> have sworn I uncovered the aforementioned issue before but cannot for >>> >> the life of me replicate it now. Anyone else know what I''m talking >>> >> about? >>> >> >>> >> >>> >> -- >>> >> Digant C Kasundra< digant@stanford.edu> >>> >> Technical Lead, ITS Unix Systems and Applications, Stanford University >>> >> >>> >> -- >>> >> >>> >> 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<puppet-users%2Bunsubscribe@googlegroups.com>. >>> >> For more options, visit this group at >>> >> http://groups.google.com/group/puppet-users?hl=en . >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> -- >>> >> Tony >>> >> >>> >> >>> >> >>> >> >>> >> -- 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<puppet-users%2Bunsubscribe@googlegroups.com> >>> . >>> >> For more options, visit this group at >>> >> http://groups.google.com/group/puppet-users?hl=en. >>> >> >>> > >>> >>> -- >>> >>> 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<puppet-users%2Bunsubscribe@googlegroups.com> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/puppet-users?hl=en. >>> >>> >>> >> >> >> -- >> Tony >> >> -- >> 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. >> >> >> -- >> 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<puppet-users%2Bunsubscribe@googlegroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en. >> > > -- > 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. > > > -- > 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<puppet-users%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. >-- Tony -- 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.
Tony G.
2009-Dec-11 20:30 UTC
Re: [Puppet Users] Timestamps need to be in sync on all puppetmasters?
I looked into the manifest and modules for any reference to manage the
checksum of /var/lib/puppet/lib/* and couldn''t find anything.
Is there a way to find out where/why these directories are being
checksum''ed?
The state.yaml contains this info:
File[/var/lib/puppet/lib/puppet/parser/functions]:
:checked: 2009-10-14 14:42:25.623364 +00:00
:checksums:
:*ctime: "{mtime}Thu Oct 08 06:07:35 -0700 2009"*
That snippet corresponds to this log snippet:
Dec 11 20:18:00 puppetclient01 puppetd[31604]:
(/File[/var/lib/puppet/lib/puppet/parser/functions]/checksum) checksum
changed ''*{mtime}Thu Oct 08 06:07:35 -0700 2009*'' to
''{mtime}Fri Dec 11
20:04:01 +0000 2009''
Thanks
On Tue, Dec 8, 2009 at 6:07 PM, Tony G. <tonysk8@gmail.com> wrote:
> The output is the same on both:
>
> puppetmaster:
> $ ruby -e ''puts Time.at(0)''
> Thu Jan 01 00:00:00 +0000 1970
>
> puppetclient:
>
> ruby -e ''puts Time.at(0)''
> Thu Jan 01 00:00:00 +0000 1970
>
> Then sometime else might be causing the checksum output.
>
> Thanks for the other suggestions and explanations.
>
>
> On Tue, Dec 8, 2009 at 5:59 PM, Silviu Paragina
<silviu@paragina.ro>wrote:
>
>> The output should give a clue if the timezone is wrong for ruby on the
>> client/server machine. If I use utc it will discard that info so it is:
>> ruby -e ''puts Time.at(0)''
>> and if all things are sane it should output
>> Thu Jan 01 00:00:00 +000 1970 (without +something or -something)
>> Not sure how much it can help, since there are a lot of other
components
>> that could change the standard behavior depending on setup
>> (apache/nginx/passenger/mongrel etc)
>>
>>
>> Silviu
>>
>>
>> On 09.12.2009 03:53, Ohad Levy wrote:
>>
>> if you want utc, you should use:
>>
>> ruby -e ''puts Time.at(0).utc''
>>
>> cheers,
>> Ohad
>>
>>
>> On Wed, Dec 9, 2009 at 9:51 AM, Silviu Paragina
<silviu@paragina.ro>wrote:
>>
>>> Try this
>>> ruby -e ''puts Time.at(0)''
>>> In case ruby treats timezones different from how it should (how I
think
>>> it should actually)
>>>
>>>
>>> Silviu
>>>
>>>
>>> On 09.12.2009 03:21, Tony G. wrote:
>>>
>>> Hi,
>>>
>>> They are supposed to have GMT:
>>> puppetmaster:
>>> $ date
>>> Wed Dec 9 00:59:02 *GMT* 2009
>>> puppetclient:
>>> $ date
>>> Wed Dec 9 00:58:59 *GMT* 2009
>>>
>>> But digging more I found this:
>>> puppetmaster:
>>> $ cat /etc/sysconfig/clock
>>> *ZONE="GMT"*
>>> *UTC=false*
>>> ARC=false
>>>
>>> puppetclient:
>>> $ cat /etc/sysconfig/clock
>>> *ZONE="US/Pacific"*
>>> *UTC=true*
>>> ARC=false
>>>
>>>
>>> But the timezone file in */etc/localtime* is the same on them:
>>> md5sum /usr/share/zoneinfo/* 2>/dev/null|grep $(md5sum
/etc/localtime|cut
>>> -d" " -f1)
>>> fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT
>>> fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT0
>>> fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT-0
>>> fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT+0
>>> fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/Greenwich
>>>
>>> Could the /etc/sysconfig/clock file cause this?
>>>
>>> Thanks!
>>>
>>> On Tue, Dec 8, 2009 at 1:50 PM, Silviu Paragina
<silviu@paragina.ro>wrote:
>>>
>>>> The log you posted looks like a bad date/time timezone
conversion, are
>>>> all the clients/puppetmasters on the same timezone?
>>>> Notice that the dates are actually identical but one is in utc
the other
>>>> US eastern (I think).
>>>>
>>>>
>>>> Silviu
>>>>
>>>> On 08.12.2009 22:43, Digant C Kasundra wrote:
>>>> > This is similar to what I''m talking about. It
looks like this
>>>> resource is specifically using modified time as the
"checksum." Is this
>>>> something you''ve configured or is this a default of
those directories as
>>>> something internal to puppet.
>>>> >
>>>> > ----- "Tony G."<tonysk8@gmail.com> wrote:
>>>> >
>>>> >
>>>> >> I''ve see this very often but not sure if this
is the issue you are
>>>> >> describing:
>>>> >>
>>>> >> Dec 4 03:36:19 puppetclient puppetd[16163]:
>>>> >> (/File[/var/lib/puppet/lib]/checksum) checksum changed
''{mtime}Fri
>>>> Oct
>>>> >> 30 11:05:32 -0700 2009'' to
''{mtime}Fri Oct 30 18:05:50 +0000 2009''
>>>> >> Dec 4 03:36:20 puppetclient puppetd[16163]:
>>>> >> (/File[/var/lib/puppet/lib/puppet]/checksum) checksum
changed
>>>> >> ''{mtime}Fri Oct 30 11:05:33 -0700
2009'' to ''{mtime}Fri Oct 30
>>>> 18:05:50
>>>> >> +0000 2009''
>>>> >> Dec 4 03:36:21 puppetclient puppetd[16163]:
>>>> >> (/File[/var/lib/puppet/lib/puppet/type]/checksum)
checksum changed
>>>> >> ''{mtime}Fri Oct 30 11:05:49 -0700
2009'' to ''{mtime}Fri Oct 30
>>>> 18:05:50
>>>> >> +0000 2009''
>>>> >> Dec 4 03:36:24 puppetclient puppetd[16163]:
>>>> >> (/File[/var/lib/puppet/lib/puppet/parser]/checksum)
checksum changed
>>>> >> ''{mtime}Fri Oct 30 11:05:50 -0700
2009'' to ''{mtime}Fri Oct 30
>>>> 18:05:50
>>>> >> +0000 2009''
>>>> >> Dec 4 03:36:29 puppetclient puppetd[16163]:
>>>> >>
(/File[/var/lib/puppet/lib/puppet/parser/functions]/checksum)
>>>> checksum
>>>> >> changed ''{mtime}Fri Oct 30 11:05:50 -0700
2009'' to ''{mtime}Fri Oct 30
>>>> >> 18:05:50 +0000 2009''
>>>> >> Dec 4 03:36:29 puppetclient puppetd[16163]:
>>>> >> (/File[/var/lib/puppet/lib/puppet/provider]/checksum)
checksum
>>>> changed
>>>> >> ''{mtime}Fri Oct 30 11:05:33 -0700
2009'' to ''{mtime}Fri Oct 30
>>>> 18:05:48
>>>> >> +0000 2009''
>>>> >> Dec 4 03:36:36 puppetclient puppetd[16163]:
>>>> >>
(/File[/var/lib/puppet/lib/puppet/provider/package]/checksum)
>>>> checksum
>>>> >> changed ''{mtime}Fri Oct 30 11:05:35 -0700
2009'' to ''{mtime}Fri Oct 30
>>>> >> 18:05:48 +0000 2009''
>>>> >> Dec 4 03:37:00 puppetclient puppetd[16163]:
>>>> >>
(/File[/var/lib/puppet/lib/puppet/provider/sysctl]/checksum) checksum
>>>> >> changed ''{mtime}Fri Oct 30 11:05:48 -0700
2009'' to ''{mtime}Fri Oct 30
>>>> >> 18:05:49 +0000 2009''
>>>> >> Dec 4 03:37:01 puppetclient puppetd[16163]:
>>>> >>
(/File[/var/lib/puppet/lib/puppet/provider/volumegroup]/checksum)
>>>> >> checksum changed ''{mtime}Fri Oct 30 11:05:34
-0700 2009'' to
>>>> >> ''{mtime}Fri Oct 30 18:05:35 +0000
2009''
>>>> >> Dec 4 03:37:06 puppetclient puppetd[16163]:
>>>> >>
(/File[/var/lib/puppet/lib/puppet/provider/logicalvolume]/checksum)
>>>> >> checksum changed ''{mtime}Fri Oct 30 11:05:33
-0700 2009'' to
>>>> >> ''{mtime}Fri Oct 30 18:05:34 +0000
2009''
>>>> >> Dec 4 03:37:07 puppetclient puppetd[16163]:
>>>> >>
(/File[/var/lib/puppet/lib/puppet/provider/physicalvolume]/checksum)
>>>> >> checksum changed ''{mtime}Fri Oct 30 11:05:34
-0700 2009'' to
>>>> >> ''{mtime}Fri Oct 30 18:05:34 +0000
2009''
>>>> >> Dec 4 03:37:15 puppetclient puppetd[16163]:
>>>> >> (/File[/var/lib/puppet/lib/facter]/checksum) checksum
changed
>>>> >> ''{mtime}Fri Oct 30 11:05:50 -0700
2009'' to ''{mtime}Tue Nov 03
>>>> 08:00:05
>>>> >> +0000 2009''
>>>> >> Dec 4 03:37:33 puppetclient puppetd[16163]: Starting
catalog run
>>>> >> Dec 4 03:39:46 puppetclient puppetd[16163]: Finished
catalog run in
>>>> >> 133.44 seconds
>>>> >>
>>>> >> I''ve not been able to look on what is causing
it, I belive it''s
>>>> coming
>>>> >> after we change the environment the puppetclient is
pointing to,
>>>> >> although we use the same puppetmaster to use different
>>>> >> environments(dev, prod).
>>>> >>
>>>> >> Thoughts?
>>>> >>
>>>> >> Thanks
>>>> >>
>>>> >>
>>>> >> On Thu, Dec 3, 2009 at 2:31 PM, Digant C Kasundra<
>>>> >> digant@stanford.edu> wrote:
>>>> >>
>>>> >>
>>>> >> Hey guys,
>>>> >>
>>>> >> We''re using multiple puppetmasters and I
could have sworn I had
>>>> >> uncovered an issue once where if a file had a
different timestamp on
>>>> >> two puppetmasters, clients would keep replacing the
file depending on
>>>> >> which puppetmaster they talked to because the clients
thought the
>>>> >> files were changing. But I''ve been unable to
reproduce this problem.
>>>> >> Is this only an issue in certain situations?
We''re not using the
>>>> >> checksum parameter to tell file resources to use
timestamps and the
>>>> >> type references seems to indicate that the default is
md5 but I could
>>>> >> have sworn I uncovered the aforementioned issue before
but cannot for
>>>> >> the life of me replicate it now. Anyone else know what
I''m talking
>>>> >> about?
>>>> >>
>>>> >>
>>>> >> --
>>>> >> Digant C Kasundra< digant@stanford.edu>
>>>> >> Technical Lead, ITS Unix Systems and Applications,
Stanford
>>>> University
>>>> >>
>>>> >> --
>>>> >>
>>>> >> 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<puppet-users%2Bunsubscribe@googlegroups.com>.
>>>> >> For more options, visit this group at
>>>> >> http://groups.google.com/group/puppet-users?hl=en .
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >> --
>>>> >> Tony
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >> -- 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<puppet-users%2Bunsubscribe@googlegroups.com>
>>>> .
>>>> >> For more options, visit this group at
>>>> >> http://groups.google.com/group/puppet-users?hl=en.
>>>> >>
>>>> >
>>>>
>>>> --
>>>>
>>>> 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<puppet-users%2Bunsubscribe@googlegroups.com>
>>>> .
>>>> For more options, visit this group at
>>>> http://groups.google.com/group/puppet-users?hl=en.
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Tony
>>>
>>> --
>>> 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.
>>>
>>>
>>> --
>>> 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<puppet-users%2Bunsubscribe@googlegroups.com>
>>> .
>>> For more options, visit this group at
>>> http://groups.google.com/group/puppet-users?hl=en.
>>>
>>
>> --
>> 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.
>>
>>
>> --
>> 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<puppet-users%2Bunsubscribe@googlegroups.com>
>> .
>> For more options, visit this group at
>> http://groups.google.com/group/puppet-users?hl=en.
>>
>
>
>
> --
> Tony
>
--
Tony
--
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.