[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Consensus drops node
- To: or-talk@xxxxxxxxxxxxx
- Subject: Consensus drops node
- From: Hans Schnehl <torvallenator@xxxxxxxxx>
- Date: Mon, 23 Mar 2009 22:51:32 +0100
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Mon, 23 Mar 2009 17:51:44 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject :message-id:mime-version:content-type:content-disposition:user-agent; bh=yl/vhZoRABwoeGRMLZTnUpCS61QNHLicOl8L0zrT+RQ=; b=PFAPUrHo3LmD9jBel7a9INOx/pcM3ypVQuZ9PynCotp17JKMNryBK8ImSCm6fw/qfc x4qxzhVG6MxUoQ/32ypNEiVCZ/WrakSHI1ihBG93oBPMqLgPnTYGYufeQ9EPydKkuH5J r9f0XgKiPrbOwhY153fBUPZF9sA8O3YyKa5is=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:mime-version:content-type :content-disposition:user-agent; b=aU4UY366nfnI/w6okLEd0v9wrAXOLvizNEQmWLN8SFT2Znl7bsuQIyyJKINZdbMXX3 h4bjU2drK2NpX2wRWD8uahP5h547uXUp8/215zhHH/tnthCM8lz4vLPgHGwsg/Lq78VJ QB0L+kO6lXQX5uPjwfCRPpXvJ0IPr5YzyKEZU=
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
- User-agent: Mutt/1.5.19 (2009-01-05)
Hi all,
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
happening.
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 ?
Regards
Hans