See Matt's post HERE

Bernie

---

He did also say that AP work would likely be able to continue, so that's the solution for those who run out of MBs for CPU and CUDA. Some of you may not like running AP, but if that's all there is, there's only two choices: crunch AP or use a back-up project.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

Looks like SETI Beta has plenty to do...132k WUs at the moment...

---

Clk2HlpSetiCty:::PayIt4ward

I have a couple of back-up projects if I have to fall back on them.

---

To help alleviate panic, here's the gist of our general plan:

1. get thumper back up and running with a three-way root mirror. If all goes well, this will be done enough sometime tomorrow (Wednesday), i.e. we'll have a two-way root mirror and let the third one sync up in the background while we bring the system up, then during next week's outage do more drive swapping to install grub/finish the resync on this third drive.

Splitting/assimilating will be completely off for all projects until thumper is back up.

2. as soon as thumper is back up (tomorrow?) we can turn splitting/assimilating on for AP and get to work on the pulse table reconfiguration (which we can only do if the system/database is up). The plan (in simplest terms) is: create new database chunks, copy the current pulse table to these new chunks, then drop the old table and rename the new one. We estimate at least 24 hours for that.

So if we time things right we may be fully functional before the end of thursday, maybe friday. However considering the lost time this morning and the usual unexpected hurdles that crop up.. that's why I give it a week if only to keep expectations realistic, yet leave room for potential pleasant surprises.

- 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

See Matt's post HERE

Bernie

Bummer Dude, Looks like the well is dry at the moment, But then We're going through a Drought here, Rain will come one day soon, Until then I'll wait.

---

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

Would reissues of AP 5.00 be affected?

Reissues for wu-errors or missed deadlines will continue as normal, so there will be a small trickle of work available.

---

"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."

So if it takes a week to get Thumper and everything else back up to speed, it'll be two before there is a steady work flow of units once again. Network traffic will be hell the moment it's brought back on line.

No biggie, just have to find something else to crunch.

---

Well even though it's a dev version, I installed 6.6.17 on both of my CUDA machines and it's working well. Unlike 6.4.5, it is capable of running GPU Grid and Seti@home at the same time without scheduling issues. So if your GPU goes cold during this outage, subscribe to GPU Grid as a backup project.

---

You will be assimilated...bunghole!

Well even though it's a dev version, I installed 6.6.17 on both of my CUDA machines and it's working well. Unlike 6.4.5, it is capable of running GPU Grid and Seti@home at the same time without scheduling issues. So if your GPU goes cold during this outage, subscribe to GPU Grid as a backup project.

I wish I could right now, But It will be several months before I can upgrade to a gpu that can crunch as I don't think the old 7800GTX will do the job.

---

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

Set to nnt and will use the time to do all thats necessary to run 6.6.17 , then maybe gpu grid.

---

Set to nnt and will use the time to do all thats necessary to run 6.6.17, then maybe gpu grid.

I earlier set Boinc to nnt also, Gpugrid I can't do.

---

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

Well, if it is going to be that long a drought, time to schedule some periodic maintenance on the CUDA cruncher. At least the silent majority who seems to be mostly on AP will not notice it.

---

Interestingly, very occasional tasks do seem to be leaking out. One arrived here at 8.43 UTC this morning.

---

I have just had 3 MBs all resends, with all 3 it seems that one of the wingmen doing them has detached. Do not know if it is the same person.

---

This is not a newly split WU but one that's been resend to you. This will occasionally happen.

---

I guess there's one good thing out of this. It turns out that if there are no AP_v5's to send, computers that have the right settings in the venue will actually get MBs afterall, but the AP_v5 bucket has to be empty. :p

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

Nothing wrong with AP's.....

Sure it takes a tad longer, but the credits more then make up for it.....

---

Nothing wrong with AP's.....

Sure it takes a tad longer, but the credits more then make up for it.....

No, there isn't anything wrong with APs, I was just mentioning that from what I have seen, if AP_v5 is selected, that's all you get. Then I noticed that if the AP bucket is empty, it is in fact possible to get MB, but the AP bucket has to be empty.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

After a quick glance at the cricket graph, it looks as if around 7pm PDT (utc-7) work of some kind started flowing. Looking at the server status page, it looks as if the crew did get things working well enough to get AP rolling again.

Good job guys!

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)