TVHeadend Crashing On Startup When Detecting HDHomeRun

dedc · 2024-07-13T06:26:27+00:00

I am having a problem with tvheadend crashing on startup when it detects hdhomerun tuners. See the relevant section of the log below: 2024-07-12 21:43:31...

davep

Sorry tvheadend needs to be built with debug symbols - the last few lines of the log beginning with CRASH would then point to the line of code where the error occurred.

See https://docs.tvheadend.org/documentation/appendices/debugging

dedc

Thanks for the quick reply. Do you mean that i need to build tvheadend from source with debug sysmbols? In the repo I saw an installer called tvheadend-dbg and thought that was the installer that had the debug symbols so I installed it and expected to see the updated logging as it indicates on the debug page but that didn't work out. Specifically, on a new install of Ubuntu, I am running the below commands:

sudo apt install curl
sudo curl -1sLf 'https://dl.cloudsmith.io/public/tvheadend/tvheadend/setup.deb.sh' | sudo -E bash
sudo install TVHeadEnd: sudo apt-get install tvheadend-dbg

DeltaMikeCharlie

dedc In the repo I saw an installer called tvheadend-dbg and thought that was the installer that had the debug symbols so I installed it and expected to see the updated logging as it indicates on the debug page but that didn't work out.

I think that there is some confusion regarding the term 'debugging'.

I the executable program, having the 'debugging' symbols can give more information when a program crashes.

The TVH 'Debugging' page refers to some extra logging that TVH can provide to help isolate problems.

If you use the TVH with debugging symbols, the log file that you originally posted would also include the module/function (and probably line number) that caused the crash.

davep

I don't use Ubuntu or any Debian-based distribution - maybe someone who does will chip in with a better answer?

Looking at the Ubuntu wiki, it seems there may be a crash report in /var/crash. The wiki page https://wiki.ubuntu.com/DebuggingProgramCrash has details.

dedc

Thanks for the response and sorry for being a bit dense. I think I have the logging asked for. Hopefully this means something more to you than it does to me : ). Below is what i think is the relevant section. Full trace log attached. Appreciate the help.

2024-07-14 16:09:12.305 [ INFO]:tvhdhomerun: Found HDHomerun device 10aa39db with 4 tuners
2024-07-14 16:09:12.747 [ ALERT]:CRASH: Signal: 11 in PRG: tvheadend (4.3-2344_gd2e41b553) [b324760ac04acdc3c659bab0f33a67308e7b22b9] CWD: /home/test
2024-07-14 16:09:12.747 [ ALERT]:CRASH: Fault address (nil) (Address not mapped)
2024-07-14 16:09:12.747 [ ALERT]:CRASH: Loaded libraries: linux-vdso.so.1 /lib/x86_64-linux-gnu/libdvbcsa.so.1 /lib/x86_64-linux-gnu/libssl.so.3 /lib/x86_64-linux-gnu/libcrypto.so.3 /lib/x86_64-linux-gnu/libz.so.1 /lib/x86_64-linux-gnu/libpcre.so.3 /lib/x86_64-linux-gnu/liburiparser.so.1 /lib/x86_64-linux-gnu/libavahi-common.so.3 /lib/x86_64-linux-gnu/libavahi-client.so.3 /lib/x86_64-linux-gnu/libdbus-1.so.3 /lib/x86_64-linux-gnu/libm.so.6 /lib/x86_64-linux-gnu/libmvec.so.1 /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/libcap.so.2 /lib/x86_64-linux-gnu/libgcrypt.so.20 /lib/x86_64-linux-gnu/liblz4.so.1 /lib/x86_64-linux-gnu/liblzma.so.5 /lib/x86_64-linux-gnu/libzstd.so.1 /lib/x86_64-linux-gnu/libgpg-error.so.0
2024-07-14 16:09:12.747 [ ALERT]:CRASH: Register dump [23]: 00007a65b40008e0000000000000000700007a65b4000b702573149effd0587c00007a65b4000d40000000000000000000007a66055ff3e000007a66055ff410000000000000000000005edca6d3f53100007a65b4000bc000007a66055ff59000000000000000610000000000000000000000000000000100007a66055ff35800007a660a2c7e610000000000010297002b0000000000330000000000000004000000000000000efffffffe7ffbba130000000000000000
2024-07-14 16:09:12.747 [ ALERT]:CRASH: STACKTRACE
2024-07-14 16:09:12.913 [ ALERT]:CRASH: /w/tvheadend/tvheadend/src/trap.c:176 0x5edca5e1e6c6 0x5edca5bd4000
2024-07-14 16:09:13.340 [ ALERT]:CRASH: ??:0 0x7a660a245320 0x7a660a200000
2024-07-14 16:09:13.781 [ ALERT]:CRASH: ??:0 0x7a660a2c7e61 0x7a660a200000
2024-07-14 16:09:13.995 [ ALERT]:CRASH: /w/tvheadend/tvheadend/src/input/mpegts/tvhdhomerun/tvhdhomerun.c:338 0x5edca5ef86de 0x5edca5bd4000
2024-07-14 16:09:14.202 [ ALERT]:CRASH: /w/tvheadend/tvheadend/src/input/mpegts/tvhdhomerun/tvhdhomerun.c:435 0x5edca5ef8c48 0x5edca5bd4000
2024-07-14 16:09:14.349 [ ALERT]:CRASH: /w/tvheadend/tvheadend/src/tvh_thread.c:91 0x5edca5dd930e 0x5edca5bd4000
2024-07-14 16:09:14.799 [ ALERT]:CRASH: ??:0 0x7a660a29ca94 0x7a660a200000

