<!DOCTYPE html>
<html><head>
<meta charset="UTF-8">
</head><body><p>OK, but what is this:<br></p><p>Mar 03 21:36:31.000 [warn] Failed to start child process "tor-fw-helper" in state 9: No such file or directory<br>Mar 03 21:51:46.000 [warn] Failed to start child process "tor-fw-helper" in state 9: No such file or directory<br>Mar 03 21:56:51.000 [warn] Failed to start child process "tor-fw-helper" in state 9: No such file or directory</p><p>Tor is now online for about 36 hours, the log says 6 hours because the computer was restarted.<br></p><p>This is the latest log:<br></p><p>Mar 03 23:45:12.000 [notice] Bootstrapped 0%: Starting<br>Mar 03 23:45:24.000 [notice] Bootstrapped 80%: Connecting to the Tor network<br>Mar 03 23:45:24.000 [notice] Signaled readiness to systemd<br>Mar 03 23:45:24.000 [notice] Opening Socks listener on /var/run/tor/socks<br>Mar 03 23:45:24.000 [notice] Opening Control listener on /var/run/tor/control<br>Mar 03 23:45:25.000 [notice] Guessed our IP address as 81.10.248.112 (source: 154.35.175.225).<br>Mar 03 23:45:25.000 [notice] Bootstrapped 85%: Finishing handshake with first hop<br>Mar 03 23:45:26.000 [notice] Bootstrapped 90%: Establishing a Tor circuit<br>Mar 03 23:45:27.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.<br>Mar 03 23:45:27.000 [notice] Bootstrapped 100%: Done<br>Mar 03 23:45:27.000 [notice] Now checking whether ORPort 81.10.248.112:443 and DirPort 81.10.248.112:80 are reachable... (this may take up to 20 minutes -- look for log messages indicating success)<br>Mar 03 23:45:33.000 [notice] New control connection opened.<br>Mar 03 23:46:49.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent.<br>Mar 03 23:46:52.000 [notice] Performing bandwidth self-test...done.<br>Mar 03 23:47:03.000 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent. Publishing server descriptor.<br>Mar 04 05:45:24.000 [notice] Heartbeat: Tor's uptime is 5:59 hours, with 0 circuits open. I've sent 8.65 MB and received 15.91 MB.<br>Mar 04 05:45:24.000 [notice] Average packaged cell fullness: 12.249%. TLS write overhead: 13%<br>Mar 04 05:45:24.000 [notice] Circuit handshake stats since last time: 2/2 TAP, 1107/1107 NTor.<br>Mar 04 05:45:24.000 [notice] Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 454 v4 connections; and received 0 v1 connections, 0 v2 connections, 0 v3 connections, and 635 v4 connections.<br>Mar 04 07:35:06.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.<br>Mar 04 07:35:06.000 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".</p><p>How long does it last until the relay will be in use?<br></p><p>What do the "flags" in tor-arm mean? Sometimes it says "Running, V2Dir, Valid"<br></p><p>Yours<br></p><p>-Peter<br></p><p><br></p><p class="ox-b10055640d-default-style">Am 03.03.2018 um 10:31 schrieb teor:<br>><br>>> On 3 Mar 2018, at 18:32, peter.zehetner@liwest.at wrote:<br>>><br>>> Mar 03 00:05:38.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent.<br>>> Mar 03 00:05:45.000 [notice] Performing bandwidth self-test...done.<br>>> Mar 03 00:09:29.000 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent. Publishing server descriptor.<br>><br>> It is ok.<br>><br>>> …<br>>> Mar 03 00:52:47.000 [warn] Controller gave us config lines that didn't validate: RelayBandwidthBurst must be at least equal to RelayBandwidthRate.<br>><br>> You should check these options have the values you want.<br>><br>> T<br>> _______________________________________________<br>> tor-relays mailing list<br>> tor-relays@lists.torproject.org<br>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</p></body></html>