@ Richard, Jason Gee, Simon, Joe, and anyone else that feels like it (LOL)

Perhaps a good idea is to automate a batch file for different common platforms like what Jason did?

@ Richard, Jason Gee, Simon, Joe, and anyone else that feels like it (LOL)

Perhaps a good idea is to automate a batch file for different common platforms like what Jason did?

Not tonight, thanks! (approaching 2 a.m.....)

But it's a good idea. I think it might be possible to expand on Jason's model, by using BOINCCMD to automate the allow work/update steps in the first half, and the no new work step in the second half.

It must be getting close to locking-up time in Berkeley, and Eric hasn't blogged that he's found any solution yet: so we're probably stuck with the present situation through the weekend at least. Go for it.

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?

Thanks Richard..........
I have also discovered that if you leave the app_info file renamed all work that is downloaded will be crunched by the optimized app and comms with Berkekey will be normal as before the infamous system crash on May 1.

[edit]Also the only executable file in the setiathome.berkeley.edu folder is the KWSN optimized exe. Looks like it did not download the stock app.[/edit]

---

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

@ Richard, Jason Gee, Simon, Joe, and anyone else that feels like it (LOL)

Perhaps a good idea is to automate a batch file for different common platforms like what Jason did?

Not tonight, thanks! (approaching 2 a.m.....)

But it's a good idea. I think it might be possible to expand on Jason's model, by using BOINCCMD to automate the allow work/update steps in the first half, and the no new work step in the second half.

It must be getting close to locking-up time in Berkeley, and Eric hasn't blogged that he's found any solution yet: so we're probably stuck with the present situation through the weekend at least. Go for it.

I hear ya on the time. I've barely had a chance to read all this stuff, and am watching Atlantis right now...

Get some sleep...and thanks to you and everyone who helped identify what was going on...

I've changed my app_info on both my computers now and have got new

work on both. All i did was stop Boinc edit the app_info to

this: app_info.xml.old then restarted.

No problems.

Edit/ By the way it didn't download a new app still using chicken's.

Edit No.2/ Just U/L 2 results & reported. ;)

---

And do we have nay new input on why the server won't give us new work when we're optimizing??

It's a damned conspiracy, I tell you!!!!

---

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

And do we have nay new input on why the server won't give us new work when we're optimizing??

It's a damned conspiracy, I tell you!!!!

---

OK. I'm officially confused - this one has me stumped (and more than a little worried).

Here is my log since I restarted the client following the workaround. Apologies for the length, but you need to see all of it...

