• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

where did my blocks go?

M

mindless

Senior member
I was saving up for a miniflush (from sat till today) nothing big, just wanted today to be my best day. Well about 30 min ago I dumped my proxy (out file was 206k), I know it dumped, my modem lit up and it went down to 8 bytes. Well the weekly and total stats updated on Mika's and Ive got a total of 1300 today minus the 100 that were on there from my work machine that leaves me with 1200 blocks for 6 days work. I know I dont do much but I should have about 5 times that from my two home machines. Where the hell did my blocks go?

**EDIT**
See my reply, blocks got submitted, but earlier than they should
 
Probably overlap. Wait until Mika's next update and it's likely they'll show up. The pproxy software has a little lag in it. For example, when mine rolls over each day, the previous days total always goes up on the next half hour run.

Russ, NCNE
 
Ok I think I found a problem

2000-09-19 15:28:05,rc564 r=2835/3822, d=3937/10000, 3.0 Mkeys/sec, tot=1560
2000-09-19 15:28:05,ogr r=0/0, d=0/0, 0.0 Mnodes/sec, tot=0 stubs
2000-09-19 15:28:05,Status: Uptime: 1.12:57:42, 2 listeners, 0 uplinks
2000-09-19 15:28:05,Status: 0 active clients (peak: 1, mean: 0.00)
2000-09-19 15:28:20,Status: Uplink needed... (thresholds exceeded)

Now on 9/19 I uploaded blocks to dnet, why they were sent is beyond me, it was less than 1/2 my max out buffer. At least I got credit for them. too bad they missed Mika's.

Anyone know why my proxy uploaded all those?
 
Oh, you're running a pproxy.🙂 The only way I've found to prevent the pproxy from flushing blocks at all, is to put a keyserver address in the ini file that isn't really a keyserver.

Russ, NCNE
 
So it ignores the max value I set?

Ok then I need about 15,000 blocks, this next one is going to work right. How can I get them? the proxy wont download that many for my two systems. and if I enter a proxy with a bad name it can't fetch. do I just pull my out buffer file out of the directory and change it to a valid keyserver?
 
In the RC5-64 section of the ini file, you need to add the following entry to bypass the built in limitations:

expertmode=1

Then, after it's grabbed what you need in your in-buff, edit the ini with a bad keyserver address.

Russ, NCNE

 
To insure the expertmode works, you will want to restart the proxy. Additionally, some settings seem not to be included in a restart, requiring the proxy to be shut down and re-started (I think this only applies if it is running on a Win9x PC, not sure as I have not tested it out fully to see). Just warning in case!🙂
 
damn thats alot of blocks, all those would be reissued long before I ussed em, hell its gonna take me close to 20 days to use up the ones I downloaded
 
The only way I've found to prevent the pproxy from flushing blocks at all, is to put a keyserver address in the ini file that isn't really a keyserver.

I did that too, until HeaviIron taught me a trick he got from bphantom :



<< > > Here is what you need to do:
>
> expertmode=1
> minkeysready=5000 (whatever)
> maxkeysready=10000 (whatever)
> minkeysdone=500000 (This is what does it)
> maxkeysdone=500000 (Has to equal if not exceed minkeysdone)
>
> The pproxy will talk to the upstream keyservers whenever it needs blocks,
> but will not flush any of it's blocks (at least not until it hits 500000).
> Expertmode must be enabled. This was usually how I would run the PTE
> dumps.
 >>

 
leblatt, your positive this works, correct?

not that I dont trust you, just I want this one to work right. I want to have my best day by far (stupid wanna be trojaned phf screwed it all up for me)
 
mindless, as the original author of that email, YES! It works great. The minkeysdone=500000 (maxkeysdone HAS to equal or be higher then minkeysdone!) is the key to make it work. Basically it will not allow the first 500000 blocks to be dumped. Any blocks over 500000 will dump to the keyserver, but that original 500000 stays no matter what.

Russ, every now and then you might want to set minkeysready and maxkeysready to zero and allow your pproxy to flush out all of your blocks. Otherwise a lot of the small 2^28 - 2^29 blocks get pushed to the back and never get used (my personal experience and opinion). I usually do this once a month.

Brad..
 
bphantom - from your description it seems that a risk exist for 'stale' blocks. No FIFO queue. Correct?
 
As stated, it is my personal opinion that the smallest blocks get stuck in the pproxy no matter what sort of a FIFO/LILO queue is supposed to be running. Why I think it behaves this way is that fresh large blocks are immediately sent out to clients. When I do the flushing of the pproxy (min/max keysready = 0), the blocks start to get smaller and smaller until the pproxy is eventually sending only 1*2^28, 2*2^28 and some 3*2^28 blocks.

I must admit I'm running the older 313 pproxy, so that may be the problem. I would have upgraded to the newest beta release, but I do not want to run a beta version on my master pproxy (all of the original 319 betas have had an annoying bug (fixed in 319c)). And (BoberFett would make note if I didn't say this 🙂 ) also partly because my pproxy has the highest uptime so far on the TA PProxy Status page. 🙂

Brad..
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top