Issue with official stats site

[Napoleon]

Official stats site seems to have some problems keeping up with my recently resurrected ION folding - username ION, team _Solo_ (team number 191980). The most recent ION WU I returned was 2011-12-20T02:52:03, Kakao stats has it credited already, and EOC stats is likely to follow suit within 20 minutes, I'll update this post after that... yep, this WU now shows up in EOC stats as well.

Code: Select all

02:52:01:Sending unit results: id:02 state:SEND error:OK project:5769 run:8 clone:400 gen:517 core:0x11 unit:0x7ef07b514eef500c0205019000081689
02:52:01:Unit 02: Uploading 88.54KiB to 171.67.108.11
02:52:03:Unit 02: Upload complete
02:52:03:Server responded WORK_ACK (400)
02:52:03:Cleaning up Unit 02

And a screen capture from current official stats (2011-12-20T06:10:00)


Not a big deal for me, the WU seems to be uploaded and credited properly anyway, but maybe it'd worthwhile to take a closer look at the official stats server? I also have usernames Napoleon (CPU folding) and Zotac430 (GPU3 folding) under team _Solo_, those appear to work OK. I'm actually running only one v7 client and team _Solo_ is just me in my various incarnations, I like to goof around with multiple user names and passkeys within slot configurations.

[bruce]

Earlier today there were some strange readings for that WS. I think they might have been working on it. Serverstat isn't always keeping up-to-date either.

[Napoleon]

I forgot to mention, v7 client reports an unknown Base Credit, therefore also unknown Estimated Credit and Estimated PPD. Timeout is also Unknown, but Assigned and Expiration (final deadline) info is correct. Perhaps that has some impact on how official stats display the dates, times and active client count.

I presume such cosmetic quirks are quite typical when dealing with older GROPU2 Work Servers. Main thing is that the WUs are getting done right, and at least 3rd party stats show up-to-date credit info for it, too. The official stats haven't been updated yet as I'm posting this reply. I don't consider this something that needs urgent fixing, when there a better things to do with the developers' time. I figured to point this out "just in case".