Re: [tor-relays] Tor-arm failure
Oops, sorry - my bad. Didn't spot that this was already answered under a different email subject. :) On Sat, Sep 2, 2017 at 6:27 PM, Damian Johnson wrote: > Hi Ralph, I think there's some confusion about the ssh verses tor > password. All I'm suggesting is that instead of > 'HashedControlPassword' you use 'CookieAuthentication 1' in your torrc > instead. This is discussed a bit on the following in case you'd care > to read more... > > https://stem.torproject.org/faq.html#can-i-interact-with-tors-controller-interface-directly > > Cheers! -Damian > > > On Sat, Sep 2, 2017 at 2:01 PM, Ralph Seichter > wrote: >> On 02.09.17 21:26, Damian Johnson wrote: >> >>> I dropped that since it posed a security issue. >> >> Sigh... That seems a bit overzealous to me. >> >>> I'd suggest cookie authentication if you'd care to rely on file >>> permissions rather than something you know. That'll work transparently. >> >> I don't think I understand what exactly you are suggesting. Could you >> provide an example? I can currently do the following with 'arm', and >> want to it with 'nyx' as well: >> >> me@mynotebook $ ssh foo@tornode >> foo@tornode $ sudo -u tor /usr/bin/arm >> >> I have to enter SSH keyfile password(*) and SUDO password already, and >> don't want to enter yet another password for the Tor controller. Since >> I am the only human who can SSH to my Tor nodes, having a password in >> ~/.nyx/config would be a "risk" (grin) I'm perfectly willing to take. >> >> -Ralph >> >> (*) I'm aware of ssh-agent. >> ___ >> 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
Re: [tor-relays] Tor-arm failure
Hi Ralph, I think there's some confusion about the ssh verses tor password. All I'm suggesting is that instead of 'HashedControlPassword' you use 'CookieAuthentication 1' in your torrc instead. This is discussed a bit on the following in case you'd care to read more... https://stem.torproject.org/faq.html#can-i-interact-with-tors-controller-interface-directly Cheers! -Damian On Sat, Sep 2, 2017 at 2:01 PM, Ralph Seichter wrote: > On 02.09.17 21:26, Damian Johnson wrote: > >> I dropped that since it posed a security issue. > > Sigh... That seems a bit overzealous to me. > >> I'd suggest cookie authentication if you'd care to rely on file >> permissions rather than something you know. That'll work transparently. > > I don't think I understand what exactly you are suggesting. Could you > provide an example? I can currently do the following with 'arm', and > want to it with 'nyx' as well: > > me@mynotebook $ ssh foo@tornode > foo@tornode $ sudo -u tor /usr/bin/arm > > I have to enter SSH keyfile password(*) and SUDO password already, and > don't want to enter yet another password for the Tor controller. Since > I am the only human who can SSH to my Tor nodes, having a password in > ~/.nyx/config would be a "risk" (grin) I'm perfectly willing to take. > > -Ralph > > (*) I'm aware of ssh-agent. > ___ > 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
Re: [tor-relays] Tor-arm failure
On 02.09.17 21:26, Damian Johnson wrote: > I dropped that since it posed a security issue. Sigh... That seems a bit overzealous to me. > I'd suggest cookie authentication if you'd care to rely on file > permissions rather than something you know. That'll work transparently. I don't think I understand what exactly you are suggesting. Could you provide an example? I can currently do the following with 'arm', and want to it with 'nyx' as well: me@mynotebook $ ssh foo@tornode foo@tornode $ sudo -u tor /usr/bin/arm I have to enter SSH keyfile password(*) and SUDO password already, and don't want to enter yet another password for the Tor controller. Since I am the only human who can SSH to my Tor nodes, having a password in ~/.nyx/config would be a "risk" (grin) I'm perfectly willing to take. -Ralph (*) I'm aware of ssh-agent. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Tor-arm failure
HI Ralph. I dropped that since it posed a security issue. When using password authentication nyx provides a prompt, then drop the reference so the memory can be released (if someone knows a better way of purging a password from memory in python I'm all ears). I'd suggest cookie authentication if you'd care to rely on file permissions rather than something you know. That'll work transparently. Cheers! -Damian On Sat, Sep 2, 2017 at 4:32 AM, Ralph Seichter wrote: > On 01.09.2017 21:26, Damian Johnson wrote: > >> Nyx (aka arm) is undergoing a rewrite. Mind giving the new codebase >> a whirl? > > I had a look, and I am wondering if there is any way to specify the > controller password in ~/.nyx/config ? It is supported in arm, via > the startup.controlPassword option in ~/.arm/armrc . > > -Ralph > ___ > 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
Re: [tor-relays] Tor-arm failure
On 01.09.2017 21:26, Damian Johnson wrote: > Nyx (aka arm) is undergoing a rewrite. Mind giving the new codebase > a whirl? I had a look, and I am wondering if there is any way to specify the controller password in ~/.nyx/config ? It is supported in arm, via the startup.controlPassword option in ~/.arm/armrc . -Ralph ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Tor-arm failure
Hi Arisbe. Think I vaguely recall seeing a report about this before. Nyx (aka arm) is undergoing a rewrite. Mind giving the new codebase a whirl? https://nyx.torproject.org/ Unfortunately there aren't any releases yet so you'll need to snag it from git. Think the following should do the trick... % git clone https://git.torproject.org/stem.git % git clone https://git.torproject.org/nyx.git % cd nyx % ln -s ../stem/stem stem % ./run_nyx On Fri, Sep 1, 2017 at 11:27 AM, Arisbe wrote: > Hello people, > > I'm not a python programmer so I need some help with a problem. I have a > number of Tor nodes and some bridges. Occasionally, when I install tor_arm > I get a divide by zero message as follows: > > Exception in thread Thread-69: Traceback (most recent call last): > > File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner > selt.run() > > File "/usr/share/arm/util/sysTools.py", line 517, in runnewValues["cpuAvg"] > = total CpuTime / uptime > > ZeroDivisionError: integer division or modulo by zero > > Exception in thread Thread-70 .. > > I'm running debian jessie in this most recent example. 2 G memory, 20 G > hdd. This is a bridge with only some daily use but typically 10-12 > circuits. > > Does someone have experience debugging this problem? > > Thanks! > > > ___ > 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
[tor-relays] Tor-arm failure
Hello people, I'm not a python programmer so I need some help with a problem. I have a number of Tor nodes and some bridges. Occasionally, when I install tor_arm I get a divide by zero message as follows: Exception in thread Thread-69: Traceback (most recent call last): File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner selt.run() File "/usr/share/arm/util/sysTools.py", line 517, in runnewValues["cpuAvg"] = total CpuTime / uptime ZeroDivisionError: integer division or modulo by zero Exception in thread Thread-70 .. I'm running debian jessie in this most recent example. 2 G memory, 20 G hdd. This is a bridge with only some daily use but typically 10-12 circuits. Does someone have experience debugging this problem? Thanks! ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Tor-arm
>> Is this ok or is it deprecated and I should install something else? And >> how? > > It works well enough now and it is being improved slowly with a name change. > (As far as I can tell.). Yup, that is correct. I was hoping to have the next release out for you by around this time but it's coming along pretty slowly. None the less it is making progress and I should be putting out a call for beta testers in a few months. Cheers! -Damian ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Tor-arm
Cristian, > tor-arm > > Is this ok or is it deprecated and I should install something else? And > how? It works well enough now and it is being improved slowly with a name change. (As far as I can tell.). Robert ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Tor-arm
This package is usually running fine for me... Le 16/06/2016 à 12:07, Cristian Consonni a écrit : > 2016-06-16 3:00 GMT+02:00 grarpamp : >> On 6/14/16, NotRandom Someone wrote: >>> What do you think about using tor-arm ? >> https://gitweb.torproject.org/nyx.git/ >> >> Arm now known as Nyx. > On my node (running with Debian Jesse as OS) I have installed this package: > https://packages.debian.org/jessie/tor-arm > > Is this ok or is it deprecated and I should install something else? And how? > > Thank you. > > Cristian > ___ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays -- Petrusko PubKey EBE23AE5 C0BF 2184 4A77 4A18 90E9 F72C B3CA E665 EBE2 3AE5 signature.asc Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Tor-arm
2016-06-16 3:00 GMT+02:00 grarpamp : > On 6/14/16, NotRandom Someone wrote: >> What do you think about using tor-arm ? > > https://gitweb.torproject.org/nyx.git/ > > Arm now known as Nyx. On my node (running with Debian Jesse as OS) I have installed this package: https://packages.debian.org/jessie/tor-arm Is this ok or is it deprecated and I should install something else? And how? Thank you. Cristian ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Tor-arm
On 6/14/16, NotRandom Someone wrote: > What do you think about using tor-arm ? https://gitweb.torproject.org/nyx.git/ Arm now known as Nyx. Your query lack detailed context or specifics for further advice you. So just try it, see if suits you. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] Tor-arm
Hi everyone, I have a question about monitoring a tor middle relay. What do you think about using tor-arm ? Is it safe ? (Bugs, leaks,etc) ? Or using just the informations on globe/atlas.torproject.org is more useful ? Thank you. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] tor-arm bandwidth state file -xxxx seconds is missing?
Thanks! On Jan 29, 2016 1:08 AM, "Louie Cardone-Noott" wrote: > > If I've understood your question: press i and select 1 second, then > enter. > > Press h for other keyboard options. > > On Fri, 29 Jan 2016, at 12:17 AM, SuperSluether wrote: > > How would I change the interval? Arm keeps telling me there's no armrc > > loaded, and to see the sample file for options, but I can't find an > > armrc.sample file anywhere. > > > > On 01/28/2016 01:08 PM, Pierre L. wrote: > > > And about live graphic, I usually change 'interval' to 1second for > example, in the arm menu, and it's ok > > > > > > tor-relays@lists.torproject.org a écrit : > > >> Ok, so just wait for arm to get updated then? I guess as long as it's > not hurting anything, it doesn't matter too much.> On 01/28/2016 12:06 PM, > Damian Johnson wrote:>> When arm starts it attempts to read tor's state > file to get past > > >>> bandwidth information. That is a notice level message, not an error, > > >>> and it's simply telling you that it wasn't able to prepopulate all > the > > >>> data. > > >>> > > >>> Tor has changed its state file format which actually breaks that > > >>> feature entirely. The next release of arm (now called nyx) accounts > > >>> for this. > > >>> > > >>> > > >>> On Thu, Jan 28, 2016 at 10:02 AM, SuperSluether < > supersluet...@gmail.com> wrote:>>> Found this error when checking my > relay today: > > ARM_NOTICE Read the last day of bandwidth history from the state > file (- > > seconds is missing) > > > > Every time I start arm, the -xxx seconds missing is different. The > bandwidth > > graph is also stuck, but real-time data is still shown. > > > > Is this a problem with Tor, or with Arm? Anyone know a fix? > > ___ > > 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 > > > ___ > > > 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 > ___ > 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
Re: [tor-relays] tor-arm bandwidth state file -xxxx seconds is missing?
If I've understood your question: press i and select 1 second, then enter. Press h for other keyboard options. On Fri, 29 Jan 2016, at 12:17 AM, SuperSluether wrote: > How would I change the interval? Arm keeps telling me there's no armrc > loaded, and to see the sample file for options, but I can't find an > armrc.sample file anywhere. > > On 01/28/2016 01:08 PM, Pierre L. wrote: > > And about live graphic, I usually change 'interval' to 1second for example, > > in the arm menu, and it's ok > > > > tor-relays@lists.torproject.org a écrit : > >> Ok, so just wait for arm to get updated then? I guess as long as it's not > >> hurting anything, it doesn't matter too much.> On 01/28/2016 12:06 PM, > >> Damian Johnson wrote:>> When arm starts it attempts to read tor's state > >> file to get past > >>> bandwidth information. That is a notice level message, not an error, > >>> and it's simply telling you that it wasn't able to prepopulate all the > >>> data. > >>> > >>> Tor has changed its state file format which actually breaks that > >>> feature entirely. The next release of arm (now called nyx) accounts > >>> for this. > >>> > >>> > >>> On Thu, Jan 28, 2016 at 10:02 AM, SuperSluether > >>> wrote:>>> Found this error when checking my relay today: > ARM_NOTICE Read the last day of bandwidth history from the state file > (- > seconds is missing) > > Every time I start arm, the -xxx seconds missing is different. The > bandwidth > graph is also stuck, but real-time data is still shown. > > Is this a problem with Tor, or with Arm? Anyone know a fix? > ___ > 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 > > ___ > > 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 ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] tor-arm bandwidth state file -xxxx seconds is missing?
How would I change the interval? Arm keeps telling me there's no armrc loaded, and to see the sample file for options, but I can't find an armrc.sample file anywhere. On 01/28/2016 01:08 PM, Pierre L. wrote: And about live graphic, I usually change 'interval' to 1second for example, in the arm menu, and it's ok tor-relays@lists.torproject.org a écrit : Ok, so just wait for arm to get updated then? I guess as long as it's not hurting anything, it doesn't matter too much.> On 01/28/2016 12:06 PM, Damian Johnson wrote:>> When arm starts it attempts to read tor's state file to get past bandwidth information. That is a notice level message, not an error, and it's simply telling you that it wasn't able to prepopulate all the data. Tor has changed its state file format which actually breaks that feature entirely. The next release of arm (now called nyx) accounts for this. On Thu, Jan 28, 2016 at 10:02 AM, SuperSluether wrote:>>> Found this error when checking my relay today: ARM_NOTICE Read the last day of bandwidth history from the state file (- seconds is missing) Every time I start arm, the -xxx seconds missing is different. The bandwidth graph is also stuck, but real-time data is still shown. Is this a problem with Tor, or with Arm? Anyone know a fix? ___ 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 ___ 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
Re: [tor-relays] tor-arm bandwidth state file -xxxx seconds is missing?
Not hurting anything and in general if you see a message that's 'notice' that means 'this is fine, just for your information'. If it was a problem it would way it was a warning or error. On Thu, Jan 28, 2016 at 10:29 AM, SuperSluether wrote: > Ok, so just wait for arm to get updated then? I guess as long as it's not > hurting anything, it doesn't matter too much. > > > On 01/28/2016 12:06 PM, Damian Johnson wrote: >> >> When arm starts it attempts to read tor's state file to get past >> bandwidth information. That is a notice level message, not an error, >> and it's simply telling you that it wasn't able to prepopulate all the >> data. >> >> Tor has changed its state file format which actually breaks that >> feature entirely. The next release of arm (now called nyx) accounts >> for this. >> >> >> On Thu, Jan 28, 2016 at 10:02 AM, SuperSluether >> wrote: >>> >>> Found this error when checking my relay today: >>> >>> ARM_NOTICE Read the last day of bandwidth history from the state file >>> (- >>> seconds is missing) >>> >>> Every time I start arm, the -xxx seconds missing is different. The >>> bandwidth >>> graph is also stuck, but real-time data is still shown. >>> >>> Is this a problem with Tor, or with Arm? Anyone know a fix? >>> ___ >>> 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 > > > ___ > 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
Re: [tor-relays] tor-arm bandwidth state file -xxxx seconds is missing?
Ok, so just wait for arm to get updated then? I guess as long as it's not hurting anything, it doesn't matter too much. On 01/28/2016 12:06 PM, Damian Johnson wrote: When arm starts it attempts to read tor's state file to get past bandwidth information. That is a notice level message, not an error, and it's simply telling you that it wasn't able to prepopulate all the data. Tor has changed its state file format which actually breaks that feature entirely. The next release of arm (now called nyx) accounts for this. On Thu, Jan 28, 2016 at 10:02 AM, SuperSluether wrote: Found this error when checking my relay today: ARM_NOTICE Read the last day of bandwidth history from the state file (- seconds is missing) Every time I start arm, the -xxx seconds missing is different. The bandwidth graph is also stuck, but real-time data is still shown. Is this a problem with Tor, or with Arm? Anyone know a fix? ___ 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 ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] tor-arm bandwidth state file -xxxx seconds is missing?
When arm starts it attempts to read tor's state file to get past bandwidth information. That is a notice level message, not an error, and it's simply telling you that it wasn't able to prepopulate all the data. Tor has changed its state file format which actually breaks that feature entirely. The next release of arm (now called nyx) accounts for this. On Thu, Jan 28, 2016 at 10:02 AM, SuperSluether wrote: > Found this error when checking my relay today: > > ARM_NOTICE Read the last day of bandwidth history from the state file (- > seconds is missing) > > Every time I start arm, the -xxx seconds missing is different. The bandwidth > graph is also stuck, but real-time data is still shown. > > Is this a problem with Tor, or with Arm? Anyone know a fix? > ___ > 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
[tor-relays] tor-arm bandwidth state file -xxxx seconds is missing?
Found this error when checking my relay today: ARM_NOTICE Read the last day of bandwidth history from the state file (- seconds is missing) Every time I start arm, the -xxx seconds missing is different. The bandwidth graph is also stuck, but real-time data is still shown. Is this a problem with Tor, or with Arm? Anyone know a fix? ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] tor-arm question
Last 'log' entry was from a few days ago when I started it. Just shows bootstrapping 0-100% without errors. 'notices.log' entries happen fairly regularly. Mostly heartbeat uptime notifications and lifetime sent/received. Also bugging me to add my ContactInfo. No errors relating to tor-arm's odd behavior. On Thu, Jun 19, 2014 at 8:24 AM, Contra Band wrote: > What does the > > cat /var/log/tor/log > > says? > > On Tuesday, June 17, 2014 6:56 PM, Adam Griffin > wrote: > > > > Running top in a separate SSH session shows ~50% load average. I imagine > spikes would cause the CLI interruptions and maybe relay > unresponsive/resumed notices. Did you have the same blank uptime issue? > > > > On Tue, Jun 17, 2014 at 2:08 PM, Elrippo > wrote: > > -BEGIN PGP SIGNED MESSAGE- > >Hash: SHA512 > > > >Had the same issues on my pi when running over ssh. > >It simply is the fact, that your pi is running almost on max load. Type > top in your console, and watch the pi working :) > > > > > >On 17. Juni 2014 19:28:23 MESZ, Adam Griffin wrote: > >>Hi, > >> > >>Just started a new tor relay on my raspberry pi yesterday and I'm > >>monitoring with tor-arm over ssh. I'm currently listed on > >>atlas.torproject.org with flags 'Fast', 'Running', 'V2Dir', and 'Valid' > >>with > 17hrs uptime. > >> > >>However, tor-arm is showing a blank for uptime and about once a minute, > >>the > >>CLI goes blank and then flickers back. (the flickering happens at the > >>same > >>rate for local and remote SSH) Also, about once every couple hours I > >>get a > >>'Relay unresponsive' and then 10 seconds later 'Relay resumed'. > >> > >>Anything to do to remedy these issues? > >> > >> > >> > >> > >>___ > >>tor-relays mailing list > >>tor-relays@lists.torproject.org > >>https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > > >- -- > >We don't bubble you, we don't spoof you ;) > >Keep your data encrypted! > >Log you soon, > >your Admin > >elri...@elrippoisland.net > > > >Encrypted messages are welcome. > >0x84DF1F7E6AE03644 > > > >- -BEGIN PGP PUBLIC KEY BLOCK- > >Version: GnuPG v1.4.11 (GNU/Linux) > > > >mQINBFH797MBEAC0Y0NeI7lmDR9szTEcWuHuRe0r/WjSRC0Nr5nXsghuMcxpJ3Dd > >BOBimi4hdMMK4iqPVMwNw6GpKYR3A9LHHjbYRXHUKrJmB+BaJVyzJXN5H6XvxTTb > >UfX+DaXAGJW/G+3cBB3qm/QaU8QGkBKfXq0DLTaTGPkGKxEAldj/8onGZhawdJs+ > >B92JrW+S2HDh15pIuXzSqe7eCcIOdvvwfWe0fJi2AraA7LYGpxP6GcC/b9JJpbq5 > >Y6DfE2Aun9ZK3iHqURyrms0Whbv1CgmUahL2MVYCsTsXwe0GwlAxxKvjXAiXuo+R > >9wO5wsXvVVSVNqsk9Yqi+wYzdPKndTU0GyxSApQHroF+cxaZ8Lk0xloj18+LdCSs > >e5IiTSXH0MMsDdWWdHlrgk+bgDG+0Gu3ne4vMwGdKO7AhYgQW/ueMy4RnkG/nsV9 > >jry5BO4gGAI1Ij8KvqUzEnvJFGE3ptJogU+zazWWDUWmL3ecKb3aDRlJFnZ3kJ5h > >q8GolZVjpk99V+4B5WVRPXdej/p5J19tXycK/jdNmr4oC8NyUhIpe8xHELnfoB4z > >+rxiTx+KMnW0rY8EQg8O2ixEYt5my90IwQkxcxIxextVrqjJjYn8extc2/v8yGzI > >KmTEJxdADB5v/Jx4HiLHNDSfBUb8gfONCkNSTYvTcSwTjWzHOkXeE/9ZbQARAQAB > >tD5lbHJpcHBvIChrZWVwIHlvdXIgZGF0YSBlbmNyeXB0ZWQpIDxlbHJpcHBvQGVs > >cmlwcG9pc2xhbmQubmV0PokCOAQTAQIAIgUCUfv3swIbLwYLCQgHAwIGFQgCCQoL > >BBYCAwECHgECF4AACgkQhN8ffmrgNkT8+BAAoAXBqu4/O2Cs5FSWWZpzgScNEgq7 > >uHhOKeYmRfgKlOUPoYlPB1DBqdOAXSKb9OvsmyOvpoGnqijB7aAJBoyQYW/OCQgd > >U8L4eTCf4yRZnfFLdgskcPfN1p0Rs/yinGEooBJFtYa7mT6J0UTW2JjCLZK2AFCW > >oF+KBu5JICXGBXigb2ZbX1jWjxP5H1RidQw6HF5z4z34SjLWAOOeZ8B/Xfz6Fs0s > >IAuLu2O4HE4DI8Qu196LhSVHHgr3uMTkvN1t5nKwyjrRQztwXXk9qIomII3ydNYb > >BYAGdWNNMfLb1kmDwC5wQHAFvSP1aiMF3aKAY+gl2wXSGO6JqM0SteJS3dytIljI > >kzu0atc9HuGs/HDQgdmpAS4WU2YefEr/WieltSiAKlwuC+3wg+CONJ6TE1vgNDU/ > >axerttb0jq7UQb/nAp05bsrB7XH1Vs+1ON9lUPEfWRmwQcrVK5JUrUWa/4tA/UeM > >XvFcPFtFluGTlLewgJIqcvjPXFwpbDZprXJsMkwew/A6B6n3+0sbgf7p3QSGkVbi > >dwQAymTbHdYqLnbcnKZhjto3Wjw1J5QB2wuiRYlpjV3i7AWTGlqoSTOWCCV+HamQ > >qeFYNYAWNFx3+J/oi7xDi8t9bHVNA205equ+y2sj3G5uGJ6LSHQ8AXp9uOipUUvU > >1MJN0yLXr9PIwvi5Ag0EUfv3swEQAL0+MnxHGrTjSYdfdua4SBpmytDONM1EngeY > >s+WyaC/760MughKbaysI/nK2LB1vnwEY7f3NM4fxBx8u2T7VBm6Ez6Fs23Bb8Rkz > >f97bPSdxCmg64GPHfLA9uwTIXcYS+MpI86WOf6eWY0rRpf7Y9Nl7YoUNvzOyUPqc > >ggdcnHce8zYv7A/WS8flZDm8tVFPsHrQDEwNMws7ZhiNnHkeZeRJrvCuB7oEVich > >O/ROYoA5o6NozWYQbjxe1f6Yur4Q10qgVcxVnyLFJSbg6vZSzL7KYh3Z5iBOzPHt > >7cwEDrW8W4Kl2Qj8rhJ4Wxs94CAtua7IXK44sVZWQbyHcOXRikgGMZKkEZzVCQa5 > >KD1u1ZrcBCyuMAir0hsmS3jhCUwpiE2c3SRk8O8CgixhTcBk0X/k9ZFu3Hbi1JMB > >FLzs/Nq3tYAYvVivhPloSxmYBPsafYHCZM83yBNNsralXh5zjB+di90G+AMXt2PN > >LTcdovZuWtC0s8/jrx+zv/AA4FAGYU9OVl+YL9ybFX8gSdMEcixyzQcKfiFBjpWv > >5iFrwIuDlaXMcheyrhc9aGOxfx44OXc505+VjO/1Q/8EOWlJ6UwOi6GMkj5T+RFJ > >MDyP0UixS7dt6wTuD5t6PRuyWWxZswgrbL9hjwGFr154Z19TWeNWc23pWtUvQJos > >UCxl2nFHABEBAAGJBD4EGAECAAkFAlH797MCGy4CKQkQhN8ffmrgNkTBXSAEGQEC > >AAYFAlH797MACgkQJEPd69lQ0evA+Q/+M7lSFlrQWiRsFqDjh+kTJc+0OEBCvnfo > >N2KPyXXbfc//qup55PfEygE6C60zvrlv3WE33GZ5GS5MLuDMP82b+a5Yt16NQU7L > >WtAg1g0S0BvazW+28TgnfO8bhbGaFeE9ccw3xLmlbwZQ3f3LtMKdwFIROiG6hvAs > >9U54QYti3tv9DowRYYWpdr0Ga8RqeGNtCKc0v2opy51MpzKWjwUW0i3XlSlyY8Lj > >1KT8PyznNPw32nYpmDizz+0OUJNnn/
Re: [tor-relays] tor-arm question
What does the cat /var/log/tor/log says? On Tuesday, June 17, 2014 6:56 PM, Adam Griffin wrote: Running top in a separate SSH session shows ~50% load average. I imagine spikes would cause the CLI interruptions and maybe relay unresponsive/resumed notices. Did you have the same blank uptime issue? On Tue, Jun 17, 2014 at 2:08 PM, Elrippo wrote: -BEGIN PGP SIGNED MESSAGE- >Hash: SHA512 > >Had the same issues on my pi when running over ssh. >It simply is the fact, that your pi is running almost on max load. Type top in >your console, and watch the pi working :) > > >On 17. Juni 2014 19:28:23 MESZ, Adam Griffin wrote: >>Hi, >> >>Just started a new tor relay on my raspberry pi yesterday and I'm >>monitoring with tor-arm over ssh. I'm currently listed on >>atlas.torproject.org with flags 'Fast', 'Running', 'V2Dir', and 'Valid' >>with > 17hrs uptime. >> >>However, tor-arm is showing a blank for uptime and about once a minute, >>the >>CLI goes blank and then flickers back. (the flickering happens at the >>same >>rate for local and remote SSH) Also, about once every couple hours I >>get a >>'Relay unresponsive' and then 10 seconds later 'Relay resumed'. >> >>Anything to do to remedy these issues? >> >> >> >> >>___ >>tor-relays mailing list >>tor-relays@lists.torproject.org >>https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > >- -- >We don't bubble you, we don't spoof you ;) >Keep your data encrypted! >Log you soon, >your Admin >elri...@elrippoisland.net > >Encrypted messages are welcome. >0x84DF1F7E6AE03644 > >- -BEGIN PGP PUBLIC KEY BLOCK- >Version: GnuPG v1.4.11 (GNU/Linux) > >mQINBFH797MBEAC0Y0NeI7lmDR9szTEcWuHuRe0r/WjSRC0Nr5nXsghuMcxpJ3Dd >BOBimi4hdMMK4iqPVMwNw6GpKYR3A9LHHjbYRXHUKrJmB+BaJVyzJXN5H6XvxTTb >UfX+DaXAGJW/G+3cBB3qm/QaU8QGkBKfXq0DLTaTGPkGKxEAldj/8onGZhawdJs+ >B92JrW+S2HDh15pIuXzSqe7eCcIOdvvwfWe0fJi2AraA7LYGpxP6GcC/b9JJpbq5 >Y6DfE2Aun9ZK3iHqURyrms0Whbv1CgmUahL2MVYCsTsXwe0GwlAxxKvjXAiXuo+R >9wO5wsXvVVSVNqsk9Yqi+wYzdPKndTU0GyxSApQHroF+cxaZ8Lk0xloj18+LdCSs >e5IiTSXH0MMsDdWWdHlrgk+bgDG+0Gu3ne4vMwGdKO7AhYgQW/ueMy4RnkG/nsV9 >jry5BO4gGAI1Ij8KvqUzEnvJFGE3ptJogU+zazWWDUWmL3ecKb3aDRlJFnZ3kJ5h >q8GolZVjpk99V+4B5WVRPXdej/p5J19tXycK/jdNmr4oC8NyUhIpe8xHELnfoB4z >+rxiTx+KMnW0rY8EQg8O2ixEYt5my90IwQkxcxIxextVrqjJjYn8extc2/v8yGzI >KmTEJxdADB5v/Jx4HiLHNDSfBUb8gfONCkNSTYvTcSwTjWzHOkXeE/9ZbQARAQAB >tD5lbHJpcHBvIChrZWVwIHlvdXIgZGF0YSBlbmNyeXB0ZWQpIDxlbHJpcHBvQGVs >cmlwcG9pc2xhbmQubmV0PokCOAQTAQIAIgUCUfv3swIbLwYLCQgHAwIGFQgCCQoL >BBYCAwECHgECF4AACgkQhN8ffmrgNkT8+BAAoAXBqu4/O2Cs5FSWWZpzgScNEgq7 >uHhOKeYmRfgKlOUPoYlPB1DBqdOAXSKb9OvsmyOvpoGnqijB7aAJBoyQYW/OCQgd >U8L4eTCf4yRZnfFLdgskcPfN1p0Rs/yinGEooBJFtYa7mT6J0UTW2JjCLZK2AFCW >oF+KBu5JICXGBXigb2ZbX1jWjxP5H1RidQw6HF5z4z34SjLWAOOeZ8B/Xfz6Fs0s >IAuLu2O4HE4DI8Qu196LhSVHHgr3uMTkvN1t5nKwyjrRQztwXXk9qIomII3ydNYb >BYAGdWNNMfLb1kmDwC5wQHAFvSP1aiMF3aKAY+gl2wXSGO6JqM0SteJS3dytIljI >kzu0atc9HuGs/HDQgdmpAS4WU2YefEr/WieltSiAKlwuC+3wg+CONJ6TE1vgNDU/ >axerttb0jq7UQb/nAp05bsrB7XH1Vs+1ON9lUPEfWRmwQcrVK5JUrUWa/4tA/UeM >XvFcPFtFluGTlLewgJIqcvjPXFwpbDZprXJsMkwew/A6B6n3+0sbgf7p3QSGkVbi >dwQAymTbHdYqLnbcnKZhjto3Wjw1J5QB2wuiRYlpjV3i7AWTGlqoSTOWCCV+HamQ >qeFYNYAWNFx3+J/oi7xDi8t9bHVNA205equ+y2sj3G5uGJ6LSHQ8AXp9uOipUUvU >1MJN0yLXr9PIwvi5Ag0EUfv3swEQAL0+MnxHGrTjSYdfdua4SBpmytDONM1EngeY >s+WyaC/760MughKbaysI/nK2LB1vnwEY7f3NM4fxBx8u2T7VBm6Ez6Fs23Bb8Rkz >f97bPSdxCmg64GPHfLA9uwTIXcYS+MpI86WOf6eWY0rRpf7Y9Nl7YoUNvzOyUPqc >ggdcnHce8zYv7A/WS8flZDm8tVFPsHrQDEwNMws7ZhiNnHkeZeRJrvCuB7oEVich >O/ROYoA5o6NozWYQbjxe1f6Yur4Q10qgVcxVnyLFJSbg6vZSzL7KYh3Z5iBOzPHt >7cwEDrW8W4Kl2Qj8rhJ4Wxs94CAtua7IXK44sVZWQbyHcOXRikgGMZKkEZzVCQa5 >KD1u1ZrcBCyuMAir0hsmS3jhCUwpiE2c3SRk8O8CgixhTcBk0X/k9ZFu3Hbi1JMB >FLzs/Nq3tYAYvVivhPloSxmYBPsafYHCZM83yBNNsralXh5zjB+di90G+AMXt2PN >LTcdovZuWtC0s8/jrx+zv/AA4FAGYU9OVl+YL9ybFX8gSdMEcixyzQcKfiFBjpWv >5iFrwIuDlaXMcheyrhc9aGOxfx44OXc505+VjO/1Q/8EOWlJ6UwOi6GMkj5T+RFJ >MDyP0UixS7dt6wTuD5t6PRuyWWxZswgrbL9hjwGFr154Z19TWeNWc23pWtUvQJos >UCxl2nFHABEBAAGJBD4EGAECAAkFAlH797MCGy4CKQkQhN8ffmrgNkTBXSAEGQEC >AAYFAlH797MACgkQJEPd69lQ0evA+Q/+M7lSFlrQWiRsFqDjh+kTJc+0OEBCvnfo >N2KPyXXbfc//qup55PfEygE6C60zvrlv3WE33GZ5GS5MLuDMP82b+a5Yt16NQU7L >WtAg1g0S0BvazW+28TgnfO8bhbGaFeE9ccw3xLmlbwZQ3f3LtMKdwFIROiG6hvAs >9U54QYti3tv9DowRYYWpdr0Ga8RqeGNtCKc0v2opy51MpzKWjwUW0i3XlSlyY8Lj >1KT8PyznNPw32nYpmDizz+0OUJNnn/kT+GnFoR3DJnFosTOrnxFJp+N+nejMp/gW >r9NM0/E7H+P53IiytBOt5/0vsOaCFGdYGhKEjmJi3dHS4Xk1ObD1mjdD1YDOlWWU >3Md6BDHd4W7Q8gT7oQfTIMLd3HzV+WNPIdocPLBaeA/tRD8Pg5CCmncAmSub4F5T >An7FlnACtSOv3cIWQ0TymS42DihDaJ5d1RvNzKw+zHYdPvf471JFZR3TDhkPbLIr >9czR7kbpnXRwchgwXQn306NVWf37TgA8wpbnFTazZ38iOeqcb9oKprqnbgEdr3PN >OhKSlMTkzAqf3MEi2Fyua4BADMhS3oBwCRgDTlt6wquEytpNSlZaHnyiyIgOpekF >Uy5K3w8NhHqeifRPrNb/UcCbXtXz+puqIEZHMenpv6FRlTTKpdoHoVXSkp1TPMGN >/VaCiLbP4Z3xEw/9EbAJJkhmmx1Qw3ueoqc4h1MmhUtIdxSZ/oA9SjwlnY++zvaZ >6w1wTS4P+OUkETNDtItdpxXMJ9qfSy9voAQc2K43WMZCCmpPJYSdqaZZNPFj+Ne8 >6
Re: [tor-relays] tor-arm question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Yes, especially when hitting Enter after "sudo -u debian-tor arm" Then it took a few seconds and the relay resumed. It never seemed to have these problems when running on it's own, so I think this is just due to the limited resources of the pi On 17. Juni 2014 20:13:44 MESZ, Adam Griffin wrote: >Running top in a separate SSH session shows ~50% load average. I >imagine >spikes would cause the CLI interruptions and maybe relay >unresponsive/resumed notices. Did you have the same blank uptime issue? > > >On Tue, Jun 17, 2014 at 2:08 PM, Elrippo >wrote: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA512 >> >> Had the same issues on my pi when running over ssh. >> It simply is the fact, that your pi is running almost on max load. >Type >> top in your console, and watch the pi working :) >> >> On 17. Juni 2014 19:28:23 MESZ, Adam Griffin >wrote: >> >Hi, >> > >> >Just started a new tor relay on my raspberry pi yesterday and I'm >> >monitoring with tor-arm over ssh. I'm currently listed on >> >atlas.torproject.org with flags 'Fast', 'Running', 'V2Dir', and >'Valid' >> >with > 17hrs uptime. >> > >> >However, tor-arm is showing a blank for uptime and about once a >minute, >> >the >> >CLI goes blank and then flickers back. (the flickering happens at >the >> >same >> >rate for local and remote SSH) Also, about once every couple hours I >> >get a >> >'Relay unresponsive' and then 10 seconds later 'Relay resumed'. >> > >> >Anything to do to remedy these issues? >> > >> > >> >> >> > >> >___ >> >tor-relays mailing list >> >tor-relays@lists.torproject.org >> >https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >> >> - -- >> We don't bubble you, we don't spoof you ;) >> Keep your data encrypted! >> Log you soon, >> your Admin >> elri...@elrippoisland.net >> >> Encrypted messages are welcome. >> 0x84DF1F7E6AE03644 >> >> - -BEGIN PGP PUBLIC KEY BLOCK- >> Version: GnuPG v1.4.11 (GNU/Linux) >> >> mQINBFH797MBEAC0Y0NeI7lmDR9szTEcWuHuRe0r/WjSRC0Nr5nXsghuMcxpJ3Dd >> BOBimi4hdMMK4iqPVMwNw6GpKYR3A9LHHjbYRXHUKrJmB+BaJVyzJXN5H6XvxTTb >> UfX+DaXAGJW/G+3cBB3qm/QaU8QGkBKfXq0DLTaTGPkGKxEAldj/8onGZhawdJs+ >> B92JrW+S2HDh15pIuXzSqe7eCcIOdvvwfWe0fJi2AraA7LYGpxP6GcC/b9JJpbq5 >> Y6DfE2Aun9ZK3iHqURyrms0Whbv1CgmUahL2MVYCsTsXwe0GwlAxxKvjXAiXuo+R >> 9wO5wsXvVVSVNqsk9Yqi+wYzdPKndTU0GyxSApQHroF+cxaZ8Lk0xloj18+LdCSs >> e5IiTSXH0MMsDdWWdHlrgk+bgDG+0Gu3ne4vMwGdKO7AhYgQW/ueMy4RnkG/nsV9 >> jry5BO4gGAI1Ij8KvqUzEnvJFGE3ptJogU+zazWWDUWmL3ecKb3aDRlJFnZ3kJ5h >> q8GolZVjpk99V+4B5WVRPXdej/p5J19tXycK/jdNmr4oC8NyUhIpe8xHELnfoB4z >> +rxiTx+KMnW0rY8EQg8O2ixEYt5my90IwQkxcxIxextVrqjJjYn8extc2/v8yGzI >> KmTEJxdADB5v/Jx4HiLHNDSfBUb8gfONCkNSTYvTcSwTjWzHOkXeE/9ZbQARAQAB >> tD5lbHJpcHBvIChrZWVwIHlvdXIgZGF0YSBlbmNyeXB0ZWQpIDxlbHJpcHBvQGVs >> cmlwcG9pc2xhbmQubmV0PokCOAQTAQIAIgUCUfv3swIbLwYLCQgHAwIGFQgCCQoL >> BBYCAwECHgECF4AACgkQhN8ffmrgNkT8+BAAoAXBqu4/O2Cs5FSWWZpzgScNEgq7 >> uHhOKeYmRfgKlOUPoYlPB1DBqdOAXSKb9OvsmyOvpoGnqijB7aAJBoyQYW/OCQgd >> U8L4eTCf4yRZnfFLdgskcPfN1p0Rs/yinGEooBJFtYa7mT6J0UTW2JjCLZK2AFCW >> oF+KBu5JICXGBXigb2ZbX1jWjxP5H1RidQw6HF5z4z34SjLWAOOeZ8B/Xfz6Fs0s >> IAuLu2O4HE4DI8Qu196LhSVHHgr3uMTkvN1t5nKwyjrRQztwXXk9qIomII3ydNYb >> BYAGdWNNMfLb1kmDwC5wQHAFvSP1aiMF3aKAY+gl2wXSGO6JqM0SteJS3dytIljI >> kzu0atc9HuGs/HDQgdmpAS4WU2YefEr/WieltSiAKlwuC+3wg+CONJ6TE1vgNDU/ >> axerttb0jq7UQb/nAp05bsrB7XH1Vs+1ON9lUPEfWRmwQcrVK5JUrUWa/4tA/UeM >> XvFcPFtFluGTlLewgJIqcvjPXFwpbDZprXJsMkwew/A6B6n3+0sbgf7p3QSGkVbi >> dwQAymTbHdYqLnbcnKZhjto3Wjw1J5QB2wuiRYlpjV3i7AWTGlqoSTOWCCV+HamQ >> qeFYNYAWNFx3+J/oi7xDi8t9bHVNA205equ+y2sj3G5uGJ6LSHQ8AXp9uOipUUvU >> 1MJN0yLXr9PIwvi5Ag0EUfv3swEQAL0+MnxHGrTjSYdfdua4SBpmytDONM1EngeY >> s+WyaC/760MughKbaysI/nK2LB1vnwEY7f3NM4fxBx8u2T7VBm6Ez6Fs23Bb8Rkz >> f97bPSdxCmg64GPHfLA9uwTIXcYS+MpI86WOf6eWY0rRpf7Y9Nl7YoUNvzOyUPqc >> ggdcnHce8zYv7A/WS8flZDm8tVFPsHrQDEwNMws7ZhiNnHkeZeRJrvCuB7oEVich >> O/ROYoA5o6NozWYQbjxe1f6Yur4Q10qgVcxVnyLFJSbg6vZSzL7KYh3Z5iBOzPHt >> 7cwEDrW8W4Kl2Qj8rhJ4Wxs94CAtua7IXK44sVZWQbyHcOXRikgGMZKkEZzVCQa5 >> KD1u1ZrcBCyuMAir0hsmS3jhCUwpiE2c3SRk8O8CgixhTcBk0X/k9ZFu3Hbi1JMB >> FLzs/Nq3tYAYvVivhPloSxmYBPsafYHCZM83yBNNsralXh5zjB+di90G+AMXt2PN >> LTcdovZuWtC0s8/jrx+zv/AA4FAGYU9OVl+YL9ybFX8gSdMEcixyzQcKfiFBjpWv >> 5iFrwIuDlaXMcheyrhc9aGOxfx44OXc505+VjO/1Q/8EOWlJ6UwOi6GMkj5T+RFJ >> MDyP0UixS7dt6wTuD5t6PRuyWWxZswgrbL9hjwGFr154Z19TWeNWc23pWtUvQJos >> UCxl2nFHABEBAAGJBD4EGAECAAkFAlH797MCGy4CKQkQhN8ffmrgNkTBXSAEGQEC >> AAYFAlH797MACgkQJEPd69lQ0evA+Q/+M7lSFlrQWiRsFqDjh+kTJc+0OEBCvnfo >> N2KPyXXbfc//qup55PfEygE6C60zvrlv3WE33GZ5GS5MLuDMP82b+a5Yt16NQU7L >> WtAg1g0S0BvazW+28TgnfO8bhbGaFeE9ccw3xLmlbwZQ3f3LtMKdwFIROiG6hvAs >> 9U54QYti3tv9DowRYYWpdr0Ga8RqeGNtCKc0v2opy51MpzKWjwUW0i3XlSlyY8Lj >> 1KT8PyznNPw32nYpmDizz+0OUJNnn/kT+GnFoR3DJnFosTOrnxFJp+N+nejMp/gW >> r9NM0/E7H+P53IiytBOt5/0vsOaCFGdYGhKEjmJi3dHS4Xk1ObD1mjdD1YDOlWWU >> 3Md6BDHd4W7Q8gT7oQfTIMLd3HzV+WNPId
Re: [tor-relays] tor-arm question
Running top in a separate SSH session shows ~50% load average. I imagine spikes would cause the CLI interruptions and maybe relay unresponsive/resumed notices. Did you have the same blank uptime issue? On Tue, Jun 17, 2014 at 2:08 PM, Elrippo wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Had the same issues on my pi when running over ssh. > It simply is the fact, that your pi is running almost on max load. Type > top in your console, and watch the pi working :) > > On 17. Juni 2014 19:28:23 MESZ, Adam Griffin wrote: > >Hi, > > > >Just started a new tor relay on my raspberry pi yesterday and I'm > >monitoring with tor-arm over ssh. I'm currently listed on > >atlas.torproject.org with flags 'Fast', 'Running', 'V2Dir', and 'Valid' > >with > 17hrs uptime. > > > >However, tor-arm is showing a blank for uptime and about once a minute, > >the > >CLI goes blank and then flickers back. (the flickering happens at the > >same > >rate for local and remote SSH) Also, about once every couple hours I > >get a > >'Relay unresponsive' and then 10 seconds later 'Relay resumed'. > > > >Anything to do to remedy these issues? > > > > > > > > > >___ > >tor-relays mailing list > >tor-relays@lists.torproject.org > >https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > - -- > We don't bubble you, we don't spoof you ;) > Keep your data encrypted! > Log you soon, > your Admin > elri...@elrippoisland.net > > Encrypted messages are welcome. > 0x84DF1F7E6AE03644 > > - -BEGIN PGP PUBLIC KEY BLOCK- > Version: GnuPG v1.4.11 (GNU/Linux) > > mQINBFH797MBEAC0Y0NeI7lmDR9szTEcWuHuRe0r/WjSRC0Nr5nXsghuMcxpJ3Dd > BOBimi4hdMMK4iqPVMwNw6GpKYR3A9LHHjbYRXHUKrJmB+BaJVyzJXN5H6XvxTTb > UfX+DaXAGJW/G+3cBB3qm/QaU8QGkBKfXq0DLTaTGPkGKxEAldj/8onGZhawdJs+ > B92JrW+S2HDh15pIuXzSqe7eCcIOdvvwfWe0fJi2AraA7LYGpxP6GcC/b9JJpbq5 > Y6DfE2Aun9ZK3iHqURyrms0Whbv1CgmUahL2MVYCsTsXwe0GwlAxxKvjXAiXuo+R > 9wO5wsXvVVSVNqsk9Yqi+wYzdPKndTU0GyxSApQHroF+cxaZ8Lk0xloj18+LdCSs > e5IiTSXH0MMsDdWWdHlrgk+bgDG+0Gu3ne4vMwGdKO7AhYgQW/ueMy4RnkG/nsV9 > jry5BO4gGAI1Ij8KvqUzEnvJFGE3ptJogU+zazWWDUWmL3ecKb3aDRlJFnZ3kJ5h > q8GolZVjpk99V+4B5WVRPXdej/p5J19tXycK/jdNmr4oC8NyUhIpe8xHELnfoB4z > +rxiTx+KMnW0rY8EQg8O2ixEYt5my90IwQkxcxIxextVrqjJjYn8extc2/v8yGzI > KmTEJxdADB5v/Jx4HiLHNDSfBUb8gfONCkNSTYvTcSwTjWzHOkXeE/9ZbQARAQAB > tD5lbHJpcHBvIChrZWVwIHlvdXIgZGF0YSBlbmNyeXB0ZWQpIDxlbHJpcHBvQGVs > cmlwcG9pc2xhbmQubmV0PokCOAQTAQIAIgUCUfv3swIbLwYLCQgHAwIGFQgCCQoL > BBYCAwECHgECF4AACgkQhN8ffmrgNkT8+BAAoAXBqu4/O2Cs5FSWWZpzgScNEgq7 > uHhOKeYmRfgKlOUPoYlPB1DBqdOAXSKb9OvsmyOvpoGnqijB7aAJBoyQYW/OCQgd > U8L4eTCf4yRZnfFLdgskcPfN1p0Rs/yinGEooBJFtYa7mT6J0UTW2JjCLZK2AFCW > oF+KBu5JICXGBXigb2ZbX1jWjxP5H1RidQw6HF5z4z34SjLWAOOeZ8B/Xfz6Fs0s > IAuLu2O4HE4DI8Qu196LhSVHHgr3uMTkvN1t5nKwyjrRQztwXXk9qIomII3ydNYb > BYAGdWNNMfLb1kmDwC5wQHAFvSP1aiMF3aKAY+gl2wXSGO6JqM0SteJS3dytIljI > kzu0atc9HuGs/HDQgdmpAS4WU2YefEr/WieltSiAKlwuC+3wg+CONJ6TE1vgNDU/ > axerttb0jq7UQb/nAp05bsrB7XH1Vs+1ON9lUPEfWRmwQcrVK5JUrUWa/4tA/UeM > XvFcPFtFluGTlLewgJIqcvjPXFwpbDZprXJsMkwew/A6B6n3+0sbgf7p3QSGkVbi > dwQAymTbHdYqLnbcnKZhjto3Wjw1J5QB2wuiRYlpjV3i7AWTGlqoSTOWCCV+HamQ > qeFYNYAWNFx3+J/oi7xDi8t9bHVNA205equ+y2sj3G5uGJ6LSHQ8AXp9uOipUUvU > 1MJN0yLXr9PIwvi5Ag0EUfv3swEQAL0+MnxHGrTjSYdfdua4SBpmytDONM1EngeY > s+WyaC/760MughKbaysI/nK2LB1vnwEY7f3NM4fxBx8u2T7VBm6Ez6Fs23Bb8Rkz > f97bPSdxCmg64GPHfLA9uwTIXcYS+MpI86WOf6eWY0rRpf7Y9Nl7YoUNvzOyUPqc > ggdcnHce8zYv7A/WS8flZDm8tVFPsHrQDEwNMws7ZhiNnHkeZeRJrvCuB7oEVich > O/ROYoA5o6NozWYQbjxe1f6Yur4Q10qgVcxVnyLFJSbg6vZSzL7KYh3Z5iBOzPHt > 7cwEDrW8W4Kl2Qj8rhJ4Wxs94CAtua7IXK44sVZWQbyHcOXRikgGMZKkEZzVCQa5 > KD1u1ZrcBCyuMAir0hsmS3jhCUwpiE2c3SRk8O8CgixhTcBk0X/k9ZFu3Hbi1JMB > FLzs/Nq3tYAYvVivhPloSxmYBPsafYHCZM83yBNNsralXh5zjB+di90G+AMXt2PN > LTcdovZuWtC0s8/jrx+zv/AA4FAGYU9OVl+YL9ybFX8gSdMEcixyzQcKfiFBjpWv > 5iFrwIuDlaXMcheyrhc9aGOxfx44OXc505+VjO/1Q/8EOWlJ6UwOi6GMkj5T+RFJ > MDyP0UixS7dt6wTuD5t6PRuyWWxZswgrbL9hjwGFr154Z19TWeNWc23pWtUvQJos > UCxl2nFHABEBAAGJBD4EGAECAAkFAlH797MCGy4CKQkQhN8ffmrgNkTBXSAEGQEC > AAYFAlH797MACgkQJEPd69lQ0evA+Q/+M7lSFlrQWiRsFqDjh+kTJc+0OEBCvnfo > N2KPyXXbfc//qup55PfEygE6C60zvrlv3WE33GZ5GS5MLuDMP82b+a5Yt16NQU7L > WtAg1g0S0BvazW+28TgnfO8bhbGaFeE9ccw3xLmlbwZQ3f3LtMKdwFIROiG6hvAs > 9U54QYti3tv9DowRYYWpdr0Ga8RqeGNtCKc0v2opy51MpzKWjwUW0i3XlSlyY8Lj > 1KT8PyznNPw32nYpmDizz+0OUJNnn/kT+GnFoR3DJnFosTOrnxFJp+N+nejMp/gW > r9NM0/E7H+P53IiytBOt5/0vsOaCFGdYGhKEjmJi3dHS4Xk1ObD1mjdD1YDOlWWU > 3Md6BDHd4W7Q8gT7oQfTIMLd3HzV+WNPIdocPLBaeA/tRD8Pg5CCmncAmSub4F5T > An7FlnACtSOv3cIWQ0TymS42DihDaJ5d1RvNzKw+zHYdPvf471JFZR3TDhkPbLIr > 9czR7kbpnXRwchgwXQn306NVWf37TgA8wpbnFTazZ38iOeqcb9oKprqnbgEdr3PN > OhKSlMTkzAqf3MEi2Fyua4BADMhS3oBwCRgDTlt6wquEytpNSlZaHnyiyIgOpekF > Uy5K3w8NhHqeifRPrNb/UcCbXtXz+puqIEZHMenpv6FRlTTKpdoHoVXSkp1TPMGN > /VaCiLbP4Z3xEw/9EbAJJkhmmx1Qw3ueoqc4h1MmhUtIdxSZ/oA9SjwlnY++zvaZ > 6w1wTS4P+OUkETNDtItdpxXMJ9qfSy9voAQc2K43WMZCCmpPJYSdqaZZNPFj+Ne8 > 6FNtNKuUkXREybpHwlVAX
Re: [tor-relays] tor-arm question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Had the same issues on my pi when running over ssh. It simply is the fact, that your pi is running almost on max load. Type top in your console, and watch the pi working :) On 17. Juni 2014 19:28:23 MESZ, Adam Griffin wrote: >Hi, > >Just started a new tor relay on my raspberry pi yesterday and I'm >monitoring with tor-arm over ssh. I'm currently listed on >atlas.torproject.org with flags 'Fast', 'Running', 'V2Dir', and 'Valid' >with > 17hrs uptime. > >However, tor-arm is showing a blank for uptime and about once a minute, >the >CLI goes blank and then flickers back. (the flickering happens at the >same >rate for local and remote SSH) Also, about once every couple hours I >get a >'Relay unresponsive' and then 10 seconds later 'Relay resumed'. > >Anything to do to remedy these issues? > > > > >___ >tor-relays mailing list >tor-relays@lists.torproject.org >https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays - -- We don't bubble you, we don't spoof you ;) Keep your data encrypted! Log you soon, your Admin elri...@elrippoisland.net Encrypted messages are welcome. 0x84DF1F7E6AE03644 - -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.4.11 (GNU/Linux) mQINBFH797MBEAC0Y0NeI7lmDR9szTEcWuHuRe0r/WjSRC0Nr5nXsghuMcxpJ3Dd BOBimi4hdMMK4iqPVMwNw6GpKYR3A9LHHjbYRXHUKrJmB+BaJVyzJXN5H6XvxTTb UfX+DaXAGJW/G+3cBB3qm/QaU8QGkBKfXq0DLTaTGPkGKxEAldj/8onGZhawdJs+ B92JrW+S2HDh15pIuXzSqe7eCcIOdvvwfWe0fJi2AraA7LYGpxP6GcC/b9JJpbq5 Y6DfE2Aun9ZK3iHqURyrms0Whbv1CgmUahL2MVYCsTsXwe0GwlAxxKvjXAiXuo+R 9wO5wsXvVVSVNqsk9Yqi+wYzdPKndTU0GyxSApQHroF+cxaZ8Lk0xloj18+LdCSs e5IiTSXH0MMsDdWWdHlrgk+bgDG+0Gu3ne4vMwGdKO7AhYgQW/ueMy4RnkG/nsV9 jry5BO4gGAI1Ij8KvqUzEnvJFGE3ptJogU+zazWWDUWmL3ecKb3aDRlJFnZ3kJ5h q8GolZVjpk99V+4B5WVRPXdej/p5J19tXycK/jdNmr4oC8NyUhIpe8xHELnfoB4z +rxiTx+KMnW0rY8EQg8O2ixEYt5my90IwQkxcxIxextVrqjJjYn8extc2/v8yGzI KmTEJxdADB5v/Jx4HiLHNDSfBUb8gfONCkNSTYvTcSwTjWzHOkXeE/9ZbQARAQAB tD5lbHJpcHBvIChrZWVwIHlvdXIgZGF0YSBlbmNyeXB0ZWQpIDxlbHJpcHBvQGVs cmlwcG9pc2xhbmQubmV0PokCOAQTAQIAIgUCUfv3swIbLwYLCQgHAwIGFQgCCQoL BBYCAwECHgECF4AACgkQhN8ffmrgNkT8+BAAoAXBqu4/O2Cs5FSWWZpzgScNEgq7 uHhOKeYmRfgKlOUPoYlPB1DBqdOAXSKb9OvsmyOvpoGnqijB7aAJBoyQYW/OCQgd U8L4eTCf4yRZnfFLdgskcPfN1p0Rs/yinGEooBJFtYa7mT6J0UTW2JjCLZK2AFCW oF+KBu5JICXGBXigb2ZbX1jWjxP5H1RidQw6HF5z4z34SjLWAOOeZ8B/Xfz6Fs0s IAuLu2O4HE4DI8Qu196LhSVHHgr3uMTkvN1t5nKwyjrRQztwXXk9qIomII3ydNYb BYAGdWNNMfLb1kmDwC5wQHAFvSP1aiMF3aKAY+gl2wXSGO6JqM0SteJS3dytIljI kzu0atc9HuGs/HDQgdmpAS4WU2YefEr/WieltSiAKlwuC+3wg+CONJ6TE1vgNDU/ axerttb0jq7UQb/nAp05bsrB7XH1Vs+1ON9lUPEfWRmwQcrVK5JUrUWa/4tA/UeM XvFcPFtFluGTlLewgJIqcvjPXFwpbDZprXJsMkwew/A6B6n3+0sbgf7p3QSGkVbi dwQAymTbHdYqLnbcnKZhjto3Wjw1J5QB2wuiRYlpjV3i7AWTGlqoSTOWCCV+HamQ qeFYNYAWNFx3+J/oi7xDi8t9bHVNA205equ+y2sj3G5uGJ6LSHQ8AXp9uOipUUvU 1MJN0yLXr9PIwvi5Ag0EUfv3swEQAL0+MnxHGrTjSYdfdua4SBpmytDONM1EngeY s+WyaC/760MughKbaysI/nK2LB1vnwEY7f3NM4fxBx8u2T7VBm6Ez6Fs23Bb8Rkz f97bPSdxCmg64GPHfLA9uwTIXcYS+MpI86WOf6eWY0rRpf7Y9Nl7YoUNvzOyUPqc ggdcnHce8zYv7A/WS8flZDm8tVFPsHrQDEwNMws7ZhiNnHkeZeRJrvCuB7oEVich O/ROYoA5o6NozWYQbjxe1f6Yur4Q10qgVcxVnyLFJSbg6vZSzL7KYh3Z5iBOzPHt 7cwEDrW8W4Kl2Qj8rhJ4Wxs94CAtua7IXK44sVZWQbyHcOXRikgGMZKkEZzVCQa5 KD1u1ZrcBCyuMAir0hsmS3jhCUwpiE2c3SRk8O8CgixhTcBk0X/k9ZFu3Hbi1JMB FLzs/Nq3tYAYvVivhPloSxmYBPsafYHCZM83yBNNsralXh5zjB+di90G+AMXt2PN LTcdovZuWtC0s8/jrx+zv/AA4FAGYU9OVl+YL9ybFX8gSdMEcixyzQcKfiFBjpWv 5iFrwIuDlaXMcheyrhc9aGOxfx44OXc505+VjO/1Q/8EOWlJ6UwOi6GMkj5T+RFJ MDyP0UixS7dt6wTuD5t6PRuyWWxZswgrbL9hjwGFr154Z19TWeNWc23pWtUvQJos UCxl2nFHABEBAAGJBD4EGAECAAkFAlH797MCGy4CKQkQhN8ffmrgNkTBXSAEGQEC AAYFAlH797MACgkQJEPd69lQ0evA+Q/+M7lSFlrQWiRsFqDjh+kTJc+0OEBCvnfo N2KPyXXbfc//qup55PfEygE6C60zvrlv3WE33GZ5GS5MLuDMP82b+a5Yt16NQU7L WtAg1g0S0BvazW+28TgnfO8bhbGaFeE9ccw3xLmlbwZQ3f3LtMKdwFIROiG6hvAs 9U54QYti3tv9DowRYYWpdr0Ga8RqeGNtCKc0v2opy51MpzKWjwUW0i3XlSlyY8Lj 1KT8PyznNPw32nYpmDizz+0OUJNnn/kT+GnFoR3DJnFosTOrnxFJp+N+nejMp/gW r9NM0/E7H+P53IiytBOt5/0vsOaCFGdYGhKEjmJi3dHS4Xk1ObD1mjdD1YDOlWWU 3Md6BDHd4W7Q8gT7oQfTIMLd3HzV+WNPIdocPLBaeA/tRD8Pg5CCmncAmSub4F5T An7FlnACtSOv3cIWQ0TymS42DihDaJ5d1RvNzKw+zHYdPvf471JFZR3TDhkPbLIr 9czR7kbpnXRwchgwXQn306NVWf37TgA8wpbnFTazZ38iOeqcb9oKprqnbgEdr3PN OhKSlMTkzAqf3MEi2Fyua4BADMhS3oBwCRgDTlt6wquEytpNSlZaHnyiyIgOpekF Uy5K3w8NhHqeifRPrNb/UcCbXtXz+puqIEZHMenpv6FRlTTKpdoHoVXSkp1TPMGN /VaCiLbP4Z3xEw/9EbAJJkhmmx1Qw3ueoqc4h1MmhUtIdxSZ/oA9SjwlnY++zvaZ 6w1wTS4P+OUkETNDtItdpxXMJ9qfSy9voAQc2K43WMZCCmpPJYSdqaZZNPFj+Ne8 6FNtNKuUkXREybpHwlVAXnHzInmFOOM9RAmF70r3zEmKt77W1ztBLo2o9X79gPgL u9ThgrH6Oc2k46n+9nc3joccr7miiX/bp976DNWcWdOYThiSSOCb8Zw9/Zs935i1 wUVkYTj24tmBH4H5ov9ib7RPmU21ru458RbUKG0ONAqBtAHNyXHzUnXsrke+D4VW MI06YcXSk8YeYgQ8GxgHQc+W2bb8LIbKN1hEYJ0wzM62vKR2/Oiwuf8lXutIKTuz +v7Vj1PQd66DGHsxtWRaWnr1c54JTL2wICHJYKFH4grp7864+GL/uQ1O/Z/XxVku E1JQ/AnwBGU1M1S6otwWGWVRjzEzQtxsfcCEPvV/9td3FIFQAbGTPb+48XFU+TY9 8AlcXBlDzXq7c5f8Evn/oSIsZDt63K4HNTmMGqOTl/p1aA0e4eyX76LczY06rDP5 GMSNs+
[tor-relays] tor-arm question
Hi, Just started a new tor relay on my raspberry pi yesterday and I'm monitoring with tor-arm over ssh. I'm currently listed on atlas.torproject.org with flags 'Fast', 'Running', 'V2Dir', and 'Valid' with > 17hrs uptime. However, tor-arm is showing a blank for uptime and about once a minute, the CLI goes blank and then flickers back. (the flickering happens at the same rate for local and remote SSH) Also, about once every couple hours I get a 'Relay unresponsive' and then 10 seconds later 'Relay resumed'. Anything to do to remedy these issues? ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
