留言板 :
Number crunching :
State file error
留言板合理
| 作者 | 消息 |
|---|---|
Jord 发送消息 已加入:9 Jun 99 贴子:15170 积分:4,362,181 近期平均积分:3
|
|
|
KB7RZF 发送消息 已加入:15 Aug 99 贴子:9549 积分:3,308,926 近期平均积分:2
|
I'll have a root about and see if I can spot it. No problem, I'm digging myself right now. :-) Ill let ya know if I find it.
|
Suzuki 发送消息 已加入:17 Sep 01 贴子:318 积分:4,474,402 近期平均积分:1
|
I'll have a root about and see if I can spot it. Thanks for your help with this ... |
|
KB7RZF 发送消息 已加入:15 Aug 99 贴子:9549 积分:3,308,926 近期平均积分:2
|
I'll give it a go - thank you. Now where's the alpha release?! <checking BOINC site> Its over on the BOINC site, but I don't have the address handy. It won't be on the download part, you have to go into another page. Hopefully someone can post it. It has all the versions on it. Ill see if someone posts it otherwise ill try and dig through and find it. Jeremy
|
Suzuki 发送消息 已加入:17 Sep 01 贴子:318 积分:4,474,402 近期平均积分:1
|
I'll give it a go - thank you. Now where's the alpha release?! <checking BOINC site> |
|
KB7RZF 发送消息 已加入:15 Aug 99 贴子:9549 积分:3,308,926 近期平均积分:2
|
That's a distinct possibility. Thanks! There is 2 things you can do. 1 is to change one of your entries in your app_info.xml file to have 517 in it, or, you can download an alpha release of the BOINC client, at least 5.5.13 or higher, and that will cure the problem. I am currently running 5.5.13, and I had this same problem. I did the alpha version upgrade to cure it. Hope that helps. Jeremy
|
Richard Haselgrove ![]() 发送消息 已加入:4 Jul 99 贴子:14141 积分:200,643,578 近期平均积分:874
|
That's a distinct possibility. Thanks! I don't claim to be a definitive source on app_info.xml files, but I think my judgement would be: If you have any cached WUs or work in progress, add an extra section. Copy an entire block, and just change the version number. If, as in your case, you have no current WUs (e.g. because of errors/outage/deliberate cache run-down), why not take the opportunity to do a bit of housekeeping and take out everything except a reference to the 517 you need to match the (current) beta. When collecting new work, I think the BOINC/SETI conversation only concerns itself with the highest version number in the .XML [edit] and remember this conversation - you'll need to edit everything again if/when either beta or mainstream moves on to v518 [/edit] |
Suzuki 发送消息 已加入:17 Sep 01 贴子:318 积分:4,474,402 近期平均积分:1
|
That's a distinct possibility. Thanks! My app_info.xml has many entries relating to <version_num>, there's individual entries starting at 512, going up to 515. The last of these reads: - <app_version> <app_name>setiathome_enhanced</app_name> <version_num>515</version_num> - <file_ref> <file_name>setiathome-5.15-kwsn-sse2-p4.exe</file_name> <main_program /> </file_ref> </app_version> Do I add another to include 517, or amend one of them? I'm not sure what effect this would have and don't want to screw things up even more! |
Richard Haselgrove ![]() 发送消息 已加入:4 Jul 99 贴子:14141 积分:200,643,578 近期平均积分:874
|
I was wondering if someone could help me out here. I'm getting the following errors when communicating with the SETI servers: You're a 'Volunteer tester' (beta user), and your messages reference app version 517. Could you be having the problems described in this thread? |
Suzuki 发送消息 已加入:17 Sep 01 贴子:318 积分:4,474,402 近期平均积分:1
|
I was wondering if someone could help me out here. I'm getting the following errors when communicating with the SETI servers: 15/09/2006 10:58:45|SETI@home|State file error: no application version setiathome_enhanced 517 15/09/2006 10:58:45|SETI@home|Can't handle task 13jn02aa.6561.22913.561076.3.13 in scheduler reply 15/09/2006 10:58:45|SETI@home|State file error: no application version setiathome_enhanced 517 15/09/2006 10:58:45|SETI@home|Can't handle task 13jn02aa.6561.22913.561076.3.6 in scheduler reply 15/09/2006 10:58:45|SETI@home|State file error: no application version setiathome_enhanced 517 And this results in me receiving no work due to: 15/09/2006 11:09:01|SETI@home|Message from server: No work sent 15/09/2006 11:09:01|SETI@home|Message from server: (reached daily quota of 100 results) 15/09/2006 11:09:01|SETI@home|No work from project Any ideas what this is and how I can fix it? One of my boxes did have a drive error that caused a computational error on a load of units - but its not this box that the errors are appearing on. Cheers. |
©2020 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.