-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
I do wonder about a log message which seems not to appear before :
==> /tmp/notice.log <== Nov 26 20:10:45.000 [notice] Performing bandwidth self-test...done. Nov 26 20:19:44.000 [notice] New control connection opened from 127.0.0.1. Nov 26 20:31:13.000 [notice] Received reload signal (hup). Reloading config and resetting internal state. Nov 26 20:31:13.000 [notice] Read configuration file "/etc/tor/torrc". Nov 26 20:31:13.000 [notice] Tor 0.2.9.5-alpha opening log file. Nov 26 20:36:23.000 [notice] New control connection opened from 127.0.0.1. Nov 27 02:10:32.000 [notice] Heartbeat: Tor's uptime is 5:59 hours, with 41 circuits open. I've sent 406.63 MB and received 127.30 MB. Nov 27 02:10:32.000 [notice] Average packaged cell fullness: 96.772%. TLS write overhead: 96% Nov 27 02:10:32.000 [notice] Circuit handshake stats since last time: 0/0 TAP, 3640/3640 NTor. Nov 27 02:10:32.000 [notice] Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 16 v4 connections; and received 0 v1 connections, 1 v2 connections, 15 v3 connections, and 136434 v4 connections.
- -- Toralf PGP: C4EACDDE 0076E94E
On 27 Nov. 2016, at 20:09, Toralf Förster toralf.foerster@gmx.de wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
I do wonder about a log message which seems not to appear before :
==> /tmp/notice.log <== Nov 26 20:10:45.000 [notice] Performing bandwidth self-test...done. Nov 26 20:19:44.000 [notice] New control connection opened from 127.0.0.1. Nov 26 20:31:13.000 [notice] Received reload signal (hup). Reloading config and resetting internal state. Nov 26 20:31:13.000 [notice] Read configuration file "/etc/tor/torrc". Nov 26 20:31:13.000 [notice] Tor 0.2.9.5-alpha opening log file. Nov 26 20:36:23.000 [notice] New control connection opened from 127.0.0.1. Nov 27 02:10:32.000 [notice] Heartbeat: Tor's uptime is 5:59 hours, with 41 circuits open. I've sent 406.63 MB and received 127.30 MB. Nov 27 02:10:32.000 [notice] Average packaged cell fullness: 96.772%. TLS write overhead: 96% ...
This message is normally logged at info level, unless the TLS write overhead exceeds 15%. (Or the fullness drops below 80%.)
Perhaps your relay sent a lot of very small packets? (Interactive protocols like chat and SSH could be responsible.)
T
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 11/27/2016 10:16 AM, teor wrote:
Perhaps your relay sent a lot of very small packets? (Interactive protocols like chat and SSH could be responsible.)
Hhm,
it is a very fresh exit (setup yesterday evening) - so that might be the reason.
(My server crashed yesterday w/o any known reason and was down for an hour. I decided to kick off the old data directory and use the chance to use an ext4 fs encrypted data directory)
- -- Toralf PGP: C4EACDDE 0076E94E
tor-relays@lists.torproject.org
-
teor -
Toralf Förster