1) Forums : Technical Support : calculation errors (Message 22273)
Posted 9 days ago by Moor
Post:
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.
2) Forums : Technical Support : calculation errors (Message 22269)
Posted 13 days ago by Moor
Post:
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.
3) Forums : Technical Support : calculation errors (Message 22238)
Posted 2 Sep 2019 by Moor
Post:
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
4) Forums : Technical Support : calculation errors (Message 22235)
Posted 1 Sep 2019 by Moor
Post:
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>
]]>
5) Forums : Technical Support : calculation errors (Message 22224)
Posted 29 Aug 2019 by Moor
Post:
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