Eeeeoooo. Looks like this minor corruption in the science database is really snagging us, at least right now. We're talking one or two rows of the zillions in the astropulse signal table - but informix isn't being very informative about which row or two, nor what to do about it. Meanwhile, this broke the replication of astropulse - or at least we think it broke replication. This may very well have failed for some other reason.

This hasn't been a public data flow issue - we can still split/assimilate multibeam and astropulse work for the most part. Still, it's been preventing us from doing any science for a while now. So it's roll-up-our-sleeves time. We're doing a more robust table check (and hopefully repair) overnight tonight, and had to shut off astropulse splitting for now. Which means only multibeam workunits for the near term.

Meanwhile we filled up the raw data drive during all this software blanking analysis. I forgot to carry the one or something. Anyway, no big deal, some minor cleanup this morning, and we're back on track with that.

- 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

Thanks for the update Matt,

Claggy

---

Yeah, databases generally can only fix pages, not rows. Let's hope your repair operation reports success in the morning.

Morning Matt,

Thanks for keeping us posted on the difficulties.

I may not understand some (all?) of the technical language, but I do get the "flavor."

Does any of this (and this may demonstrate my relative ignorance)affect tabulation of results? My little laptop is working silly churning out tasks as they are received. However, the "pending" table is growing ever larger (up to 37 now - going back to early September).

Please advise.

Thanks,

ront

---

Does any of this (and this may demonstrate my relative ignorance)affect tabulation of results? My little laptop is working silly churning out tasks as they are received. However, the "pending" table is growing ever larger (up to 37 now - going back to early September).

It's best to post these questions in Number Crunching or the "help" forums, not Technical News.

SETI@Home sends each work unit to two different machines to process, and I looked through your pendings, and all of the ones I saw were waiting for the other machine (your "wingman") to report results.

Sometimes, that takes a while, and other times, crunchers just quit, or the machine breaks, or the boss finds out and orders work deleted, or a half-dozen other issues I haven't noted causes work to be lost.

That's why we have deadlines, and why those will be reassigned to new wingmen just as soon as the deadlines pass.

It looks to me like it's just normal pendings....

---

What happened to the database servers Matt? Any specifics about why they went down, or no?

- Luke.

---

- Luke.

To whomever spent time fixing it on Sunday, THANKS.

---