Since upgrading to 4.2, when Kodi client crashes it sometimes takes Tvheadend with it. Is this a known issue?

Added by K Shea 2 months ago

I am running Tvheadend 4.2.3-87~g5b7886e under Ubuntu Server 16.04 and every so odten one of my Kodi clients (elsewhere on the network) crashes, and when it does it takes Tvheadend with it. By which I mean, Tvheadend itself crashes and the backend has to be rebooted to get it to start again. So far this has never happened while Tvheadend is recording anything, and I hope it never does, but it has me worried (to the point that I'm seriously considering going back to 4.0, if I can get it to install under Ubuntu 16.04).

This is what the crash log looks like:

Oct  6 22:10:02 pvr tvheadend[1108]: htsp: 192.168.1.96 [ pvr | Kodi Media Center ]: Disconnected
Oct  6 22:10:03 pvr tvheadend[1108]: CRASH: Signal: 6 in PRG: /usr/bin/tvheadend (4.2.3-87~g5b7886e) [2c4f88e20a6fa4bffbb0271aa237fa5d765b33f0] CWD: /
Oct  6 22:10:03 pvr tvheadend[1108]: CRASH: Fault address 0x6f00000454 (N/A)
Oct  6 22:10:03 pvr tvheadend[1108]: CRASH: Loaded libraries: /usr/lib/libdvben50221.so /usr/lib/libdvbapi.so /usr/lib/libucsi.so /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/x86_64-linux-gnu/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 /usr/lib/x86_64-linux-gnu/libstdc++.so.6 /lib/x86_64-linux-gnu/libc.so.6 /lib/x86_64-linux-gnu/libsystemd.so.0 /lib64/ld-linux-x86-64.so.2 /lib/x86_64-linux-gnu/libgcc_s.so.1 /lib/x86_64-linux-gnu/libselinux.so.1 /lib/x86_64-linux-gnu/liblzma.so.5 /lib/x86_64-linux-gnu/libgcrypt.so.20 /lib/x86_64-linux-gnu/libpcre.so.3 /lib/x86_64-linux-gnu/libgpg-error.so.0 /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
Oct  6 22:10:03 pvr tvheadend[1108]: CRASH: Register dump [23]: 00007f95597eb700000000000000002a000000000000000800000000000002020000000000000002000055cd195c75c00000000000000023000055cd195c790800000000000004540000000000007e82000000000000000000007f953800ffd00000000000000006000000000000000000007f9588fc042800007f95597ea31800007f9588fc04280000000000000202000000000000003300000000000000000000000000000000fffffffe7ffbba130000000000000000
Oct  6 22:10:03 pvr tvheadend[1108]: CRASH: STACKTRACE
Oct  6 22:10:04 pvr tvheadend[1108]: CRASH: ??:0 0x55cd1839eaed 0x55cd1819d000
Oct  6 22:10:04 pvr tvheadend[1108]: CRASH: ??:0 0x7f9589bf9390 0x7f9589be8000
Oct  6 22:10:04 pvr tvheadend[1108]: CRASH: gsignal+0x38  (/lib/x86_64-linux-gnu/libc.so.6)
Oct  6 22:10:04 pvr tvheadend[1108]: CRASH: abort+0x16a  (/lib/x86_64-linux-gnu/libc.so.6)
Oct  6 22:10:04 pvr tvheadend[1108]: CRASH: ??:0 0x55cd18326a14 0x55cd1819d000
Oct  6 22:10:04 pvr tvheadend[1108]: CRASH: ??:0 0x55cd1838667f 0x55cd1819d000
Oct  6 22:10:04 pvr tvheadend[1108]: CRASH: ??:0 0x55cd1838c719 0x55cd1819d000
Oct  6 22:10:04 pvr tvheadend[1108]: CRASH: ??:0 0x55cd18391375 0x55cd1819d000
Oct  6 22:10:04 pvr tvheadend[1108]: CRASH: ??:0 0x55cd1836909d 0x55cd1819d000
Oct  6 22:10:04 pvr tvheadend[1108]: CRASH: ??:0 0x55cd18364785 0x55cd1819d000
Oct  6 22:10:04 pvr tvheadend[1108]: CRASH: ??:0 0x7f9589bef6ba 0x7f9589be8000
Oct  6 22:10:04 pvr tvheadend[1108]: CRASH: clone+0x6d  (/lib/x86_64-linux-gnu/libc.so.6)

Although it says that Kodi disconnected, it was actually a hard crash. Meaning, I had to reboot both the Kodi client machine AND the Tvheadend machine to get everything working again.

I am not as worried about Kodi crashing as I am about the fact that apparently it can take Tvheadend with it. Has anyone else ever seen this, and is there anything I can do to prevent it?

This is NOT something I can repeat at will, it just happens now and then. I think the common thread is that it happens if Kodi crashes while a recording is playing or paused, but I can't be 100% certain of that.


Replies (3)

RE: Since upgrading to 4.2, when Kodi client crashes it sometimes takes Tvheadend with it. Is this a known issue? - Added by K Shea 2 months ago

Alan S, thank you for the reply. I looked at that bug and it looks like it might be the same thing I experienced, and I note that a new version of Tvheadend is available so I'll try installing it over the weekend and see if it helps.

I didn't really understand anything at all in that first link you sent. I am just a user, not a developer, and I can barely get around in Linux. I just install the stable build from the repository. If there is some build available with extra debugging help available, I have no idea where you get it or how to install it, not that I'd really want to anyway because I'd be afraid of losing my settings. What I guess I don't understand is, if the stable build isn't giving enough debugging information to help diagnose a crash, why not just include that extra debugging code in all builds instead of asking users to install some special build? Seems kind of silly to expect regular users, many of whom have a lot of difficulty getting regular Tvheadend installed and working, to then turn around and install some special build with "debugging symbols", whatever those are. Unless it would cause some performance issue, I'd say just put the "debugging symbols" in all builds so when someone tries to send information on a crash or bug, everything needed is already there. Also, it would be good if you could turn on extra debugging from within the web interface, and not have to run Tvheadend in some special way, or do some Linux mumbo-jumbo.

(Also that page was obviously written by a programmer, and probably makes some sense to other programmers, but definitely not to just regular users!)

And anyway, none of that would have helped here, because these crashes seem to happen at random. So even if I could somehow figure out how to enable extra debugging, I could not reproduce the issue at will. But all that aside, thank you very much for pointing me to that bug report and fix. It gives me some hope that this problem has already been addressed!

RE: Since upgrading to 4.2, when Kodi client crashes it sometimes takes Tvheadend with it. Is this a known issue? - Added by Mark Clarkstone 2 months ago

K Shea wrote:

Alan S, thank you for the reply. I looked at that bug and it looks like it might be the same thing I experienced, and I note that a new version of Tvheadend is available so I'll try installing it over the weekend and see if it helps.

I didn't really understand anything at all in that first link you sent. I am just a user, not a developer, and I can barely get around in Linux. I just install the stable build from the repository. If there is some build available with extra debugging help available, I have no idea where you get it or how to install it, not that I'd really want to anyway because I'd be afraid of losing my settings. What I guess I don't understand is, if the stable build isn't giving enough debugging information to help diagnose a crash, why not just include that extra debugging code in all builds instead of asking users to install some special build? Seems kind of silly to expect regular users, many of whom have a lot of difficulty getting regular Tvheadend installed and working, to then turn around and install some special build with "debugging symbols", whatever those are. Unless it would cause some performance issue, I'd say just put the "debugging symbols" in all builds so when someone tries to send information on a crash or bug, everything needed is already there.

I think there is a reason for not having the symbols built in. Open a feature request for it. :)

Also, it would be good if you could turn on extra debugging from within the web interface, and not have to run Tvheadend in some special way, or do some Linux mumbo-jumbo.

There is! It's called the debugging tab :)

(Also that page was obviously written by a programmer, and probably makes some sense to other programmers, but definitely not to just regular users!)

I'll look into writing a less technical guide :)

And anyway, none of that would have helped here, because these crashes seem to happen at random.
So even if I could somehow figure out how to enable extra debugging, I could not reproduce the issue at will. But all that aside, thank you very much for pointing me to that bug report and fix. It gives me some hope that this problem has already been addressed!

Look into installing corekeeper. That'll capture all core dumps that you can use with gdb.

<doc>

(1-3/3)