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

Re: [tor-relays] Upgraded relay non show in ATLAS

To: tor-relays@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [tor-relays] Upgraded relay non show in ATLAS
From: teor <teor2345@xxxxxxxxx>
Date: Fri, 26 Jan 2018 11:23:01 +1100
Delivered-to: archiver@xxxxxxxx
Delivery-date: Thu, 25 Jan 2018 19:23:23 -0500
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:date:message-id:subject :references:in-reply-to:to; bh=F7O7lY7gK4BV8BZCfwwB6qOXOrIXppQI9H4w3noTtfo=; b=V1RcQJ716sQRePEB2OFTF20BmuKE2qoFHL0RO/jJhmJ/9sXlOfSOeDa2OYY3sN41o6 hORornkcKTpOTEjpwaQMWq/N1KKuPmuTcT4AFtQagwComraa6EkC5z33N8KUZ3HnPowd OggH4dznatid7c2rnQuGc3lBxoLcU0QTflzv+zWpEjyr5+/6ZmlP0zvmwWqjlfAKsb+n dsKznLRZKV6+PaSZFAc+Bz9LvQFDpwHHmdreLq+lu79NEqcuKPfRC2i2jxjAj/quOu3U ABArTbblrJ1u4r7mgBFoyyku+kP/cUnNm+Wo9msac7ExCDc8c6DFMvm9310t9usaGsOq 8NLA==
In-reply-to: <1516923668.13151.6.camel@arcaik.net>
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: <dc054705-ff53-b354-feee-c106adcec146@gmail.com> <1516923668.13151.6.camel@arcaik.net>
Reply-to: tor-relays@xxxxxxxxxxxxxxxxxxxx
Sender: "tor-relays" <tor-relays-bounces@xxxxxxxxxxxxxxxxxxxx>

> On 26 Jan 2018, at 10:41, Johan Fleury <jfleury@xxxxxxxxxx> wrote:
> 
> Hey ! I have the exact same problem, I operate 2 instances that had a little bit
> of downtime for a few weeks. I restarted them a week ago, but they haven't
> received any tor traffic since then.
> 
> This line shows up periodically in the logs: `Heartbeat: It seems like we are
> not in the cached consensus.`
> 
> The instances are:
> 
> prospero1 BFB01CAB4C4CFDD398F3548BD071E3F6E204DF0E
> prospero2 EC5A3E0C3548AB19B53ABDE6B1F9D1DB498DEF29
> 
> Both behind 46.105.84.177 and 2001:470:ccfc:201::2.
> 
> How can I debug this?

4 authorities are voting running for your first relay, 5 are not.
The authorities that vote running are only on IPv4.

Looks like your IPv6 is unreachable.

T 
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Follow-Ups:
- Re: [tor-relays] Upgraded relay non show in ATLAS
  - From: Johan Fleury

References:
- [tor-relays] Upgraded relay non show in ATLAS
  - From: MLTor Node
- Re: [tor-relays] Upgraded relay non show in ATLAS
  - From: Johan Fleury

Prev by Author: Re: [tor-relays] Combined relay and hidden service, good idea or not?
Next by Author: Re: [tor-relays] connlimit: better to use "DROP" or "REJECT --reject-with tcp-reset"?
Previous by thread: Re: [tor-relays] Upgraded relay non show in ATLAS
Next by thread: Re: [tor-relays] Upgraded relay non show in ATLAS
Index(es):
- Author
- Thread