RE: [squid-users] RE: Squid Up Time is shown as negative

Yeah you are right Amos. Actually it was not NTP but some other script in my setup that was changing the system time.

Thank You Amos!

Regards,
Saurabh

-----Original Message-----
From: Amos Jeffries [mailto:squid3_at_treenet.co.nz]
Sent: Tuesday, March 29, 2011 3:07 PM
To: squid-users_at_squid-cache.org
Subject: Re: [squid-users] RE: Squid Up Time is shown as negative

On 29/03/11 21:53, Saurabh Agarwal wrote:
> Yeah "Start time" is earlier compared to "Current time". This is the cachemgr output and this also shows that "current time" is less than "start time".
>
> HTTP/1.0 200 OK
> Server: squid/2.7.STABLE7
> Date: Mon, 28 Mar 2011 11:36:04 GMT
> Content-Type: text/plain
> Expires: Mon, 28 Mar 2011 11:36:04 GMT
> X-Cache: MISS from wanscaler
> Via: 1.0 wanscaler:3128 (squid/2.7.STABLE7)
> Connection: close
>
> Squid Object Cache: Version 2.7.STABLE7
> Start Time: Tue, 29 Mar 2011 05:34:35 GMT
> Current Time: Mon, 28 Mar 2011 11:36:04 GMT
>
> Regards,
> Saurabh

There is your answer then. Something is seriously screwed with your
system clock.

18 hours difference is too much for a local vs GMT difference (max 13
hours difference). I notice you said in your other email that this
appears a minute or two after starting the box. This makes me think the
box hardware is set with a very badly wrong time, which gets adjusted
shortly after bootup by NTP.

Amos

-- 
Please be using
   Current Stable Squid 2.7.STABLE9 or 3.1.11
   Beta testers wanted for 3.2.0.5