Lucky Green 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
On Mon, 31 Mar 2008 20:44:25 -0700 Lucky Greeen [EMAIL PROTECTED]
wrote:
Lucky Green 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
I'm guessing this is a kernel thing, so running date a lot will probably
not help to notice it. Is gettimeofday() the wrong way to ask what time
it is under vmware? :)
Using select (or poll) and gettimeofday, while not technically
correct, is the only portable way of writing an even-driven
On Thu, 28 Feb 2008, Lucky Green wrote:
I tried several potential fixes. Unfortunately none of them worked.
1) removed ntp from the guest
2) Enabled time sync from the guest to the host using vmware-guest
--cmd vmx.set_options synctime 0 1 (which, unlike editing the .vmx
file by hand is
On Fri, Feb 29, 2008 at 09:01:48AM +0100, Florian Reitmeir wrote:
I continue to see Tor report errors of jumps in the system time from
4397-4399 seconds. Strangely, this jump in time does not appear to be
reflected in the time stamp that Tor assigns to the error message.
maybe it will
On Fri, 29 Feb 2008, Roger Dingledine wrote:
On Fri, Feb 29, 2008 at 09:01:48AM +0100, Florian Reitmeir wrote:
I continue to see Tor report errors of jumps in the system time from
4397-4399 seconds. Strangely, this jump in time does not appear to be
reflected in the time stamp that Tor
On Thu, February 28, 2008 06:14, Lucky Green wrote:
NTP:
ntp is installed on the guest. ntpq -p shows a solid lock.
remove ntp from the guest, it causes troubles.
also, search vmware kb for clock issues, the most common fixes are
removing ntp services from guest, installing tools on the guest
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
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 [EMAIL PROTECTED] wrote:
I am seeing the following errors in the Tor log:
[...]
Feb 28 04:54:43.008 [notice] Your
Marco Bonetti wrote:
On Thu, February 28, 2008 06:14, Lucky Green wrote:
NTP:
ntp is installed on the guest. ntpq -p shows a solid lock.
remove ntp from the guest, it causes troubles.
also, search vmware kb for clock issues, the most common fixes are
removing ntp services from guest,
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
11 matches
Mail list logo
