Proxy

Many thanks, page title of pproxy-stats are now new :D :thumbs:

but what exactly do you mean with that you don't know how to check that?
it is long time ago I worked with a pproxy myself, but doesn't every project has its file for input-buffer and output-buffer? - it would be the easiest to stop the pproxy, remove the ogr-buffer which holds the unprocessed stubs, start the proxy and let it fetch brandnew stubspace 4 stubs (which are 6-diff, i.e. 27/1-20-6-30-11-18; that means that after the "27/" are 6 numbers divided by a minus...)

I can certainly remove the file, but you asked how many were in it.. it's compressed in some way I think, at least looking with vi or cat or head does not display anything meaningful :)

stopping and deleting now..

Bok

everything is perfect now! many thanks!

Bok, what value is the blocksize option in the rc5-72 section of the config?

If it's not already, can we get it bumped to 1024 please? From the manual:

Quote:

---

[rc5-72]/blocksize: the preferred size of blocks when requesting additional workunits from the upstream server. The default is 256. If clients need smaller block sizes, then your proxy will automatically split large blocks into the needed size, however clients will not be able to request blocks larger than the size your proxy currently has available, since the proxy cannot combine smaller blocks together. Be aware that when your proxy requests additional workunits from the upstream server, this blocksize value may cause your proxy to temporarily exceed the "maxkeysready" since requests will always be done in multiples of this value.

---

Didn't even have a config for that value at all. I've added one and restarted, see if that works.

Bok

What is the cache size for RC5-72? We won't know if it had the desired effect until we crunch everything that was already cached and get to the new stuff.

Between me and DP, we've probably fetched over 30,000 blocks since you made the change. I'm keeping an eye on my Stream client and it's still only getting a maximum of 256 block packets so far.

[rc5-72]
logfilekeyblock=pproxyrc572
logfilekeyblockrotation=daily
minkeysready=3000
maxkeysready=10000
maxkeysdone=20
blocksize=1024

Ah, I forgot about the 20,000 block cache on my end. I'll give it a few more days and then see what comes through. Thanks!

OK, still haven't been getting any come through so I've done some more research and come up with something curious.

The proxyper manual was what I quoted from before, and it clearly says to use "blocksize" to specify the block size and that the default is 256. However, in the included example proxyper.ini it has the option "requestsize=256" in the RC5-72 section. I checked the latest FreeBSD and Linux tarballs and it was apparent for both.

Looks like a mix up on their part. I've changed my proxyper to include both blocksize=1024 and requestsize=1024 and there were no warnings about unknown options when I restarted. Please can you do the same?

edit: Looks good. My proxyper just hit the FDC one up for some more blocks and I saw "[2010-02-10 12:49:52] server: Queueing rc5-72 request for iter 1024."

done.

Can someone please kick the server for me.

crappity crap crap. I forgot to start this up again. When the server moves I'll make sure and put this in the startup script..

It's running now. Sorry Guru!

Thanks Bok.

pproxy.free-dc.org is still the correct entry for the personal proxy server?
I'm currently not able to connect to it :cry:

It died about an hour 1/2 ago by the looks of it, it does occasionally crash out for some reason, has done for years..

Restarted it now. And yes, pproxy.free-dc.org is the correct address.

Many thanks, client flushes now to pproxy.free-dc.org as I can see from pproxy-message ;)
But: is http://stats.free-dc.org/dnet/ogr/byemail.html still the valid URL for pproxy-stats? It says "Last Updated: 31 Jul 2010 10:40 GMT"
I am asking because I had to shutdown my pproxy because of power maintenance during weekends...

I never reconfigured the proxy stats after moving the boxen. Ran it once and had to kill it after 2 hours as it was still running and never ha a chance to debug it.