I will waite. I still have an AP cruncing for 10 more hours. The last WU on the i7. Not bad, my 3 day cache was perfect. When the dust settles and I report all my work, I will update lunatics to the new version, Ive allready updated my GPU drivers.

---

[/quote]

Old James

I have validate errors for at least 2 WU. They have been reported up to at least 3 weeks ago and are still waiting on validation. One both wingman reported in august 20th and 27th and looking at the output file they match but the validator never got to them. 645067344

2nd WU
652149026

The most recent seems to be hours old from when the 2nd reported in.

---

Technical News : 'the upload store is full - working on it'

Uploads are disabled for the moment.

---

Think I see the problem.

Results returned and awaiting validation	8,295,094	110,926

I'll upload the rest on Monday. Have a good weekend.

Think I see the problem.

Results returned and awaiting validation	8,295,094	110,926

I'll upload the rest on Monday. Have a good weekend.

Me I'm already waiting until later, So Sunday or Monday make no difference to Me either.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Think I see the problem.

Results returned and awaiting validation	8,295,094	110,926

I'll upload the rest on Monday. Have a good weekend.

That's results waiting for a wingmate's return. Your choice, but getting tasks uploaded and reported so they can be validated and assimilated allows the WU and result files to be deleted. WU files are about 15 times larger than typical result files, so even if only a third of your uploads allow a WU to be retired it still reduces disk space used considerably.

                                                                 Joe

"Update" may give you an updated total + RAC but it also increases the load on the servers by one more request, so for that reason at this particular time of the week I would not recommend it.

This needs confirmation from one of the Devs.
I do know that even if a WU is "uploaded", if it is not "reported" by the due date it still times out. Therefore it must still be held in storage somewhere until the full reporting sequence is complete. Hence my post above.
Can someone please explain?

T.A.

Edited for clarity

"Update" may give you an updated total + RAC but it also increases the load on the servers by one more request, so for that reason at this particular time of the week I would not recommend it.

This needs confirmation from one of the Devs.
I do know that even if a WU is "uploaded", if it is not "reported" by the due date it still times out. Therefore it must still be held in storage somewhere until the full reporting sequence is complete. Hence my post above.
Can someone please explain?

T.A.

Edited for clarity

I fully agree with your idea. The storage space is obviously more critical than the costs of one more request. Anyone who has NNT set and has uploaded several task results ought to use Update to get them reported. During the initial 4 hours when the download servers are disabled is a very good time to get as many reported as possible, that's exactly why the project is starting up that way.

As to the wisdom of a large enough cache to not need more work until Sunday, I don't know. If all users did that, the storage space would be even more an issue than it is now.

                                                                 Joe

"Update" may give you an updated total + RAC but it also increases the load on the servers by one more request, so for that reason at this particular time of the week I would not recommend it.

This needs confirmation from one of the Devs.
I do know that even if a WU is "uploaded", if it is not "reported" by the due date it still times out. Therefore it must still be held in storage somewhere until the full reporting sequence is complete. Hence my post above.
Can someone please explain?

T.A.

Edited for clarity

I fully agree with your idea. The storage space is obviously more critical than the costs of one more request. Anyone who has NNT set and has uploaded several task results ought to use Update to get them reported. During the initial 4 hours when the download servers are disabled is a very good time to get as many reported as possible, that's exactly why the project is starting up that way.

As to the wisdom of a large enough cache to not need more work until Sunday, I don't know. If all users did that, the storage space would be even more an issue than it is now.

                                                                 Joe

Depending on how they deploy it.......maybe 'Oscar' will help.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Shoot me down in flames why don't you ;). What I meant was not just 1 update by 1 user but if this is extrapolated to being done by everyone. Though thinking now that's more an issue with ppl hitting "retry". I agree "update"-ing seems to push things through, though obviously the client does this auto eventually.

Shoot me down in flames why don't you ;). What I meant was not just 1 update by 1 user but if this is extrapolated to being done by everyone. Though thinking now that's more an issue with ppl hitting "retry". I agree "update"-ing seems to push things through, though obviously the client does this auto eventually.

No flames.......everybody's in the same ship..

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Shoot me down in flames why don't you ;). What I meant was not just 1 update by 1 user but if this is extrapolated to being done by everyone. Though thinking now that's more an issue with ppl hitting "retry". I agree "update"-ing seems to push things through, though obviously the client does this auto eventually.

The problem is that after an outage the client will not auto "Report" until after the it has uploaded all the backed up units. If the client is trying to "Report" a large number of units, the size of the file it has to upload in order to make a successful report is "big", if the server is busy it will probably time out before the report is complete.

In the current situation where server storage is at a premium, getting the units assimilated and off the hard drives is the priority. This is why I suggested manually reporting tasks. If you hit "Report" when there are only 50 or so units to check in, you are much more likely to get through than if there are a couple of hundred plus.

T.A.

When SETI comes back online what I see here are uploads being done and the wu state being changed to "ready to report". Boinc is continually reporting 3 or 5 or whatever is ready while the process of uploading is going on.

I see this by watching the messages. What version of Boinc are you using? Mine is 6.10.58

---

Boinc....Boinc....Boinc....Boinc....

Boinc is continually reporting 3 or 5 or whatever is ready while the process of uploading is going on.

But BOINC does that only if asking for new work (I think), not with NNT set.

Gruß,
Gundolf

Boinc is continually reporting 3 or 5 or whatever is ready while the process of uploading is going on.

But BOINC does that only if asking for new work (I think), not with NNT set.

Gruß,
Gundolf

I've had reports going through (while uploading) even with NNT set, depends on how far deadlines are away, and cache settings,

Claggy

With NNT set uploads and reporting still occur.

---

Boinc....Boinc....Boinc....Boinc....

With NNT set uploads and reporting still occur.

Yeppo, uploads go through immediately but from what I've seen, auto reporting only happens once every 24 hours.

With NNT set uploads and reporting still occur.

Do you have <report_results_immediately> set?

Gruß,
Gundolf

With NNT set uploads and reporting still occur.

Yeppo, uploads go through immediately but from what I've seen, auto reporting only happens once every 24 hours.

According to this Boinc FAQ page:

For BOINC 5.8 and above: Completed work is reported at the first of:

1) 24 hours before deadline
2) Connect Every X before deadline.
3) 24 hours after task completion.
4) Immediately if the upload completes later than either 1, 2, or 3 upon completion of the task.
5) On a trickle up message (CPDN only, I believe).
6) On a trickle down request.
7) On a server scheduled connection. Used, but I am not certain by which project.
8) On a request for new work.
9) When the user pushes the update button.
10) On a request from an account manager.

The reports while uploading, with NNT set will be because of 3) and 4) (and maybe 2) depending how big X is and how close to deadlines any Wu's are)

Claggy

If it makes you feel better, I reported as many as I could before shutdown (at work).