The following has worked for me on three systems - two late version 5.8 BOINC, and a 5.3.12.tx. All were service installs, running appropriate Chicken 2.2B, and had run completely dry.

Recipe:

Rename app_info.xml so it won't be recognised
Restart BOINC (service)
Update SETI - may not get through first time, but keep trying
Restore app_info.xml to original name
Wait until all transfers have finished
Restart BOINC (service)

Outcome - decent sized cache (if I haven't nabbed them all already, LOL), still running optimised, time to open a beer.

That stops the client getting it's version and it's app name. The app name in mine is setiathome_enhanced. There has to be a clue in there somewhere.

---

Same here. I sure hope someone will find a cure for this anti-KWSN-flu.. ;)

It's not just bird flu. Same problem with alexkan's application for macs.

The app_info.xml file is used to define many different things. Specifying custom applications is only one of many. So anyone who is using app_info.xml at all will probably be having this problem.

---

Dublin, California
Team: SETI.USA

The following has worked for me on three systems - two late version 5.8 BOINC, and a 5.3.12.tx. All were service installs, running appropriate Chicken 2.2B, and had run completely dry.

Recipe:

Rename app_info.xml so it won't be recognised
Restart BOINC (service)
Update SETI - may not get through first time, but keep trying
Restore app_info.xml to original name
Wait until all transfers have finished
Restart BOINC (service)

