-
-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] tvheadend throws Error on Unraid Syslog #255
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
What CPU do you have? |
I have an AMD Ryzen 7 3700X 8-Core |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue is locked due to inactivity |
Is there an existing issue for this?
Current Behavior
When the tvheadend Container is starting the following Error is persistant on the UnRaid SysLog with different Cores
Jun 20 07:28:28 Tower kernel: tvheadend[30730]: segfault at 0 ip 0000146a6e9c4458 sp 00007ffd933c63c8 error 4 in ld-musl-x86_64.so.1[146a6e97f000+54000] likely on CPU 11 (core 3, socket 0) Jun 20 07:28:29 Tower kernel: tvheadend[30798]: segfault at 0 ip 000014bc12db7458 sp 00007fffb89bbfc8 error 4 in ld-musl-x86_64.so.1[14bc12d72000+54000] likely on CPU 3 (core 3, socket 0) Jun 20 07:28:31 Tower kernel: tvheadend[31154]: segfault at 0 ip 00001523bba8d458 sp 00007ffc3d7992a8 error 4 in ld-musl-x86_64.so.1[1523bba48000+54000] likely on CPU 2 (core 2, socket 0) Jun 20 07:28:32 Tower kernel: tvheadend[31221]: segfault at 0 ip 000014c6f17d8458 sp 00007ffcd3f27c28 error 4 in ld-musl-x86_64.so.1[14c6f1793000+54000] likely on CPU 0 (core 0, socket 0) Jun 20 07:28:34 Tower kernel: tvheadend[31317]: segfault at 0 ip 000014786a4dc458 sp 00007fff621f3478 error 4 in ld-musl-x86_64.so.1[14786a497000+54000] likely on CPU 5 (core 5, socket 0) Jun 20 07:28:35 Tower kernel: tvheadend[31382]: segfault at 0 ip 000014c2190e2458 sp 00007fff2b9bef58 error 4 in ld-musl-x86_64.so.1[14c21909d000+54000] likely on CPU 2 (core 2, socket 0) Jun 20 07:28:36 Tower kernel: tvheadend[31481]: segfault at 0 ip 000014bdea1c0458 sp 00007fffc4558678 error 4 in ld-musl-x86_64.so.1[14bdea17b000+54000] likely on CPU 14 (core 6, socket 0) Jun 20 07:28:38 Tower kernel: tvheadend[31571]: segfault at 0 ip 000014bd1499a458 sp 00007ffe8316fe18 error 4 in ld-musl-x86_64.so.1[14bd14955000+54000] likely on CPU 12 (core 4, socket 0) Jun 20 07:28:39 Tower kernel: tvheadend[31643]: segfault at 0 ip 0000150cd3273458 sp 00007ffe08c22a38 error 4 in ld-musl-x86_64.so.1[150cd322e000+54000] likely on CPU 12 (core 4, socket 0) Jun 20 07:28:41 Tower kernel: tvheadend[31704]: segfault at 0 ip 000015036bccd458 sp 00007fff76d042a8 error 4 in ld-musl-x86_64.so.1[15036bc88000+54000] likely on CPU 13 (core 5, socket 0) Jun 20 07:28:42 Tower kernel: tvheadend[31944]: segfault at 0 ip 0000147c5b60d458 sp 00007fff8a9bffe8 error 4 in ld-musl-x86_64.so.1[147c5b5c8000+54000] likely on CPU 12 (core 4, socket 0) Jun 20 07:28:44 Tower kernel: tvheadend[32057]: segfault at 0 ip 000014dc3a383458 sp 00007fffd92d8df8 error 4 in ld-musl-x86_64.so.1[14dc3a33e000+54000] likely on CPU 14 (core 6, socket 0) Jun 20 07:28:45 Tower kernel: tvheadend[32122]: segfault at 0 ip 000014fff0459458 sp 00007fff395d8948 error 4 in ld-musl-x86_64.so.1[14fff0414000+54000] likely on CPU 7 (core 7, socket 0) Jun 20 07:28:47 Tower kernel: tvheadend[32252]: segfault at 0 ip 000014d9bb546458 sp 00007ffd63ed6258 error 4 in ld-musl-x86_64.so.1[14d9bb501000+54000] likely on CPU 9 (core 1, socket 0) Jun 20 07:28:48 Tower kernel: tvheadend[32379]: segfault at 0 ip 00001485e83db458 sp 00007fffc45e9a08 error 4 in ld-musl-x86_64.so.1[1485e8396000+54000] likely on CPU 14 (core 6, socket 0) Jun 20 07:28:49 Tower kernel: tvheadend[32456]: segfault at 0 ip 0000152cd2322458 sp 00007fffee11e4a8 error 4 in ld-musl-x86_64.so.1[152cd22dd000+54000] likely on CPU 4 (core 4, socket 0) Jun 20 07:28:51 Tower kernel: tvheadend[32531]: segfault at 0 ip 000015365f3ed458 sp 00007ffcc0572e58 error 4 in ld-musl-x86_64.so.1[15365f3a8000+54000] likely on CPU 15 (core 7, socket 0) Jun 20 07:28:52 Tower kernel: tvheadend[32623]: segfault at 0 ip 000014ac3b5de458 sp 00007ffdd68d0b18 error 4 in ld-musl-x86_64.so.1[14ac3b599000+54000] likely on CPU 5 (core 5, socket 0) Jun 20 07:28:54 Tower kernel: tvheadend[32727]: segfault at 0 ip 0000152b76f87458 sp 00007ffd5a63a6b8 error 4 in ld-musl-x86_64.so.1[152b76f42000+54000] likely on CPU 6 (core 6, socket 0) Jun 20 07:28:55 Tower kernel: tvheadend[338]: segfault at 0 ip 000014624f697458 sp 00007ffd75636ea8 error 4 in ld-musl-x86_64.so.1[14624f652000+54000] likely on CPU 12 (core 4, socket 0) Jun 20 07:28:57 Tower kernel: tvheadend[440]: segfault at 0 ip 0000147ab8904458 sp 00007ffd5309ec08 error 4 in ld-musl-x86_64.so.1[147ab88bf000+54000] likely on CPU 11 (core 3, socket 0) Jun 20 07:28:58 Tower kernel: tvheadend[564]: segfault at 0 ip 00001501bdbb1458 sp 00007fff53ea4558 error 4 in ld-musl-x86_64.so.1[1501bdb6c000+54000] likely on CPU 14 (core 6, socket 0)
Expected Behavior
No response
Steps To Reproduce
Starting the Container brings this error.
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: