[tor-relays] Tor 0.4.2.5 - Unable to Run Tor Relay on Ubuntu 18.04 LTS VPS

[Clément Février]

On 22/12/2019 22:19, David Croft wrote:
> Hi,
> 
> I'm unable to start newly setup/configured guard/middle relay Tor version 0.4.2.5 after setup & configuration of Tor on an Ubuntu 18.04 VPS server.
> 
> I'm already running a couple of Guard relays on Ubuntu 18.04 with the same VPS provider who allows for Tor Guard/Middle relays.
> 
> I've followed a blueprint for setting up the Tor relay on Tor 0.4.2.5 which worked no problem on 6 other relays I've configured & operated without issue in the last month on Ubuntu 18.04 Tor version 0.4.1.6.
> 
> I've carefully reviewed the steps I've taken to ensure I haven't made any errors during the setup/configuration process.
> 
> The issue described here is accompanied by the arrival of 0.4.2.5 & this is, in fact, the first time I've tried to set up a Tor relay on 0.4.2.5. I've also included a screenshot that highlights the issues.
> 
> I realize there might very well be other possible reasons for these errors, so I keep an open mind & will be grateful for any support or advice.
> 
> Regards,
> 
> Toni
> 
> output from:
> 
> systemctl status tor at default.service
> 
> ● tor at default.service - Anonymizing overlay network for TCP
>    Loaded: loaded (/lib/systemd/system/tor at default.service; enabled-runtime; vendor preset: enabled)
>    Active: failed (Result: exit-code) since Sun 2019-12-22 16:33:12 CET; 40min ago
>   Process: 3707 ExecStart=/usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc --RunAsDaemon 0 (code=exited, status=0/SUCCESS)
>   Process: 4643 ExecStartPre=/usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc --RunAsDaemon 0 --verify-config (code=exited, status=1/FAILURE)
>   Process: 4642 ExecStartPre=/usr/bin/install -Z -m 02755 -o debian-tor -g debian-tor -d /run/tor (code=exited, status=0/SUCCESS)
> Main PID: 3707 (code=exited, status=0/SUCCESS)

Hi,

I have the same issue after upgrading form tor version
0.4.2.5-1~bionic+1 over 0.4.1.6-1~bionic+1 in Ubuntu 18.04 in an LXD
container. It stopped working.

Here what I have in /var/log/syslog

Dec 23 13:22:29 tor systemd[1]: tor at default.service: Failed to reset
devices.list: Operation not permitted

                        Dec 23 13:22:29 tor systemd[1]: Failed to set
devices.allow on /system.slice/system-tor.slice/tor at default.service:
Operation not permitted
                                                  Dec 23 13:22:29 tor
systemd[1]: message repeated 2 times: [ Failed to set devices.allow on
/system.slice/system-tor.slice/tor at default.service: Operation not
permitted]
        Dec 23 13:22:29 tor tor[5887]: Dec 23 13:22:29.582 [notice] Tor
0.4.2.5 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1, Zlib
1.2.11, Liblzma 5.2.2, and Libzstd 1.3.3.
                            Dec 23 13:22:29 tor tor[5887]: Dec 23
13:22:29.582 [notice] Tor can't help you if you use it wrong! Learn how
to be safe at https://www.torproject.org/download/download#warning
                                                       Dec 23 13:22:29
tor tor[5887]: Dec 23 13:22:29.582 [notice] Read configuration file
"/usr/share/tor/tor-service-defaults-torrc".

         Dec 23 13:22:29 tor tor[5887]: Dec 23 13:22:29.582 [notice]
Read configuration file "/etc/tor/torrc".

                                 Dec 23 13:22:29 tor tor[5887]: Dec 23
13:22:29.583 [notice] Based on detected system memory, MaxMemInQueues is
set to 6260 MB. You can override this by setting MaxMemInQueues by hand.
                                                     Dec 23 13:22:29 tor
tor[5887]: Dec 23 13:22:29.584 [warn] ControlPort is open, but no
authentication method has been configured.  This means that any program
on your computer can reconfigure your Tor.  That's bad!  You should
upgrade your Tor controller as soon as possible.


                                Dec 23 13:22:29 tor systemd[1]: Failed
to set devices.allow on
/system.slice/system-tor.slice/tor at default.service: Operation not
permitted
                                    Dec 23 13:22:29 tor tor[5887]:
Configuration was valid


Regards,
Clément Février