What's up with these messages I get in tor-arm and log?
Caching new entry debian-tor for debian-tor [62 duplicates hidden]
What is tor doing??
Sep 20 19:10:21.000 [notice] Caching new entry debian-tor for debian-tor Sep 20 19:10:45.000 [notice] Caching new entry debian-tor for debian-tor Sep 20 19:11:09.000 [notice] Caching new entry debian-tor for debian-tor Sep 20 19:11:33.000 [notice] Caching new entry debian-tor for debian-tor Sep 20 19:11:57.000 [notice] Caching new entry debian-tor for debian-tor Sep 20 19:12:21.000 [notice] Caching new entry debian-tor for debian-tor Sep 20 19:12:45.000 [notice] Caching new entry debian-tor for debian-tor Sep 20 19:13:09.000 [notice] Caching new entry debian-tor for debian-tor Sep 20 19:13:33.000 [notice] Caching new entry debian-tor for debian-tor Sep 20 19:13:57.000 [notice] Caching new entry debian-tor for debian-tor Sep 20 19:14:21.000 [notice] Caching new entry debian-tor for debian-tor Sep 20 19:14:45.000 [notice] Caching new entry debian-tor for debian-tor Sep 20 19:15:09.000 [notice] Caching new entry debian-tor for debian-tor Sep 20 19:15:33.000 [notice] Caching new entry debian-tor for debian-tor Sep 20 19:15:57.000 [notice] Caching new entry debian-tor for debian-tor Sep 20 19:16:21.000 [notice] Caching new entry debian-tor for debian-tor Sep 20 19:16:45.000 [notice] Caching new entry debian-tor for debian-tor Sep 20 19:17:09.000 [notice] Caching new entry debian-tor for debian-tor Sep 20 19:17:33.000 [notice] Caching new entry debian-tor for debian-tor
seems to try to do it quite often?
/scooby
On Tue, Sep 20, 2016 at 07:20:03PM +0200, shraptor wrote:
It looks like this notice-level entry was changed to an info-level entry starting in Tor 0.2.7.1-alpha:
$ git show 251f6cfc commit 251f6cfcd829d3f7b8ac7bce8477a6e14ad47a1e Author: Nick Mathewson nickm@torproject.org Date: Thu Feb 19 12:30:34 2015 -0500
Quiet "caching debian-tor for debian-tor" notice
diff --git a/src/common/compat.c b/src/common/compat.c index fde65d9..1788e32 100644 --- a/src/common/compat.c +++ b/src/common/compat.c @@ -1793,8 +1793,8 @@ tor_getpwnam(const char *username) if ((pw = getpwnam(username))) { tor_passwd_free(passwd_cached); passwd_cached = tor_passwd_dup(pw); - log_notice(LD_GENERAL, "Caching new entry %s for %s", - passwd_cached->pw_name, username); + log_info(LD_GENERAL, "Caching new entry %s for %s", + passwd_cached->pw_name, username); return pw; }
So it looks like you are running an old version of Tor? You should upgrade and the line should go away. In any case it should be harmless.
Hope that helps, --Roger
On 2016-09-20 20:58, Roger Dingledine wrote:
...
So it looks like you are running an old version of Tor? You should upgrade and the line should go away. In any case it should be harmless.
Yeah well I'm running on rpi3 and it says in tor-arm that 0.2.5 is the recommended version for this architecture.
Anyway I checked out your public repo's of armhf compiled tor packages. These packages are unfortunately dependent on libsystemd that is not welcome on my systems. I am running devuan as OS.
So I have looked into building a newer version myself but it is a bit of jungle to setup the tool chain for me.
I hadn't noticed this log-message before and had some trouble with my relay so felt the need to seek information.
/scooby
Well, according to this question I asked on Tor's StackExchange, version 0.2.4.26 is still technically in the recommended consensus.
At any rate, running an older version is better for diversity, isn't it?
On Sep 21, 2016 2:13 AM, "shraptor" shraptor@bahnhof.se wrote:
Whoops, forgot to paste the link: https://tor.stackexchange.com/questions/12638/how-old-is-too-old-tor-version...
On Sep 21, 2016 7:46 AM, "Tristan" supersluether@gmail.com wrote:
On 21 Sep 2016, at 22:46, Tristan supersluether@gmail.com wrote:
Well, according to this question I asked on Tor's StackExchange, version 0.2.4.26 is still technically in the recommended consensus.
And it will be the next to go, likely when the next directory authority's details change, or a serious security issue is discovered.
At any rate, running an older version is better for diversity, isn't it?
Sort of, but the accumulated security fixes and performance improvements in later versions tend to outweigh the benefit of running a really old version. You'd actually contribute more to Tor's diversity by running 0.2.6, and even 0.2.7 isn't the most common version any more.
Tim
Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org
Well, until someone decides to update Orbot, Android users are still on 0.2.7.5.
On Sep 21, 2016 8:30 AM, "teor" teor2345@gmail.com wrote:
tor-relays@lists.torproject.org
-
Roger Dingledine -
shraptor -
teor -
Tristan