<div dir="ltr"><div><div>As a follow-up on this issue: I can't easily hook up my Raspberry Pi with a network cable, but I've had this command running for the past few days:<br> $ while :; do ping -c 3 <a href="http://www.google.com">www.google.com</a> &> /dev/null; if [ $? != 0 ]; then date; fi; done<br><br></div>There's been occasional output that doesn't correspond to the tor-arm's "Relay unresponsive" complaints. I'll contact the tor-arm people!<br><br></div>Thanks.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jan 31, 2016 at 5:27 PM, Deep Lodokus <span dir="ltr"><<a href="mailto:deep.lodokus@gmail.com" target="_blank">deep.lodokus@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">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!<br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jan 30, 2016 at 7:21 PM, Tristan <span dir="ltr"><<a href="mailto:supersluether@gmail.com" target="_blank">supersluether@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">I also have a relay running on Raspberry Pi B+. Not overclocked, connected directly via ethernet, capped at 200 KBytes bursting to 250 KBytes. </p>
<p dir="ltr">Tor is logging heartbeats just fine, and I haven't seen any unresponsive messages from arm. </p>
<p dir="ltr">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. </p>
<div class="gmail_quote"><div><div>On Jan 30, 2016 11:06 AM, "Deep Lodokus" <<a href="mailto:deep.lodokus@gmail.com" target="_blank">deep.lodokus@gmail.com</a>> wrote:<br type="attribution"></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div><div>Hi All!<br><br></div>Running a TOR relay on a Raspberry Pi B+, not overclocked, over WiFi, running Raspbian.<br>TOR is capped at<br> RelayBandwidthRate 1000 KBytes<br></div> and<br><div> RelayBandwidthBurst 1500 KBytes<br><br></div><div>While my /var/log/tor/log suggests that all is fine, my tor-arm logs suggest otherwise. See some copy/paste from logs below.<br><br></div><div>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.<br></div><div><br></div><div>Thanks!<br><br><br></div><div><br></div><div>Snippet from /var/log/tor/log:<br><i>Jan 28 19:30:51.000 [notice] Circuit handshake stats since last time: 576/576 TAP, 1281/1281 NTor.<br>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.<br>Jan 29 01:30:51.000 [notice] Average packaged cell fullness: 98.805%<br></i><br></div><div><br></div>Snippet from tor-arm logs:<br><i> │ 21:26:44 [ARM_NOTICE] Relay resumed<br> │ 21:26:17 [ARM_NOTICE] Relay unresponsive (last heartbeat: Fri Jan 29 21:26:07 2016)<br> │ 20:04:22 [ARM_NOTICE] Relay resumed<br> │ 20:03:56 [ARM_NOTICE] Relay unresponsive (last heartbeat: Fri Jan 29 20:03:42 2016)<br> │ 19:30:51 [NOTICE] Circuit handshake stats since last time: 639/639 TAP, 1104/1104 NTor.<br> │ 19:30:51 [NOTICE] TLS write overhead: 3%<br> │ 19:30:51 [NOTICE] Average packaged cell fullness: 98.954%<br> │
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.<br> │ 19:18:33 [ARM_NOTICE] Relay resumed<br> │ 19:18:12 [ARM_NOTICE] Relay unresponsive (last heartbeat: Fri Jan 29 19:17:57 2016) 21:26:07 2016)<br> │ 18:21:37 [ARM_NOTICE] Relay resumed<br> │ 18:21:15 [ARM_NOTICE] Relay unresponsive (last heartbeat: Fri Jan 29 18:21:00 2016)<br> │ 17:22:44 [ARM_NOTICE] Relay resumed<br> │ 17:22:16 [ARM_NOTICE] Relay unresponsive (last heartbeat: Fri Jan 29 17:22:02 2016)<br> │ 16:14:26 [ARM_NOTICE] Relay resumed<br> │ 16:14:10 [ARM_NOTICE] Relay unresponsive (last heartbeat: Fri Jan 29 16:13:55 2016)<br> │ 15:19:40 [ARM_NOTICE] Relay resumed<br> │ 15:19:13 [ARM_NOTICE] Relay unresponsive (last heartbeat: Fri Jan 29 15:19:02 2016)<br> │ 14:04:23 [ARM_NOTICE] Relay resumed<br> │ 14:04:01 [ARM_NOTICE] Relay unresponsive (last heartbeat: Fri Jan 29 14:03:48 2016)<br> │ 13:30:51 [NOTICE] Circuit handshake stats since last time: 593/593 TAP, 895/895 NTor.</i></div>
<br></div></div>_______________________________________________<br>
tor-relays mailing list<br>
<a href="mailto:tor-relays@lists.torproject.org" target="_blank">tor-relays@lists.torproject.org</a><br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" rel="noreferrer" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br>
<br></blockquote></div>
<br>_______________________________________________<br>
tor-relays mailing list<br>
<a href="mailto:tor-relays@lists.torproject.org" target="_blank">tor-relays@lists.torproject.org</a><br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" rel="noreferrer" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>