^ r | rt rt | rt rt | rt rt rt | rt rt rt rt | rt rt rt rt | rt rt rt rt rt | rt rt rt rt rt rt | rt rt rt rt rt rt rt | rt rt rt rt rt rt rt -+---------------------------------------------------------------------------> | 12 13 14 15 16 17 18 19 20 21 22 23 00 01 02 03 04 05 06 07 08 09 10 11
h rx (MiB) tx (MiB) h rx (MiB) tx (MiB) h rx (MiB) tx (MiB) 12 11.14 14.76 20 666.90 679.48 04 11.68 15.05 13 98.65 102.77 21 27.54 29.01 05 22.50 22.41 14 961.83 954.33 22 49.58 51.97 06 14.50 17.09 15 1028.29 1021.80 23 50.87 51.47 07 11.75 15.13 16 1529.16 1520.73 00 28.72 29.68 08 10.71 13.05 17 1779.50 1768.45 01 16.91 19.62 09 32.82 14.84 18 2477.60 2456.01 02 10.76 14.93 10 13.86 15.48 19 2380.83 2358.08 03 10.06 12.70 11 1.57 2.32
From time to time I do get DSL interruptions which look like above on the traffic on one of my smaller relays. This usually last until I restart the machine manually. Anybody having a good quick idea, script to solve this and restart automatically when DSL is up again? Its on Raspian latest..
Thanks and regards
Paul
5.7 Mbps (power of ten bps is proper network context) and N number of open connections (which you don't show) is enough traffic to lockup incapable hardware like some DSL and other cheap routers and intermediate devices.
You first need to determine if the DSL link itself is truly down and for how long so if it affect tor's auto recovery, or if it's the DSL box choking, or if it's whatever else you have in your custom setup. Turn up logging and see what's going on each hardware. See what the kernel and tor daemon is saying, search all the messages. Dig in and find out what and why exactly. Then you can learn and fun to fix or design a solution that works. There is no magic "script", and not enough info provided for one other than some silly thing like
/etc/rc.local: ( sleep 86400 ; reboot ; ) & or while : ; do sleep 900 ; ping google || reboot ; done
tor-relays@lists.torproject.org
-
grarpamp -
Paul