Advanced search

Forums : Technical Support : calculation errors
Message board moderation

To post messages, you must log in.

AuthorMessage
Moor

Send message
Joined: 2 May 17
Posts: 5
Credit: 46,822,950
RAC: 91,978
Message 22224 - Posted: 29 Aug 2019, 7:15:45 UTC

Hello everybody,

I have since the last maintenance only calculation errors. I also updated from Debian 9.9 to 10.0. Where can I find the exact error log for more accurate information?

Thanks
ID: 22224 · Report as offensive     Reply Quote
Jonathan

Send message
Joined: 27 Sep 17
Posts: 161
Credit: 7,580,022
RAC: 1,014
Message 22228 - Posted: 31 Aug 2019, 6:20:54 UTC - in response to Message 22224.  

It should be on the individual task or workunit web page. You had your computers hidden so I couldn't take a look at any of your tasks errors.
ID: 22228 · Report as offensive     Reply Quote
Moor

Send message
Joined: 2 May 17
Posts: 5
Credit: 46,822,950
RAC: 91,978
Message 22235 - Posted: 1 Sep 2019, 15:45:39 UTC

Hello,

I found it, here the error message:

<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)</message>
<stderr_txt>
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
Stack trace (64 frames):
[0x46390d]
........
[0x56a60b]

Exiting...

</stderr_txt>
]]>
ID: 22235 · Report as offensive     Reply Quote
Jonathan

Send message
Joined: 27 Sep 17
Posts: 161
Credit: 7,580,022
RAC: 1,014
Message 22236 - Posted: 2 Sep 2019, 5:39:05 UTC - in response to Message 22235.  

Either you need to unhide your computer details or post all the information on what application you are running, your computer details and the entire error log.
If you don't want to do that, you can try resetting the project in the Boinc manager.
ID: 22236 · Report as offensive     Reply Quote
Moor

Send message
Joined: 2 May 17
Posts: 5
Credit: 46,822,950
RAC: 91,978
Message 22238 - Posted: 2 Sep 2019, 7:03:58 UTC

I reinstalled a VM and got the same error. But I'll delete it on another VM completely and try again.

Is that the complete error log?

<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)</message>
<stderr_txt>
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
Stack trace (64 frames):
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]
[0x4d1cf8]
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]
[0x4d1cf8]
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]
[0x4d1cf8]
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]
[0x4d1cf8]
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]
[0x4d1cf8]
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]
[0x4d1cf8]
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]
[0x4d1cf8]
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]
[0x4d1cf8]
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]
[0x4d1cf8]
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]
[0x4d1cf8]
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]
[0x4d1cf8]
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]
[0x4d1cf8]
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]

Exiting...

</stderr_txt>
]]>


CPU Typ
GenuineIntel Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz [Family 6 Model 45 Stepping 2]

Linux Debian
Debian GNU/Linux 10 (buster) [4.19.0-5-amd64|libc 2.28 (Debian GLIBC 2.28-10)]

camb_legacy 2.17 x86_64-pc-linux-gnu
ID: 22238 · Report as offensive     Reply Quote
Hal Bregg
Avatar

Send message
Joined: 31 Oct 18
Posts: 22
Credit: 284,331
RAC: 2
Message 22249 - Posted: 5 Sep 2019, 19:13:43 UTC - in response to Message 22238.  
Last modified: 5 Sep 2019, 19:18:31 UTC

I reinstalled a VM and got the same error. But I'll delete it on another VM completely and try again.

Is that the complete error log?

<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)</message>
<stderr_txt>
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
SIGSEGV: segmentation violation
Stack trace (64 frames):
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]
[0x4d1cf8]
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]
[0x4d1cf8]
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]
[0x4d1cf8]
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]
[0x4d1cf8]
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]
[0x4d1cf8]
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]
[0x4d1cf8]
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]
[0x4d1cf8]
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]
[0x4d1cf8]
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]
[0x4d1cf8]
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]
[0x4d1cf8]
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]
[0x4d1cf8]
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]
[0x4d1cf8]
[0x46390d]
[0x48a030]
[0x569228]
[0x56a60b]

Exiting...

</stderr_txt>
]]>


CPU Typ
GenuineIntel Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz [Family 6 Model 45 Stepping 2]

Linux Debian
Debian GNU/Linux 10 (buster) [4.19.0-5-amd64|libc 2.28 (Debian GLIBC 2.28-10)]

camb_legacy 2.17 x86_64-pc-linux-gnu


Faulty memory perhaps or try to limit the number of tasks running at the same time.
Speaking of the number of tasks running consecutively create app_config.xml file in projects folder
and paste this


<app_config>
   <app>
      <name>boinc2docker</name>
      <max_concurrent>1</max_concurrent> 
     </app>
  </app_config>


Replace 1 with the number of tasks you wish to run.

Alternatively, try to install VirtualBox 5.2.8.
ID: 22249 · Report as offensive     Reply Quote
Moor

Send message
Joined: 2 May 17
Posts: 5
Credit: 46,822,950
RAC: 91,978
Message 22269 - Posted: 2 Oct 2019, 14:37:51 UTC - in response to Message 22249.  

