all uploaded results seem to be "pending" for a week now

blaubo
blaubo
Joined: 22 Dec 06
Posts: 10
Credit: 287,155
RAC: 0

Thanks for all the

Thanks for all the explanation.

Now in my account slowly some of the pending WUs got the credit granted. But the new score is not shown in the Boincstats.com account even after two days. Do I have do anything about that, or is it fixed automatically as well?

BarryAZ
BarryAZ
Joined: 8 May 05
Posts: 190
Credit: 320,543,393
RAC: 2,938

The BOINC stats updates will

Message 60913 in response to message 60912

The BOINC stats updates will happen automatically, the data base 'ping pong' effect causes the stats programs to not get updates as well. When (if???) the Einstein program returns to its historic reliable self (and assuming they post status note informing the vast unwashed of that successful implementation), then results will get uploaded, credited and the stats programs will get regular updates.

Quote:

Thanks for all the explanation.

Now in my account slowly some of the pending WUs got the credit granted. But the new score is not shown in the Boincstats.com account even after two days. Do I have do anything about that, or is it fixed automatically as well?


Odysseus
Odysseus
Joined: 17 Dec 05
Posts: 372
Credit: 19,466,387
RAC: 2,532

RE: Now in my account

Message 60914 in response to message 60912

Quote:
Now in my account slowly some of the pending WUs got the credit granted. But the new score is not shown in the Boincstats.com account even after two days. Do I have do anything about that, or is it fixed automatically as well?


Sometimes when a project is overloaded, or is working on the database, the usual daily statistics ‘dump’ is skipped, perhaps because the records aren’t fit to be queried, or because the program or server that performs the task is down—or just to save time & resources. The BOINCstats summary display indicates the “Last XML update� for E@h to be over two days old now. Whether or not it’ll get fixed automatically, it’s certainly on the project’s side, not the participants’.

Augie
Augie
Joined: 3 Oct 05
Posts: 3
Credit: 1,934,486
RAC: 0

I am experiencing similar

I am experiencing similar backlogs on "pending" - over 5000 credits at this point; at least 102 files pending. The error message is can't find "Fstat.out.ckp. No usable checkpoint found". This on a newly installed Vista Ultimate machine (since about 2007FEB08) and a "not touched lately" laptop with WIN XP Pro SP2 (since 2007FEB08). Now and then credit is granted to a file, buit most pend. I'm not familiar with ther stderr codes used and wonder if I have clobbered up something.

Sou'westerly
Sou'westerly
Joined: 9 Jun 06
Posts: 57
Credit: 715,838
RAC: 0

Augie, The reason that your

Message 60916 in response to message 60915

Augie, The reason that your “pendings� are rising is because of problems with the project’s database on its servers. Your computers seem fine apart from a little hiccup on the 10th of Feb with your Vista machine. That seems to have sorted itself out now. The reason for the “no usable checkpoint found� is that when the application starts it looks to see if it has been running previously and has a checkpoint to start from. This is so that if you close down BOINC and then later start it again it does not start the WU from the beginning but starts from the last checkpoint. Obviously the first time that it starts a new WU it does not find a checkpoint and so prints that message. The clue that all is OK is the “[normal]� included in the message. Dave.

Augie
Augie
Joined: 3 Oct 05
Posts: 3
Credit: 1,934,486
RAC: 0

RE: Augie, The reason that

Message 60917 in response to message 60916

Quote:
Augie, The reason that your “pendings� are rising is because of problems with the project’s database on its servers. Your computers seem fine apart from a little hiccup on the 10th of Feb with your Vista machine. That seems to have sorted itself out now. The reason for the “no usable checkpoint found� is that when the application starts it looks to see if it has been running previously and has a checkpoint to start from. This is so that if you close down BOINC and then later start it again it does not start the WU from the beginning but starts from the last checkpoint. Obviously the first time that it starts a new WU it does not find a checkpoint and so prints that message. The clue that all is OK is the “[normal]� included in the message. Dave.

Thanks for the nice explanation, Dave; I have been too long in Windows-land, I guess. So I'll settle back and relax and let things continue.
Augie

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.