Hello,
I'd like to hear if anyone else experienced this and has an idea of what
the cause might be.
I did not oped a ticket about this yet because I am not sure there is a
problem in Tor, and it eventually healed by itself.
The relay was running just fine. Server had an accurate time before
upg
Hi,
> On 7 Sep 2019, at 20:25, s7r wrote:
>
> So, Tor had the time Sep 06 21:03:46.000 before restart.
>
> After restart, it thought it had Aug 28 07:40:07.000 and then Aug 28
> 07:40:08.000 and then it healed and reported Sep 06 21:04:50.000.
>
> This is kind of odd. What could be the reason
teor wrote:
> Hi,
>
>> On 7 Sep 2019, at 20:25, s7r wrote:
>>
>> So, Tor had the time Sep 06 21:03:46.000 before restart.
>>
>> After restart, it thought it had Aug 28 07:40:07.000 and then Aug 28
>> 07:40:08.000 and then it healed and reported Sep 06 21:04:50.000.
>>
>> This is kind of odd. Wha
s7r wrote:
> teor wrote:
>> Hi,
>>
>>> [SNIP]
I have received the email below from Ron off-list, and it was very
useful. Posting it here.
Ron, I have tried to email back but apparently your mail server treats
me as spam and I get bounce back with permanent failure - hopefully you
are still gett
> On Sep 7, 2019, at 04:13, s7r wrote:
>
> after upgrading from 0.4.1.2 to 0.4.2.0, I did an entire system
> reboot because I also updated some other stuff. So the entire OS
> restarted, not just Tor daemon
It seems likely that your machine's hardware clock is off. During a reboot, the
system
