[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-relays] new warning with Tor 0.3.4.0-alpha-dev (git-efc105716283bbdf)

To: tor-relays@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [tor-relays] new warning with Tor 0.3.4.0-alpha-dev (git-efc105716283bbdf)
From: eric gisse <jowr.pi@xxxxxxxxx>
Date: Mon, 19 Feb 2018 20:05:29 -0600
Delivered-to: archiver@xxxxxxxx
Delivery-date: Mon, 19 Feb 2018 21:05:43 -0500
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-transfer-encoding; bh=OIfc28U8U0SXl0sE5WkCrw1SouY3u6JUxdTVkCZBiK0=; b=oOvgyk2n2GnbaWPOAsc6IlE2ODE+5FF07e60E36mhRclqOu9LsP2bvoydX+COTlblJ 4CB7Kuep0qBFo8rQeohk4zyIXmMAI/I4bAYaPrzLpT1BILqtgsUy3gU/gwUKi9DBWhBR ujp7QCFesNKyVMCPrnw679j//FZO2OrlhkAg7V8ax7g7zflSzMdBtt7lSBMuneTcPo2s vYDeI6uFk1ob6DGx5yS7N4jAQyy6315t20E0Ct3toHXWbGhioJfjI285OMWN24N6Ulw3 N/MCrySr4UCLjrbclUjjhhgV3yy6N5IryxMIr/cnvsD24QjLt4NOqOdJZXx79P6KL/u0 lFSA==
In-reply-to: <2b1e6d15-a940-2cb5-02db-576f9596dbd9@gmx.de>
List-archive: <http://lists.torproject.org/pipermail/tor-relays/>
List-help: <mailto:tor-relays-request@lists.torproject.org?subject=help>
List-id: "support and questions about running Tor relays \(exit, non-exit, bridge\)" <tor-relays.lists.torproject.org>
List-post: <mailto:tor-relays@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=unsubscribe>
References: <2b1e6d15-a940-2cb5-02db-576f9596dbd9@gmx.de>
Reply-to: tor-relays@xxxxxxxxxxxxxxxxxxxx
Sender: "tor-relays" <tor-relays-bounces@xxxxxxxxxxxxxxxxxxxx>

NTP?

On Mon, Feb 19, 2018 at 12:32 PM, Toralf Förster <toralf.foerster@xxxxxx> wrote:
> This happenes here now with that version usually once a day.
>
> Feb 19 18:59:00.000 [warn] Our clock is 1 minutes, 1 seconds behind the time published in the consensus network status document (2018-02-19 18:00:00 UTC).  Tor needs an accurate clock to work correctly. Please check your time and date settings!
> Feb 19 18:59:00.000 [warn] Received microdesc flavor consensus with skewed time (CONSENSUS): It seems that our clock is behind by 1 minutes, 1 seconds, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings.
>
>
> --
> Toralf
> PGP C4EACDDE 0076E94E
>
>
> _______________________________________________
> tor-relays mailing list
> tor-relays@xxxxxxxxxxxxxxxxxxxx
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

References:
- [tor-relays] new warning with Tor 0.3.4.0-alpha-dev (git-efc105716283bbdf)
  - From: Toralf Förster

Prev by Author: Re: [tor-relays] Publishing bridge contact information
Next by Author: [tor-relays] DoS mitigation
Previous by thread: [tor-relays] new warning with Tor 0.3.4.0-alpha-dev (git-efc105716283bbdf)
Next by thread: Re: [tor-relays] new warning with Tor 0.3.4.0-alpha-dev (git-efc105716283bbdf)
Index(es):
- Author
- Thread