Of course after days of failures and only 15 minutes after I post the question I get: 5/18/2007 1:34:07 PM|SETI@home|Scheduler request succeeded

I am receiving the following messages. The main problem seems to be that I cannot report results. I have 6 completed and waiting to report. Any sugggestions?

5/18/2007 1:16:08 PM||Project communication failed: attempting access to reference site
5/18/2007 1:16:10 PM||Access to reference site succeeded - project servers may be temporarily down.
5/18/2007 1:16:12 PM|SETI@home|Scheduler request failed: couldn't connect to server
5/18/2007 1:16:12 PM|SETI@home|Deferring scheduler requests for 1 minutes and 0 seconds
5/18/2007 1:17:13 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
5/18/2007 1:17:13 PM|SETI@home|Reason: To report completed tasks
5/18/2007 1:17:13 PM|SETI@home|Requesting 8640 seconds of new work, and reporting 6 completed tasks

Hi peeps. I've followed most suggestions, and I've found, for whatever reason, cos I'm not a techie person, 'reverting' to the standard app from from an optimised app, gets me downloads, and as units complete, I get a couple more. Sure I have some 'ghosties' but I'm hopeful in time they'll work out.
Regards, Wheelie

Good job! Thank's for the enthusiasm despite all the hazzle; we on our side will not disappoint you. ;)

Sorry to get off topic.

Remember - Everyone has something to contribute. We just have to be willing to keep our minds open and pay attention.

This is all just my opinion. Please consider it and do with it what you will.

Joe

And I knew one of those 9,000 people very, very well, She was My Mother. A copper plaque on the Lunar Lander(Apollo 11, Under the Steps), My Mom did touch up on It, Some places say It's stainless, Don't believe them as stainless steel is expensive and and copper doesn't corrode in a Vacuum.

Actually, there is no rust in space, period.....

---

i have noticed a problem with this renaming the app_info.xml file temporaly, and that is, boinc will still try to launch the seti app but heh just does the FFT and nothing else.. If i have to do this all the time that would mean being up 24/7, No thanks, Im gonna just go the regular route until this issue is seriously fixed...

---

i have noticed a problem with this renaming the app_info.xml file temporaly, and that is, boinc will still try to launch the seti app but heh just does the FFT and nothing else.. If i have to do this all the time that would mean being up 24/7, No thanks, Im gonna just go the regular route until this issue is seriously fixed... (EDIT) Opps i didnt mean for a double post, sorry, by the way the regular route, using the normal SETI Enhanced app and stuff, works fine for me, got WU's and everything. (/EDIT)

---

I am receiving the following messages. The main problem seems to be that I cannot report results. I have 6 completed and waiting to report. Any sugggestions?

For what it's worth, I found that re-booting two of my computers caused BOINC to send and recieve units on both just a few minutes ago...

Sorry to get off topic.

Remember - Everyone has something to contribute. We just have to be willing to keep our minds open and pay attention.

This is all just my opinion. Please consider it and do with it what you will.

Joe

And I knew one of those 9,000 people very, very well, She was My Mother. A copper plaque on the Lunar Lander(Apollo 11, Under the Steps), My Mom did touch up on It, Some places say It's stainless, Don't believe them as stainless steel is expensive and and copper doesn't corrode in a Vacuum.

Actually, there is no rust in space, period.....

Hmmm. You got me thinking (and I did start this subject).

The process that causes rust requires oxygen and hydrogen (water).
You say:

"there is no rust in space, period"

Well, there is an awful lot of ice in space (ice crystals peck at Earth's atmosphere constantly). Ice is water in it's solid form - thus there is hydrogen and oxygen - even in the "vacuum" of space. So to me, at least theoretically, it would be possible to form rust in the vacuum of space. It might take a very long time, but it would happen.

Also, the interior of the International Space Station (ISS) surely has a humidification process to aid in the moisturization of the lungs, mouth, nose and eyes of the astronauts (etc.) - at least. There is air (the human-friendly form - Hydrogen, nitrogen, oxygen, etc) in the interior of the ISS. Therefore rust can occur in the ISS interior environment as well - probably close to the speed at which it happens on Earth.

<<<-EDIT BEGIN->>>

I just found the following:

http://setas-www.larc.nasa.gov/LDEF/index.html
This is an overview of the LDEF (Long Duration Exposure Facility) - a NASA project that was launched into space by space shuttle Challenger in 1984 and retrieved in 1990. It was tasked with collecting information about the exposure of various materials to the space environment. It is quite interesting, though I did not read it all.

http://setas-www.larc.nasa.gov/LDEF/CONTAMINATION/contamination_intro.html
An analysis from the LDEF, this validates that oxidation occurs in space, to the point of deteriorating silicone.
It seems to me that by showing oxidation of one kind or another occurs in space, that oxidation resulting in rust is at least *possible*

<<<-EDIT END->>>

Can someone please validate or challenge my assumptions? I am most interested to know if and where I deviate from reality here.

Thanks,
Joe

---

Hm, another choking in the system?

18.05.2007 03:20:43|SETI@home|Reason: no work from project

I'm running out of work threads again.. lol

At least you -had- some work :)
My computer is "unemployed" since the start of all this :(

---

-=[ Not all who wander are lost ]=-

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!!!

---

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.

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

---

...
And I knew one of those 9,000 people very, very well, She was My Mother. A copper plaque on the Lunar Lander(Apollo 11, Under the Steps), My Mom did touch up on It, Some places say It's stainless, Don't believe them as stainless steel is expensive and and copper doesn't corrode in a Vacuum.

Actually, there is no rust in space, period.....

Depends on your definition of "rust" ... if by "rust" you mean the chemical combination of a metal and oxygen, then there is. http://setas-www.larc.nasa.gov/LDEF/index.html can give you lots of information about this.

C

---

Join Team MacNN

Nevermind, corrected myself, obloslete post.

---

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.. Thank you for keeping us informed. Hopefully things will be up and running soon Hugs QM

- Matt

---

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 ?

---

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