Well.. No bad news, really. Everything under my domain was working more or less. We did fill the data pipeline directory - an eight terabyte filesystem - with backlogged raw data. I'm only just now implementing my "janitor" scripts that check these files to make sure they have been successfully copied to our off site archives and fully processed by the splitters so we can safely delete our local copies. In the meantime we've been forming a long "delete queue." No big deal, except we were also keeping our db_purge archives on the same filesystem, which meant the db_purger stopped working, which in and of itself is also no big deal, but it's all getting cleaned up now.

- 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

For your attention:
Parse error: syntax error, unexpected T_STRING in /disks/setifiler1/home/boincadm/projects/sah/html/user/host_venue_action.php on line 21
result of summary update the last 3-4 days.

---

Really hate to rain on your parade but...

Client connection stats script (or its connection to the data collection script) is broken... again...

otherwise nice job, Berkeley!

---

.

Hello, from Albany, CA!...

Several new threads in the Forums over the last few days have a common link, an error message that includes a reference to setifiler1

A Forum Search on "setifiler1" will reveal many unusual errors over the last 5 or 6 days, about the same time that many new validate errors have occured. Is this a co-incidence?

[edit]
Thanks for updating the outage messages, how did the changeover from PDT to PST go at the w/e? Keith.
[/edit]

---

Sir Arthur C Clarke 1917-2008