Bug #4106
Problems after upgrade from 4.0.9.5 to 4.0.9.13
0%
Description
Hello,
Today I've done an update from version 4.0.9.5 to 4.0.9.13 and now tvheadend is not running anymore.
After rebooting the system the webinterface is a blank page (err_connection_reset).
sudo ps aux | grep -v grep | grep tvhead
This is telling me, that tvheadend is running by the user hts.
When I stop tvheadend (sudo service tvheadend stop) and restart it as root (sudo tvheadend) I have access to the webinterface but many configurations are not show anymore. The TV adapters are still there (2 universal LNB) but everything else is empty (networks, muxes, channels and so on).
The DVR entries are missing as well.
On the file system I can still see that the configuration is there (/home/hts/.hts/tvheadend/input/dvb/networks/xxx/muxes/xxx/services/xxx).
When I "sudo tvheadend" I'm getting the following:
2016-11-29 16:42:03.304 [ INFO] main: Log started 2016-11-29 16:42:03.340 [ INFO] config: loaded 2016-11-29 16:42:03.342 [ ERROR] profile: wrong class profile-transcode! 2016-11-29 16:42:03.342 [ ERROR] profile: wrong class profile-transcode! 2016-11-29 16:42:03.342 [ ERROR] profile: wrong class profile-transcode! 2016-11-29 16:42:03.434 [ INFO] scanfile: DVB-T - loaded 43 regions with 1106 networks 2016-11-29 16:42:03.434 [ INFO] scanfile: DVB-S - loaded 1 regions with 112 networks 2016-11-29 16:42:03.434 [ INFO] scanfile: DVB-C - loaded 17 regions with 56 networks 2016-11-29 16:42:03.434 [ INFO] scanfile: ATSC - loaded 2 regions with 14 networks 2016-11-29 16:42:03.464 [ INFO] linuxdvb: adapter added /dev/dvb/adapter1 2016-11-29 16:42:03.482 [ INFO] linuxdvb: adapter added /dev/dvb/adapter0 2016-11-29 16:42:03.886 [ INFO] dvr: Creating new configuration '' 2016-11-29 16:42:03.886 [ INFO] CSA: Using SSE2 128bit parallel descrambling 2016-11-29 16:42:03.886 [ INFO] epggrab: module eit created 2016-11-29 16:42:03.886 [ INFO] epggrab: module uk_freesat created 2016-11-29 16:42:03.886 [ INFO] epggrab: module uk_freeview created 2016-11-29 16:42:03.886 [ INFO] epggrab: module viasat_baltic created 2016-11-29 16:42:03.891 [ INFO] epggrab: module opentv-ausat created 2016-11-29 16:42:03.891 [ INFO] epggrab: module opentv-skyuk created 2016-11-29 16:42:03.891 [ INFO] epggrab: module opentv-skyit created 2016-11-29 16:42:03.891 [ INFO] epggrab: module opentv-skynz created 2016-11-29 16:42:03.892 [ INFO] epggrab: module pyepg created 2016-11-29 16:42:03.892 [ INFO] epggrab: module xmltv created 2016-11-29 16:42:03.894 [ INFO] spawn: Executing "/usr/bin/tv_find_grabbers" 2016-11-29 16:42:04.720 [ INFO] epggrab: module /usr/bin/tv_grab_fr created 2016-11-29 16:42:04.720 [ INFO] epggrab: module /usr/bin/tv_grab_is created 2016-11-29 16:42:04.720 [ INFO] epggrab: module /usr/bin/tv_grab_hr created 2016-11-29 16:42:04.720 [ INFO] epggrab: module /usr/bin/tv_grab_pt_meo created 2016-11-29 16:42:04.720 [ INFO] epggrab: module /usr/bin/tv_grab_il created 2016-11-29 16:42:04.720 [ INFO] epggrab: module /usr/bin/tv_grab_za created 2016-11-29 16:42:04.720 [ INFO] epggrab: module /usr/bin/tv_grab_eu_egon created 2016-11-29 16:42:04.720 [ INFO] epggrab: module /usr/bin/tv_grab_eu_epgdata created 2016-11-29 16:42:04.720 [ INFO] epggrab: module /usr/bin/tv_grab_fi created 2016-11-29 16:42:04.720 [ INFO] epggrab: module /usr/bin/tv_grab_fr_kazer created 2016-11-29 16:42:04.720 [ INFO] epggrab: module /usr/bin/tv_grab_na_dd created 2016-11-29 16:42:04.720 [ INFO] epggrab: module /usr/bin/tv_grab_uk_bleb created 2016-11-29 16:42:04.720 [ INFO] epggrab: module /usr/bin/tv_grab_huro created 2016-11-29 16:42:04.720 [ INFO] epggrab: module /usr/bin/tv_grab_it created 2016-11-29 16:42:04.720 [ INFO] epggrab: module /usr/bin/tv_grab_uk_rt created 2016-11-29 16:42:04.720 [ INFO] epggrab: module /usr/bin/tv_grab_se_tvzon created 2016-11-29 16:42:04.720 [ INFO] epggrab: module /usr/bin/tv_grab_in created 2016-11-29 16:42:04.720 [ INFO] epggrab: module /usr/bin/tv_grab_dk_dr created 2016-11-29 16:42:04.720 [ INFO] epggrab: module /usr/bin/tv_grab_ch_search created 2016-11-29 16:42:04.720 [ INFO] epggrab: module /usr/bin/tv_grab_na_dtv created 2016-11-29 16:42:04.720 [ INFO] epggrab: module /usr/bin/tv_grab_combiner created 2016-11-29 16:42:04.720 [ INFO] epggrab: module /usr/bin/tv_grab_es_laguiatv created 2016-11-29 16:42:04.720 [ INFO] epggrab: module /usr/bin/tv_grab_se_swedb created 2016-11-29 16:42:04.720 [ INFO] epggrab: module /usr/bin/tv_grab_ar created 2016-11-29 16:42:04.720 [ INFO] epggrab: module /usr/bin/tv_grab_no_gfeed created 2016-11-29 16:42:04.721 [ INFO] epgdb: loaded v2 2016-11-29 16:42:04.721 [ INFO] epgdb: config 1 2016-11-29 16:42:04.721 [ INFO] epgdb: channels 0 2016-11-29 16:42:04.721 [ INFO] epgdb: brands 0 2016-11-29 16:42:04.721 [ INFO] epgdb: seasons 0 2016-11-29 16:42:04.721 [ INFO] epgdb: episodes 0 2016-11-29 16:42:04.721 [ INFO] epgdb: broadcasts 0 2016-11-29 16:42:04.721 [ NOTICE] START: HTS Tvheadend version 4.0.9-13~g64fec81~trusty started, running as PID:3505 UID:0 GID:0, CWD:/home/chris CNF:/home/chris/.hts/tvheadend 2016-11-29 16:42:05.497 [ INFO] AVAHI: Service 'Tvheadend' successfully established.
Is this "profile: wrong class profile-transcode!" the problem?
I've searched for that but I found only such logs where this message was ignored when trying to find a solution.
Thanks a lot in advance!
History
Updated by Chris K almost 8 years ago
Updated by I've now checked the syslog and it looks like tvheadend is running after the reboot and getting to a crash:
Nov 29 18:29:50 htpc tvheadend[8743]: mpegts: 12034V in Hotbird - add service 2B7B InBlu Nov 29 18:29:50 htpc tvheadend[8743]: mpegts: 12034V in Hotbird - add service 2B6A Disney Ch. +2 Nov 29 18:29:50 htpc tvheadend[8743]: mpegts: 12034V in Hotbird - add service 2BC7 Eurosport 2 Nov 29 18:29:50 htpc tvheadend[8743]: CRASH: Signal: 6 in PRG: tvheadend (4.0.9-13~g64fec81~trusty) [a03b84b5aeb97e605e2201002d56f1b566a6ac34] CWD: / Nov 29 18:29:50 htpc tvheadend[8743]: CRASH: Fault address 0x6c00002227 (N/A) Nov 29 18:29:50 htpc tvheadend[8743]: 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 Nov 29 18:29:50 htpc tvheadend[8743]: CRASH: Register dump [23]: 00007f65f66dbc40000014000000000000000000000000080000000000000206000000000000000000000000000000000000000002135fc000000000000000000000000000002227000000000000222700000000015621a0000000000266482000000000000000060000000000000000ffffffffffffffff00007fff59f9b72800007f65f474ac370000000000000206000000000000003300000000000000000000000000000000fffffffe7ffbfa170000000000000000 Nov 29 18:29:50 htpc tvheadend[8743]: CRASH: STACKTRACE Nov 29 18:29:50 htpc tvheadend[8743]: CRASH: /tmp/buildd/tvheadend-4.0.9/src/trap.c:148 0x43f259 Nov 29 18:29:50 htpc tvheadend[8743]: CRASH: ??:0 0x7f65f4ff7330 Nov 29 18:29:50 htpc tvheadend[8743]: CRASH: gsignal+0x37 (/lib/x86_64-linux-gnu/libc.so.6) Nov 29 18:29:50 htpc tvheadend[8743]: CRASH: abort+0x148 (/lib/x86_64-linux-gnu/libc.so.6) Nov 29 18:29:50 htpc tvheadend[8743]: CRASH: /tmp/buildd/tvheadend-4.0.9/src/idnode.c:155 0x4101d1 Nov 29 18:29:50 htpc tvheadend[8743]: CRASH: /tmp/buildd/tvheadend-4.0.9/src/service.c:929 0x4310a4 Nov 29 18:29:50 htpc tvheadend[8743]: CRASH: /tmp/buildd/tvheadend-4.0.9/src/input/mpegts/mpegts_service.c:597 0x494da7 Nov 29 18:29:50 htpc tvheadend[8743]: CRASH: /tmp/buildd/tvheadend-4.0.9/src/input/mpegts/mpegts_mux_dvb.c:796 0x4a31e8 Nov 29 18:29:50 htpc tvheadend[8743]: CRASH: /tmp/buildd/tvheadend-4.0.9/src/input/mpegts/mpegts_network_dvb.c:633 0x4a1ee2 Nov 29 18:29:50 htpc tvheadend[8743]: CRASH: /tmp/buildd/tvheadend-4.0.9/src/input/mpegts/mpegts_network_dvb.c:683 0x4a205f Nov 29 18:29:50 htpc tvheadend[8743]: CRASH: /tmp/buildd/tvheadend-4.0.9/src/input/mpegts.c:41 0x488685 Nov 29 18:29:50 htpc tvheadend[8743]: CRASH: /tmp/buildd/tvheadend-4.0.9/src/main.c:1015 0x40934e Nov 29 18:29:50 htpc tvheadend[8743]: CRASH: __libc_start_main+0xf5 (/lib/x86_64-linux-gnu/libc.so.6) Nov 29 18:29:50 htpc kernel: [ 253.844450] init: tvheadend main process (8743) killed by ABRT signal Nov 29 18:29:50 htpc kernel: [ 253.844458] init: tvheadend main process ended, respawning Nov 29 18:29:50 htpc tvheadend[8766]: main: Log started Nov 29 18:29:50 htpc tvheadend[8766]: config: loaded
This is repeating automatically as long as the service is not manually stopped.
Updated by Jaroslav Kysela almost 8 years ago
Updated by There is id node collision! Run tvh from the command line and check for 'Id node collision' messsage. Look for the duplicate files (the hexa string) in your config directory and remove the duplicates.
Updated by Hero of Shapeir almost 8 years ago
Updated by I spent this afternoon debugging the same issue here (after pulling the latest 4.0 branch so I could see the ID), though I hadn't seen this particular bug yet.
In my case, it was a conflicting network ID (input/dvb/networks/XXX) and a service ID (input/dvb/networks/XXX/muxes/YYY/services/XXX). Any idea how those two would have ended up with the same ID? Collision or bug? The after inspecting the service, it appeared to be a mostly-duplicate of another service in the same folder, so I was able to successfully kill the dupe and restore service.
I checked my monthly tvh backups, and it appeared since my Nov 1 backup.
Updated by Chris K almost 8 years ago
Jaroslav Kysela wrote:
There is id node collision! Run tvh from the command line and check for 'Id node collision' messsage. Look for the duplicate files (the hexa string) in your config directory and remove the duplicates.
Thanks for the help Jaroslav and sorry for the late reply.
O couldn't find this string "a03b84b5aeb97e605e2201002d56f1b566a6ac34" in the config directory, so I've removed some muxes and it is working again. Is there any hint in the error message, that it is a node collision? So that next time I can start the search for conflicting nodes directly?
@Brian: I had the same problem more than a year ago: https://tvheadend.org/issues/3023
I think it is probably a specific constellation causing this problem.
Updated by Hero of Shapeir almost 8 years ago
If you're on the 4.0 release branch, the latest commit includes it in the log:
https://github.com/tvheadend/tvheadend/commit/931ecee52b038454778d8a3af6d60de7a98d5bbb
$ grep collision /var/log/syslog.1
Dec 1 12:31:58 tvh tvheadend470: idnode: Id node collision (f3b556042944dd340fa06c71554fbf07)
Dec 1 12:34:34 tvh tvheadend537: idnode: Id node collision (f3b556042944dd340fa06c71554fbf07)
Dec 1 13:15:07 tvh tvheadend15749: idnode: Id node collision (f3b556042944dd340fa06c71554fbf07)
Dec 1 13:48:17 tvh tvheadend16165: idnode: Id node collision (f3b556042944dd340fa06c71554fbf07)