I'm still missing a lot of blocks after rejoining :(

[BGod]

I don't quite understand what's going on here. My name wasn't in the list of people that need to re-join, but I did it anyway, just to make doubly sure. I've verified on most of my remote machines that they are using my current e-mail address. I've got 2 or 3 left to check but they are 125 miles away. What else am I missing besides a bunch of blocks?

Jay's Proxy
20 Nov 2000 GMT 8947 blocks
19 Nov 2000 GMT 8198 blocks
18 Nov 2000 GMT 5273 blocks
17 Nov 2000 GMT 9188 blocks
16 Nov 2000 GMT 6963 blocks
15 Nov 2000 GMT 6120 blocks
14 Nov 2000 GMT 8101 blocks

Mika's Proxy
20 Nov 2000 GMT 8915 blocks
19 Nov 2000 GMT 8166 blocks
18 Nov 2000 GMT 5305 blocks
17 Nov 2000 GMT 9156 blocks
16 Nov 2000 GMT 6963 blocks
15 Nov 2000 GMT 6120 blocks
14 Nov 2000 GMT 8101 blocks

Dnet summary Mika's Jay's
20-Nov-2000 6,335 -2,580 -2,612
19-Nov-2000 4,405 -3,761 -3,793
18-Nov-2000 2,532 -2,773 -2,750
17-Nov-2000 8,132 -1,024 -1,056
16-Nov-2000 6,924 - 39 - 39
15-Nov-2000 5,942 - 178 - 178
14-Nov-2000 7,726 - 375 - 375
--------------------------------------
Total missing blocks 10,730 10,803

 

[mindless]

randoms maybe?

 

[BGod]

Not a chance. My pProxy always stays full (30K+ buffered). I feed the two machines at work myself(4K+). All the remote machines are set up to buffer over 2K+ blocks each, which is a couple days worth of work. If they are dumping the blocks then they are fetching fresh ones first from Jay's pProxy.

I bet I'm not the only one that's short each day.

 

[mindless]

If you bypass Jator's proxy do you still miss blocks?
If not something is happening between you and him, or him and Mika...

I think skipping proxys might be a good place to start.

 

[Joe O]

Skipping Jator's and/or Mika's PProxy will not solve the problem.
ßGød, It's not that you are doing random's, someone else is.
Either that, or DNet is sending out duplicate blocks. I've sent in a 32 WU packet only to see that 31 WUs are credited. I highlited the word packet to emphasize that this was a single block. I received it directly from DNet and shipped it back the next day. This was not an isolated occurence. I emailed them offering to send them logs. Once I even backed up the buff-in file before working on it and offered it to them. No response, NADA, NIHIL, NICZ!

Now I know that, in theory, the random space is separate from the assigned space. BUT, someone could have changed their INI file to point to different spaces.

By the way, this is still occurring. Yesterday I sent 12124 WUs to Mika, and was credited with 11998 WU's at DNet. Go figure!

 

[Jator]

Mindless,

Since Mika's and my count are almost identical, I doubt it is between Mika and I. Something is amiss as even if randoms came into play, I find it hard to believe that nearly a 1/4 of his daily output is being lost due to others randoms. Not sure where to look though. Only thing I can think is to check e-mail addys. Maybe some machines with an old e-mail addy aren't getting creditied correctly.

I can run a seperate stats page without the retire function for you Jeff so that you can see what e-mail addy is being submitted on a daily basis and the amount of blocks for each.

ICQ or e-mail me if you want me to.

Jay

 

[Engineer]

Since D.net has had problems with individuals still being part of a team, is it possible that a "retired" e-mail may have possibly become un-retired? Just a thought...

 

[BGod]

All clients have now been checked, and they are all using my current e-mail address. There are some IP address and networking computer names that show up under Jay's pProxy that I can't identify. They don't have the output to make up the difference I've found in my block count if they were only doing randoms. I've also sent an e-mail to decible to see if he can make heads or tails out of this mess.

I've had two other people retire into my old e-mail address. Since then, they have changed to that e-mail address, then to the new one the last time I retired my account.

I'm at a loss here. I'll get ahold of you Jay.

 

[ViRGE]

Humm, I have to admit that that's the biggest block loss I've seen in a while.:Q Hopefully, it's just a small error at Dnet.