dedc

Log attached.

tvheadendwithtraceanddebugsymbols.txt

701kB

DeltaMikeCharlie

I know nothing about HDHomeRun, sorry.

At first guess, it looks maybe like your HDHomeRun source may not be sending a model identification string, but I could be wrong.

tvheadend/tvheadendblob/1dc8ffe781b688f6ba7bacddd518399ea289efa6/src/input/mpegts/tvhdhomerun/tvhdhomerun.c#L338C1-L346C4

Are there any setting on your HDHomeRun device that you can look into?

davep

Agreed it seems that Tvheadend is not receiving the HDHomeRun model string. It uses the string to determine what type of device the HDHomeRun is emulating (terrestrial, cable etc). Of course lack of the model string ought not to cause a crash...

There is a command-line utility for working with HDHomeRun devices, available fromhttps://info.hdhomerun.com/info/hdhomerun_config - the Windows version is perhaps easier to work with if you have a Windows box on your network. Are you able to run this utility against your device to check what data it is returning?

dedc

In General Settings I found the “Tvheadend model name for HDHomeRun Server Emulation” settings below (screenshot). Not sure what server emulation is (I have a lot to learn) but since it was asking specifically for an HDHomeRun model name and that seemed to be causing the crash I gave it a try and it seems to be working. Tvheadend is now detecting the tuners in my HDHomeRun. Not sure why this would make a difference when the HDHomeRun Server Emulation setting isn’t even enabled but its nice to see the tuners show up.

DeltaMikeCharlie

From the help text:

Tvheadend model name for HDHomeRun Server Emulation : When Tvheadend is acting as an HDHomeRun Server (emulating an HDHomeRun device for downstream media devices to stream Live TV) then we use this as the type of HDHomeRun model number that we send to clients. Some clients may require a specific model number to work. Leave blank for Tvheadend to use a default.

dedc

In case anyone else has the problem – the issue turned out to be that my hdhomerun was on a different network than tvheadend. There are, of course, warnings in almost every install guide not to do this. In my case I was installing tvheadend on a virtualbox vm on my laptop to work through the setup and config before installing it on the actual hardware it would be running on and I had forgotten virtual box creates a separate network for the VM. Once I stopped berating myself for being dense and got tvheadend and hdhomerun on the same network things ran much better.

Thanks for the help