-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The host ran out of free inodes, I sent a request to admins to make
more inodes available. It might take another 12 or 24 hours until the
service is back. Sorry for the inconvenience.
On 03/10/15 12:02, Tim Wilson-Brown - teor wrote:
>
>> On 3
seems to be up now, no errors at my end
2015-10-03 7:30 GMT+02:00 Tim Wilson-Brown - teor :
>
> On 3 Oct 2015, at 01:19, Geoff Down wrote:
>
> A query using Globe stalls at the 'processing - please wait' stage, so I
> assume the problem is actually
Routers running at or near a BandwidthRate setting offer terrible
latency and induce connection time-outs. Refuse all DIR-port requests
with "HTTP/1.0 503 Directory busy, try again later ".
'tc' ingress filter is dramatically better for rate-limiting.
For case and 'tc' example see
final post
Was going to wait a few days before reporting back, but early results
are decisive.
The overload situation continued to worsen over a two-day period, with
consensus weight continuing to rise despite the relay often running in
a state of extreme overload and performing its exit function quite
Spent a few minutes activating the DNSSEC trust-anchor for 'unbound'.
Ran 'dig' on a few signed domains and observed that queries that took
under 50 milliseconds without went to 2000 milliseconds with.
My attitude toward DNSSEC has deteriorated steadily over time and this
finishes it off for me.
> On 3 Oct 2015, at 19:09, Dhalgren Tor wrote:
>
> Was going to wait a few days before reporting back, but early results
> are decisive.
>
> The overload situation continued to worsen over a two-day period, with
> consensus weight continuing to rise despite the relay