strange ARM results
Hi folks, I'm on a quest to find the average circuit-creation rate of clients. I looked in path-spec.txt to find an answer, but it wasn't there. So I thought: lets take some measurements using ARM. This got me some strange results. I start ARM, do some browsing, and close my browser. During the browsing ARM reports 3 circuits with ID's: 398, 399 and 400. These circuits are still there 45 minutes after the browser was closed. If I then restart ARM it reports that there are only two circuits, with circuit ID's 405 and 406. It looks to me that ARM does not update the circuits page when old circuits are closed and replaced by new circuits. It's also possible that ARM keeps old circuits alive after they are not being used anymore by my Tor proxy. Note: I use ARM version: 1.4.5.0, Tor version: 0.2.5.12 Regards, Rob. https://hoevenstein.nl
On 17 Oct 2016, at 22:04, Rob van der Hoeven <robvanderhoeven@ziggo.nl> wrote:
Hi folks,
I'm on a quest to find the average circuit-creation rate of clients. I looked in path-spec.txt to find an answer, but it wasn't there. So I thought: lets take some measurements using ARM. This got me some strange results. I start ARM, do some browsing, and close my browser. During the browsing ARM reports 3 circuits with ID's: 398, 399 and 400. These circuits are still there 45 minutes after the browser was closed. If I then restart ARM it reports that there are only two circuits, with circuit ID's 405 and 406. It looks to me that ARM does not update the circuits page when old circuits are closed and replaced by new circuits. It's also possible that ARM keeps old circuits alive after they are not being used anymore by my Tor proxy.
It seems more likely that this is a refresh issue, either in arm or in the tor event code. Can you replicate it with the latest stable versions of tor and arm?
Note: I use ARM version: 1.4.5.0, Tor version: 0.2.5.12
That's a very old version of tor. I wouldn't use it to measure anything, we've made significant improvements in the last few years. T
Regards, Rob. https://hoevenstein.nl
_______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
T -- Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------------
On Mon, 2016-10-17 at 22:30 +1100, teor wrote:
On 17 Oct 2016, at 22:04, Rob van der Hoeven <robvanderhoeven@ziggo.nl> wrote:
Hi folks,
I'm on a quest to find the average circuit-creation rate of clients. I looked in path-spec.txt to find an answer, but it wasn't there. So I thought: lets take some measurements using ARM. This got me some strange results. I start ARM, do some browsing, and close my browser. During the browsing ARM reports 3 circuits with ID's: 398, 399 and 400. These circuits are still there 45 minutes after the browser was closed. If I then restart ARM it reports that there are only two circuits, with circuit ID's 405 and 406. It looks to me that ARM does not update the circuits page when old circuits are closed and replaced by new circuits. It's also possible that ARM keeps old circuits alive after they are not being used anymore by my Tor proxy.
It seems more likely that this is a refresh issue, either in arm or in the tor event code.
Can you replicate it with the latest stable versions of tor and arm?
Note: I use ARM version: 1.4.5.0, Tor version: 0.2.5.12
That's a very old version of tor. I wouldn't use it to measure anything, we've made significant improvements in the last few years.
ARM version 1.4.5 seems to be the latest version. I checked out NYX but failed to get it running (Unable to load nyx's internal configurations: [Errno 21] Is a directory: '/home/rob/src/nyx/nyx/settings') Did test with Tor version 0.2.9.3-alpha-dev. Same problem.... Regards, Rob. https://hoevenstein.nl
Hi Rob. I suppose it's possible arm is having a refresh issue but can't say there's a known bug around that. To double check try running tor-prompt and giving it 'GETINFO circuit-status'... https://stem.torproject.org/tutorials/down_the_rabbit_hole.html This is the command arm uses to get the circuit information.
ARM version 1.4.5 seems to be the latest version. I checked out NYX but failed to get it running (Unable to load nyx's internal configurations: [Errno 21] Is a directory: '/home/rob/src/nyx/nyx/settings')
Interesting! How did you attempt to run it? Nyx is under active development so quite possible I buggered something up but can't say I've seen this one. Please provide the exact commands you ran - for instance... % git clone http://dccbbv6cooddgcrq.onion/nyx.git % cd nyx % ./run_nyx
On Mon, 2016-10-17 at 09:29 -0700, Damian Johnson wrote:
Hi Rob. I suppose it's possible arm is having a refresh issue but can't say there's a known bug around that. To double check try running tor-prompt and giving it 'GETINFO circuit-status'...
Hi Damian, If I run tor-prompt and ARM side by side, the tor-prompt results are updated when I do a GETINFO circuit-status. The ARM circuits page only updates after a restart. Maybe my system/configuration has something to do with the problem. I run my Tor proxy (and ARM) on an Allwinner A20 ARM system with Debian Jessie as OS. Debian does not use the latests versions of software...
https://stem.torproject.org/tutorials/down_the_rabbit_hole.html
This is the command arm uses to get the circuit information.
ARM version 1.4.5 seems to be the latest version. I checked out NYX but failed to get it running (Unable to load nyx's internal configurations: [Errno 21] Is a directory: '/home/rob/src/nyx/nyx/settings')
Interesting! How did you attempt to run it? Nyx is under active development so quite possible I buggered something up but can't say I've seen this one. Please provide the exact commands you ran - for instance...
% git clone http://dccbbv6cooddgcrq.onion/nyx.git % cd nyx % ./run_nyx
I did: git clone https://git.torproject.org/nyx.git cd nyx ./run_nyx Regards, Rob https://hoevenstein.nl
If I run tor-prompt and ARM side by side, the tor-prompt results are updated when I do a GETINFO circuit-status. The ARM circuits page only updates after a restart.
Gotcha. Definitely a refresh bug then. Sorry about that. :(
ARM version 1.4.5 seems to be the latest version. I checked out NYX but failed to get it running (Unable to load nyx's internal configurations: [Errno 21] Is a directory: '/home/rob/src/nyx/nyx/settings')
Interesting! How did you attempt to run it? Nyx is under active development so quite possible I buggered something up but can't say I've seen this one. Please provide the exact commands you ran - for instance...
% git clone http://dccbbv6cooddgcrq.onion/nyx.git % cd nyx % ./run_nyx
I did:
git clone https://git.torproject.org/nyx.git cd nyx ./run_nyx
Ahh, think I know the issue. Nyx requires the copy of Stem from its git repo too... https://git.torproject.org/stem.git Cheers! -Damian
On Wed, 2016-10-19 at 11:49 -0700, Damian Johnson wrote:
If I run tor-prompt and ARM side by side, the tor-prompt results are updated when I do a GETINFO circuit-status. The ARM circuits page only updates after a restart.
Gotcha. Definitely a refresh bug then. Sorry about that. :(
No need to apologize, I think Stem/Nyx/Arm is wonderful software. Very useful, thank you (and all contributors) for writing it!
I did:
git clone https://git.torproject.org/nyx.git cd nyx ./run_nyx
Ahh, think I know the issue. Nyx requires the copy of Stem from its git repo too...
SUCCESS! Nyx updates the circuits page, the data is in-sync with tor-prompt and seems to be correct. Thanks! Rob. https://hoevenstein.nl
Gotcha. Definitely a refresh bug then. Sorry about that. :(
No need to apologize, I think Stem/Nyx/Arm is wonderful software. Very useful, thank you (and all contributors) for writing it!
Ahh, think I know the issue. Nyx requires the copy of Stem from its git repo too...
SUCCESS!
Nyx updates the circuits page, the data is in-sync with tor-prompt and seems to be correct.
Thanks Rob! And glad to hear it's working!
participants (3)
-
Damian Johnson -
Rob van der Hoeven -
teor