recent woes

In my experience with overheating and main intensive DB server, hardware will be probably totaly dead in a year (first RAM, then disk and at the end a motherboard), at he same time replica server (same hardware, in the same rack) was alive, and alive, ... and good spare for the main server :-)
____________

I'd like more units but I'm grateful for the few I'm getting. You guys keep up the good work and I'll send another case...heh...Thanks!
____________
You talk'n to me?

Temprature inside the cabinets exceeded 48 degrees (we are measuring in Celcius) and many servers shut down on the overheatprotection.

I have to say that for those of us who only have computers at work, where there is a shut down of everything over the weekend, the fact that the weekly outage always falls in the middle of the week means a very reduced window to upload/download. I have 3 big Astropulses that my machine hammered in a great time and finished on Monday evening but they may not report until next Monday.

I know this is a bad time but the 3 day outage hits me like this every week.
I appreciate that work can only be done when people are available but I thought I should point out that my long term results (7 years) are slowly dwindling away.

.... I have a question. I've just looked at the server status page and in the list is db_purge.x86_64. Now, I've also noticed that during the downtimes when the upload / download servers are offline, unlike the other stat lines "Workunits waiting for db purging" and "Results waiting for db purging" never seem to zero out. I'm curious as to why this is. Surely it would make sense that if the db_purge server is up, that the purging zero's out with no new records being added to the queue.

Like I said, just curious.
____________

This entry on the Seti home page is making me smile:

The weekly Seti outage allows for a "focus on science processing." Hmmm.

I feel an urge to giggle hysterically when I read, "On Friday, you may experience connectivity issues as the servers catch up with demand."

On the other hand the tasks of Jeff and Matt et al are no doubt arduous and often thankless and I am grateful for their efforts.

There may be merit in what some have suggested in terms of shutting it all down until ways can be found to make Seti run reliably.


____________

I have tasks ready to upload that will expire in 6 days!

I expect the admins will try and clear the backlog of uploading & reporting tasks before turning on the validator(s). As long as a given result is found when the parent WU goes up for validation, having been reported late makes no difference. To put it another way, the “deadline” can be understood, for all practical purposes, as the earliest moment that a task will be liable to validation—rather than automatic rejection. It’s even possible for a result to be accepted after missing a validator pass: if the validation is unsuccessful (whether due to errors or other missing results) or was inconclusive, resulting in a ‘resend’, it effectively gets a deadline extension to match the replacement tasks.

Anyway, the short version is that I wouldn’t give up on any work until I saw that the corresponding WUs had been validated without it.