We've had numerous database problems within the past few days. The one we just fixed minutes ago was innodb log files getting too large due to debugging of the original problems. Problems on top of problems. Hopefully we're ok now.

---

Dave Przybylo
MilkyWay@home Developer
Department of Computer Science
Rensselaer Polytechnic Institute

We've had numerous database problems within the past few days. The one we just fixed minutes ago was innodb log files getting too large due to debugging of the original problems. Problems on top of problems. Hopefully we're ok now.

Sorry you guys are having such troubles.

Thanks for fixing it that quickly.... phew! ;-)

---

Lovely greetings, Cori

Good news.

And think of these as great learning experiences, at least next time you will know how to fix these issues quicker.

I knew there was a reason that I did not start up a BOINC project -

Thanks for working so hard on keeping this up, and communicating with us on the problems.


Still getting connect errors :)

2/9/2009 13:39:28|Milkyway@home|Message from server: Server error: feeder not running
2/9/2009 13:39:28|Milkyway@home|Deferring communication for 1 hr 0 min 0 sec
2/9/2009 13:39:28|Milkyway@home|Reason: project is down

---

.

That word "hopefully" might have saved you this time! Otherwise it seems like you're jinxing yourself!! ;o)

---

A clear conscience is usually the sign of a bad memory

These things are like peeling an Onion. There's always more...sigh

I'm sure that you'll finally get to the end tho.

Hmm:


2/9/2009 1:46:21 PM|Milkyway@home|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 2 completed tasks
2/9/2009 1:46:26 PM|Milkyway@home|Scheduler request completed: got 0 new tasks
2/9/2009 1:46:26 PM|Milkyway@home|Message from server: Project is temporarily shut down for maintenance

We've had numerous database problems within the past few days. The one we just fixed minutes ago was innodb log files getting too large due to debugging of the original problems. Problems on top of problems. Hopefully we're ok now.

---

Hmm:


2/9/2009 1:46:21 PM|Milkyway@home|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 2 completed tasks
2/9/2009 1:46:26 PM|Milkyway@home|Scheduler request completed: got 0 new tasks
2/9/2009 1:46:26 PM|Milkyway@home|Message from server: Project is temporarily shut down for maintenance

Yes well, check the status page.

Dave didn't start up the services :P It should be running now.

---

Yes I did -- it's running now.

Yes well, check the status page.

---

It is -- so did you ask him it he plugged it in? <g>

Dave didn't start up the services :P It should be running now.

---

He did a good job fixing the database while i was asleep though :D

I come back, see some messages "oh @(#*&$ it broke again" then check my stuff on milkyway and see it's back working again :) that was nice.

---

He did a good job fixing the database while i was asleep though :D

I come back, see some messages "oh @(#*&$ it broke again" then check my stuff on milkyway and see it's back working again :) that was nice.

Makes up for working all Saturday, that does!

He did a good job fixing the database while i was asleep though :D

Sleep? You got time to SLEEP!?! That's just not good enough! <j/k>

Seriously though, you're both doing a great job keeping on top of this, and I hope you get a trouble-free week this week :)

---

We've had numerous database problems within the past few days.

Really? ;)

But, seriously, well done and thanks for all the hard work sorting it out!

It would seem there is still problems as the site won't load at times & these:

2/9/2009 9:15:36 PM|Milkyway@home|Message from server: No work sent
2/9/2009 9:15:36 PM|Milkyway@home|Message from server: (reached per-CPU limit of 12 tasks)
2/9/2009 10:45:27 PM||Project communication failed: attempting access to reference site
2/9/2009 10:45:28 PM||Access to reference site succeeded - project servers may be temporarily down.
2/9/2009 10:45:31 PM|Milkyway@home|Scheduler request failed: Couldn't connect to server

It comes and goes, 1 min nothing, the next it works.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

It would seem there is still problems as the site won't load at times & these:

2/9/2009 9:15:36 PM|Milkyway@home|Message from server: No work sent
2/9/2009 9:15:36 PM|Milkyway@home|Message from server: (reached per-CPU limit of 12 tasks)
2/9/2009 10:45:27 PM||Project communication failed: attempting access to reference site
2/9/2009 10:45:28 PM||Access to reference site succeeded - project servers may be temporarily down.
2/9/2009 10:45:31 PM|Milkyway@home|Scheduler request failed: Couldn't connect to server

It comes and goes, 1 min nothing, the next it works.

Yeah, I've noticed it too. That, and Firefox sometimes times out on a refresh request. I'm guessing the server's still under some heavy load.

---

Very true
The site can be loaded quickly some times, and others it times out completely. It seems slow ATM.

I guess jedirock is correct, from comments Travis posted when the server/DB crash was in progress but before the servers were shutdown.