Astropulse always crashes out.
Astropulse always crashes out. |
|
| log in |
Message boards : Number crunching : Astropulse always crashes out.
| Author | Message |
|---|---|
|
For some months now, I've noticed that Astropulse work-units give a computation error almost immediately. I had assumed that someone was aware, but maybe they are not, so this is a "heads up". | |
ID: 1179716 ·  | |
For some months now, I've noticed that Astropulse work-units give a computation error almost immediately. I had assumed that someone was aware, but maybe they are not, so this is a "heads up". Yes, that seems to be the rule rather than the exception when running AP on Linux. The "process got signal 11" error can often be seen when running AP's on Linux. I know there was a solution to that, and I'm sure someone who knows about Linux, will help you solve that issue. Edit: I have had hundreds of wingmen on my AP's running Linux, and erroring out, so the WU has to be sent out again to a third wingman. I do remember though, that there was a solution to the problem, but since I am not running Linux, I did not pay attention to what it was. ____________ /The grumpy old Swede.  "I'm so old, that 98% of all trees in the forest, are younger than I am" | |
| ID: 1179719 · | |
For some months now, I've noticed that Astropulse work-units give a computation error almost immediately. I had assumed that someone was aware, but maybe they are not, so this is a "heads up". The solution is to run the Optimised Linux apps, they are a lot faster and a lot less prone to erroring out, check out Arkayn's site for downloads: Crunchers Anonymous Downloads Be aware that once you go onto Anonymous Platform, the Setiathome apps won't get updated by the project, you'll have to do that yourself when new Optimised apps are available, or by reverting back to the Stock apps. (we're probably only a few months away from the Rollout of Setiathome v7 and Astropulse v6) Claggy | |
| ID: 1179722 · | |
 James Sotherden Volunteer moderator  Send message Joined: 16 May 99 Posts: 6075 Credit: 15,262,931 RAC: 24,223  | |
|
exit139 | |
| ID: 1179727 · | |
|
This is happening for years now... | |
| ID: 1179730 · | |
|
Thanks for all the replies. I'll investigate the optimised versions. | |
| ID: 1179767 · | |
|
I had an issue with that way back when we went from AP_v5 to AP_v505. All of my tasks would instantly error out with a segment violation. The solution was to upgrade my GLIBC to at least 3.6, I believe it was, as I only had something like 3.1 at the time. | |
| ID: 1179807 · | |
Thanks for all the replies. I'll investigate the optimised versions. You may find some useful discussion here: http://setiathome.berkeley.edu/forum_thread.php?id=66123 ____________   - ALF - "Find out what you don't do well ..... then don't do it!" :) | |
| ID: 1179917 · | |
|
I notices that I got "signal 11" when suspend my computer or I hit the snooze button in boinc manager, computing is without problem until one of this event happened, maybe some other comes. I'm runing boinc v. 6.12.42 on Gentoo 32bit. | |
| ID: 1185886 · | |
|
Personally I wish that AP's were stopped from being given to Linux hosts all together as I've only ever seen 1 Linux host that returns good results, all the rest have just trashed them, and as a result this impacts on the connection due to resends (1 AP that I did recently was sent out 7 times because 4 separate Linux hosts trashed it, 1 Win machine timed out on it, before it was finally put to rest. | |
| ID: 1190305 · | |
|
mine always does because I use the optimized apps. prior to the Opt app install the AP's were always trashed. Thanks again to the Lunatics folks for their diligent work | |
| ID: 1190357 · | |
Message boards : Number crunching : Astropulse always crashes out.
| Copyright © 2013 University of California |
