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 <sil...@paragina.ro > <mailto:sil...@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 >> <sil...@paragina.ro <mailto:sil...@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."<tony...@gmail.com >> <mailto:tony...@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< >> >> dig...@stanford.edu <mailto:dig...@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< dig...@stanford.edu >> <mailto:dig...@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+unsubscr...@googlegroups.com >> <mailto:puppet-users%2bunsubscr...@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+unsubscr...@googlegroups.com >> <mailto:puppet-users%2bunsubscr...@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+unsubscr...@googlegroups.com >> <mailto:puppet-users%2bunsubscr...@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+unsubscr...@googlegroups.com >> <mailto:puppet-users+unsubscr...@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+unsubscr...@googlegroups.com > <mailto:puppet-users%2bunsubscr...@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-us...@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. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
