that is good news!

woot, i'm all uploaded and reported! :D
now for new work.

---

Al 300+ WU's have been DL-ed and a new stock has appeared. This happened overnight (The Netherlands.) I've only been out of stock for 1.5 days...

Happy you fixed it all.

Ronald Zaneveld

---

On a serious note, there's a report of a significant number of validate errors on host 5161387. I suspect the old problem of reporting too soon after upload, with everything desparately scrabbling to catch up. Could you run the 'reset validation state' script later today, when the rush has died down, please?

I have just noticed a few bad work units from my other machine 5297346 which is about 30 miles from my main pc! dunno what i have done wrong as the laptops been sat on my desk grrrr!!!

The wierd thing is they are both my machines!

all good work thats been done to get the servers up and running

If you'd used the 'quote' button, you would have been able to keep the emphasis and the clickable link to show Eric the nature of the problem (even if you - quite rightly - want to trim the extraneous stuff):

validate errors on host 5161387

You would also see how to do 5297346, too!

If you'd used the 'quote' button, you would have been able to keep the emphasis and the clickable link to show Eric the nature of the problem (even if you - quite rightly - want to trim the extraneous stuff):

validate errors on host 5161387

You would also see how to do 5297346, too!

Whoops my bad was in the train with no heating with a hangover and the smellest guy sat next ti me!

Wow! Even the block of ice on the GPU is gone this morning! :)

Thanks Everyone!

Martin

Matt's still on board, but we're all a little overworked today, so he may not post tech news today (even though he's probably still working right now).

No worries -- you all have done a fantastic job getting everything up and running again. From the look of things, you had the Perfect Storm of server problems (not to mention A/C failures)... and you have safely brought the project through the storm. As others have said, we are so grateful for the work you all do to keep things running and I'm extremely excited to push ahead with the SETI mission. My PC is happily crunching SETI@home data once again!

---

"That's no moon. It's a space station." -Obi-Wan Kenobi
...If there's a Galactic Empire out there with a Death Star that's about to destroy us all, SETI will find it.

Thanx Seti! Terrific job!

---

rOZZ
Music
Pictures

fyi, downloads are really strugling. will we postpone the server backup (a motherly hint).

---

fyi, downloads are really strugling. will we postpone the server backup (a motherly hint).

Actually, under these circumstances, doing the backup as normal would actually help.

Assuming it's just a normal database backup/compression (and it probably needs it after the last 24 hours), the upload and download servers can continue to run, and clear the backlog of already allocated but not yet downloaded work without any new allocations adding to the load.

(And they'd get a chance to fix

validate errors on host 5161387

while they're at it).

if the traffic is mostly d/l requests, i would agree; but it is probably requests for new work, and that is not going away.

---

validate errors on host 5161387

Or run the script across all hosts, example: 5117170 , as every task legitimately cleared off the plate in advance of backup saves time.

The kitties would like to extend their sincere appreciation to Eric, Matt, and anybody else who helped sort this outage.
All rigs have reported in and are doing well again. Save the i7 920...which had soooooooo much work to report backlogged that I had to suspend crunching to allow the work to download and report. But it is slowly catching up too.

Thanks guys!!

The kitties salute you.

---

"Time is simply the mechanism that keeps everything from happening all at once."

validate errors on host 5161387

Or run the script across all hosts, example: 5117170 , as every task legitimately cleared off the plate in advance of backup saves time.

"Running the script" automatically means "for all workunits in the database".

There is no way on earth that Matt or Eric would have time to manually copy in the IDs of each host affected - nor would we want them to waste their time that way.

But it is helpful to have an example of the sort of problem we're talking about, and further instances to give an idea of how widespread it is.

Was SETI@Home hacked?

Came on this morning and a thing for Viagra popped up.

---

Did this have anything to do with the DDoS attack a day or two ago? Somebody testing the waters???

:/

---

Was SETI@Home hacked?

Came on this morning and a thing for Viagra popped up.

I hate those viagra popups. They are rather annoying.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Matt's still on board, but we're all a little overworked today, so he may not post tech news today (even though he's probably still working right now).

Whatever was done has caused some hiccups on Beta. Check the Beta Q&A.

---

I am getting a strange message
2/24/2010 9:16:14 PM SETI@home Restarting task 11ja07ac.12429.22976.8.10.232_0 using setiathome_enhanced version 603

I am not sure why this task is restarting, but it seems to occure every two hours.

any thoughts?

I am getting a strange message
2/24/2010 9:16:14 PM SETI@home Restarting task 11ja07ac.12429.22976.8.10.232_0 using setiathome_enhanced version 603

I am not sure why this task is restarting, but it seems to occure every two hours.

any thoughts?

Seems to me that the fix may have been a temporary thing. After rebooting my lappie due to a couple of updates I tried to upload a few shorties that had finished and got the following messages which seem to be reminescent of previous messages:

2/24/2010 10:59:35 PM SETI@home Restarting task 08ja07ac.8837.6616.11.10.254_2 using setiathome_enhanced version 603
2/24/2010 10:59:35 PM SETI@home Restarting task 04ja07ac.7248.12752.4.10.146_2 using setiathome_enhanced version 603
2/24/2010 11:45:58 PM SETI@home update requested by user
2/24/2010 11:46:01 PM SETI@home Sending scheduler request: Requested by user.
2/24/2010 11:46:01 PM SETI@home Reporting 9 completed tasks, not requesting new tasks
2/24/2010 11:46:02 PM Project communication failed: attempting access to reference site
2/24/2010 11:46:03 PM Internet access OK - project servers may be temporarily down.
2/24/2010 11:46:06 PM SETI@home Scheduler request failed: Server returned nothing (no headers, no data)

Granted the server seems to be getting a lot of hits, but the question is why the server isn't able to reply to queries.

---