Advanced search

Message boards : Technical Support : Constant failures with "process exited with code 193 (0xc1, -63)"

Author Message
anton
Send message
Joined: 2 Feb 15
Posts: 4
Credit: 75,030
RAC: 324
Message 21559 - Posted: 24 Oct 2017, 21:08:54 UTC

Hello, I get that message for all tasks on one of my machines - 64bit Debian 10 Buster with Intel E6850. This is happening since installing OS on that computer a few days ago and start using it for BOINC. Looking at the "tasks" section for my account it seems all tasks for this PC are failing like that. Did a "reset project" using the boinctui that I use as manager, "detach project" and "attach" again, rebooted several times to no avail. Here is one of those recent WU with a failure https://www.cosmologyathome.org/result.php?resultid=59587856
Only Cosmology and SETI tasks seem to fail on that PC which is also attached to Milkyway & Asteroids(both running without any obvious errors).

Can I do anything to troubleshoot this? I wasn't able to find much information about this by googling.

Jonathan
Send message
Joined: 27 Sep 17
Posts: 19
Credit: 1,240,187
RAC: 12,069
Message 21560 - Posted: 24 Oct 2017, 21:39:06 UTC - in response to Message 21559.

I would guess problems with your Debian being too 'new' or library issues.

How did you end up with Boinc 7.8.3? Boinc website shows 7.2.42 as stable and 7.4.22 as testing / development

anton
Send message
Joined: 2 Feb 15
Posts: 4
Credit: 75,030
RAC: 324
Message 21561 - Posted: 25 Oct 2017, 18:25:26 UTC - in response to Message 21560.

Hey there! Everything "boinc" was installed using debian packages from testing(buster) with the usual

sudo apt-get install
. Here it is as listed by dpkg:
antonhp@hp-debian:~$ sudo dpkg-query -l |grep boinc ii boinc-app-seti 8.00~svn3701-1 amd64 SETI@home application for the BOINC client ii boinc-client 7.8.3+dfsg-1 amd64 core client for the BOINC distributed computing infrastructure ii boinctui 2.5.0-1 amd64 Fullscreen text mode manager for Boinc client ii libboinc-app7:amd64 7.8.3+dfsg-1 amd64 libraries for BOINC's scientific applications ii libboinc7:amd64 7.8.3+dfsg-1 amd64 libraries of BOINC the client depends on

That version seems to be lurking in the Debian testing repos(https://packages.debian.org/buster/boinc). More interesting might be that in Debian stable the Boinc package is also newer(7.6 https://packages.debian.org/stretch/boinc) than what is on the website.

Should I try with Boinc from their website? Or better just reinstall to get Debian stable, which is on my other dedicated computer where projects seem to run without errors?

Jonathan
Send message
Joined: 27 Sep 17
Posts: 19
Credit: 1,240,187
RAC: 12,069
Message 21562 - Posted: 25 Oct 2017, 20:00:56 UTC - in response to Message 21561.

I am not really sure since your errors seem to be seg faults. You might try the actual Boinc forums to see if everything is working with your setup. The Cosmology at home forum is kind of quiet actually.
Cosmology is putting it's resources toward the boinc2docker application and the legacy is old and may be causing problems. I don't know about the SETI app.

anton
Send message
Joined: 2 Feb 15
Posts: 4
Credit: 75,030
RAC: 324
Message 21563 - Posted: 26 Oct 2017, 20:13:11 UTC - in response to Message 21562.

Well I will try reinstall to get Debian stable then. It would take 15 min and I guess there is no benefit with the newer packages of testing. Thanks for the help.

anton
Send message
Joined: 2 Feb 15
Posts: 4
Credit: 75,030
RAC: 324
Message 21567 - Posted: 27 Oct 2017, 7:14:42 UTC - in response to Message 21563.

To update the situation for anyone that might experience the same scenario as me - installing Debian stable solved the issue. I suppose the problem were the libraries as initially suggested. Both Cosmology and SETI tasks started calculation after attaching projects. Thanks again for the assistance, I didn't even thought of the problem being related to the distribution containing new packages and was thinking to do Memtest. Cheers!

Message boards : Technical Support : Constant failures with "process exited with code 193 (0xc1, -63)"