I also get the same Scheduler error and I think It is a major problem and I said to Ned Slider It's something I detest, so the "fix" is not worth My effort as I'd have to do It to 5 PCs. Until It's fixed correctly at Berkeley I'll keep crunching for Rosetta.
"[FIX] For those using optimized SETI app and can't get new work Ned Slider"

5/18/2007 9:35:16 AM|SETI@home|Sending scheduler request: Requested by user
5/18/2007 9:35:16 AM|SETI@home|(not requesting new work or reporting completed tasks)
5/18/2007 9:35:38 AM||Project communication failed: attempting access to reference site
5/18/2007 9:35:40 AM||Access to reference site succeeded - project servers may be temporarily down.
5/18/2007 9:35:42 AM|SETI@home|Scheduler request failed: couldn't connect to server
5/18/2007 9:35:42 AM|SETI@home|Deferring communication 1 min 0 sec, because scheduler request failed

Very nice workaround, works perfectly. Thanks!!!

I had the same issue, but I rebooted two of my boxes and they are now connecting fine. Perhaps an IP or someting has changed somewhere. Anyway, I'm now reporting and downloading without issue.

Rob.

---

Keep getting error messages like this group:

5/19/2007 3:47:59 AM|SETI@home|Scheduler request failed: HTTP internal server error
5/19/2007 3:47:59 AM|SETI@home|Deferring communication for 1 min 0 sec
5/19/2007 3:47:59 AM|SETI@home|Reason: scheduler request failed5/19/2007 3:46:59 AM|SETI@home|Deferring communication for 1 min 0 sec
5/19/2007 3:46:59 AM|SETI@home|Reason: scheduler request failed

5/19/2007 3:47:54 AM|SETI@home|Sending scheduler request: Requested by user
5/19/2007 3:47:59 AM|SETI@home|Scheduler request failed: HTTP internal server error
5/19/2007 3:47:59 AM|SETI@home|Deferring communication for 1 min 0 sec
5/19/2007 3:47:59 AM|SETI@home|Reason: scheduler request failed
5/19/2007 3:49:04 AM|SETI@home|Scheduler request failed: HTTP internal server error
5/19/2007 3:50:09 AM|SETI@home|Deferring communication for 1 min 2 sec
5/19/2007 3:50:09 AM|SETI@home|Reason: scheduler request failed
5/19/2007 3:51:14 AM|SETI@home|Sending scheduler request: Requested by user
5/19/2007 3:51:15 AM||Project communication failed: attempting access to reference site
5/19/2007 3:51:16 AM||Access to reference site succeeded - project servers may be temporarily down.
5/19/2007 3:51:19 AM|SETI@home|Scheduler request failed: server returned nothing (no headers, no data)
5/19/2007 3:51:19 AM|SETI@home|Deferring communication for 2 min 23 sec
5/19/2007 3:51:19 AM|SETI@home|Reason: scheduler request failed
5/19/2007 3:53:44 AM|SETI@home|Sending scheduler request: Requested by user
5/19/2007 3:54:34 AM|SETI@home|Scheduler request failed: HTTP internal server error
5/19/2007 3:54:34 AM|SETI@home|Deferring communication for 17 min 19 sec
5/19/2007 3:54:34 AM|SETI@home|Reason: scheduler request failed

I have shutdown and restarted Boinc and still get these messages.

---

Come and Visit Us at
BBR TeamStarFire


****My 9th year of Seti****A Founding Member of the Original Seti Team Starfire at Broadband Reports.com ****

Hey what about the old machine 'Thumper', the one which conked off and started all this. Only the motherboard is faulty in that machine right ?

If so can't it fixed, i mean now we have time on our hands now with the replacement online but if the old machine can be fixed we'll have more server.

Chip level repairs are possible but if in this case they are not, you can place an AD in the newpapers or somthing or even contact SUN for a new motherboard.

If we can get that machine working again, it would be great and its definitely worth a shot.

What do you think ?

Thumper has already been replaced, and up and running. You can read that on the front page news as well as in some of the other Tech News items here. Its a lot more deeper than I understand, and a lot of it has been explained by Matt pretty much every day he works. Check out some of the other threads, and you'll see. Hope that helps.

Jeremy

---

Keep getting error messages like this group:

