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

[tor-relays] Relay has Low Consensus and No Exit Flag Following Upgrade

To: "N:" <tor-relays@xxxxxxxxxxxxxxxxxxxx>
Subject: [tor-relays] Relay has Low Consensus and No Exit Flag Following Upgrade
From: Chris <chris@xxxxxxxxxxxxxx>
Date: Sun, 7 May 2017 14:20:42 +0100
Delivered-to: archiver@xxxxxxxx
Delivery-date: Sun, 07 May 2017 09:21:06 -0400
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chrisada-co-uk.20150623.gappssmtp.com; s=20150623; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=kyv4xZqhG7e5cC+SbM3LqkzH2Rv/+FG2xzcR5MfBD74=; b=h43an0FivCwsDF8cOVIw5R96gv0Z3+22Y+NaXcjebP0VbxBZNqBJx1GXRPjDCnV1K8 neeEudu+hU6fkCU9CQGO4ErpIUsL9uRx0JF3RPvhnTCy2ZotQN1fmsnYR2Nt+eZAMb2D Op9OioYkjVBZoxjdVko++Ojm7WkoEw1Z8oen6B0BggVRWugZUWmjj0wWi/7KQP11A2rh nWchIaTeecc1J1kkekyLJZp5gXcI02/4NOYqBkCHqo8TZceKgDvG+67yUcj9x3KV/nl8 jHMDBX79BGn0x8QDom4p88GSsl0ZqpQuwmrcvoY2xoSPCM/HrCrSM1sfFeFUXFBYImXi vgFQ==
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>
Reply-to: tor-relays@xxxxxxxxxxxxxxxxxxxx
Sender: "tor-relays" <tor-relays-bounces@xxxxxxxxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.0

Hello,

I recently upgraded my tor exit relay's tor version to 0.2.8.12.

The uptime is 51 days and it has valid, running and stable flags.

However, it no longer has the exit node flag and the consensus is very
low (20). It also is not listed as a directory.

I suspect something else during the upgrade has broken it as I had some
SELinux issues binding to the ports before - which I resolved.

There are no errors in ARM although the log is non existent? -
permissions error?

The fingerprint is 575F2C60045805ABFDB2B7D7A78982F9571BC277

Where should I start to fix this?

Best Wishes,

Chris

-- 
Protect your privacy: encrypt your communications
GPG: CF7F98B2


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

Follow-Ups:
- Re: [tor-relays] Relay has Low Consensus and No Exit Flag Following Upgrade
  - From: nusenu
- Re: [tor-relays] Relay has Low Consensus and No Exit Flag Following Upgrade
  - From: Roger Dingledine

Prev by Author: [tor-relays] exit relay consensus weight
Next by Author: Re: [tor-relays] Relay has Low Consensus and No Exit Flag Following Upgrade
Previous by thread: Re: [tor-relays] niftybunny relays: MyFamily configuration needs an update -- fixed
Next by thread: Re: [tor-relays] Relay has Low Consensus and No Exit Flag Following Upgrade
Index(es):
- Author
- Thread