[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Consensus drops node
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: Consensus drops node
- From: Kyle Williams <kyle.kwilliams@xxxxxxxxx>
- Date: Mon, 23 Mar 2009 15:53:16 -0700
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Mon, 23 Mar 2009 18:53:20 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=lq4jaXeIRbY87hfa9bTx1GvrDelmBxAYNzpPnQkyGk0=; b=YpLqTLNZw3CY/w9eOFgat8N/LN+1fsxbkXtM0buEEgBzEMijqX75WNUxfsRqOunTnj kTYOiMdY2WnprfK+Lk8kNkk2PmcwLNzA9YtlQwN98+Ydk+so0YQM3sTjL660niIHMYTk wdALccQPScwxo6fbtT6pPQtxFSd3lzH5c0vTk=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=TVV6pIGqbppX7hASjIn6Ub7yaHoOFPfIUiXFbfp/kKPId/Ls17+CQ9jtE9y311QUc/ 8L9LtKJJVWYJjumu/SwK88euhNpO0JqtFMrKMbMfCXVanB7aHN8oW24TNvrwCpMoQThy xbz08A3FNmnScPU/3p79FI1qmkx71sIlw03lw=
- In-reply-to: <20090323215132.GA29025@tabulara>
- References: <20090323215132.GA29025@tabulara>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
Yes, I've seen this too. The node "JanusPAv2" just dropped out of the mix about 7 days ago.
I wasn't too concerned since I was testing the max through put of a embedded device.
I though it was probably something I did when I was half-awake, but now I'm starting to question it a bit more...hrm..
Last I saw my node, it had a Guard and Fast status. Then one morning, it was gone and no traffic was passing through.
On Mon, Mar 23, 2009 at 2:51 PM, Hans Schnehl <torvallenator@xxxxxxxxx>
six hours ago the node 'vallenator's performance began to decrease gradually
from around 18 mbit/s to at present about 1 mbit/s.
The node was running rather stable at it's upper level (see above) with an uptime
of now 32 days.
I did not do anything on this running machine, so I initially suspected my hoster
to intercept or interfere, not necessarily with a motivation against Tor, but
maybe for more or less genious technical reasons. But they did not do so.
What happened is, the node was actually 'forgotte'n, or dropped out of consensus
by the authoritive routers, it still is as of now. Since I do not have logging
enabled I am unable to search or provide logs with possible traces of what was
Anybody else experiencing this?
I'll keep the node running 'as is' and watch for any changes to occur within the
next hours but probably I'll take the chance to rebuild a few things on that
machine if if there is no change.
Any ideas about this ?