Thanks Tristan. I'll try with a network cable instead and see if it makes a difference in the tor-arm logs. I'll also monitor the connectivity with a frequent logged ping. And I'll contact the tor-arm guys if the problem is indeed with tor-arm and not with my connection!

On Sat, Jan 30, 2016 at 7:21 PM, Tristan <supersluether@gmail.com> wrote:

I also have a relay running on Raspberry Pi B+. Not overclocked, connected directly via ethernet, capped at 200 KBytes bursting to 250 KBytes.

Tor is logging heartbeats just fine, and I haven't seen any unresponsive messages from arm.

It seems to me that arm just isn't keeping up with the logs from Tor. Honestly, if the Tor logs aren't reporting an error, I'd say you're fine. Arm is just an add-on. Maybe it just isn't keeping up with the logs, so it thinks the relay is unresponsive.

On Jan 30, 2016 11:06 AM, "Deep Lodokus" <deep.lodokus@gmail.com> wrote:

Hi All!

Running a TOR relay on a Raspberry Pi B+, not overclocked, over WiFi, running Raspbian.
TOR is capped at
   RelayBandwidthRate 1000 KBytes

      and

   RelayBandwidthBurst 1500 KBytes

While my /var/log/tor/log suggests that all is fine, my tor-arm logs suggest otherwise. See some copy/paste from logs below.

Is something wrong with my setup? If there's indeed a loss of connectivity every hour or so, should I refrain from running this relay altogether? I haven't tried to connect the Raspberry Pi directly with a network cable, I could try that.

Thanks!

Snippet from /var/log/tor/log:
Jan 28 19:30:51.000 [notice] Circuit handshake stats since last time: 576/576 TAP, 1281/1281 NTor.
Jan 29 01:30:51.000 [notice] Heartbeat: Tor's uptime is 1 day 12:00 hours, with 23 circuits open. I've sent 565.53 MB and received 604.21 MB.
Jan 29 01:30:51.000 [notice] Average packaged cell fullness: 98.805%

Snippet from tor-arm logs:
 │ 21:26:44 [ARM_NOTICE] Relay resumed
 │ 21:26:17 [ARM_NOTICE] Relay unresponsive (last heartbeat: Fri Jan 29 21:26:07 2016)
 │ 20:04:22 [ARM_NOTICE] Relay resumed
 │ 20:03:56 [ARM_NOTICE] Relay unresponsive (last heartbeat: Fri Jan 29 20:03:42 2016)
 │ 19:30:51 [NOTICE] Circuit handshake stats since last time: 639/639 TAP, 1104/1104 NTor.
 │ 19:30:51 [NOTICE] TLS write overhead: 3%
 │ 19:30:51 [NOTICE] Average packaged cell fullness: 98.954%
 │ 19:30:51 [NOTICE] Heartbeat: Tor's uptime is 2 days 6:00 hours, with 40 circuits open. I've sent 1.72 GB and received 1.76 GB.
 │ 19:18:33 [ARM_NOTICE] Relay resumed
 │ 19:18:12 [ARM_NOTICE] Relay unresponsive (last heartbeat: Fri Jan 29 19:17:57 2016) 21:26:07 2016)
 │ 18:21:37 [ARM_NOTICE] Relay resumed
 │ 18:21:15 [ARM_NOTICE] Relay unresponsive (last heartbeat: Fri Jan 29 18:21:00 2016)
 │ 17:22:44 [ARM_NOTICE] Relay resumed
 │ 17:22:16 [ARM_NOTICE] Relay unresponsive (last heartbeat: Fri Jan 29 17:22:02 2016)
 │ 16:14:26 [ARM_NOTICE] Relay resumed
 │ 16:14:10 [ARM_NOTICE] Relay unresponsive (last heartbeat: Fri Jan 29 16:13:55 2016)
 │ 15:19:40 [ARM_NOTICE] Relay resumed
 │ 15:19:13 [ARM_NOTICE] Relay unresponsive (last heartbeat: Fri Jan 29 15:19:02 2016)
 │ 14:04:23 [ARM_NOTICE] Relay resumed
 │ 14:04:01 [ARM_NOTICE] Relay unresponsive (last heartbeat: Fri Jan 29 14:03:48 2016)
 │ 13:30:51 [NOTICE] Circuit handshake stats since last time: 593/593 TAP, 895/895 NTor.

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

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