Dear experts,
my relay
https://metrics.torproject.org/rs.html#details/0FBABB8C7B22CEDDFC849331E8E9E29C18081235
is shown as "down since more than three days" in Metrics.
The logs on the server however seem to show normal activity:
Nov 10 06:45:35 odin Tor[87753]: Heartbeat: It seems like we are not in the
cached consensus.
Nov 10 06:45:35 odin Tor[87753]: Heartbeat: Tor's uptime is 12:00 hours, with
59518 circuits open. I've sent 69.19 GB and received 71.95 GB. I've received
24885 connections on IPv4 and 524 on IPv6. I've made 326621 connections with
IPv4
and 106790 with IPv6.
Nov 10 06:45:35 odin Tor[87753]: While not bootstrapping, fetched this many
bytes: 10227682 (server descriptor fetch); 6336 (server descriptor upload);
595320 (consensus network-status fetch); 307663 (microdescriptor fetch)
Nov 10 06:45:35 odin Tor[87753]: Average packaged cell fullness: 12.651%. TLS
write overhead: 2%
Nov 10 06:45:35 odin Tor[87753]: Circuit handshake stats since last time: 0/0
TAP, 36156/36641 NTor.
Nov 10 06:45:35 odin Tor[87753]: Since startup we initiated 0 and received 0 v1
connections; initiated 0 and received 0 v2 connections; initiated 0 and
received 0 v3 connections; initiated 0 and received 0 v4 connections; initiated
61280 and received 25404 v5 connections.
What caught my attention is the "seems like we are not in the cached consensus"
log statement and also the Platform "Tor 0.4.8.13 on FreeBSD (version is
0.4.8.12 in consensus)" on Metrics
While being shown as "down" in Metrics, the stats continue to be updated and
config changes like 'MaxAdvertisedBandwidth' are properly reflected in Metrics
Is there some issue with Metrics in conjunction with FreeBSD ?
On the OS, the only changes were automated OS updates.
Thanks for your feedback
Regards, C.
--
Sent with https://mailfence.com
Secure and private email
_______________________________________________
tor-relays mailing list -- [email protected]
To unsubscribe send an email to [email protected]
