The problems last week with bruno (which continue, and I'll address below) completely overshadowed problems with our radar blanking suite which suddenly was unable to convert raw data into clean data which can then be split into workunits. So we ran out of work to send out over the weekend, and I was personally unable to do anything to help the effort in figuring out why. However, immediately this morning I spotted the problem. Long story short, this was one of those cases where the wild error messages with impossible number values were obscuring the less obvious real problem, which was simply a configuration file had gone missing. I replaced this file, and new work should be coming down the pike shortly.

Back to bruno: the woes continue with this system regarding its drives, though I am trying a few more things out before I throw my hands up in complete frustration. It would indeed be a shame to simply abandon this server as it has a lot to offer if it works. We'll have our server meeting later today to discuss where to go next on this front - I just wanted to give y'all an earlier than normal "heads up" today given the loss of work, etc.

- 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

Good news - I was just now able to get an OS on the old bruno and reboot the system and it worked! There must have been some data gunk on the old root drives messing up the FC14 install. The installer kept crashing until I finally shredded these three drives (putting all zeros on them).

Of course, we still have to figure out the RAID situation for the remaining 21 drives. We currently have no working controller in the system, so we need to decide what to do next.

- 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

Great news Matt, now I don't have to turn Einstein back on. I shut it down when the new servers got going so Seti could catch up after being down all that time and only Einstein was running. Hooray for Seti@Home and keep up the great work.
____________
Seti@Home Classic Work Units 413
Seti@Home Classic CPU time 3,869 hours

Guess it wasn't as simple as Matt made it sound. They must have run into some more problems as there is still no new work. :-( Hope it's not too serious and they are able to get back up soon.
____________

Guess it wasn't as simple as Matt made it sound. They must have run into some more problems as there is still no new work. :-( Hope it's not too serious and they are able to get back up soon.

Ain't necessarily so. Doing anything at all with a 50 GB file takes time - even if he squirted one into the upstream end of the pipe just as he posted, we don't really know how long it takes before the complete thing emerges out of the other end of the sausage machine, ready to be mounted and offered up to the splitters.

For a continuous process like this, steady-state throughput gives no indication of how long it takes to recharge the (? many parallel) pipes from a drought.