5/19/2007 3:47:59 AM|SETI@home|Scheduler request failed: HTTP internal server error
5/19/2007 3:47:59 AM|SETI@home|Deferring communication for 1 min 0 sec
5/19/2007 3:47:59 AM|SETI@home|Reason: scheduler request failed5/19/2007 3:46:59 AM|SETI@home|Deferring communication for 1 min 0 sec
5/19/2007 3:46:59 AM|SETI@home|Reason: scheduler request failed

5/19/2007 3:47:54 AM|SETI@home|Sending scheduler request: Requested by user
5/19/2007 3:47:59 AM|SETI@home|Scheduler request failed: HTTP internal server error
5/19/2007 3:47:59 AM|SETI@home|Deferring communication for 1 min 0 sec
5/19/2007 3:47:59 AM|SETI@home|Reason: scheduler request failed
5/19/2007 3:49:04 AM|SETI@home|Scheduler request failed: HTTP internal server error
5/19/2007 3:50:09 AM|SETI@home|Deferring communication for 1 min 2 sec
5/19/2007 3:50:09 AM|SETI@home|Reason: scheduler request failed
5/19/2007 3:51:14 AM|SETI@home|Sending scheduler request: Requested by user
5/19/2007 3:51:15 AM||Project communication failed: attempting access to reference site
5/19/2007 3:51:16 AM||Access to reference site succeeded - project servers may be temporarily down.
5/19/2007 3:51:19 AM|SETI@home|Scheduler request failed: server returned nothing (no headers, no data)
5/19/2007 3:51:19 AM|SETI@home|Deferring communication for 2 min 23 sec
5/19/2007 3:51:19 AM|SETI@home|Reason: scheduler request failed
5/19/2007 3:53:44 AM|SETI@home|Sending scheduler request: Requested by user
5/19/2007 3:54:34 AM|SETI@home|Scheduler request failed: HTTP internal server error
5/19/2007 3:54:34 AM|SETI@home|Deferring communication for 17 min 19 sec
5/19/2007 3:54:34 AM|SETI@home|Reason: scheduler request failed

I have shutdown and restarted Boinc and still get these messages.

I have phyically rebooted my machines(2 x XP, 2 x linux and 1 Vista), all now download and report. No idea why.

Rob.

---

Hello all,
I have a couple of new questions.

1) "Waiting for memory" on one work-unit in BOINC.

I am running a dual-processor P4 with 1GB of RAM.
In BOINC on the Tasks tab, I always see that one of the work units' status is "Waiting for memory". This occurs even after a reboot. There is actually work being performed on that work unit, but it is significantly lower than the first work unit (16% versus 24%).
Can someone help me figure out what is going on and if there is anything I can do to jump start processing on that unit.

I can help you with this one...

http://setiathome.berkeley.edu/prefs.php?subset=global
Disk and memory usage If you have BOINC ver 5.8 or above.

2) Abandoned work units after reinstalling BOINC.

When I upgraded my version of BOINC a couple of days ago, I had to uninstall the existing version of BOINC first. I made a backup copy of the BOINC directory before uninstalling. I think there is at least one work unit in that old directory and I would rather not abandon it. I tried with all my might to trick BOINC/SAH into processing the old work unit, but I had no luck.
Can someone help me figure out how to put these abandoned work-units back into play?

Thanks!
Joe

The second one I can't realy help with, but for future reference. If you are upgrading BOINC to a higher version, it should be a simple process (no need to un-install first), you should not lose work. If you are going down to a lower version you do need to uninstall the higher version first.

---

Sir Arthur C Clarke 1917-2008

Quick note as I gotta catch a bus..

Wow - what a mess. I think we're in the middle of our biggest outage recovery to date, and it's breaking everything. The good news is we're coming into some newer hardware which we'll get on line to help somehow.

See Eric's thread in the Staff Blog. He's been working overtime getting a new frankenstein machine together to act as another upload/download server and reduce the load on bruno. The scheduling server (galileo) has been choking - I just now moved all that over to bruno as well. So we may retire galileo soon, too. Jeff has been going nuts trying to track down errors in validator/assimilator code so we can get those on line as well. And our old friend "slow feeder query" is back, probably just being aggravated by the heavy load.

Gotta go..

- Matt

For economic reasons the light at the end of the tunnel has been turned off .

