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]:
The output is the same on both:
puppetmaster:
$ ruby -e 'puts Time.at(0)'
Thu Jan 01 00:00:00 + 1970
puppetclient:
ruby -e 'puts Time.at(0)'
Thu Jan 01 00:00:00 + 1970
Then sometime else might be causing the checksum output.
Thanks for the other suggestions and explanations.
On Tue, De
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
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 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.1
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
>
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)
> fcccbcf95
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
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 wh
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." wrote:
> I've see this very often but
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 + 2009'
Dec 4 03:36:20 puppetclient puppetd
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 chang
11 matches
Mail list logo