18/05/2007 23:38:27||Starting BOINC client version 5.8.16 for windows_intelx86
18/05/2007 23:38:27||log flags: task, file_xfer, sched_ops
18/05/2007 23:38:27||Libraries: libcurl/7.16.0 OpenSSL/0.9.8a zlib/1.2.3
18/05/2007 23:38:27||Executing as a daemon
18/05/2007 23:38:27||Data directory: C:\\Program Files\\BOINC
18/05/2007 23:38:27||BOINC is running as a service and as a non-system user.
18/05/2007 23:38:27||No application graphics will be available.
18/05/2007 23:38:27|SETI@home|Found app_info.xml; using anonymous platform
18/05/2007 23:38:27||Processor: 2 GenuineIntel Genuine Intel(R) CPU T2400 @ 1.83GHz [x86 Family 6 Model 14 Stepping 8] [fpu tsc sse sse2 mmx]
18/05/2007 23:38:27||Memory: 503.36 MB physical, 1.20 GB virtual
18/05/2007 23:38:27||Disk: 55.89 GB total, 40.15 GB free
18/05/2007 23:38:27|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 3035794; location: work; project prefs: default
18/05/2007 23:38:27||General prefs: from SETI@home (last modified 2007-04-10 17:39:40)
18/05/2007 23:38:27||Host location: work
18/05/2007 23:38:27||General prefs: no separate prefs for work; using your defaults
18/05/2007 23:38:28|SETI@home|Restarting task 05mr05aa.27245.32960.978394.3.69_3 using setiathome_enhanced version 515
18/05/2007 23:38:28|SETI@home|Restarting task 05mr05aa.27245.32960.978394.3.71_3 using setiathome_enhanced version 515
19/05/2007 01:26:04|SETI@home|Computation for task 05mr05aa.27245.32960.978394.3.69_3 finished
19/05/2007 01:26:04|SETI@home|Starting 04mr05ab.17213.16384.884652.3.184_3
19/05/2007 01:26:04|SETI@home|Starting task 04mr05ab.17213.16384.884652.3.184_3 using setiathome_enhanced version 515
19/05/2007 01:26:07|SETI@home|[file_xfer] Started upload of file 05mr05aa.27245.32960.978394.3.69_3_0
19/05/2007 01:26:25|SETI@home|[file_xfer] Finished upload of file 05mr05aa.27245.32960.978394.3.69_3_0
19/05/2007 01:26:25|SETI@home|[file_xfer] Throughput 3315 bytes/sec
19/05/2007 01:26:43|SETI@home|Computation for task 05mr05aa.27245.32960.978394.3.71_3 finished
19/05/2007 01:26:43|SETI@home|Starting 29ja04ab.27703.9697.254826.3.105_4
19/05/2007 01:26:43|SETI@home|Starting task 29ja04ab.27703.9697.254826.3.105_4 using setiathome_enhanced version 515
19/05/2007 01:26:45|SETI@home|[file_xfer] Started upload of file 05mr05aa.27245.32960.978394.3.71_3_0
19/05/2007 01:30:27||Project communication failed: attempting access to reference site
19/05/2007 01:30:27|SETI@home|[file_xfer] Temporarily failed upload of 05mr05aa.27245.32960.978394.3.71_3_0: http error
19/05/2007 01:30:27|SETI@home|Backing off 1 min 0 sec on upload of file 05mr05aa.27245.32960.978394.3.71_3_0
19/05/2007 01:30:29||Access to reference site succeeded - project servers may be temporarily down.
19/05/2007 01:31:28|SETI@home|[file_xfer] Started upload of file 05mr05aa.27245.32960.978394.3.71_3_0
19/05/2007 01:31:33|SETI@home|[file_xfer] Finished upload of file 05mr05aa.27245.32960.978394.3.71_3_0
19/05/2007 01:31:33|SETI@home|[file_xfer] Throughput 16157 bytes/sec
19/05/2007 03:44:38|SETI@home|Computation for task 29ja04ab.27703.9697.254826.3.105_4 finished
19/05/2007 03:44:38|SETI@home|Starting 29ja04ab.27703.9697.254826.3.129_4
19/05/2007 03:44:38|SETI@home|Starting task 29ja04ab.27703.9697.254826.3.129_4 using setiathome_enhanced version 515
19/05/2007 03:44:40|SETI@home|[file_xfer] Started upload of file 29ja04ab.27703.9697.254826.3.105_4_0
19/05/2007 03:45:18||Project communication failed: attempting access to reference site
19/05/2007 03:45:18|SETI@home|[file_xfer] Temporarily failed upload of 29ja04ab.27703.9697.254826.3.105_4_0: http error
19/05/2007 03:45:18|SETI@home|Backing off 1 min 0 sec on upload of file 29ja04ab.27703.9697.254826.3.105_4_0
19/05/2007 03:45:20||Access to reference site succeeded - project servers may be temporarily down.
19/05/2007 03:46:18|SETI@home|[file_xfer] Started upload of file 29ja04ab.27703.9697.254826.3.105_4_0
19/05/2007 03:46:43||Project communication failed: attempting access to reference site
19/05/2007 03:46:43|SETI@home|[file_xfer] Temporarily failed upload of 29ja04ab.27703.9697.254826.3.105_4_0: http error
19/05/2007 03:46:43|SETI@home|Backing off 1 min 0 sec on upload of file 29ja04ab.27703.9697.254826.3.105_4_0
19/05/2007 03:46:45||Access to reference site succeeded - project servers may be temporarily down.
19/05/2007 03:47:43|SETI@home|[file_xfer] Started upload of file 29ja04ab.27703.9697.254826.3.105_4_0
19/05/2007 03:48:09|SETI@home|Computation for task 04mr05ab.17213.16384.884652.3.184_3 finished
19/05/2007 03:48:09|SETI@home|Starting 05mr05aa.27245.32960.978394.3.145_3
19/05/2007 03:48:09|SETI@home|Starting task 05mr05aa.27245.32960.978394.3.145_3 using setiathome_enhanced version 515
19/05/2007 03:48:11|SETI@home|[file_xfer] Started upload of file 04mr05ab.17213.16384.884652.3.184_3_0
19/05/2007 03:48:31|SETI@home|[file_xfer] Finished upload of file 29ja04ab.27703.9697.254826.3.105_4_0
19/05/2007 03:48:31|SETI@home|[file_xfer] Throughput 695 bytes/sec
19/05/2007 03:48:46|SETI@home|[file_xfer] Finished upload of file 04mr05ab.17213.16384.884652.3.184_3_0
19/05/2007 03:48:46|SETI@home|[file_xfer] Throughput 2344 bytes/sec
19/05/2007 06:01:46|SETI@home|Computation for task 29ja04ab.27703.9697.254826.3.129_4 finished
19/05/2007 06:01:46|SETI@home|Starting 05mr05aa.27245.32960.978394.3.168_3
19/05/2007 06:01:46|SETI@home|Starting task 05mr05aa.27245.32960.978394.3.168_3 using setiathome_enhanced version 515
19/05/2007 06:01:49|SETI@home|[file_xfer] Started upload of file 29ja04ab.27703.9697.254826.3.129_4_0
19/05/2007 06:02:38|SETI@home|[file_xfer] Finished upload of file 29ja04ab.27703.9697.254826.3.129_4_0
19/05/2007 06:02:38|SETI@home|[file_xfer] Throughput 746 bytes/sec
19/05/2007 06:09:15|SETI@home|Computation for task 05mr05aa.27245.32960.978394.3.145_3 finished
19/05/2007 06:09:15|SETI@home|Starting 04mr05ab.17213.16432.559642.3.5_3
19/05/2007 06:09:15|SETI@home|Starting task 04mr05ab.17213.16432.559642.3.5_3 using setiathome_enhanced version 515
19/05/2007 06:09:17|SETI@home|[file_xfer] Started upload of file 05mr05aa.27245.32960.978394.3.145_3_0
19/05/2007 06:09:23|SETI@home|[file_xfer] Finished upload of file 05mr05aa.27245.32960.978394.3.145_3_0
19/05/2007 06:09:23|SETI@home|[file_xfer] Throughput 11275 bytes/sec
19/05/2007 06:47:18|SETI@home|Sending scheduler request: Requested by user
19/05/2007 06:47:18|SETI@home|Reporting 6 tasks
19/05/2007 06:47:23|SETI@home|Scheduler RPC succeeded [server version 509]
19/05/2007 06:47:23|SETI@home|Deferring communication for 11 sec
19/05/2007 06:47:23|SETI@home|Reason: requested by project

