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

Re: [tor-relays] Relay JPsi2 not getting into consensus anymore

To: tor-relays@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [tor-relays] Relay JPsi2 not getting into consensus anymore
From: William Kane <ttallink@xxxxxxxxxxxxxx>
Date: Mon, 12 Oct 2020 10:55:13 +0000
Delivered-to: archiver@xxxxxxxx
Delivery-date: Mon, 12 Oct 2020 08:19:23 -0400
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=aL6hW/un+nbfLxk0RFDJwy7NWB23/5Ms7cGIR0/4EYQ=; b=EGq8gZGZWNtkaY7IwPbJQ/usWbEzRHC9lIY281abpEJnSjsD/GQOSSei3sZJ5AlX8P kJfjtL+E/fbzF/1645XBfp1da6aolN2YJlLg94OqqCc02S7inoQGoa0DiQw926s2UGqk ZGZR9Mbl3WCgY6jkTTnYymk+8K5ceCLKQHyE1B/ZMlM/XVm2N6PvwTz+JwD+H4qBfBRe IVdhiMXWbVy7/v17qsI/U6dwkqB4z34rqz9gygasD31QGuXrDNNwVeci4xR2nX33op+l yVTQ6oPffc77s28Tmta/EkZMFdtKMDvPeKhRixJDdwrfDxoN2Hqj1MbSwTcZGzKW/QTF NwdA==
In-reply-to: <6034846f-57fb-665f-f873-f1a6c7e18f7f@unterderbruecke.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: <6034846f-57fb-665f-f873-f1a6c7e18f7f@unterderbruecke.de>
Reply-to: tor-relays@xxxxxxxxxxxxxxxxxxxx
Sender: "tor-relays" <tor-relays-bounces@xxxxxxxxxxxxxxxxxxxx>

>The provider said it was due to Spectre mitigations and the only way for me
to fix this would be to switch to a newer (more expensive) plan...

What?

Your provider lied to you / scammed you, Spectre/Meltdown etc.
mitigations have nothing to do with applications freezing or having to
get a faster downstream/upstream speed.. at worst there's a 5-10%
performance hit if you don't have the newest CPU microcode installed
and an OS that makes use of the new insturctions (use the latest linux
kernel and intel-ucode if you can).