Hey what about the old machine 'Thumper', the one which conked off and started all this. Only the motherboard is faulty in that machine right ?

If so can't it fixed, i mean now we have time on our hands now with the replacement online but if the old machine can be fixed we'll have more server.

Chip level repairs are possible but if in this case they are not, you can place an AD in the newpapers or somthing or even contact SUN for a new motherboard.

If we can get that machine working again, it would be great and its definitely worth a shot.

What do you think ?

Thumper has already been replaced, and up and running. You can read that on the front page news as well as in some of the other Tech News items here. Its a lot more deeper than I understand, and a lot of it has been explained by Matt pretty much every day he works. Check out some of the other threads, and you'll see. Hope that helps.

Jeremy

We all know thumper is replaced
but the only thing wrong with it is the "sata controlers"
we got perfectly good working
Ram
Cpu's
mainboard (exept sata)
Harddrive's (from new thumper)
if we can get an alternative way to get at least 1 hard drive going it can make an mean spliter,upload/download server,sceduler
if we cand get old chasis working
get an barebone chassis and put old thumper mem and cpus + HDD's in there (nice replica master science DB)
Just my 2c

Conrad

---

Well, this seems to be the latest of the threads about the recent troubles, and I've had little time to troll through the boards, to find info, so apologies if this is the wrong thread!

19/05/2007 10:33:46 PM|SETI@home|Sending scheduler request: To fetch work
19/05/2007 10:33:46 PM|SETI@home|Requesting 170199 seconds of new work
19/05/2007 10:35:51 PM|SETI@home|Scheduler request failed: HTTP internal server error
19/05/2007 10:35:51 PM|SETI@home|Deferring communication for 28 min 15 sec
19/05/2007 10:35:51 PM|SETI@home|Reason: scheduler request failed

I've been getting no contact with the project for a couple of days now. (Since S@h started sending out WUs after the outage)

Have I missed something?

---

Well, this seems to be the latest of the threads about the recent troubles, and I've had little time to troll through the boards, to find info, so apologies if this is the wrong thread!

19/05/2007 10:33:46 PM|SETI@home|Sending scheduler request: To fetch work
19/05/2007 10:33:46 PM|SETI@home|Requesting 170199 seconds of new work
19/05/2007 10:35:51 PM|SETI@home|Scheduler request failed: HTTP internal server error
19/05/2007 10:35:51 PM|SETI@home|Deferring communication for 28 min 15 sec
19/05/2007 10:35:51 PM|SETI@home|Reason: scheduler request failed

I've been getting no contact with the project for a couple of days now. (Since S@h started sending out WUs after the outage)

Have I missed something?

Yes - you need to be here.

Have I missed something?

Yes, you need to look for Eric's posts in the staff blog, and Richard Haselgrove & the chicken verified workaround ( There is a link to Richard's method in my profile. )

First, if you get the 'incomplete request received' you need to restart Boinc according to Eric.

Also There seems to be a breakage in the way the 'anonymous platform' interacts with the scheduler, please trawl around for Richard Haselgrove's temporary workaround ( There is a link on my profile to his manual method. plus if you understand Richard's method, are on a windows platform running as a service, and are comfortable with batch files in windows - there I've put 2 semi automated methods which work enough to fill a cache, preferably large so as not to require redoing often)

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Have I missed something?

Yes, you need to look for Eric's posts in the staff blog, and Richard Haselgrove & the chicken verified workaround ( There is a link to Richard's method in my profile. )

First, if you get the 'incomplete request received' you need to restart Boinc according to Eric.

Also There seems to be a breakage in the way the 'anonymous platform' interacts with the scheduler, please trawl around for Richard Haselgrove's temporary workaround ( There is a link on my profile to his manual method. plus if you understand Richard's method, are on a windows platform running as a service, and are comfortable with batch files in windows - there I've put 2 semi automated methods which work enough to fill a cache, preferably large so as not to require redoing often)

OMG!

I hadn't looked at my "Results" list in quite a while.

Last time I had that happen, I had to detach from the project, and re-attach.

I'll check out Richard's link.

Thanks, Jason amd Richard :)

---

Well, this seems to be the latest of the threads about the recent troubles, and I've had little time to troll through the boards, to find info, so apologies if this is the wrong thread!

