Yes, now that you mention it ... :)

---

Sorry, my eye locked onto bite not bit. So that is why people use weird spellings toMakeThePoint.

what does Tom Akethepoint have to do with any of this?

I think he runs the SetiServers during the evenings and on weekends.

---

May this Farce be with You

With a long weekend coming up... I prefer a non-running validator over not being able to up- or download workunits.

http://fragment1.berkeley.edu/~cricket/inr-668-interfaces.html

Anyone else noticed the graph lost its dots the last hour?

I just glanced at some of the other router images [ inr-230, etc ], and some of them show the same data loss. So something major happened an hour ago.

---

<I>So something major happened an hour ago.</I>

I <I>think</I> that something happened at 30 Jun 2005 6:30:10 UTC.

If you look at the server status page, you'll notice that time stamp in the top left corner. And all the graphs you and PhoneAcg detailed seem to have stopped at that particular moment in time, too.

---

<I>So something major happened an hour ago.</I>

I <I>think</I> that something happened at 30 Jun 2005 6:30:10 UTC.

If you look at the server status page, you'll notice that time stamp in the top left corner. And all the graphs you and PhoneAcg detailed seem to have stopped at that particular moment in time, too.

The router graphs [ inr-668, etc ] display berkeley local time. :-)

So there were two error conditions, one at 6:30 UTC, and one at 6:00 PST.

---

So there were two error conditions, one at 6:30 UTC, and one at 6:00 PST.

Ooooooo.

I think I'm going to need a chart of what time system is used where. Meanwhile, I'm getting more coffee.

---

So there were two error conditions, one at 6:30 UTC, and one at 6:00 PST.

Ooooooo.

I think I'm going to need a chart of what time system is used where. Meanwhile, I'm getting more coffee.

Ya, I just started my Mr. Coffee. :-)

BTW: The inr-668 graph seems to have gotten some more dots to use, as the graph is climbing.

:-)

---

The cricket software is being upgraded.

---

BOINC WIKI

cricket has had that notice up for months

---

I see they are still using the old tried and true fix. Kick the hardware, I must.

June 30, 2005 - 17:00 UTC
Last night the upload/download server ran out of processes. This happened because the load was very heavy, which causes adverse effects in apache. When hourly apache restarts were issued (for log rotation), old processes wouldn't die and new ones would fill the process queue. By this morning we had over 7000 httpd processes on the machine! Apparently some apache tuning is in order.
This went unnoticed, though the lack of server status page updates did get noticed. The page gets updated every 10 minutes (along with all kinds of internal-use BOINC status files). Once every few hours the whole system "skips a turn" due to some funny interaction with cron. But occasionally the whole system stops altogether until somebody comes along and "kicks it" (i.e. removes some stale lock files).

So we noticed the status page was stale, "kicked" the whole system and it started up again (temporarily). Everything looked okay, so we went to bed, only to realize the gravity of the problem in the morning (the system was hanging because it would get stuck trying to talk to hosed server).

There was also a 2-hour lab-wide network outage during all this. Not sure what happened there, but that's out of our hands.

---

Red Bull Air Racing

Gas price by zip at Seti

It is almost like, if it wasn't for bad luck they would have no luck at all ...

---