I finally got around to install a later software version, so now I'm up and running again.

That's great! Welcome aboard.

---

I finally got around to install a later software version, so now I'm up and running again.

---

September 11, 2006 - 22:00 UTC
We're back on line, more or less, after the science database crash last Friday. Work is being generated, and the assimilators are catching up on the backlogged results. But we're far from out of the woods.
We aren't quite finished getting the data unloaded from the old (broken) database. There is no data corruption, but we are currently operating on only one half of a RAID 10 mirror. In other words, one more drive failure and the whole database is toast. What happened? The two mirrors are on two separate drive arrays, and one of the two enclosures went belly-up, causing all our headaches this past Friday, and our cautionary measures over the weekend.

The rest of the data should be unloaded within the next 24 hours. Then we have to check the data, and load it onto the new server. Then we check to make sure the data on both databases match. And then we shut down the whole project for a day and migrate all the workunits created and results uploaded since we started this whole project a week ago.

Finally, we turn things over to the new database and start the project back up. If all is well, we'll be completely on the new server and can fully retire the old one.

Meanwhile there is positive news about the data recorder. We haven't been able to take much data with the new multi-beam recorder because of DLT drive problems galore. In an effort to move away from that technology, we successfully implemented and tested using swappable SATA drives to store the data. As of this morning we have all the parts working at Arecibo. Soon we will get the parts ordered/installed/tested up here at the lab. Eventually, instead of shipping data back on forth on tapes, we'll be shipping whole 500GB drives.

---

September 11, 2006
Outage update: Though we moved a bulk of the data onto the new science database server over the weekend, there is still plenty to do before we can start using this new server. In the meantime, we may be able to start creating new work to send out later today.

---

Can someone help me out here, or is it just a temp server problem that will fix itself eventually?

It will fix itself eventually. It might take a couple of days.

Patience is required or you can sign up for other projects to keep your PC busy.

Please read...
No New Work!

From the Seti Technical News:

September 8, 2006 - 22:00 UTC
We are out of work to send out, and probably will be for the whole weekend.

---

I am getting almost the same errors, but without the response from the server as to why no work is sent. I have just downloaded and installed the latest version from the website for the first time since seti-clasic. I used my existing username and password (which worked correctly on the website). Clicking through the tabs I see that it is taking up 0 bytes of disk space, no transfers, no tasks, with SETI@home as the only project.

9/9/2006 10:07:31 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
9/9/2006 10:07:31 AM|SETI@home|Reason: To fetch work
9/9/2006 10:07:31 AM|SETI@home|Requesting 17280 seconds of new work
9/9/2006 10:07:36 AM|SETI@home|Scheduler request succeeded
9/9/2006 10:07:36 AM|SETI@home|No work from project
9/9/2006 10:17:46 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
9/9/2006 10:17:46 AM|SETI@home|Reason: To fetch work
9/9/2006 10:17:46 AM|SETI@home|Requesting 17280 seconds of new work
9/9/2006 10:17:51 AM|SETI@home|Scheduler request succeeded
9/9/2006 10:17:51 AM|SETI@home|No work from project
9/9/2006 10:28:01 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
9/9/2006 10:28:01 AM|SETI@home|Reason: To fetch work
9/9/2006 10:28:01 AM|SETI@home|Requesting 17280 seconds of new work
9/9/2006 10:28:06 AM|SETI@home|Scheduler request succeeded
9/9/2006 10:28:06 AM|SETI@home|No work from project
9/9/2006 10:29:11 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
9/9/2006 10:29:11 AM|SETI@home|Reason: Requested by user
9/9/2006 10:29:11 AM|SETI@home|Requesting 17280 seconds of new work
9/9/2006 10:29:16 AM|SETI@home|Scheduler request succeeded

Can someone help me out here, or is it just a temp server problem that will fix itself eventually?

It seems no work has been done by Boinc since 20 May. I haven't touched the Boinc installation and it ran for some months without any problems before that. The log file shows these messages repeatedly:

2006-08-30 23:48:09 [SETI@home] Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2006-08-30 23:48:09 [SETI@home] Reason: To fetch work
2006-08-30 23:48:09 [SETI@home] Requesting 8640 seconds of new work
2006-08-30 23:48:18 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
2006-08-30 23:48:20 [SETI@home] Message from server: No work sent
2006-08-30 23:48:20 [SETI@home] No work from project
2006-08-30 23:48:24 [SETI@home] Deferring communication with project for 59 minutes and 54 seconds

Navigate to the folder C:\\program files\\boinc\\projects\\setiathome.berkeley.edu and see if you have a file named app_info.xml.
If you do then delete it and try to connect again. It means you were running an optimized version of Boinc and it is no longer supported.
If you do not have that file...then do you run other projects besides Seti? If so you may be in the deficit range and you may "owe" time to the other projects and Boinc is now paying it/them back.
If none of the above...download the newest version of Boinc and install that right over the top of the current version.
Let us know how it goes.

---

Some 4 months ago a new application version came out.
If you are using an optimized application, close Boinc, delete the file called app_info.xml that is in your project directory and start Boinc again.
Once this is done, Boinc will download the new application in order to crunch the new enhanced work units.

It seems no work has been done by Boinc since 20 May. I haven't touched the Boinc installation and it ran for some months without any problems before that. The log file shows these messages repeatedly:

2006-08-30 23:48:09 [SETI@home] Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2006-08-30 23:48:09 [SETI@home] Reason: To fetch work
2006-08-30 23:48:09 [SETI@home] Requesting 8640 seconds of new work
2006-08-30 23:48:18 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
2006-08-30 23:48:20 [SETI@home] Message from server: No work sent
2006-08-30 23:48:20 [SETI@home] No work from project
2006-08-30 23:48:24 [SETI@home] Deferring communication with project for 59 minutes and 54 seconds

---