python segfault in ld-musl-x86_64.so

[paramehdic]

anyone able to help with this, upon checking log see the below errors over and over and its usually the same with the odd error 0 vs error 6

 

Jan 22 15:02:32 Tower kernel: python[11570]: segfault at 7261726e8d ip 00002ab3348e861c sp 00002ab3448fb1b8 error 6 in ld-musl-x86_64.so.1[2ab3348c5000+88000]

Jan 22 15:02:33 Tower kernel: python[11578]: segfault at 7261726e8d ip 00002ab3348e861c sp 00002ab3448fb7a8 error 6 in ld-musl-x86_64.so.1[2ab3348c5000+88000]

Jan 22 15:02:33 Tower kernel: python[11580]: segfault at 7261726e8d ip 00002ab3348e861c sp 00002ab3448fb558 error 6 in ld-musl-x86_64.so.1[2ab3348c5000+88000]

Jan 22 15:02:33 Tower kernel: python[11581]: segfault at 7261726e8d ip 00002ab3348e861c sp 00002ab3448fb7a8 error 6 in ld-musl-x86_64.so.1[2ab3348c5000+88000]

Jan 22 15:02:33 Tower kernel: python[11582]: segfault at 7261726e8d ip 00002ab3348e861c sp 00002ab3448fb1b8 error 6 in ld-musl-x86_64.so.1[2ab3348c5000+88000]

Jan 22 15:02:35 Tower kernel: python[11598]: segfault at 7261726e8d ip 00002ab3348e861c sp 00002ab3448fb1b8 error 6 in ld-musl-x86_64.so.1[2ab3348c5000+88000]

Jan 22 15:02:46 Tower kernel: python[11751]: segfault at 7261726e8d ip 00002ab3348e861c sp 00002ab3448fb7a8 error 6 in ld-musl-x86_64.so.1[2ab3348c5000+88000]

Jan 22 15:02:46 Tower kernel: python[11752]: segfault at 7261726e8d ip 00002ab3348e861c sp 00002ab3448fb278 error 6 in ld-musl-x86_64.so.1[2ab3348c5000+88000]

Jan 22 15:02:46 Tower kernel: python[11754]: segfault at 7261726e8d ip 00002ab3348e861c sp 00002ab3448fb7a8 error 6 in ld-musl-x86_64.so.1[2ab3348c5000+88000]

Jan 22 15:02:47 Tower kernel: python[11763]: segfault at 7261726e8d ip 00002ab3348e861c sp 00002ab3448fb7a8 error 6 in ld-musl-x86_64.so.1[2ab3348c5000+88000]

 

Jan 22 11:22:11 Tower kernel: traps: python[16304] general protection ip:2ab3348e8614 sp:2ab3448fb558 error:0 in ld-musl-x86_64.so.1[2ab3348c5000+88000]

 

last few parity checks have reported 3 errors

 

Jan 26 07:30:01 Tower kernel: md: recovery thread: check P ...

Jan 26 07:30:01 Tower kernel: md: using 1536k window, over a total of 5860522532 blocks.

Jan 26 10:28:39 Tower kernel: md: recovery thread: P corrected, sector=2663115304

Jan 26 12:00:48 Tower kernel: md: recovery thread: P corrected, sector=4033210264

Jan 26 12:22:35 Tower kernel: md: recovery thread: P corrected, sector=4348507728

 

cant see any pattern to the segfault as some days there wont be any, other days itll happen every few hours.

[John_M]

Tools -> Diagnostics and post the zip file.

[paramehdic]

diagostics attached

tower-diagnostics-20170126-2156.zip

[saarg]

This is from a container that uses must, which is in alpine Linux. And then it's most likely one of our containers.

Which one from us have you installed?

[paramehdic]

plexpy, sickrage and deluge

 

an issue with deluge docker has also been posted

https://lime-technology.com/forum/index.php?topic=43430.msg532140#msg532140

 

[paramehdic]

also seeing a few of these errors in the log as well

 

error 4 in libpython2.7.so.1.0[2ab334b55000+341000]

[therapist]

Version: 6.7.0-rc7

 

Seeing random segfaults related to musl recently:

Apr 8 23:59:32 OCHO kernel: python[34253]: segfault at 6e6f68747988 ip 000014ed29501411 sp 000014ed226c2d38 error 6 in ld-musl-x86_64.so.1[14ed294f4000+45000] 

Apr 8 23:59:32 OCHO kernel: Code: 48 8b 47 10 48 39 47 18 75 14 89 f1 48 c7 c0 fe ff ff ff 48 d3 c0 f0 48 21 05 1b b6 06 00 48 8b 57 18 48 8b 47 10 48 89 42 10 <48> 89 50 18 48 8b 47 08 48 89 c2 48 83 e0 fe 48 83 ca 01 48 89 57 

Apr 9 00:12:33 OCHO kernel: python[2565]: segfault at 561700000090 ip 000014ed2950140d sp 000014ed226c2f08 error 6 in ld-musl-x86_64.so.1[14ed294f4000+45000] 

Apr 9 00:12:33 OCHO kernel: Code: 83 c0 10 c3 48 8b 47 10 48 39 47 18 75 14 89 f1 48 c7 c0 fe ff ff ff 48 d3 c0 f0 48 21 05 1b b6 06 00 48 8b 57 18 48 8b 47 10 <48> 89 42 10 48 89 50 18 48 8b 47 08 48 89 c2 48 83 e0 fe 48 83 ca

 

have unifi-controller / ombi / nextcloud / resilio-sync / tautulli / duplicati installed from linuxserver repo

how do I go about identifying the culprit container? Its not like its happening with any kind of frequency 

 

ocho-diagnostics-20190409-1212.zip

[Coco]

Also having this issue, how do I fix it ?

 

If it is a container causing this how to know which one?

jarvis-diagnostics-20230305-1122.zip