Note: I have 'No new work set' and the only scheduler contact was at 06:47 UTC.

Okay. Now explain this...

http://setiathome.berkeley.edu/results.php?userid=227035

Where the hell did the WU on the 19th come from - who requested them and why? Can they be related to the failed uploads that worked on automatic retries (while I was dreaming of a trouble-free Seti experience)?

---

Note: I have 'No new work set' and the only scheduler contact was at 06:47 UTC.

Okay. Now explain this...


Where the hell did the WU on the 19th come from - who requested them and why? Can they be related to the failed uploads that worked on automatic retries (while I was dreaming of a trouble-free Seti experience)?

Make sure you're not confusing the SENT column with the Reported/Deadline column... or that you're not accidentally looking at the Celeron instead of the T2400...

Bugger! You're right - FUD prevails and I start seeing major issues when I should know better!!

It does flag up the need to visit my parents and remove the optimised app - it's clearly repeat requesting work (it usually only has 1 or 2 in progress) which are not getting to the client...

---

Have got units on both the Mac and the PC. MAc ws easier than PC. Only had to change app_info.xml name, no problems with enanced application.

PC, had all the hassle as mentioned above. I don't mind doing this but I only have two machines, thank god. Any one like Batman or MSattler good luck, you have our deepest sympathies.

Hi folks,

to clear up a common misconception: the optimized apps have nothing at all to do with the current problem. All transfers are handled by BOINC itself, the science apps only crunch what BOINC fetches for them.

The current problem lies within the anonymous platform mechanism and app_info.xml, the associated settings file. Somehow, the scheduler is erroring out when such a file is present, no matter what application you have in there. Try making an app_info.xml containing the stock app and see for yourself ;o)

