Reply With Quote
makes sense...
From the .plans:
Could be related.Originally Posted by snikkel
makes sense...
the-mk
Bok, could it be that the pproxy is out of order?
from my clients log:
[Jan 18 03:00:01 UTC] The perproxy says: "Free-DC Dnet Proxy!"
[Jan 18 05:00:04 UTC] The keyserver says: "Hai c0w! (cdy)"
[Jan 18 07:00:03 UTC] The keyserver says: "OGR-NG.. Sounds like a new Star Trek series.. (bang)"
the-mk
yup. IB had to reboot the webserver last night. I just restarted the proxy.
Bok
in answer to ^
today
And I'm now running a fresh new database with only the OGRNG data in it...
The older ones are still available (and being updated) if you use dnet2 rather than dnet..
I know we are close to finish anyways, better late than never !
Thanks!
the-mk
I've updated the proxy to the latest build to server ogr27. Seems to be working ok and has downloaded lots of work.
Hey, IB: I don't suppose I could talk you into hiding my email address on the proxy stats pages? I'll be your best friend!
I found it by doing a google search for "lfawkes". I was wondering why I just started getting spam out of the blue a few months ago.
Thanks man!
I'll do it now.. next update will reflect.
D'oh, observation fail on my part.
Thanks Bok!
*hands Bok one certificate of best friendship*
If anyone would ask me, I'd suggest to wipe out the free-dc pproxy server to get fresh ogr-stubs from the keymaster.
http://stats.distributed.net/project...?project_id=27
--> stubspace 3 is almost done, today only 40 are over, but the proxy is still providing a lot of stubspace-3-stubs, which I think is useless, the remaining stubs in the pproxy-buffer don't contribute to the remaining stubs of that stubspace...
anyone shares a part of my opinion?
have a nice day!
the-mk
great
btw, could we rename the title of that page to something different?
http://stats.free-dc.org/dnet/ogr/byemail.html
OGR-25 ended long time ago, maybe we should call it OGR-NG? should be future-proof
the-mk
depends on how you see it...
we usually have in Austria GMT+1, but during summer with daylight-saving-time we have GMT+2, so the time shown on pproxy-stats seem to be correct to me.
the-mk
Have updated (I think) the code which generates the title on the page to be OGR-27.. Let's see next update.
I'm sorry, it did not update
the-mk
I'm still processing unnecessary stubspace 3 ogr-stubs from pproxy.free-dc.org!
http://stats.distributed.net/project...?project_id=27
stubspace 3 is finished!
how many stubspace-3-stubs are waiting on pproxy.free-dc.org to be processed?
the-mk
I don't even know how to check that ?
And as for the page title, found it, I forgot I had two copies of ppstats installed and had changed the old one.. this time it should take effect.
Many thanks, page title of pproxy-stats are now new
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...)
the-mk
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!
the-mk
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:
[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.
I'm having fun!!! I'm just not sure if it's net fun or gross fun.
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.
I'm having fun!!! I'm just not sure if it's net fun or gross fun.
pproxy.free-dc.org is still the correct entry for the personal proxy server?
I'm currently not able to connect to it
the-mk
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...
the-mk
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.
Posting Permissions
