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

[Keifer Bly]

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 at gmail.com> 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 at gmail.com> 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 at 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 at 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 at for-privacy.net> 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 at lists.torproject.org
>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20190518/d9b8e3ff/attachment.html>