| A problem can arise getting a freshly installed 311 proxyper to serve blocks to clients that were previously connecting directly to d.net keyservers. The proxy will not serve clients if its input buffer is empty, but it will not go out to a keyserver and get blocks until there are some completed blocks in the output buffer to send. Clients try to fetch blocks first, and when the connection is refused by the proxyper they do not attempt to flush. A lockout situation thus occurs.
One way to kick the proxyper off is to set maxblocksdone to a small number, then go to a client and manually flush some blocks. This induces the proxyper to connect to a keyserver, whereupon it will fill its input buffer. Now restore maxblocksdone to your preferred setting and restart your proxy. All will be well from now on.
|
distributed.net Faq-O-Matic : 
My newly installed perproxy won't serve blocks to my clients. What gives?