Every task results in "error while computing"

Questions and Answers : Unix/Linux : Every task results in "error while computing"
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile m0z
Avatar

Send message
Joined: 25 Feb 17
Posts: 5
Credit: 519,222
RAC: 0
United States
Message 1902719 - Posted: 24 Nov 2017, 17:03:43 UTC

Hey everyone- semi-new to SETI, nice to meet you. :)

I recently got the BOINC manager running on my Linux machine- although my computer seems to be actively looking for/fetching new tasks, I don't seem to be making any progress.

https://setiathome.berkeley.edu/results.php?hostid=8390027&offset=0&show_names=0&state=6&appid=

Every task results in the status "Error while computing"- is this something going on via my end, or do I need to reconfigure something with BOINC/SETI?

Thanks!
ID: 1902719 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15184
Credit: 4,362,181
RAC: 3
Netherlands
Message 1902739 - Posted: 24 Nov 2017, 19:17:24 UTC - in response to Message 1902719.  

When you click on the task ID of any of your tasks, you will get the stderr.txt output of such a task, with the actual error. In your case, all say process got signal 11, SIGSEGV: segmentation violation , which is usually caused by bad memory. See this BOINC FAQ for options and other possible causes.
ID: 1902739 · Report as offensive
Profile m0z
Avatar

Send message
Joined: 25 Feb 17
Posts: 5
Credit: 519,222
RAC: 0
United States
Message 1902782 - Posted: 24 Nov 2017, 23:25:52 UTC

Perfect, thank you!
ID: 1902782 · Report as offensive
Profile ML1
Volunteer moderator
Volunteer tester

Send message
Joined: 25 Nov 01
Posts: 20147
Credit: 7,508,002
RAC: 20
United Kingdom
Message 1903336 - Posted: 28 Nov 2017, 12:50:55 UTC - in response to Message 1902739.  
Last modified: 28 Nov 2017, 12:51:28 UTC

When you click on the task ID of any of your tasks, you will get the stderr.txt output of such a task, with the actual error. In your case, all say process got signal 11, SIGSEGV: segmentation violation , which is usually caused by bad memory. See this BOINC FAQ for options and other possible causes.

I also get that exact same error due to the "VSYSCALL deprecated - s@h client recompile needed".

Memtest86+ is always good to check the system memory.

However, for the deprecated VSYSCALL error for the newer Linux kernels/distros: Is this fixed in the new upcoming v10 s@h clients?

;-) ;-)


Happy crunchin',
Martin
See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)
ID: 1903336 · Report as offensive

Questions and Answers : Unix/Linux : Every task results in "error while computing"


 
©2024 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.