Hello,

I do not use camb_boinc2docker.
I only have the bugs on Linux Debian GNU / Linux 10 (buster) [4.19.0-5-amd64 | libc 2.28 (Debian GLIBC 2.28-10)].
With Linux 4.9.0-9-amd64 # 1 SMP Debian 4.9.168-1 + deb9u5 (2019-08-11) x86_64 or Linux 4.9.0-11-amd64 # 1 SMP Debian 4.9.189-3 + deb9u1 (2019 -09-20) x86_64 I have no problems.
Something with Debian 10 seems to be different.
ID: 22269 · Report as offensive     Reply Quote
Jonathan

Send message
Joined: 27 Sep 17
Posts: 161
Credit: 7,580,022
RAC: 1,014
Message 22270 - Posted: 4 Oct 2019, 1:06:17 UTC - in response to Message 22269.  

camb_legacy applications have not changed since October, 2015.

Since you have your computers hidden, we can't look at all your details and the errors returned to the project to help narrow guesses down. You post about a VM and that made us think you were running the camb_boinc2docker application. This is all information that we could have seen and investigated if your computers were not hidden.

You can look at my computer and the tasks run to get an idea of the information you need to post if you do not wish to change your project preferences. I had 9 errors showing when I checked but I only run camb_boinc2docker. You can click on each user link under Author in this forum to see .
ID: 22270 · Report as offensive     Reply Quote
Moor

Send message
Joined: 2 May 17
Posts: 5
Credit: 46,822,950
RAC: 91,978
Message 22273 - Posted: 7 Oct 2019, 12:44:14 UTC - in response to Message 22270.  

Hi,

the computers are now visible. The top computer with the ID 402657 and Debian 10 has the problems, including the ID 402062 is back from Debian 10 to Debian 9.11 and has no problems.
ID: 22273 · Report as offensive     Reply Quote
Jonathan

Send message
Joined: 27 Sep 17
Posts: 161
Credit: 7,580,022
RAC: 1,014
Message 22274 - Posted: 7 Oct 2019, 22:48:14 UTC - in response to Message 22273.  

Thanks Moor,
I started going through your info and I came across workunit 16473006. That one had been sent to three computers running Debian 10 and all failed with the same error. There is probably something wrong with Debian 10 since it isn't just your computer.

You might want to try looking at Debian forums elsewhere to see if there are reported problems with this type of error.

Link to workunit 16473006
http://www.cosmologyathome.org/workunit.php?wuid=16473006
ID: 22274 · Report as offensive     Reply Quote
Jonathan

Send message
Joined: 27 Sep 17
Posts: 161
Credit: 7,580,022
RAC: 1,014
Message 22275 - Posted: 9 Oct 2019, 0:27:17 UTC - in response to Message 22274.  

I created a VM using Virtual Box and installed the latest version of Debian 10. I got the same errors on camb_legacy work units so it appears to be a problem with that version of Debian.

Moor, you might consider changing those Debian 10 computers over to a different project and just wait to see if anything is posted here. I don't know if we will get anyone to look at the project results and see if it is just Debian 10 or other Linux has this problem and error code (193 (0x000000C1) EXIT_SIGNAL)
ID: 22275 · Report as offensive     Reply Quote
Alien Seeker
Avatar

Send message
Joined: 7 Mar 20
Posts: 4
Credit: 2,073
RAC: 13
Message 22491 - Posted: 4 May 2020, 18:54:00 UTC - in response to Message 22275.  

Now I've managed to get some credits, I can post here: the problem is likely that Cosmology@home uses the deprecated and now disabled by default vsyscall. A look at the kernel messages should say something like:
camb_2.16_x86_6[1234] vsyscall attempted with vsyscall=none ip:ffffffffff600000 cs:33 sp:7ffd85a64268 ax:ffffffffff600000 si:0 di:7ffd85a64280


In my case, the camb_legacy 2.17 i686-pc-linux-gnu app works (only x86_64-pc-linux-gnu seems to use vsyscall), but I get a lot of invalids despite apparently normal runs on my end.
ID: 22491 · Report as offensive     Reply Quote
Tom Miller
Avatar

Send message
Joined: 1 Jul 14
Posts: 3
Credit: 106,213
RAC: 0
Message 22493 - Posted: 5 May 2020, 16:32:57 UTC

I am now set on NNT till I figure out what I have screwed up.

I have started getting "computation errors" under my VM machine. This is a new linux OS install on a "new" system.

Is this possibly "you are running a current version (ver 6?) and need to run an older version (ver 5?)" issue?

Thank you.
Tom M
If at first you don't succeed that means you either haven't practiced enough or you have no talent for it. Unfortunately that means you have to practice a lot to find out if you can't do it.
ID: 22493 · Report as offensive     Reply Quote
Jonathan

Send message
Joined: 27 Sep 17
Posts: 161
Credit: 7,580,022
RAC: 1,014
Message 22495 - Posted: 5 May 2020, 21:41:55 UTC - in response to Message 22493.  

