Tvheadend

OK well i don't know what I did, but i noticed EPG Grabber Modules looked crazy different. It had all this stuff enabled and the internal XML TV-grabber disabled. Turned that on, then disabled it and enabled the External XMLDB grabber, but then I couldn't recall which was the one I had originally.

So I went with the internal grabber, and then I noticed there was two channels listed in the EPG Grabber Channels. Deleted the XMLTV ones, and then I saw I had to remap (add) the grabber source to the channels.

Basically it boiled down to the Internal XMLTV EPG Grabber Module was showing Green but in reality was not enabled.

(exhausted)

still not resolved. The real problem has risen its ugly head. For some reason when I tried to tune to a channel, the tvheadend service crashed. When I restarted it all that was there was the one channel again. I looked at everything i did previously and it was all there, nice and neat.

I clicked on [Rerun internal EPG Grabbers] and the guide populated. So the real question is why does the tvheadend service crash? Any log data I can look at?

Build: 4.2.3 (2017-08-10T11:00:31+0200)

Please install the dbg package and corekeeper.

Then see Debugging & Traces on how to collect crash info.

Thanks but that is entirely impossible on a synology box

Joe Miller: Hmh, not sure. Can you deliver a regular log then? If you log into the Web-interface, under Configuration --> Debugging --> Configuration you can specify a log file location and start logging (see the Help button on that page for details). Could you provide that one once you ran into your issues again?

Another question: Have you installed 4.2.3 cleanly/from scratch or have you upgraded from 4.0.x?

Great idea; I totally didn't even think about that section.

Ok I gave it a path, enabled all checkboxes and Applied the settings. We shall see how it goes

as far as being cleanly. No i did not. It was over the 4.0.9 version. If I new how to save my configuration I would totally give it a shot

Ok this morning we had a crash. I have the trace.log attached.

Hmh, sorry, Joe. Cannot interpret the result.

Mark Hunting, can you?

Joe Miller: Give Mark (and maybe others) some time, but if you do not hear back in the next days, please open a ticket and attach the log again, so that the main developer can look at it.

Sadly, I can't either as they're not full trace lines, just the addresses.

Please make sure you're using the debug versions of tvh for your system. For an example of a full debug log see Debugging and Traces

What syno package source are you using? If you can contact the builder ask them to supply a debug version.

He is using my packages. Debugging on a Synology is possible but cumbersome. I have outlined the required steps in the following link:

https://github.com/SynoCommunity/spksrc/issues/2784

Joe Miller: If you are willing to try this and you feel up for the task, let me know which NAS model you have and which firmware version you are running (DSM5.2 or 6.1), so that I can build a package with debug symbols for you.

Sure I'll try.

I'm using a Bromolow model DS3615xs, Diskstation 5.2.

OK, here you go (bromolow-5.2 with debug symbols):

https://www.dropbox.com/s/b1nq2yws8pm3p6p/tvheadend_bromolow-5.2_4.2.3-10.spk?dl=0

The toolchains you have to download to your NAS are here:

https://sourceforge.net/projects/dsgpl/files/DSM%205.2%20Tool%20Chains/Intel%20x86%20Linux%203.2.40%20%28Bromolow%29/

Instructions for debuggging as above:

https://github.com/SynoCommunity/spksrc/issues/2784

Thank you very much. I will work on getting this one going, installed, and we will see what we can see.

Strange as it sounds, I only got a chance to work on this now. work and life has been extremely busy.

So i installed the version supplied here, and when i started the GDB it said that its "not in executable format: File format not recognized",

Am I doing this correct?

DiskStation> gdb /usr/local/tvheadend/bin/tvheadend 4241
GNU gdb (GDB) 7.8
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
"/usr/local/tvheadend/bin/tvheadend": not in executable format: File format not recognized
Attaching to process 4241
"/volume1/@appstore/tvheadend/bin/tvheadend": not in executable format: File format not recognized
(gdb)

When you are logged into your Syno as root and you have installed synogear, can you run

file /usr/local/tvheadend/bin/tvheadend

and report back the result?

Edit:

Please also execute

synogear list

and report back the result...

DiskStation> file tvheadend
tvheadend: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, not stripped
DiskStation>

It seems the synogear gdb is configured as 32 bit (... was configured as "i686-pc-linux-gnu" ...) whereas the tvheadend binary is 64 bit. I never ran into this issue as my evansport platform is 32 bit, and so is my tvheadend binary.

I'm somewhat out of my depth here to be honest, but doing some searches I think you have to set the architecure within gdb according to the architecture of the binary, i.e. as x86-64. Do you want to give it a go? :-)

nah. I am out of my depth here too. I'll just deal with what I have. I may even do a tvheadend sideload inside the "Debian Chroot" environment instead.

Thanks for your help otherwise.

I fully understand. Thanks for hanging in.

FYI, there were crash reports with 4.2.3 on non-Syno platforms, too. Jaroslav has addressed those with the recent maintenance release 4.2.4. I have just updated the packages on the dropbox account. Maybe that solves your problems too. Just wanted to let you know...