19/05/2007 10:33:46 PM|SETI@home|Sending scheduler request: To fetch work
19/05/2007 10:33:46 PM|SETI@home|Requesting 170199 seconds of new work
19/05/2007 10:35:51 PM|SETI@home|Scheduler request failed: HTTP internal server error
19/05/2007 10:35:51 PM|SETI@home|Deferring communication for 28 min 15 sec
19/05/2007 10:35:51 PM|SETI@home|Reason: scheduler request failed

I've been getting no contact with the project for a couple of days now. (Since S@h started sending out WUs after the outage)

Have I missed something?

I had this exact same error (HTTP internal server error), using the 5.8.11 client. I reset the S@H projects in an attempt to clear the "ghosts" I see mentioned, to no avail.

As a last resort, I uninstalled BOINC, deleted the C:/Program Files/BOINC folder, and downloaded the Beta 5.9.11 client from http://boinc.berkeley.edu/dl/?C=M;O=D

This didn't seem to work at first.....not the same HTTP error, but files still weren't downloading. At this point I had given up, and decided to rejoin my other Projects I had in the past {Rosetta and Einstein). Lo and behold, as soon as WUs started downloading from Rosetta and Einstein, S@H started downloading too! I don't know why it worked, but that's what happened.

If S@H is your only Project, I suggest joining (or rejoining) another Project or two, and see if it jump-starts the S@H WU downloads like it did for me.

Can't hurt, and at the very least your machines will simply be crunching for another worthy Project while S@H is poked and prodded.

I did not have time to read more than about the first 35 responses or so......if this was already suggested elsewhere in the thread, I apologize.

---

Well, this seems to be the latest of the threads about the recent troubles, and I've had little time to troll through the boards, to find info, so apologies if this is the wrong thread!

19/05/2007 10:33:46 PM|SETI@home|Sending scheduler request: To fetch work
19/05/2007 10:33:46 PM|SETI@home|Requesting 170199 seconds of new work
19/05/2007 10:35:51 PM|SETI@home|Scheduler request failed: HTTP internal server error
19/05/2007 10:35:51 PM|SETI@home|Deferring communication for 28 min 15 sec
19/05/2007 10:35:51 PM|SETI@home|Reason: scheduler request failed

I've been getting no contact with the project for a couple of days now. (Since S@h started sending out WUs after the outage)

Have I missed something?

I had this exact same error (HTTP internal server error), using the 5.8.11 client. I reset my projects in an attempt to clear the "ghosts" I see mentioned, to no avail.

As a last resort, I uninstalled BOINC, deleted the C:/Program Files/BOINC folder, and downloaded the Beta 5.9.11 client from http://boinc.berkeley.edu/dl/?C=M;O=D

This didn't seem to work at first.....not the same HTTP error, but files still weren't downloading. At this point I had given up, and decided to rejoin my other Projects I had in the past {Rosetta and Einstein). Lo and behold, as soon as WUs started downloading from Rosetta and Einstein, S@H started downloading too! I don't know why it worked, but that's what happened.

If S@H is your only Project, I suggest joining (or rejoining) another Project or two, and see if it jump-starts the S@H WU downloads like it did for me.

Can't hurt, and at the very least your machines will simply be crunching for another worthy Project while S@H is poked and prodded.

I did not have time to read more than about the first 35 responses or so......if this was already suggested elsewhere in the thread, I apologize.

I think the significant fact is that you deleted the C:/Program Files/BOINC folder. In doing so, you deleted your optimised application, and with it the app_info.xml file that's causing all the trouble.

If you decide to re-optimise your new installation, you should download the revised v2.2B Chicken app: the original v2.2 version you were running before had bugs which damaged the science (and gave you zero credits, if that's what you're looking for).

5/19/2007 10:27:33 PM|SETI@home|Scheduler RPC succeeded [server version 509]
5/19/2007 10:27:33 PM|SETI@home|Message from server: No work sent
5/19/2007 10:27:33 PM|SETI@home|Message from server: (reached daily quota of 2 results)
5/19/2007 10:27:33 PM|SETI@home|Deferring communication for 18 hr 19 min 15 sec
5/19/2007 10:27:33 PM|SETI@home|Reason: requested by project
5/19/2007 10:27:33 PM|SETI@home|Deferring communication for 1 min 0 sec
5/19/2007 10:27:33 PM|SETI@home|Reason: no work from project