Outcome - decent sized cache (if I haven't nabbed them all already, LOL), still running optimised, time to open a beer.

That stops the client getting it's version and it's app name. The app name in mine is setiathome_enhanced. There has to be a clue in there somewhere.

@ Rodney Pont

Under my Tasks Tab in BOINC Manager; I see my current SETI@Home WU as:

"SETI@home setiathome_enhanced 5.15 15mr05aa.455.30658.148584.3.122_0 - (with crunch time, etc...)"

So, all is well... 5.15 is Enhanced SETI under the Stock Unoptimized Application. I see no problem; am I missing something?


Sincerely,

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

By temporary renaming app_info.xml I - like many others - retrieved my many ghost units.

I used the optimized application for a while - everything okay - except that I did not get new work in the "normal" way. Again, I got the error message: HTTP internal server error.

Out of curiosity I removed the optimized app. I was at once connected to the server and got new work.

Upload is fine, too. I therefore conclude that even if download is still having bandwidth problems, up/download is actually working as long as I do not use an optimized application.

PS: I just wonder where the seti_enhanced 5.17 work units have gone. I only get seti_enhanced 5.15 - thought they were a little out of date.

---

Kind regards
Kirsten

By temporary renaming app_info.xml I - like many others - retrieved many ghost units.

I used the optimized application for a while - everything okay - except that I did not get new work in the "normal" way. Again, I got the error message: HTTP internal server error.

Out of curiosity I removed the optimized app. I was at once connected to the server and got new work.

Upload is fine, too. I therefore conclude that even if download is still having bandwidth problems, up/download is actually working as long as I do not use an optimized application.

PS: I just wonder where the seti_enhanced 5.17 work units have gone. I only get seti_enhanced 5.15 - thought they were a little out of date.

The "5.17" is a "dummy" number input by the Chicken App Staff. It is treated as a "generic" to allow the Optimized App to report in... The Validating System treats "5.17" as 5.15 - the current Enhanced WUs.


Sincerely,

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

PS: I just wonder where the seti_enhanced 5.17 work units have gone. I only get seti_enhanced 5.15 - thought they were a little out of date.

The "5.17" is a "dummy" number input by the Chicken App Staff. It is treated as a "generic" to allow the Optimized App to report in... The Validating System treats "5.17" as 5.15 - the current Enhanced WUs.


Sincerely,

Okay, my mistake.

---

Kind regards
Kirsten

PS: I just wonder where the seti_enhanced 5.17 work units have gone. I only get seti_enhanced 5.15 - thought they were a little out of date.

With Linux I even get 5.12 workunits now the moment I 'disable' the app_info.xml...


Greetings,
Sander

---

Unfortunately most of us are still unable to even contact the Scheduler, making getting work or reporting it impossible.

---

Grant
Darwin NT

Unfortuately most of us are still unable to even contact the Scheduler, making getting work impossible.

I've had only one retry when I reported the results on my Intel host earlier today. What messages are you getting when you try? Have you tried a full reboot?

Edit: I'm off to watch SG-1 / SGA... be back in about 2 hours...

Unfortunately most of us are still unable to even contact the Scheduler, making getting work or reporting it impossible.

Have you seen the news on the front page:

May 18, 2007
If your BOINC client is not able to upload to or download from the SETI@Home servers, look for the message Message from Server: Incomplete request received in the BOINC Manager messages area. If you see that message, stopping and restarting your BOINC client should fix the problem.

---

Kind regards
Kirsten

What messages are you getting when you try?

19/05/2007 9:03:49|SETI@home|Scheduler request failed: couldn't connect to server
19/05/2007 9:04:23|SETI@home|[file_xfer] Temporarily failed upload of 14fe05aa.3729.29521.792316.3.28_0_0: http error
19/05/2007 9:05:15|SETI@home|Scheduler request failed: couldn't connect to server
19/05/2007 9:06:16|SETI@home|[file_xfer] Temporarily failed upload of 14fe05aa.3729.29521.792316.3.27_0_0: http error
19/05/2007 9:07:42|SETI@home|Scheduler request failed: failed sending data to the peer

Have you tried a full reboot?

Yep.

---

Grant
Darwin NT

Unfortunately most of us are still unable to even contact the Scheduler, making getting work or reporting it impossible.

Have you seen the news on the front page:

Yep.

---

Grant
Darwin NT

read this one ? --->

http://setiathome.berkeley.edu/forum_thread.php?id=39484&nowrap=true#570723

Doing so would ease the pain a bit ... at least it would stop messing with the app_info ...

Why the update to the server software in the first place ? not enough trouble at all ?

Grrr....

---

Join BOINC United now!

Modified Instruction Set...
Disabling Optimized Application(s) for Dummies. (Like me... ;-D )



Step 9: Set SETI@Home to "No New Tasks".

Step 10: "Suspend" SETI@Home and Exit BOINC.

Step 11: Rename the "app_info-disabled.xml" to "app_info.xml".

Step 12: Restart BOINC and set SETI@Home to "Allow New Tasks"

Step 13: Reset ALL other Projects to "Allow New Tasks", and "Resume" them.

Step 14: If all works as expected/planned; delete the "Backup Folder" on Desktop.


OK - For now, I'm choosing to remain where I'm at... I went from Step 8 to Step 13 in the Modified List, above. I will be waiting for Eric, Matt, and crew to finish debugging, repairing, and whatever else is going on to restabilize SETI@Home. All of my other Projects are "Resume"-ed.

Special thanks to Richard Haselgrove, (for the original Modification Instructions), and Zombie67 for all of the assistance they gave to all of us. 8-D


Sincerely,

Well I tried all the steps including those from 9 and after restarting boinc the previously successful downloaded seti files disappeared from the directory into thin air. So alas it looks like operation with the chicken app is not possible and will have to run the stock version until another fix comes along.

---

And then after a couple of dozen attemps over the last couple of hours, it finally does contact the Scheduler & downloads some Work Units.
Maybe i should've posted it couldn't contact the Scheduler earlier?
Of course now it will no longer upload the completed results...
*repeatedly bangs head on desk*


I've got enough work for a couple of days now, so will disable network access for a day or 2. Give others a chance of getting through.

---

Grant
Darwin NT

Well I tried all the steps including those from 9 and after restarting boinc the previously successful downloaded seti files disappeared from the directory into thin air. So alas it looks like operation with the chicken app is not possible and will have to run the stock version until another fix comes along.

The original recipe was tested and endorsed by The Great Chicken himself (Simon's post here), so I would say that it is possible.

With respect, I would suggest that TimeLord's instructions are over-complicated and over-cautious: and I would disagree with some of them (Don't allow new tasks at step 12, when running in optimised mode). Perhaps one last try with the original brew?

I don't understand why this work around keeps on using the optimized app even when the app_info file is renamed. Without the app_info file present the system should download and use the Seti stock app. At least that is my understanding. Can someone enlighten me?

---

Boinc....Boinc....Boinc....Boinc....

Well I tried all the steps including those from 9 and after restarting boinc the previously successful downloaded seti files disappeared from the directory into thin air. So alas it looks like operation with the chicken app is not possible and will have to run the stock version until another fix comes along.

The original recipe was tested and endorsed by The Great Chicken himself (Simon's post here), so I would say that it is possible.

With respect, I would suggest that TimeLord's instructions are over-complicated and over-cautious: and I would disagree with some of them (Don't allow new tasks at step 12, when running in optimised mode). Perhaps one last try with the original brew?

OOPS - Thanks for the catch on # 12... Following the creation of the list; it was discovered that at present Optimized Apps aren't allowing the Download of WUs at all... So, YES, absolutely:


Step 12: Restart BOINC and leave SETI@Home at "No New Tasks".


Thanks again, Richard... As for the "complicated" - For those with ADD, (like myself), the Step by Step really helps. (Like when learning Algebra for the first time ever... Show ALL work. That's how my mind works - I absolutely need the complete list of things; no omissions.


Sincerely,

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

I don't understand why this work around keeps on using the optimized app even when the app_info file is renamed. Without the app_info file present the system should download and use the Seti stock app. At least that is my understanding. Can someone enlighten me?

Two cases.

1) Existing work in the cache, downloaded while the app_info.xml is in operation.
I <think> this is permanently bound to the optimised app when it's downloaded: a persistent entry in client_state.xml. So it goes on being crunched by the optimised app as before - unaffected by the change in app_info.

2) New work downloaded during the 'trick'
Yes, a new copy of the stock app is downloaded alongside the new work, and the new work will be crunched using it (non-optimised) if you stop my original recipe after step 3.

But it's been known for a long time that you can install the Chicken apps while you have work in the cache, and that even part-crunched WUs will be worked by the optimised app during the second half of their run. So steps 4-6 of my original recipe (reinstating app_info, and restarting BOINC) switches optimisation back on, including for the new WUs.

I suppose you just have to be careful that none of the actual Chicken application files get deleted or moved during the process?

Well I tried all the steps including those from 9 and after restarting boinc the previously successful downloaded seti files disappeared from the directory into thin air. So alas it looks like operation with the chicken app is not possible and will have to run the stock version until another fix comes along.

The original recipe was tested and endorsed by The Great Chicken himself (Simon's post here), so I would say that it is possible.

With respect, I would suggest that TimeLord's instructions are over-complicated and over-cautious: and I would disagree with some of them (Don't allow new tasks at step 12, when running in optimised mode). Perhaps one last try with the original brew?

Thanks and got it to work with the great chicken, very very important point, if you had 5.9.10 upgrade to 5.9.11. Will try and see if allow new tasks works.