Hinke (Apr 20 2009)

The mysql database crashed on Friday, then again on Saturday. The reasons are mysterious, though we've had similar crashes in the past - just not two in immediate succession like that. Most of the large, important tables (user, host, workunit, result) are using the innodb engine, while the many others (including team, forum preferences, posts, etc.) are using mysql's standard myisam engine. There's worry we may have lost a few rows in some of the myisam tables, though they seem to check out okay. The replica database, though, is in a confused state so we just shut it off for the time being. We're going to save any remaining cleanup for tomorrow's usual outage. As stated elsewhere, Jeff and I have adopted a policy of no-system-changes (except for emergencies) until after the anniversary. So as long as mysql continues to run well, we're not going to worry about this so much.

I know I write all these missives and therefore I get the brunt of the accolades (or otherwise) but Jeff/Bob pretty much took care of the entire mess above. I did log in on Sunday and cleaned up the server status page and the validators (which for some reason *have* to start on the command line, as opposed to the usual cron job which restarts stopped processes), but that's the usual drill (we're always logging in on nights/weekends to kick one process or another).

- 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

Boy did you ever start a tornado of posts in your last update!


My apologies to Jeff and Bob for not giving them more credit in the "Thank you Admins" thread in Number Crunching. While their voices are not heard, their actions are noticed even if they are mistaken to be yours Matt. Its the silent heros that know the score.
____________

I really hope that Matt, et al. don't get burned by the user group's unpolished comments on these boards. I have to slap my own fingers at times.

Let's all remember that THEY are the professionals and WE are the amateurs, despite our setifarms and quadtrillion credits. And, WE must each begin each discussion with the assumption that THEY are doing the best job they can. Afterall, over the years the system has evolved for the better despite periods of setbacks.

Now if only one of us could find ET.

Is there any chance anybody could look into why seti is not updating its Boinc stats.Hey and thanks to the guys who kicked the server over the weekend ---- much appreciated !!!!!

Boy did you ever start a tornado of posts in your last update!


My apologies to Jeff and Bob for not giving them more credit in the "Thank you Admins" thread in Number Crunching. While their voices are not heard, their actions are noticed even if they are mistaken to be yours Matt. Its the silent heros that know the score.

I'll tell you why people are bailing out of this project: the perception, right or wrong, is that SETI is unable to stay 'up'. Anyone trying to join in the last couple of months is going to be frustrated, and then they'll get asked for money. And then, they'll move on to a something else.

A newbie I think should only have a cache of 2 days regardless of the number of processors and should have a credit score higher than zero in order to UPGRADE preferences.

Some months ago I brought on board a 1Ghz Pentium for a BURN IN and got a initial load of a MB unit with a completion time of 240 hours - Was I discriminatory about aborting it?

Some months ago I brought on board a 1Ghz Pentium for a BURN IN and got a initial load of a MB unit with a completion time of 240 hours - Was I discriminatory about aborting it?