2020-10-11 16:48 GMT, Random Tor Node Operator <tor@xxxxxxxxxxxxxxxxxx>:
> Hi all,
>
> some weeks ago, my relay JPsi2
> (F6EC46933CE8D4FAD5CCDAA8B1C5A377685FC521) started experiencing moderate
> stability problems. It would freeze after a few hours or days. The
> provider said it was due to Spectre mitigations and the only way for me
> to fix this would be to switch to a newer (more expensive) plan...
>
> Some time later I did so and reinstalled it with Ubuntu 18.04 and placed
> the old keys into the new installation. It seems they are now expected
> to be in /var/lib/tor/.tor/keys, as opposed to /var/lib/tor/keys as I
> was used to in Ubuntu 16.04.
>
> However, it does not seem to be making it into the consensus anymore.
> Only the authority nodes moria1, dizum, and longclaw vote for Running.
> The others don't.
>
> So far I haven't been able to figure out the reason for that, so any
> help is appreciated.
>
> Here is part of the output of journalctl -u tor and the torrc file:
>
>
> Oct 11 15:04:32 j60204.servers.jiffybox.net tor[11183]: Oct 11
> 15:04:32.000 [notice] Heartbeat: It seems like we are not in the cached
> consensus.
> Oct 11 15:04:32 j60204.servers.jiffybox.net tor[11183]: Oct 11
> 15:04:32.000 [notice] Heartbeat: Tor's uptime is 8 days 0:00 hours, with
> 0 circuits open. I've sent 54.04 MB and received 163.30 MB.
> Oct 11 15:04:32 j60204.servers.jiffybox.net tor[11183]: Oct 11
> 15:04:32.000 [notice] While bootstrapping, fetched this many bytes:
> Oct 11 15:04:32 j60204.servers.jiffybox.net tor[11183]: Oct 11
> 15:04:32.000 [notice]     9368438 (server descriptor fetch)
> Oct 11 15:04:32 j60204.servers.jiffybox.net tor[11183]: Oct 11
> 15:04:32.000 [notice]     1060775 (consensus network-status fetch)
> Oct 11 15:04:32 j60204.servers.jiffybox.net tor[11183]: Oct 11
> 15:04:32.000 [notice]     13332 (authority cert fetch)
> Oct 11 15:04:32 j60204.servers.jiffybox.net tor[11183]: Oct 11
> 15:04:32.000 [notice]     2762395 (microdescriptor fetch)
> Oct 11 15:04:32 j60204.servers.jiffybox.net tor[11183]: Oct 11
> 15:04:32.000 [notice] While not bootstrapping, fetched this many bytes:
> Oct 11 15:04:32 j60204.servers.jiffybox.net tor[11183]: Oct 11
> 15:04:32.000 [notice]     111548029 (server descriptor fetch)
> Oct 11 15:04:32 j60204.servers.jiffybox.net tor[11183]: Oct 11
> 15:04:32.000 [notice]     100899 (server descriptor upload)
> Oct 11 15:04:32 j60204.servers.jiffybox.net tor[11183]: Oct 11
> 15:04:32.000 [notice]     15307429 (consensus network-status fetch)
> Oct 11 15:04:32 j60204.servers.jiffybox.net tor[11183]: Oct 11
> 15:04:32.000 [notice]     1785 (authority cert fetch)
> Oct 11 15:04:32 j60204.servers.jiffybox.net tor[11183]: Oct 11
> 15:04:32.000 [notice]     942746 (microdescriptor fetch)
> Oct 11 15:04:32 j60204.servers.jiffybox.net tor[11183]: Oct 11
> 15:04:32.000 [notice] Average packaged cell fullness: 96.710%. TLS write
> overhead: 31%
> Oct 11 15:04:32 j60204.servers.jiffybox.net tor[11183]: Oct 11
> 15:04:32.000 [notice] Circuit handshake stats since last time: 1/1 TAP,
> 0/0 NTor.
> Oct 11 15:04:32 j60204.servers.jiffybox.net tor[11183]: Oct 11
> 15:04:32.000 [notice] Since startup we initiated 0 and received 0 v1
> connections; initiated 0 and received 2 v2 connections; initiated 0 and
> received 114 v3 connections; initiated 0 and received 1899 v4
> connections; initiated 46 and received 5694 v5 connections.
> Oct 11 15:04:32 j60204.servers.jiffybox.net tor[11183]: Oct 11
> 15:04:32.000 [notice] DoS mitigation since startup: 0 circuits killed
> with too many cells. 0 circuits rejected, 0 marked addresses. 0
> connections closed. 0 single hop clients refused. 0 INTRODUCE2 rejected.
> Oct 11 18:14:03 j60204.servers.
>
>
> # cat /etc/tor/torrc
> OfflineMasterKey 1
> SOCKSPort 0
> SOCKSPolicy reject *
> RunAsDaemon 1
> ControlPort 9051
> HashedControlPassword
> 16:28CD63819CB35660601EB9CED4BC2A4252D3DB80488DFD4F22CA4AE930
> ORPort 9001
> ORPort [2a00:1158:3::1ba]:9001
> Nickname JPsi2
> RelayBandwidthRate 12500 KB
> RelayBandwidthBurst 12500 KB
> ContactInfo 0xF1ADC390 Random Tor Node Operator <tor at unterderbruecke
> (dot) de> bitcoin:1LBoEppezy2HauE957HzfFn9UGywK6aboB
> DirPort 9030
> MyFamily $B198C0B4B8C551F174FBB841A172616E3DB3124D,
> $F6EC46933CE8D4FAD5CCDAA8B1C5A377685FC521
> IPv6Exit 0
> ExitPolicy reject *:*
> ExitPolicy reject6 *:*
>
>
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Follow-Ups:
- Re: [tor-relays] Relay JPsi2 not getting into consensus anymore
  - From: Random Tor Node Operator

References:
- [tor-relays] Relay JPsi2 not getting into consensus anymore
  - From: Random Tor Node Operator

Prev by Author: Re: [tor-relays] My Tor exit node not visible
Next by Author: Re: [tor-relays] How long does it take for a relay IP to stop being displayed in metrics and web service?
Previous by thread: [tor-relays] Relay JPsi2 not getting into consensus anymore
Next by thread: Re: [tor-relays] Relay JPsi2 not getting into consensus anymore
Index(es):
- Author
- Thread