On 01/16/2017 11:07 AM, Petrusko wrote:
> To resume,
> So it's working by cloning the git repository as you wrote.
> chown -R debian-tor:debian-tor *
> inside folders /stem and /nyx
>
> Then (relay with default control socket)
> cd nyx
> sudo -u debian-tor ./run_nyx
This (or just "nyx")
Hi Arisbe, glad it's working for ya! Nyx should have file descriptor
counts if you're using more than 60% and there's room for it in the
header. For what it's worth here's the relevant bits...
https://gitweb.torproject.org/nyx.git/tree/nyx/panel/header.py#n407
Thanks for the effort to improve Arm (now Nyx). I've only tried NYX
with the default config file but I don't see the file descriptors
enabled. Did we lose this data?
arisbe
On 1/13/2017 11:43 AM, Damian Johnson wrote:
Thx Damian for this !
Please you give some useful commands to install
> Thx Damian for this !
> Please you give some useful commands to install and use it ?
>
> I'll be happy to try your tool!
> Many thx :)
% git clone https://git.torproject.org/stem.git
% cd stem
% sudo python setup.py install
% cd ..
% git clone https://git.torproject.org/nyx.git
% cd nyx
% sudo
Thx Damian for this !
Please you give some useful commands to install and use it ?
I'll be happy to try your tool!
Many thx :)
> I've been rewriting it from the ground up and that's Nyx...
> https://gitweb.torproject.org/nyx.git
--
Petrusko
C0BF 2184 4A77 4A18 90E9 F72C B3CA E665 EBE2 3AE5
> From MilkyWay:
> [root@clutterbuck ~]# ps -p 23780 -o etime
> ELAPSED
> 78-14:14:25
>
> Hope that helps.
Thanks Alan. All of those are indeed what Stem expects. If you run the
Nyx codebase instead does the uptime show up? Please note you'll need
to fetch both it and stem from the git
On Thu, Jan 12, 2017 at 10:43:25AM -0800, Damian Johnson wrote:
> > Does it use `ps -o etime`? If so it should work in the latest OpenBSD
> > release.
>
> Yup, I use...
>
> ps -p -o etime
>
> Glad to hear it should now work on OpenBSD! To confirm would you mind
> providing me the output of
>> Damian,
>> Milkyway (which is working) is using Centos 6
>> Andromeda is using Centos 7
>> and TheCosmos uses a raspberry pi 2, so Raspbian
>
> Interesting. Maybe that platform has a subtly different format than
> what I expect. Mind running the following for an arbitrary process and
> telling
> but I think it's not maintained anymore (?).
Hi mistral. That is incorrect, I'm the maintainer. arm's last release
was a long time ago and it indeed has quite a few issues. I've been
rewriting it from the ground up and that's Nyx...
https://gitweb.torproject.org/nyx.git
Nyx is feature
> Damian,
> Milkyway (which is working) is using Centos 6
> Andromeda is using Centos 7
> and TheCosmos uses a raspberry pi 2, so Raspbian
Interesting. Maybe that platform has a subtly different format than
what I expect. Mind running the following for an arbitrary process and
telling me the
> arm does not show uptime and the average bandwidth rate is way to high.
This is because tor changed the format of its state file since arm's
last release, causing the prepopulated values to be inaccurate. The
current codebase (nyx) uses a new capability of tor's control port to
provide much
'a reliable tool for monitoring'?
Best regards, Ralph
GESENDET: Montag, 09. Januar 2017 um 11:08 Uhr
VON: mistral.re...@posteo.net
AN: tor-relays@lists.torproject.org
BETREFF: Re: [tor-relays] Uptime missing from Arm
Just to confirm - I see the same issue (Debian). So arm is only
partially useful
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
There is a git repository with recent commits named nyx
(https://gitweb.torproject.org/nyx.git).
This seems to be the repository for arm.
When cloning the repository and running nyx (aka arm) from
the source code it shows the correct average
...@posteo.net
An: tor-relays@lists.torproject.org
Betreff: Re: [tor-relays] Uptime missing from Arm
Just to confirm - I see the same issue (Debian). So arm is only
partially useful (not being really reliable) but I think it's not
maintained anymore (?). I was looking into theonionbox for status
reporting
Missed the important bit - its the same for ubuntu 16 and 14 - no uptime and
other stats out
Cheers
Mark B
Snaptor.co.uk (non commercial)
> On 9 Jan 2017, at 11:15, Sec INT wrote:
>
> I just use webmin and cluster all relays - it has uptime monitors and various
> alerts
I just use webmin and cluster all relays - it has uptime monitors and various
alerts you can set - the cluster cron job is useful for regular updating and
clearing house plus executing one off commands on all servers e.g. Updating
myfamily row
Vnstat for stats and graphs although cactus is a
Same on plain old Debian.
Norman
Am 08.01.2017 um 21:34 schrieb Alan:
> Yes I have this exact problem aswell
>
>> I have a similar problem,
>> arm does not show uptime and the average bandwidth rate is way to high.
>> When I start arm I get a log entry that looks like this:
>> "20:37:54
Yes I have this exact problem aswell
> I have a similar problem,
> arm does not show uptime and the average bandwidth rate is way to high.
> When I start arm I get a log entry that looks like this:
> "20:37:54 [ARM_NOTICE] Read the last day of bandwidth history from the
> state file (21 minutes
Damian,
Milkyway (which is working) is using Centos 6
Andromeda is using Centos 7
and TheCosmos uses a raspberry pi 2, so Raspbian
> Hi Alan, what linux distribution is this with? The only platform I'm
> aware of having issues with the uptime is OpenBSD. This is because the
> uptime requires
I have a similar problem,
arm does not show uptime and the average bandwidth rate is way to high.
When I start arm I get a log entry that looks like this:
"20:37:54 [ARM_NOTICE] Read the last day of bandwidth history from the
state file (21 minutes is missing)"
The time varies, sometimes it is
On Sun, Jan 08, 2017 at 10:47:28AM -0800, Damian Johnson wrote:
> Hi Alan, what linux distribution is this with? The only platform I'm
> aware of having issues with the uptime is OpenBSD. This is because the
> uptime requires parsing ps output and on that sole platform they show
> it in 12-hour
Hi Alan, what linux distribution is this with? The only platform I'm
aware of having issues with the uptime is OpenBSD. This is because the
uptime requires parsing ps output and on that sole platform they show
it in 12-hour local time with am/pm indicators, and a format that
shifts if over a day
I have 3 relays running but on Arm only one shows the uptime. Also the
Averages it keeps are way off.
Alan.___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
23 matches
Mail list logo