Short status update: I turned on both the result/task pages and the resend-lost-results - the latter of course clearing out the pipes (still clogged with various ghost workunits).

The science database is fully loaded on oscar now, and we're now rebuilding all the indexes, running "update stats" on all the tables. This is taking a bit longer than we thought, though we have some knobs to turn to speed things along after the current set of queries pushes through. We're still looking at maybe starting the assimilators on Monday, and then new work creation on Tuesday. While not far fetched, that's still being optimistic. The database on thumper is indeed turned off. I'll adjust the server status page once oscar is able to show a green "running" status.

Jeff and I did some more server closet cleanup, but nothing noticeable in a picture.

- Matt

---

-- BOINC/SETI@home network/web/science/development person
-- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude

Danke, Herr Server Herder

Hey Matt, if you could ship the first WU at 11:15 local time on Monday morning, I'll share my winnings with you.

No need to tell anybody about this little agreement, right?

---

Thank you so much for switching resend-lost-work-units back on again. Much appreciated.

---

Soli Deo Gloria

Thanks for the update Matt much appreciated, i dare say a lot of hard work has gone on in the last few weeks, i hope it all works well for everyone.

---

Thanks for the update Matt. Thanks for your great job.

Teriffic
1 LOST WU
3/12/2010 7:58:40 PM SETI@home Message from server: Resent lost task 14ja10ab.10693.67.13.10.250_0
3/12/2010 7:58:40 PM SETI@home Message from server: Project has no tasks available
3/12/2010 7:58:42 PM SETI@home Started download of 14ja10ab.10693.67.13.10.250
3/12/2010 7:58:47 PM SETI@home Finished download of 14ja10ab.10693.67.13.10.250
3/12/2010 7:58:47 PM SETI@home Starting 14ja10ab.10693.67.13.10.250_0
3/12/2010 7:58:47 PM SETI@home Starting task 14ja10ab.10693.67.13.10.250_0 using setiathome_enhanced version 609

---

Sorry to ask a noob question but how do I set prefs. to get lost work units?

Thanks!
ALR

Now that SETI production is back on-line, how about turning on the verifiers on BETA, so that the (roughly...) 68k WU's there (including ~85 of mine...) can be verified, assimilated, etc.?

---

.

Hello, from Albany, CA!...

Sorry to ask a noob question but how do I set prefs. to get lost work units?

Thanks!
ALR

It's OK, nothing for you to do. The setting is controlled at the server end, and now it's on (for the time being) any lost work should be resent automatically next time you request work.

Different question.

Is a lost work unit a new work unit? Thinking of people who may have set no new tasks.

---

My understanding is that a `Lost' Work unit is one
that You've lost.

---

Different question.

Is a lost work unit a new work unit? Thinking of people who may have set no new tasks.

Yes. If you're set to NNT you will get zilch. "Allow new tasks" and the lost shall be found.....

---

Different question.

Is a lost work unit a new work unit? Thinking of people who may have set no new tasks.

Yes. If you're set to NNT you will get zilch. "Allow new tasks" and the lost shall be found.....

Then is server side smart enough to see this (assuming a connect) and immediately time out the work unit so someone else can crunch it?

---

Different question.

Is a lost work unit a new work unit? Thinking of people who may have set no new tasks.

Yes. If you're set to NNT you will get zilch. "Allow new tasks" and the lost shall be found.....

Then is server side smart enough to see this (assuming a connect) and immediately time out the work unit so someone else can crunch it?

If you set NNT and have no work to report, the server will never be contacted.

---

BOINC WIKI

Different question.

Is a lost work unit a new work unit? Thinking of people who may have set no new tasks.

Yes. If you're set to NNT you will get zilch. "Allow new tasks" and the lost shall be found.....

Then is server side smart enough to see this (assuming a connect) and immediately time out the work unit so someone else can crunch it?

If you set NNT and have no work to report, the server will never be contacted.

And if you, despite having NNT, force connection to scheduler, your lost task(s) will be (re)sent to you. NNT means that client doesn't request new tasks ... doesn't say anything about old tasks.

---

Metod ...

Doancha jus luv computers????

Different question.

Is a lost work unit a new work unit? Thinking of people who may have set no new tasks.

Yes. If you're set to NNT you will get zilch. "Allow new tasks" and the lost shall be found.....

Then is server side smart enough to see this (assuming a connect) and immediately time out the work unit so someone else can crunch it?

If you set NNT and have no work to report, the server will never be contacted.

And if you, despite having NNT, force connection to scheduler, your lost task(s) will be (re)sent to you. NNT means that client doesn't request new tasks ... doesn't say anything about old tasks.

Are you sure?, While at Einstein and Collatz this might be true, at Seti Beta you need to actually ask for work for the resends to happen, Seti Main is likely to be the same,
(i remember reading a changeset some while ago, that if the client doesn't ask for work, the server won't do a database lookup to see what tasks the client is supposed to have, so minimising the load on the database server)

Claggy

Different question.

Is a lost work unit a new work unit? Thinking of people who may have set no new tasks.

Yes. If you're set to NNT you will get zilch. "Allow new tasks" and the lost shall be found.....

Then is server side smart enough to see this (assuming a connect) and immediately time out the work unit so someone else can crunch it?

If you set NNT and have no work to report, the server will never be contacted.

And if you, despite having NNT, force connection to scheduler, your lost task(s) will be (re)sent to you. NNT means that client doesn't request new tasks ... doesn't say anything about old tasks.

Are you sure?, While at Einstein and Collatz this might be true, at Seti Beta you need to actually ask for work for the resends to happen, Seti Main is likely to be the same,
(i remember reading a changeset some while ago, that if the client doesn't ask for work, the server won't do a database lookup to see what tasks the client is supposed to have, so minimising the load on the database server)

Claggy

Yes, when resends were enabled here at Main a couple of days ago, that's what I saw.

And further, the number of resends I got seemed to match the state of my cache/work request - I didn't get them all at once. I seem to remember some concern about the old-style code, which tended to resend everything all at once - leading to obvious problems with download capacity and, in some cases, cache handling.

Different question.

Is a lost work unit a new work unit? Thinking of people who may have set no new tasks.

Yes. If you're set to NNT you will get zilch. "Allow new tasks" and the lost shall be found.....

Then is server side smart enough to see this (assuming a connect) and immediately time out the work unit so someone else can crunch it?

If you set NNT and have no work to report, the server will never be contacted.

That might be true with Seti, but it is not true with all BOINC projects. CPDN and eOn come to mind.

---