The weekend was a little bumpy. The mysql database was showing signs of trouble Saturday. Eric was the only one paying attention at the time, so he restarted the database. Everything seemed fine, except he made some posts of the forum and then they all disappeared. This is still a mystery (the cause, the exact effects, and if it still a problem). Eric is trying to recreate and diagnose.

But we were still getting web scraped to death. I played a gig Saturday night, getting home around 1:30am. I noticed the lingering problems at that point and blocked a couple more IP addresses and kicked off the long queries. Things more or less recovered on their own after that (except for the validators, which I fixed in the morning).

So this is getting to be a regular problem, which I partially addressed this morning. I dug through the php code and quickly figured out how to get a couple of the offensive long queries to point at the replica database. This seemed to be quite helpful, but the replica is still behind due to the other problems mentioned above. So people are seeing about a day in the past when checking out their current results on our web site. It's confusing, but not the worst tragedy in the world, and it's a problem that will correct itself shortly. It'll all be caught up after the outage tomorrow.

To keep things interesting, we seem to be in a middle of a spate of weird workunits - ones where the data isn't kosher and therefore returning quickly. Eric is also on top of that one. In the meantime, our outgoing traffic is a bit pegged.

Less than three weeks until the anniversary. I'm getting my powerpoint together now. And I couldn't think of a worthy thread title theme this month, so how about apt titles for a change?

- 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

Would it be possible to divide the data into two parts. One part external IP address may access and the other part blocked from all external access?

---

Thanks for the update Matt.

And THANKS for the teams vigilance over the weekend.

May the deluge ease off and give you all a well earned breather.

Thank you for your hard work over the weekend.

To keep things interesting, we seem to be in a middle of a spate of weird workunits - ones where the data isn't kosher. and therefore returning quickly.

Out of interest was this a AP or MB tape and what was the problem with the data had it skipped a process before it went through the splitters? Thanks in advance.

---

How come tapes of 0.00GB in sizes apear in the splitting queue from time to time? E.g tape 31mr09aa is at the bottom of the current splitter queue

---

The weekend was a little bumpy. The mysql database was showing signs of trouble Saturday. Eric was the only one paying attention at the time, so he restarted the database. Everything seemed fine, except he made some posts of the forum and then they all disappeared. This is still a mystery (the cause, the exact effects, and if it still a problem). Eric is trying to recreate and diagnose.

Well the forum went down again right before the posts disappeared. Perhaps those posts were never backed up and the forum returned to the state it was in right before the scheduled outage. The glorified spam thread in the Cafe would support this.

To keep things interesting, we seem to be in a middle of a spate of weird workunits - ones where the data isn't kosher and therefore returning quickly. Eric is also on top of that one. In the meantime, our outgoing traffic is a bit pegged.

Three straight days of MB VLARs at BETA.

---

me@rescam.org

How about "Control in the midst of Khaos!" As in Get Smart's Khaos.. ;)

---

Savoir-Faire is everywhere!
The T1 Trust, T1 Class 4-4-4-4 #5550, America's First HST

Phew, nice to see those WUs return after going AWOL; congratulations for all your hard work, you clever people.

---

Hi, I dont like to say this but there is a minor problem with the team lists. It expires around the 6000 place mark. I am worried this may be a symptom of a more important database problem.

---