Also, I've noticed something else that maybe points to a probable cause for our trouble - as at least one other person noticed, I can no longer grab work at all with my 64-bit BOINC client, no matter whether I delete/rename app_info.xml or not.

The specific error message looks like this -

2007-05-18 15:03:44 [SETI@home] Sending scheduler request: To report completed tasks
2007-05-18 15:03:44 [SETI@home] Requesting 259200 seconds of new work, and reporting 18 completed tasks
2007-05-18 15:04:19 [SETI@home] Scheduler RPC succeeded [server version 509]
2007-05-18 15:04:19 [SETI@home] Message from server: platform 'x86_64-pc-linux-gnu' not found
2007-05-18 15:04:19 [SETI@home] Deferring communication for 1 days 0 hr 0 min 0 sec
2007-05-18 15:04:19 [SETI@home] Reason: requested by project

which repeats as often as it tries to grab new work and actually gets through to the scheduler. It can't even report its work.

So - it really seems like it's a problem with ANY non-standard platform, be it "anonymous" or, like here, "x86_64-pc-linux-gnu". I also tried the official 64-bit BOINC build, but it wants a newer GLIBC than my Gentoo system has to offer, so no go there (it may have a different platform string, haven't checked).

Basically, it looks like the recent server code edit has a problem with platforms as a whole, not just with "anonymous" ones.

Reverting to 32-bit BOINC (platform string: i686-pc-linux-gnu) got me new work (without app_info.xml, anyway).

HTH,
Simon.

---

Donate to SETI@Home via PayPal!

Optimized SETI@Home apps + Information

Basically, it looks like the recent server code edit has a problem with platforms as a whole, not just with "anonymous" ones.

HTH,
Simon.

Hi Simon,

Maybe you shold report your important observtions in Eric Korpela's blog You can tuna fish, but you can't tune a TCP

or make a link there to this post?

---

Kind regards
Kirsten

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)

To all Danes: You will find the above recipe in Danish, a little modified though, in my forum thread HTTP internal server error.

---

Kind regards
Kirsten

Thanks to TimeLord and all the others that worked out a solution to get rid of the internal server error message and got us back on track for more computing.

---

Basically, it looks like the recent server code edit has a problem with platforms as a whole, not just with "anonymous" ones.

HTH,
Simon.

Hi Simon,

Maybe you shold report your important observtions in Eric Korpela's blog You can tuna fish, but you can't tune a TCP

or make a link there to this post?

There's already some mention of it there, specifically with regard to OS/2 Warp, but anything we can do to get the developers to focus on the specifics will be helpful.

Twelve hours later....After some sleep, beakfast and morning ablutions! I used Richard's and TImeLord04's instructions and am happily crunching again on fresh WU's. On reading through this thread I notice that some have been able to get all all their ghost WU's. (as well?)

At the expense of sounding childish how can I do the same? Any idea's?

Thanks

James

---

Twelve hours later....After some sleep, beakfast and morning ablutions! I used Richard's and TImeLord04's instructions and am happily crunching again on fresh WU's. On reading through this thread I notice that some have been able to get all all their ghost WU's. (as well?)

At the expense of sounding childish how can I do the same? Any idea's?

Thanks

James

You may or may not want to do this, it's a personal decision as the 'ghosts' can be left to time out naturally just fine.

Drain work cache and transfer queue completely, then detach/reattach... WARNING, erases setiathome project folder / optimised apps, and local stats...

It marks all ghosts for the host as 'Client Detached' and reissues them to other users (Hopefully not as ghosts!)

---

"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.

Hi Simon,

Maybe you shold report your important observtions in Eric Korpela's blog You can tuna fish, but you can't tune a TCP

or make a link there to this post?

Good idea, done.

Regards,
Simon.

---

Donate to SETI@Home via PayPal!

Optimized SETI@Home apps + Information

I keep downloading WU's from March 4, 2005 and all of the ones I am returning, have "already been reported as success."

5/19/2007 7:05:05 AM|SETI@home|Message from server: Completed result 04mr05ab.17213.23921.909646.3.57_2 refused: result already reported as success

I still have about 6 more March 4, 2005 left to crunch :-/

The to top it off, despite changing the app_info file for Optimized clients etc etc...I still would have to do that everytime I get a ghost WU and everytime I want new work.

---

"By faith we understand that the universe was formed at God's command, so that what is seen was not made out of what was visible". Hebrews 11.3