I have used the work around on one machine it downloaded 18 WUs. The other machine did the work around and I received 2 WUs after they finished I have been getting the above messages.

General pref xml exists and has the correct information in it.

---

Come and Visit Us at
BBR TeamStarFire


****My 9th year of Seti****A Founding Member of the Original Seti Team Starfire at Broadband Reports.com ****

...
I have used the work around on one machine it downloaded 18 WUs. The other machine did the work around and I received 2 WUs after they finished I have been getting the above messages

doh, must've got a few ghosts on that one :D[before the workaround]. It'll reset at midnight ( Either UTC or PDT, I'm not sure )

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

I am sorry but I dont understand all this computer geek mumbo jumbo.

Can someone please tell me in simple english why SETI is not downloading any work from the project?

Thanks.

...
I have used the work around on one machine it downloaded 18 WUs. The other machine did the work around and I received 2 WUs after they finished I have been getting the above messages

doh, must've got a few ghosts on that one :D[before the workaround]. It'll reset at midnight ( Either UTC or PDT, I'm not sure )

PDT

But he shouldn't have to wait that long. Do the workround, do a manual update (overrules the 18-hour deferral), and the finished WUs should report. Assuming they report 'success', quota will be increased: another update should then get more work.

Edit - computers are hidden, so can't confirm the details of the above.

I am sorry but I dont understand all this computer geek mumbo jumbo.

Can someone please tell me in simple english why SETI is not downloading any work from the project?

Thanks.

The Berkeley (project) servers are broken.

From the looks of the front page on the seti site the project is now up and running again? but I seem not to be getting any work. I have disconnected from the project and reconnected again and that at least got seti "to ask for some more work units" but im getting nothing and don't understand what the messages mean. The following is happening after a restart of boinc...

19/05/2007 14:52:07||Starting BOINC client version 5.8.16 for windows_intelx86
19/05/2007 14:52:07||log flags: task, file_xfer, sched_ops
19/05/2007 14:52:07||Libraries: libcurl/7.16.0 OpenSSL/0.9.8a zlib/1.2.3
19/05/2007 14:52:07||Data directory: C:\\Program Files\\BOINC
19/05/2007 14:52:07||Processor: 2 AuthenticAMD AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ [x86 Family 15 Model 75 Stepping 2] [fpu tsc pae nx sse sse2 3dnow mmx]
19/05/2007 14:52:07||Memory: 2.00 GB physical, 3.85 GB virtual
19/05/2007 14:52:07||Disk: 139.72 GB total, 89.78 GB free
19/05/2007 14:52:08|rosetta@home|URL: http://boinc.bakerlab.org/rosetta/; Computer ID: 422594; location: home; project prefs: default
19/05/2007 14:52:08|climateprediction.net|URL: http://climateprediction.net/; Computer ID: 550675; location: home; project prefs: default
19/05/2007 14:52:08|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 3104141; location: home; project prefs: default
19/05/2007 14:52:08||General prefs: from climateprediction.net (last modified 2007-05-17 11:51:09)
19/05/2007 14:52:08||Host location: home
19/05/2007 14:52:08||General prefs: no separate prefs for home; using your defaults
19/05/2007 14:52:08||Reading preferences override file
19/05/2007 14:52:08|climateprediction.net|Restarting task hadcm3pbb_c3sf_05838858_1 using hadcm3 version 515
19/05/2007 14:52:08|rosetta@home|Restarting task 1gidA_BOINC_MG_CHAINBREAK5_ALTSECSTRUCT_RNA_ABINITIO_RNA_CONTACT_RNA_LONG_RANGE_CONTACT_RNA_SASA-1gidA-_1735_14143_0 using rosetta version 564
19/05/2007 14:53:03|SETI@home|Sending scheduler request: To fetch work
19/05/2007 14:53:03|SETI@home|Requesting 3026 seconds of new work
19/05/2007 14:53:04||Project communication failed: attempting access to reference site
19/05/2007 14:53:05||Access to reference site succeeded - project servers may be temporarily down.
19/05/2007 14:53:08|SETI@home|Scheduler request failed: server returned nothing (no headers, no data)
19/05/2007 14:53:08|SETI@home|Deferring communication for 4 min 37 sec
19/05/2007 14:53:08|SETI@home|Reason: scheduler request failed

---

Resistence is futile! {evil cackle}