[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: "Your system clock just jumped" on Debian+VMware ESX
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: "Your system clock just jumped" on Debian+VMware ESX
- From: "Wilfred L. Guerin" <wilfredguerin@xxxxxxxxx>
- Date: Thu, 28 Feb 2008 10:31:05 -0500
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Thu, 28 Feb 2008 10:31:11 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=vM9cQ2eKnR4vrcxf6FyJX9VPE2XQzbPJQKzY3DgvrAQ=; b=VcZdTkNdHzM2dzmwuYK7u8CLBlFkTikqwIg+PpMh3f3bisN48hfHhRB8QiGICopjMaE/p4yL2+CJeTIKOgoKic1ctgeQpEYVYMtogm2mY/CmBRkUFyBGLb9QWhDrZxr8fLTd74O4HPkDCvkqJHZwXlTo9FuFrCk+pdePjJMdKOI=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=rSLp1obi2H6uSviu+0uffykrldhpux0lRYviHMxqJm+UT51sw8bUEL6NRnKqN0/Z6zHYeGDAT5UVvzhN1HYpLE5K+lOW7eNaqecsTqA/wG+OleUWGp9PY9eFQcA9LhEEYO5RqXNRJjxK3aOc/GI6fIWbkHMugkCVEsbVtA6s8uA=
- In-reply-to: <47C673E5.8050404@xxxxxxxxxxxx>
- References: <20080228051451.CD72D1707B@xxxxxxxxxxxxxxxxxxx> <47C673E5.8050404@xxxxxxxxxxxx>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
irupt probs on debian/etc is old kernel according to vmware,
"their kernels are old. 2.6.18+ fixed this."
though there are other concerns on heavier smp sytems
On 2/28/08, M <maillist@xxxxxxxxxxxx> wrote:
> > I am seeing the following errors in the Tor log:
> > [...]
> > Feb 28 04:54:43.008 [notice] Your system clock just jumped 4398 seconds
> > backward; assuming established circuits no longer work.
> > Feb 28 04:54:46.020 [notice] Your system clock just jumped 4399 seconds
> > forward; assuming established circuits no longer work.
> > [...]
> I was having the same exact problem on Debian which was running on Xen.
> Removed ntp as the ISP:'s admin recommended, that did not help. Then
> they moved my virtual machine to another host and everything was fine
> for a while. As for now the problem is occuring about once a week, two
> or three error messages.