Bug #2251
Bug #2296: TVH 3.9.1454 crashes with psi: tables count inconsistency (num 18, list 2)
TVH release 3.9.1353 crashes with "psi: tables count inconsistency (num 16, list 12)" as the first message
0%
Description
TVH 3.9.xxxx has been pretty stable for a while now but after I upgraded to 3.9.1353 I have seen the following crash messages in my syslog a couple of times during the last 24 hours:
Aug 24 17:14:53 tvserver tvheadend1208: psi: tables count inconsistency (num 16, list 12)
Aug 24 17:14:53 tvserver tvheadend1208: CRASH: Signal: 6 in PRG: tvheadend (3.9.1353~g99ed831) [b41a44c5da5d6a75fd9439439b4621a00565f90c] CWD: /tmp
Aug 24 17:14:53 tvserver tvheadend1208: CRASH: Fault address 0x73000004b8 (N/A)
Aug 24 17:14:53 tvserver tvheadend1208: CRASH: Loaded libraries: /lib/x86_64-linux-gnu/libssl.so.1.0.0 /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 /lib/x86_64-linux-gnu/libz.so.1 /usr/lib/liburiparser.so.1 /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 /usr/lib/x86_64-linux-gnu/libavcodec.so.53 /usr/lib/x86_64-linux-gnu/libavutil.so.51 /usr/lib/x86_64-linux-gnu/libavformat.so.53 /usr/lib/x86_64-linux-gnu/libswscale.so.2 /lib/x86_64-linux-gnu/libdbus-1.so.3 /lib/x86_64-linux-gnu/libpthread.so.0 /lib/x86_64-linux-gnu/librt.so.1 /lib/x86_64-linux-gnu/libdl.so.2 /lib/x86_64-linux-gnu/libm.so.6 /lib/x86_64-linux-gnu/libc.so.6 /usr/lib/libvpx.so.1 /usr/lib/x86_64-linux-gnu/libvorbisenc.so.2 /usr/lib/x86_64-linux-gnu/libvorbis.so.0 /usr/lib/x86_64-linux-gnu/libtheoraenc.so.1 /usr/lib/x86_64-linux-gnu/libtheoradec.so.1 /usr/lib/x86_64-linux-gnu/libspeex.so.1 /usr/lib/libschroedinger-1.0.so.0 /usr/lib/libgsm.so.1 /usr/lib/x86_64-linux-gnu/libva.so.1 /lib/x86_64-linux-gnu/libbz2.so.1.0 /lib64/ld-linux-x86-64.so.2
Aug 24 17:14:53 tvserver tvheadend1208: CRASH: Register dump [23]: fefefefefefefefffefefefeff092d630000000000000008000000000000020600000000004c316500000000004c100000007ff7807f7910000000000000006500000000000004b8000000000000060300000000004c0e4000007ff7970c600000000000000000060000000000000000ffffffffffffffff00007ff7807f772800007ff793bbc4f50000000000000206000000000000003300000000000000000000000000000000fffffffe7ffbba170000000000000000
Aug 24 17:14:53 tvserver tvheadend1208: CRASH: STACKTRACE
Aug 24 17:14:53 tvserver tvheadend1208: CRASH: /home/tvserver/tvheadend/src/trap.c:148 0x4320ac
Aug 24 17:14:53 tvserver tvheadend1208: CRASH: ??:0 0x7ff79465dcb0
Aug 24 17:14:53 tvserver tvheadend1208: CRASH: gsignal+0x35 (/lib/x86_64-linux-gnu/libc.so.6)
Aug 24 17:14:53 tvserver tvheadend1208: CRASH: abort+0x17b (/lib/x86_64-linux-gnu/libc.so.6)
Aug 24 17:14:53 tvserver tvheadend1208: CRASH: ??:0 0x7ff793bb51be
Aug 24 17:14:53 tvserver tvheadend1208: CRASH: ??:0 0x7ff793bb5262
Aug 24 17:14:53 tvserver tvheadend1208: CRASH: /home/tvserver/tvheadend/src/input/mpegts/mpegts_input.c:624 0x467d5b
Aug 24 17:14:53 tvserver tvheadend1208: CRASH: /home/tvserver/tvheadend/src/input/mpegts/mpegts_input.c:768 0x468954
Aug 24 17:14:53 tvserver tvheadend1208: CRASH: /home/tvserver/tvheadend/src/wrappers.c:125 0x40f961
Aug 24 17:14:53 tvserver tvheadend1208: CRASH: ??:0 0x7ff794655e9a
Aug 24 17:14:53 tvserver tvheadend1208: CRASH: clone+0x6d (/lib/x86_64-linux-gnu/libc.so.6)
History
Updated by Crazy Fin about 10 years ago
Yes, I am thinking of doing that as well.
What git commands do you use when you revert back to previous commits? I have tested various methods but I havenĀ“t really understand how to perform a git command to revert back to earlier commits.
Updated by Rob vh about 10 years ago
git reset 1579757 --
worked for me, i.e., the commit number you can see for August 13 https://github.com/tvheadend/tvheadend/commits/master?page=2
followed by make and make install.
Updated by NiCrAm 0oo0 about 10 years ago
Crazy Fin wrote:
TVH 3.9.xxxx has been pretty stable for a while now but after I upgraded to 3.9.1353 I have seen the following crash messages in my syslog a couple of times during the last 24 hours:
I've noticed the same issue.
Updated by Rob vh about 10 years ago
After moving to 3.9.1355 and disabling scan on all my Networks, I have run for 1 week without seeing this msg
psi: tables count inconsistency
I still get crashes in different places when a scan starts at 4AM while a program is recording, or when multiple recordings start at exactly the same time.
Updated by Rob vh about 10 years ago
It did it again
Sep 4 22:02:31 sat tvheadend3974: psi: tables count inconsistency (num 35, list 1)
Sep 4 22:02:31 sat tvheadend3974: psi: tables count inconsistency (num 35, list 1)
Sep 4 22:02:33 sat kernel: [3816522.877389] init: tvheadend main process (3974) killed by ABRT signal
Sep 4 22:02:33 sat kernel: [3816522.877451] init: tvheadend main process ended, respawning
Updated by Crazy Fin about 10 years ago
I am on the latest build 3.9.1367 and these crashes that I had on build 3.9.1353 seems to be gone in 3.9.1367.
Updated by Crazy Fin about 10 years ago
Sorry but I was screaming OK to early... :-(
Looks like these crashes still exists i the latest build 3.9.1367.
I had Network Discovery ticked on as well as Idle Scan ticked on and the crash appeared 2 minutes before a recording was scheduled to start.
I will try with Network Discovery and Idle Scan turned off and see if the crashes disappears.
Same messages in the log as before:
Sep 6 10:42:26 tvserver tvheadend23898: psi: tables count inconsistency (num 18, list 11)
Sep 6 10:42:26 tvserver tvheadend23898: CRASH: Signal: 6 in PRG: tvheadend (3.9.1367~gca742e0~trusty) [e2f32f3a07d679a9cbb299633a70e9afaa925ef7] CWD: /
Sep 6 10:42:26 tvserver tvheadend23898: CRASH: Fault address 0x7400005d5a (N/A)
Sep 6 10:42:26 tvserver tvheadend23898: CRASH: Loaded libraries: /lib/x86_64-linux-gnu/libssl.so.1.0.0 /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 /lib/x86_64-linux-gnu/libz.so.1 /usr/lib/liburiparser.so.1 /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 /lib/x86_64-linux-gnu/libdbus-1.so.3 /lib/x86_64-linux-gnu/libdl.so.2 /lib/x86_64-linux-gnu/libpthread.so.0 /lib/x86_64-linux-gnu/libm.so.6 /lib/x86_64-linux-gnu/librt.so.1 /lib/x86_64-linux-gnu/libc.so.6 /lib64/ld-linux-x86-64.so.2 /lib/x86_64-linux-gnu/libnss_compat.so.2 /lib/x86_64-linux-gnu/libnsl.so.1 /lib/x86_64-linux-gnu/libnss_nis.so.2 /lib/x86_64-linux-gnu/libnss_files.so.2
Sep 6 10:42:26 tvserver tvheadend23898: CRASH: Register dump [23]: fefefefefefefe0000007ff6f43e96800000000000000008000000000000020600000000004c009100000000004bcec0000000000000000200000000000000120000000000005d5a0000000000005d6600007ff759cae37000007ff75bb0700000000000000000060000000000000000ffffffffffffffff00007ff74bffe7e800007ff759b63bb90000000000000206000000000000003300000000000000000000000000000000fffffffe7ffbba170000000000000000
Sep 6 10:42:26 tvserver tvheadend23898: CRASH: STACKTRACE
Sep 6 10:42:26 tvserver tvheadend23898: CRASH: ??:0 0x431369
Sep 6 10:42:26 tvserver tvheadend23898: CRASH: ??:0 0x7ff75a411340
Sep 6 10:42:26 tvserver tvheadend23898: CRASH: gsignal+0x39 (/lib/x86_64-linux-gnu/libc.so.6)
Sep 6 10:42:26 tvserver tvheadend23898: CRASH: abort+0x148 (/lib/x86_64-linux-gnu/libc.so.6)
Sep 6 10:42:26 tvserver tvheadend23898: CRASH: ??:0 0x7ff759b5ca76
Sep 6 10:42:26 tvserver tvheadend23898: CRASH: ??:0 0x7ff759b5cb22
Sep 6 10:42:26 tvserver tvheadend23898: CRASH: ??:0 0x465f2a
Sep 6 10:42:26 tvserver tvheadend23898: CRASH: ??:0 0x465f96
Sep 6 10:42:26 tvserver tvheadend23898: CRASH: ??:0 0x40e6c1
Sep 6 10:42:38 tvserver kernel: [298511.001448] init: tvheadend main process (23898) killed by ABRT signal
Sep 6 10:42:38 tvserver kernel: [298511.001461] init: tvheadend main process ended, respawning
==============================
By the way, I am running it as a daemon under Ubuntu 14.04 LTS (latest version with all updates until yesterday). If I haven set any coredumps up by myself, where does Ubuntu store coredumps since I can see the Ubuntu crash/error reporter tells me that there has been a system problem and that I can report the problem. When I do that I can see that the error report being sent has a big file (24MB) called "_usr_bin_tvheadend.0.crash" which is stored in /var/crash folder.
Is this a file with coredump (among other data) and can this be used by TVH developers to investigate? I could see before the report was being sent that there was stacktrace info generated but I am not sure how to open or what tool to use when investigating the info in the crash file.
Updated by Crazy Fin about 10 years ago
Found info about reading these crash reports locally now. Very good reading at
https://wiki.ubuntu.com/DebuggingProgramCrash
Updated by Crazy Fin about 10 years ago
Ok, I think that I was able to use apport-retrace properly now and doing the command
apport-retrace --stdout /var/crash/_usr_bin_tvheadend.0.crash
displayed the following output. et me know if this proper data or if I am doing something wrong:
=======================
E: Can not find version '3.9.1367~gca742e0~trusty' of package 'tvheadend'
E: Unable to find a source package for tvheadend
--- stack trace ---
#0 0x00007ff759b63bb9 in GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
resultvar = 0
pid = 23898
selftid = 23910
#1 0x00007ff759b67108 in _GI_abort () at abort.c:118
act = {_sigaction_handler = {sa_handler = 0x0, sa_sigaction = 0x0}, sa_mask = {__val = {18446744073709551615 <repeats 16 times>}}, sa_flags = 0, sa_restorer = 0x0}
sigs = {__val = {32, 0 <repeats 15 times>}}
#2 0x00007ff759b5ca76 in __assert_fail_base (fmt=0x7ff759cae370 "%s%s%s:%u: s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x4c0091 "0", file=file@entry=0x4bcdc8 "src/input/mpegts/mpegts_input.c", line=line@entry=624, function=function@entry=0x4bcec0 "mpegts_input_table_dispatch") at assert.c:92
str = 0x7ff6f43e9680 "\220x%x<\364\366\177"
total = 4096
#3 0x00007ff759b5cb22 in __GI_assert_fail (assertion=0x4c0091 "0", file=0x4bcdc8 "src/input/mpegts/mpegts_input.c", line=624, function=0x4bcec0 "mpegts_input_table_dispatch") at assert.c:101
No locals.
#4 0x0000000000465f2a in ?? ()
No symbol table info available.
#5 0x0000000000465f96 in ?? ()
No symbol table info available.
#6 0x000000000040e6c1 in ?? ()
No symbol table info available.
#7 0x00007ff75a409182 in start_thread (arg=0x7ff74bfff700) at pthread_create.c:312
res = <optimized out>
pd = 0x7ff74bfff700
now = <optimized out>
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140700108715776, -3360379956606703254, 0, 0, 140700108716480, 140700108715776, 3365068273784547690, 3365100120072218986}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = <optimized out>
pagesize_m1 = <optimized out>
sp = <optimized out>
freesize = <optimized out>
__PRETTY_FUNCTION = "start_thread"
#8 0x00007ff759c27fbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
No locals.
=======================
Updated by Crazy Fin about 10 years ago
I mentioned above that the crash happened just before a recording was to start but that was wrong.
The crash happened 10:42:26 which was in the middle of the recording that was running. The recording had started 10:19:00 and was about to end at 10:47:00.
Updated by Thomas Knoll about 10 years ago
Same issue here. Running TVH latest build 1445 on a 64bit ArchLinux Intel i5 NUC with two sundtek dvb-c usb sticks with standby mode activated.
Crashes in the middle of a tv show and simply doing nothing else.
Sep 11 20:16:33 TVServer tvheadend380: subscription: "192.168.10.241 [ XBMC Media Center ]" subscribing on "RTL II", weight: 150, adapter: "Sundtek DVB-C : DVB-C #0", network: "Kabel Deutschland", mux: .....
Sep 11 20:57:52 TVServer tvheadend380: psi: tables count inconsistency (num 18, list 7)
Sep 11 20:57:52 TVServer tvheadend380: CRASH: Signal: 6 in PRG: /usr/bin/tvheadend (3.9.1445~gc073538) [84b88edc0f6f3fd08a69fcf3ff0e0123412bc0d0] CWD: /
Sep 11 20:57:52 TVServer tvheadend380: CRASH: Fault address 0x5390000017c (N/A)
Sep 11 20:57:52 TVServer tvheadend380: CRASH: Loaded libraries: linux-vdso.so.1 /opt/lib/libmediaclient.so /usr/lib/ffmpeg-compat/libavcodec.so.53 /usr/lib/ffmpeg-compat/libavutil.so.51 /usr/lib/ffmpeg-compat/libavformat.so.53 /usr/lib/ffmpeg-compat/libswscale.so.2 /usr/lib/libssl.so.1.0.0 /usr/lib/libz.so.1 /usr/lib/libavahi-common.so.3 /usr/lib/libavahi-client.so.3 /usr/lib/libdbus-1.so.3 /usr/lib/libdl.so.2 /usr/lib/libpthread.so.0 /usr/lib/libm.so.6 /usr/lib/librt.so.1 /usr/lib/libc.so.6 /usr/lib/libva.so.1 /usr/lib/libxvidcore.so.4 /usr/lib/libx264.so.142 /usr/lib/libvpx.so.1 /usr/lib/libvorbisenc.so.2 /usr/lib/libvorbis.so.0 /usr/lib/libtheoraenc.so.1 /usr/lib/libtheoradec.so.1 /usr/lib/libspeex.so.1 /usr/lib/libschroedinger-1.0.so.0 /usr/lib/libopenjpeg.so.1 /usr/lib/libopencore-amrwb.so.0 /usr/lib/libopencore-amrnb.so.0 /usr/lib/libmp3lame.so.0 /usr/lib/libgsm.so.1 /usr/lib/librtmp.so.1 /usr/lib/libmodplug.so.1 /usr/lib/libbz2.so.1.0 /lib64/ld-linux-x86-64.so.2 /usr/lib/libogg.so.0 /usr/lib/liborc-0.4.so.0
Sep 11 20:57:52 TVServer tvheadend380: CRASH: Register dump [23]: 00000000ffffffff00007f456802e9c00000000000000008000000000000020200000000004cb0f100000000004c790000007f4564010ef00000000000000002000000000000017c00000000000001bd00007f45bf4f1f7e00007f45bf6ad00000000000000000060000000000000000ffffffffffffffff00007f458a7fb63800007f45bc140d670000000000000202000000000000003300000000000000000000000000000000fffffffe7ffbba170000000000000000
Sep 11 20:57:52 TVServer tvheadend380: CRASH: STACKTRACE
Sep 11 20:57:52 TVServer tvheadend380: CRASH: ??:0 0x4337a9
Sep 11 20:57:52 TVServer tvheadend380: CRASH: ??:0 0x7f45bc9d64b0
Sep 11 20:57:52 TVServer tvheadend380: CRASH: gsignal+0x37 (/usr/lib/libc.so.6)
Sep 11 20:57:52 TVServer tvheadend380: CRASH: abort+0x148 (/usr/lib/libc.so.6)
Sep 11 20:57:52 TVServer tvheadend380: CRASH: ??:0 0x7f45bc139bdd
Sep 11 20:57:52 TVServer tvheadend380: CRASH: ??:0 0x7f45bc139c92
Sep 11 20:57:52 TVServer tvheadend380: CRASH: ??:0 0x46a109
Sep 11 20:57:52 TVServer tvheadend380: CRASH: ??:0 0x46a2b8
Sep 11 20:57:52 TVServer tvheadend380: CRASH: ??:0 0x40fd5d
Sep 11 20:57:52 TVServer tvheadend380: CRASH: ??:0 0x7f45bc9ce124
Sep 11 20:57:52 TVServer systemd1: tvheadend.service: main process exited, code=killed, status=6/ABRT
Sep 11 20:57:52 TVServer systemd1: Unit tvheadend.service entered failed state.
Updated by Crazy Fin about 10 years ago
I am on 3.9.1447 (will pull the latest build tonight when back at home) and these crashes are gone since that release.
Updated by Jaroslav Kysela about 10 years ago
- Status changed from New to Rejected
- Parent task set to #2296