-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yea, maybe you will find something strange or regular
On 19.02.2014 10:59, Zenaan Harkness wrote:
> On 2/19/14, Alexander Makarov wrote:
>> On 18.02.2014 23:39, Zenaan Harkness wrote:
>>> On 2/18/14, Alexander Makarov wrote:
On 18.02.2014 22:02
Iinet are having some sort of problem this morning which was just resolved a
short while ago.
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hello people,
I'm sending you an email because your bridges are hardcoded in the
pluggable transport bundles.
We recently added PT-specific metrics in metrics.torproject.org
Specificaally, you can see a graph of PT users here:
https://metrics.torproject.org/users.html?graph=userstats-bridge-trans
On 2/19/14, Alexander Makarov wrote:
> On 18.02.2014 23:39, Zenaan Harkness wrote:
>> On 2/18/14, Alexander Makarov wrote:
>>> On 18.02.2014 22:02, Zenaan Harkness wrote:
My tor logs (running on Debian) are showing this warning:
[WARN] Your system clock just jumped 100 seconds forward;
On 2/18/14, D.S. Ljungmark wrote:
> On Tue, Feb 18, 2014 at 12:02 PM, Zenaan Harkness wrote:
>> My tor logs (running on Debian) are showing this warning:
>> [WARN] Your system clock just jumped 100 seconds forward; assuming
>> established circuits no longer work.
>>
>> I tried running openntpd as
On Tue, 18 Feb 2014 22:02:21 +, Zenaan Harkness wrote:
> My tor logs (running on Debian) are showing this warning:
> [WARN] Your system clock just jumped 100 seconds forward; assuming
> established circuits no longer work.
It may just be that your machine completely hangs for a while
occasiona
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Could you show the log? Can you rebuild you kernel with debug option and
check what kernel events have the same timestamps
On 18.02.2014 23:39, Zenaan Harkness wrote:
> On 2/18/14, Alexander Makarov wrote:
>> On 18.02.2014 22:02, Zenaan Harkness wrot
Are you on a virtual machine? Do you control the VM host? If not, it could
be that your host is migrating your VM, or not scheduling it properly,
which causes time drifts inside the VM.
On Tue, Feb 18, 2014 at 12:02 PM, Zenaan Harkness wrote:
> My tor logs (running on Debian) are showing this
I was told by a network engineer that recently there have been attacks
targetting ntp.
It may or may not have anything to do with your relay though.
Robert
>
> My tor logs (running on Debian) are showing this warning:
> [WARN] Your system clock just jumped 100 seconds forward; assuming
> establ
On 2/18/14, Alexander Makarov wrote:
> On 18.02.2014 22:02, Zenaan Harkness wrote:
>> My tor logs (running on Debian) are showing this warning:
>> [WARN] Your system clock just jumped 100 seconds forward; assuming
>> established circuits no longer work.
>>
>> I tried running openntpd as well as nt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Maybe problem with hardware clocks?
On 18.02.2014 22:02, Zenaan Harkness wrote:
> My tor logs (running on Debian) are showing this warning:
> [WARN] Your system clock just jumped 100 seconds forward; assuming
> established circuits no longer work.
>
My tor logs (running on Debian) are showing this warning:
[WARN] Your system clock just jumped 100 seconds forward; assuming
established circuits no longer work.
I tried running openntpd as well as ntp packages (debian), and both
display the same problem - once or twice a day I get this jump in ti
12 matches
Mail list logo
