Re: [tor-relays] Trouble Running Middle Relay On Google Cloud Debian VBS

Subject: Re: [tor-relays] Trouble Running Middle Relay On Google Cloud Debian VBS

From: Keifer Bly <keifer.bly@xxxxxxxxx>

Date: Sat, 18 May 2019 11:43:43 -0700

Delivery-date: Sat, 18 May 2019 16:37:15 -0400

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=SuNhBZnjz43ZgikaoRSznosIqbUdfwvrBibkkExrvbA=; b=b6/GF9utWIhLCG7xVwE9Mgot4S7Kl0USxBc45hBkvxm97O2ohYqL54KVrehtfgiRHe ONnZZUfQ9u/w6nLAUi1dyDl+YSVz4nJy2y3EtqpVY+RgVgSPtqGR4X31+1L5bq6CrvYd igSpfXxiFMiHu9a/CGGWJ71KuT8lrCR0Q+6KN33AqXSA86XLvFZBBMIZO8QuCJo3He3j TnDsI+gDEY1LK9WetmnDZBStSVPDKrf+tVMxdnHblcYnnZt4Cp5RF39WGk7i0znwe0NX IBQDxymS2c2tEj3Tb+S/DJgODnsSpjjgttvUf9YcsLFtmPD0BOOCWm5yurVeiG8r+gpJ 6SEw==

In-reply-to: <CADqUGAPAd4qrJ1PGaV7-utToO9=RJw7fPN215K2FyxRFs6us+Q@mail.gmail.com>

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: <CADqUGAMe5ixz_Gk0Spdc2T5fKcmZHGwv2Cxz9HxQbpfNHJC9VQ@mail.gmail.com> <d4df844f606ccee5160fdbfc9cf1472d@neelc.org> <1289536b3d0ffe84d69f55f7cca5b6f2@for-privacy.net> <CADqUGANqwTV9xSH+zsejisj7DaZnNQ=gZcRDyWUv5RQfaODXQQ@mail.gmail.com> <CADqUGAPAd4qrJ1PGaV7-utToO9=RJw7fPN215K2FyxRFs6us+Q@mail.gmail.com>

Reply-to: tor-relays@xxxxxxxxxxxxxxxxxxxx

Sender: "tor-relays" <tor-relays-bounces@xxxxxxxxxxxxxxxxxxxx>

May 18 07:20:01.000 [notice] Circuit handshake stats since last time: 0/0 TAP, 5/5 NTor.
May 18 07:20:01.000 [notice] Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 6 v4 connections; and received 0 v1 connections, 0 v2 connections, 0 v3 connections, and 5 v4 connections.
May 18 07:20:01.000 [notice] DoS mitigation since startup: 0 circuits rejected, 0 marked addresses. 0 connections closed. 0 single hop clients refused.
May 18 13:20:01.000 [notice] Heartbeat: It seems like we are not in the cached consensus.
May 18 13:20:01.000 [notice] Heartbeat: Tor's uptime is 11:59 hours, with 0 circuits open. I've sent 877 kB and received 15.21 MB.
May 18 13:20:01.000 [notice] Circuit handshake stats since last time: 0/0 TAP, 0/0 NTor.
May 18 13:20:01.000 [notice] Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 6 v4 connections; and received 0 v1 connections, 0 v2 connections, 0 v3 connections, and 5 v4 connections.
May 18 13:20:01.000 [notice] DoS mitigation since startup: 0 circuits rejected, 0 marked addresses. 0 connections closed. 0 single hop clients refused.

This is the recent log. So it is sending and receiving data but not appearing in the relay list. I wonder why that might be? Thanks.

--Keifer

On Sat, May 18, 2019 at 11:40 AM Keifer Bly <keifer.bly@xxxxxxxxx> wrote:

Oh sorry. What it actually says is everything is already up to date. So I wonder, why would the relay not appear in the consensus? Thanks.
--Keifer

On Sat, May 18, 2019 at 11:23 AM Keifer Bly <keifer.bly@xxxxxxxxx> wrote:
> on Debian:

apt-get install -y unattended-upgrades apt-listchanges
cp /usr/share/unattended-upgrades/20auto-upgrades
/etc/apt/apt.conf.d/20auto-upgrades
service unattended-upgrades restart

This is what happened after running that.

root@instance-1:/home/keifer_bly# apt-get install -y unattended-upgrades apt-listchanges
Reading package lists... Done
Building dependency tree
Reading state information... Done
apt-listchanges is already the newest version (3.10).
unattended-upgrades is already the newest version (0.93.1+nmu1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@instance-1:/home/keifer_bly# cp /usr/share/unattended-upgrades/20auto-upgrades
cp: missing destination file operand after '/usr/share/unattended-upgrades/20auto-upgrades'
Try 'cp --help' for more information.

What file would be missing I wonder? Thanks.

--Keifer

On Sat, May 18, 2019 at 6:35 AM <lists@xxxxxxxxxxxxxxx> wrote:
On 17.05.2019 02:22, Neel Chauhan wrote:

> But I'd advise just giving up on cron. For automatic updates, you
> should look into unattended-upgrades instead of using cron.
+1

on Debian:

apt-get install -y unattended-upgrades apt-listchanges
cp /usr/share/unattended-upgrades/20auto-upgrades
/etc/apt/apt.conf.d/20auto-upgrades
service unattended-upgrades restart

Default it upgrades the security sources.
see comments in 50unattended-upgrades

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

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