Forum > Discussion Forum
SETI Problems
Fivestar Crashtest:
--- Quote from: msattler on 18 May 2007, 05:42:23 pm --- Did they do some code mods coinciding with the crash and new server migration that are taking exceptiion to the requests the optimized apps make vs what the stock app makes?
'Tis a puzzlement.
--- End quote ---
They wouldn't do that on purpose, would they? This would hurt anybody using anonymous platform, who needs it for 64 bit or any platform not supported, not just optimizers.
Simon:
Hi Pam,
I'd think it wasn't on purpose, no. However, it came at a very inopportune time; from what I read, Matt made some changes to the code, then there were compilation problems, and Matt had to leave before they got fully fixed.
So in any case, it's never a good idea to do any sort of code changes during an outage, which is what Crunch3r wanted to express, I believe. Usually leads to what we have now, total havoc.
Regards,
Simon.
msattler:
Simon....There is some discussion going on in the Seti NC Ghost WU thread about rmoving the app info xml file and finding that the host is still running optimized apps. At what point would the host revert back to the stock app?
If you restart Boinc with the xml file in place, and then remove it to allow comms with the server, will all the WUs in the cache then continue to run optimized?
Josef W. Segur:
--- Quote from: msattler on 19 May 2007, 02:16:42 pm ---Simon....There is some discussion going on in the Seti NC Ghost WU thread about rmoving the app info xml file and finding that the host is still running optimized apps. At what point would the host revert back to the stock app?
--- End quote ---
That's certainly unclear. If the core client deletes the optimized app because it's no longer linked to anything, then it has to download the stock app. But as little as having one finished and uploaded WU left to report means the optimized app is still linked.
When I did the workaround changes on SETI Beta, the stock app was not downloaded and my personal build continued to run. There were still unreported results for those cases. But when I did the workaround for Main the stock app was downloaded and put to use immediately, I hadn't done any work on Main recently so there was nothing to report.
It seems likely that a queue of work might prevent ever switching to the stock app, every request to the Scheduler would have some linkage to work on the host. Whether that departure from the design goals is totally in the BOINC core client or part of recent changes server side, I don't know.
--- Quote ---If you restart Boinc with the xml file in place, and then remove it to allow comms with the server, will all the WUs in the cache then continue to run optimized?
--- End quote ---
Yes, because the BOINC core client only looks for app_info.xml files at startup. But that's not what you want.
After any change of app_info.xml you have to restart BOINC for the change to take effect. For minimum crunch time loss, making the change while BOINC is running, then doing an exit followed immediately by restart is a good plan.
Joe
msattler:
Joe.....
This may help explain why, when I followed your advice in Seti Beta, and removed the app info file, it was posted that my rigs were still reporting all the work as being crunched with optimized apps. A few days ago, I set all my rigs to no new work for Beta, and will crunch all as is and delete the optimized app file totally. This may take a while, seems that my quad rig has latched onto crunching Astropules WUs for 60-70 hours at a time. Ouch.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version