Tom, some of your workunits show "VBoxManage: error: AMD-V is disabled in the BIOS (or by the host OS) (VERR_SVM_DISABLED)" in the error log.
Make sure it is on in the BIOS and check the FAQ section.
Do you have any other projects successfully using Virtual Box? Do you have a limit on the number of concurrent tasks for boinc2docker?
ID: 22495 · Report as offensive     Reply Quote
Tom Miller
Avatar

Send message
Joined: 1 Jul 14
Posts: 3
Credit: 106,213
RAC: 0
Message 22497 - Posted: 6 May 2020, 22:28:11 UTC - in response to Message 22495.  

Tom, some of your workunits show "VBoxManage: error: AMD-V is disabled in the BIOS (or by the host OS) (VERR_SVM_DISABLED)" in the error log.
Make sure it is on in the BIOS and check the FAQ section.
Do you have any other projects successfully using Virtual Box? Do you have a limit on the number of concurrent tasks for boinc2docker?


You were right. The MB/Bios is new to me (X570) and in the process of resetting the defaults I missed enabling the virtual machine support in the bios. I got that fixed.

This time it ran a minute and a half before it threw a "computation" error. That is an improvement over 10 seconds previously.

I will check the FAQ's. I may have a "problem child" VM version.

I don't, yet, run any other projects with a VM.

Tom M
If at first you don't succeed that means you either haven't practiced enough or you have no talent for it. Unfortunately that means you have to practice a lot to find out if you can't do it.
ID: 22497 · Report as offensive     Reply Quote
mikey
Avatar

Send message
Joined: 30 Oct 12
Posts: 46
Credit: 5,145,330
RAC: 0
Message 22498 - Posted: 6 May 2020, 22:55:18 UTC - in response to Message 22497.  


I don't, yet, run any other projects with a VM.

Tom M


One thing could be your vbox software could be out of date, I see you run a mix of Windows and Linux machines so here is where you can get the latest versions, Boinc itself does not always have it and that can cause problems for some people.

https://www.oracle.com/virtualization/technologies/vm/downloads/virtualbox-downloads.html
ID: 22498 · Report as offensive     Reply Quote
Jonathan

Send message
Joined: 27 Sep 17
Posts: 161
Credit: 7,580,022
RAC: 1,014
Message 22502 - Posted: 7 May 2020, 5:42:46 UTC - in response to Message 22497.  

Tom, I looks at some of your returned tasks and their error messages. You have a few successful and validated ones but a bunch of ones with errors. I can't really tell what is wrong from the errors and the error codes in the logs. I am just taking a guess but maybe try to set your project preferences to run less concurrent tasks, at least for now. I have the following set for 4 core work units but I am using the 'app_config.xml' method to controls concurrency for this project. It can be found in the FAQ section. I attached my current file below, also. Are you running any other projects?

Max # jobs No limit
Max # CPUs 4

<app_config>
    <app>
        <name>camb_boinc2docker</name>
        <max_concurrent>2</max_concurrent>
    </app>
    <app_version>
        <app_name>camb_boinc2docker</app_name>
        <plan_class>vbox64_mt</plan_class>
        <avg_ncpus>4</avg_ncpus>
    </app_version>
</app_config>
ID: 22502 · Report as offensive     Reply Quote
Tom Miller
Avatar

Send message
Joined: 1 Jul 14
Posts: 3
Credit: 106,213
RAC: 0
Message 22504 - Posted: 8 May 2020, 13:52:17 UTC - in response to Message 22502.  

Are you running any other projects?


Yes. I am running Einstein @Home(~2), Rosetta@Home(~18), World Community Grid(~7), MindModeling (upto 4) and PrimeGrid(1).

I have just switched Cosmology@Home to No New Tasks until I have a larger block of time to trouble shoot it. Since it is the only VM project I am currently running it will take some more time for me to sort it out.

While the cpu I am using is not new, the X570 MB is. And I think I saw a Beta Bios update announced for all MSI X570 Motherboards.

So I have several things to work on here.

Sorry for garbling up the returns here.

Tom M
If at first you don't succeed that means you either haven't practiced enough or you have no talent for it. Unfortunately that means you have to practice a lot to find out if you can't do it.
ID: 22504 · Report as offensive     Reply Quote
Jonathan

Send message
Joined: 27 Sep 17
Posts: 161
Credit: 7,580,022
RAC: 1,014
Message 22505 - Posted: 8 May 2020, 15:10:01 UTC - in response to Message 22504.  

If you update the bios, make sure to double check the processor virtualization. Mine defaults to off every time I update.
ID: 22505 · Report as offensive     Reply Quote
spod

Send message
Joined: 25 Mar 20
Posts: 1
Credit: 42,230
RAC: 152
Message 22506 - Posted: 14 May 2020, 14:36:53 UTC - in response to Message 22269.  


Something with Debian 10 seems to be different.


Debian 10 (Buster) does not allow vsyscall by default. Add "vsyscall=emulate" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, run update-grub and reboot.
ID: 22506 · Report as offensive     Reply Quote

Forums : Technical Support : calculation errors