[RC5] RC5 keyspace finished?

Ryan Malayter rmalayter at bai.org
Wed Mar 21 13:17:30 EST 2001

I'm finally getting blocks again now. I guess all the key servers were down
at the same time for some reason. But they were still accepting submissions.
How that could happen I have no idea, unless d.net was coordinating some
work on them.

More information about what I observed:
1) It was not a general internet connectivity problem - tracert, ping were
	to various points on the internet. The keyservers were actually
responding to
	the client, flushing OK but not fetching. There was no diagnostic
logging of the fetch
	problem in my log file, just a send with no receive:

[Mar 21 16:40:14 UTC] The keyserver says:
[Mar 21 16:40:24 UTC] Sent 43 RC5 packets (129 work units) to server

2) It was the client's display reporting that the project was closed or no
more work was available.
3) Problem disappears now that the keyservers are reporting 'up' on the
d.net network stats page

-----Original Message-----
From: waldo kitty [mailto:wkitty42 at alltel.net]
Sent: Wednesday, March 21, 2001 11:24 AM
To: rc5 at lists.distributed.net
Subject: Re: [RC5] RC5 keyspace finished?

first, slow down... you seem to have started jumping off in all
directions based on one ting you may have viewed...

Ryan Malayter wrote:
> Has anyone else out there noticed that the keyservers aren't handing out
> blocks anymore?

i'm not having any problems over here... all my clients are pulling
blocks from my perproxy and the perproxy is getting blocks from the main

> How in the hell can RC5 be closed?

does it say that in your client's ini file or on its display?

> Did they d.net forget to add more keyspace to the servers?

IIRC, d.net hasn't had to do the keyspace moving stuff in a year or

> Did we find the solution?

not that i'm aware of but it may take a day or so for that info to be
> This started this morning, and I've noticed the problem on several
> machines on two different networks.

the internet, itself, has been going thru some problems here and
there... i'm aware of several large providers that have been upgrading
et al... have you tried any of the basic tcp/ip diagnostics and aimed
them at the keyserver(s) you get your keys from? ping and traceroute are
your friends...

      (@@)                      Waldo Kitty, Waldo's Place USA
__ooO_( )_Ooo_____________________ telnet://bbs.wpusa.dynip.com
_|_____|_____|_____|_____|_____|_____ http://www.wpusa.dynip.com
____|_____|_____|_____|_____|_____|_____ ftp://ftp.wpusa.dynip.com
_|_Eat_SPAM_to_email_me!_YUM!__|_____|_____ wkitty42 (at) alltel.net

To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
rc5-digest subscribers replace rc5 with rc5-digest
To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
rc5-digest subscribers replace rc5 with rc5-digest

More information about the rc5 mailing list