[tor-relays] Trouble Running Middle Relay On Google Cloud Debian VBS
neel at neelc.org
Fri May 17 00:22:30 UTC 2019
I think your Cron script is problematic.
0 0 1 * * apt-get update apt update && apt install -y --only-upgrade tor
killall tor tor
Would kill Tor and since you don't have "&& tor" after the "killall
tor", it is not restarting it.
But I'd advise just giving up on cron. For automatic updates, you should
look into unattended-upgrades instead of using cron.
Also, forcefully killing Tor using cron isn't a good idea because it
would terminate circuits using your relay instead of gracefully stopping
Disclaimer: I don't run Debian on my relays. I run FreeBSD relays. I
have used Debian on my desktop briefly in 2012 before switching to
FreeBSD as a desktop. I have never **really** run Debian as a server so
I can't help you further with unattended-upgrades.
On 2019-05-16 01:26, Keifer Bly wrote:
> Hi all,
> So I am starting a new middle relay using a VPS hosted on Google Cloud
> running Debian. though the relay is running, it is not appearing in
> the consensus after 10 hours. Here is the tor log, any thoughts on
> what is going on would be greatly appreciated thank you.
> May 15 18:23:47.096 [notice] Opening OR listener on 0.0.0.0:65534 
> May 15 18:23:47.000 [notice] Parsing GEOIP IPv4 file
> May 15 18:23:47.000 [notice] Parsing GEOIP IPv6 file
> May 15 18:23:47.000 [notice] Configured to measure statistics. Look
> for the *-stats files that will first be written to the data directory
> in 24 hours from now.
> May 15 18:23:47.000 [warn] You are running Tor as root. You don't need
> to, and you probably shouldn't.
> May 15 18:23:47.000 [notice] Your Tor server's identity key
> fingerprint is 'torworld 3A4E582092E7C6B822EC01F4D76F680F6C65B0A2'
> May 15 18:23:47.000 [notice] Bootstrapped 0%: Starting
> May 15 18:23:50.000 [notice] Bootstrapped 80%: Connecting to the Tor
> May 15 18:23:51.000 [notice] Guessed our IP address as 220.127.116.11
> (source: 18.104.22.168).
> May 15 18:23:52.000 [notice] Bootstrapped 85%: Finishing handshake
> with first hop
> May 15 18:23:52.000 [notice] Bootstrapped 90%: Establishing a Tor
> May 15 18:23:53.000 [notice] Tor has successfully opened a circuit.
> Looks like client functionality is working.
> May 15 18:23:53.000 [notice] Bootstrapped 100%: Done
> May 15 18:23:53.000 [notice] Now checking whether ORPort
> 22.214.171.124:65534  is reachable... (this may take up to 20
> minutes -- look for log messages indicating success)
> May 15 18:23:54.000 [notice] Self-testing indicates your ORPort is
> reachable from the outside. Excellent.
> May 15 18:23:56.000 [notice] Performing bandwidth self-test...done.
> May 16 00:23:50.000 [notice] Heartbeat: It seems like we are not in
> the cached consensus.
> May 16 00:23:50.000 [notice] Heartbeat: Tor's uptime is 5:59 hours,
> with 0 circuits open. I've sent 789 kB and received 7.41 MB.
> May 16 00:23:50.000 [notice] Average packaged cell fullness: 100.000%.
> TLS write overhead: 27%
> May 16 00:23:50.000 [notice] Circuit handshake stats since last time:
> 0/0 TAP, 6/6 NTor.
> May 16 00:23:50.000 [notice] Since startup, we have initiated 0 v1
> connections, 0 v2 connections, 0 v3 connections, and 8 v4 connections;
> and received 1 v1 connections, 0 v2 connections, 0 v3 connections, and
> 6 v4 connections.
> May 16 00:23:50.000 [notice] DoS mitigation since startup: 0 circuits
> rejected, 0 marked addresses. 0 connections closed. 0 single hop
> clients refused.
> May 16 00:58:51.000 [warn] Received http status code 404 ("Not found")
> from server '126.96.36.199:9030 ' while fetching consensus
> I also had another thing I wanted to ask. I am working on a crontab
> script to automatically update and restart the tor relay once a month
> automatically, as I am already running a bridge on another network
> that needs to be updated manually.
> Does this script look like it would get the job done? I don't have
> much experience with crontab.
> # m h dom mon dow command
> 0 0 1 * * apt-get update apt update && apt install -y --only-upgrade
> tor killall tor tor
> root at instance-1:/home/keifer_bly#
> Thank you very much.
>  http://0.0.0.0:65534
>  http://188.8.131.52:65534
>  http://184.108.40.206:9030
> tor-relays mailing list
> tor-relays at lists.torproject.org
More information about the tor-relays