Bug #1956
Lots of syslog messages saying "eit: invalid tsid found tid 0x50, onid:tsid 1:5 != 1:12"
0%
Description
I see LOT of syslog messages during the day in bursts when EIT EPG grabber runs:
2014-01-28 21:38:29.699 eit: invalid tsid found tid 0x50, onid:tsid 1:5 != 1:12
2014-01-28 21:38:30.290 eit: invalid tsid found tid 0x50, onid:tsid 1:5 != 1:12
2014-01-28 21:38:30.290 eit: invalid tsid found tid 0x50, onid:tsid 1:5 != 1:12
2014-01-28 21:38:30.417 eit: invalid tsid found tid 0x50, onid:tsid 1:5 != 1:12
2014-01-28 21:38:30.576 eit: invalid tsid found tid 0x50, onid:tsid 1:5 != 1:12
2014-01-28 21:38:30.736 eit: invalid tsid found tid 0x50, onid:tsid 1:5 != 1:12
2014-01-28 21:38:30.975 eit: invalid tsid found tid 0x50, onid:tsid 1:5 != 1:12
2014-01-28 21:38:31.289 eit: invalid tsid found tid 0x50, onid:tsid 1:5 != 1:12
2014-01-28 21:38:31.533 eit: invalid tsid found tid 0x50, onid:tsid 1:5 != 1:12
2014-01-28 21:38:31.720 eit: invalid tsid found tid 0x50, onid:tsid 1:5 != 1:12
Today 28th Feb it has happened approx 8-10 times and generates approx 4 lines per second during one minute. It seems to be approx 1 minute bursts when this happens.
I saw in a previous thread https://tvheadend.org/issues/1839 (EIT grab is spamming the syslog) where a similar problem was reported and a fix was reported in changeset tvheadend|commit:8d7839f43a782244e49c66b4f59cf91e397133d7.
I am using HTS Tvheadend 3.9.373~g55c2bbb~precise with Digital Devices Cine S2 quad tuner card and measuring my signal at the cable end that goes into the tuners with a Satlink WS-6926 meter and both quality and signal strength are between 85 to 90%.
I am taking the signal from Thor 0.8W for the Canal Digital channels.
I have both "Full Mux RX mode" and "Keep FE open" disabled and "Satconfig" set to Universal LNB only
I have not seen these kind of errors in versions before 3.9.
Files
History
Updated by Adam Sutton almost 11 years ago
Updated by Please can you provide a debug log using the following options :
-l tvh.log --trace mpegts,linuxdvb
I'm aware the issue exists, I'm just not sure what the problem is, could just be the data in the stream is bad and it should be ignored, could be stale data has entered the pipeline which is not good.
You wouldn't have seen this with older versions anyway since the error was silently ignored.
Adam
Updated by Crazy Fin almost 11 years ago
Updated by Haven´t done debug logging in TVH previously and I currently run my TVH as a service that starts automatically on reboot.
Should I just stop the current TVH service and then start TVH manually with ./build.linux/tvheadend -l tvh.log --trace mpegts,linuxdvb
I guess this will not work properly since the command above will run TVH with my login as the user and therefore use different TVH config instead of TVH as the user which is the case when starting it as a service?
Updated by Adam Sutton almost 11 years ago
You're correct running it like that will run as yourself.
Read Development that will give some suggestions on the best way to run TVH for debug purposes. It'll make it possible to run as yourself and show you to copy your config so that you can have a test config separate from your main one etc...
Adam
Updated by Crazy Fin almost 11 years ago
Aah so cool! I now finally understand the different ways of INSTALLING or BUILDING TVHeadend. Now I am able to download latest builds of TVH and first test them without destroying my more stable installation of TVH. :-)
Doing a build as per https://tvheadend.org/projects/tvheadend/wiki/Building but starting only from the step "Get source" I was able to copy my current config into the build directory where I am now running a TVH with me as the owner and the log is working.
No messages about "Invalid TSID" yet though. I see some few "Counter continuity errors" but that is mainly due to the veryhard winds (12-14 m/s) at the moment here in the Stockholm area of Sweden. I usually have very few "continuity counter errors".
As soon as I have seen those "Invalid TSID" messages in my log I will upload the log here (unless it is bigger than the max 488 Mb)
Updated by Crazy Fin almost 11 years ago
Ok, I have now attached a log that has some "Invalid TSID" messages.
Look at for example time stamp 10:52:23, 10:52:24 and 10:52:26 in the uploaded file.
I see also
2014-01-30 06:32:21.638 [ TRACE]:mpegts: created network IPTV Network
2014-01-30 06:32:21.638 [ DEBUG]:mpegts: IPTV - added network IPTV Network
2014-01-30 06:32:21.664 [ INFO]:charset: 138 entries loaded
2014-01-30 06:32:21.664 [ TRACE]:mpegts: created network THOR
2014-01-30 06:32:21.667 [ TRACE]:mpegts: Multiplex [onid:0001 tsid:0004] - created
I am not able to delete the IPTV network from the configurations tab for some reason? Nothing happens when I press delete while the IPTV Network is selected.
Updated by Crazy Fin over 10 years ago
Hello again
I recently added a 2nd quad tuner card Digital Devices Cine S2 and it looks like the frequency of these "eit: invalid tsid found tid 0x50, onid:tsid 4369:99 != 4369:11" messages has increased?
I see quite many of these messages and they last for approx 3-5 seconds in the log.
It looks like all these events starts with
"2014-03-10 20:09:14.755 subscription: 'epggrab' subscribing to mux, weight: 1, adapter: 'Tuner 2', network: 'THOR', mux: '12073V'" in the log (the adapter, tuner, mux can change of course).
014-03-10 20:02:25.622 eit: invalid tsid found tid 0x50, onid:tsid 1:5 != 1:12
2014-03-10 20:02:25.622 eit: invalid tsid found tid 0x4E, onid:tsid 1:5 != 1:12
2014-03-10 20:02:25.622 eit: invalid tsid found tid 0x50, onid:tsid 1:5 != 1:12
2014-03-10 20:02:25.622 eit: invalid tsid found tid 0x50, onid:tsid 1:5 != 1:12
2014-03-10 20:02:25.622 eit: invalid tsid found tid 0x50, onid:tsid 1536:15704 != 1536:704
2014-03-10 20:02:25.622 eit: invalid tsid found tid 0x4E, onid:tsid 1536:15704 != 1536:704
2014-03-10 20:02:25.622 eit: invalid tsid found tid 0x50, onid:tsid 1536:15704 != 1536:704
2014-03-10 20:02:25.622 eit: invalid tsid found tid 0x50, onid:tsid 1536:15704 != 1536:704
2014-03-10 20:02:25.623 eit: invalid tsid found tid 0x50, onid:tsid 1536:15712 != 1536:712
2014-03-10 20:02:26.779 eit: invalid tsid found tid 0x4E, onid:tsid 1536:15709 != 1536:709
2014-03-10 20:02:26.780 eit: invalid tsid found tid 0x4E, onid:tsid 1536:15712 != 1536:712
2014-03-10 20:02:26.781 eit: invalid tsid found tid 0x4E, onid:tsid 1:5 != 1:12
2014-03-10 20:02:27.935 eit: invalid tsid found tid 0x50, onid:tsid 1:5 != 1:12
2014-03-10 20:02:27.935 eit: invalid tsid found tid 0x4E, onid:tsid 1:5 != 1:12
014-03-10 20:09:15.481 eit: invalid tsid found tid 0x50, onid:tsid 4369:99 != 4369:11
2014-03-10 20:09:15.542 eit: invalid tsid found tid 0x50, onid:tsid 4369:99 != 4369:11
2014-03-10 20:09:15.609 eit: invalid tsid found tid 0x50, onid:tsid 4369:99 != 4369:11
2014-03-10 20:09:15.654 eit: invalid tsid found tid 0x50, onid:tsid 4369:99 != 4369:11
2014-03-10 20:09:15.654 eit: invalid tsid found tid 0x50, onid:tsid 4369:99 != 4369:11
2014-03-10 20:09:15.699 eit: invalid tsid found tid 0x50, onid:tsid 4369:99 != 4369:11
2014-03-10 20:09:15.811 eit: invalid tsid found tid 0x50, onid:tsid 4369:99 != 4369:11
2014-03-10 20:09:17.491 eit: invalid tsid found tid 0x50, onid:tsid 1536:15706 != 1536:706
2014-03-10 20:09:17.536 eit: invalid tsid found tid 0x50, onid:tsid 1536:15706 != 1536:706
2014-03-10 20:09:17.536 eit: invalid tsid found tid 0x50, onid:tsid 1536:15706 != 1536:706
2014-03-10 20:09:17.536 eit: invalid tsid found tid 0x50, onid:tsid 1536:15706 != 1536:706
2014-03-10 20:09:17.603 eit: invalid tsid found tid 0x50, onid:tsid 1536:15706 != 1536:706
2014-03-10 20:09:17.625 eit: invalid tsid found tid 0x50, onid:tsid 1536:15706 != 1536:706
2014-03-10 20:09:17.625 eit: invalid tsid found tid 0x50, onid:tsid 1536:15706 != 1536:706
And then it always ends with
2014-03-10 20:09:24.564 subscription: "epggrab" unsubscribing
2014-03-10 20:09:24.564 subscription: "epggrab" unsubscribing
Updated by Crazy Fin over 10 years ago
This is interestin:
I turned of all EPG grabbers and I do not have ANY "invalid tsid found tid" errors anymore.
I have also VERY few "continuity counter error"-messages as well. Mainly when switching between channels and not even on every channel switch either.
As soon as I enable EIT Grabber the problems with "invalid tsid found tid"-messages starts to appear and every time the EIT grabber starts I get also a few "continuity counter error"-messages as well.
Can the "invalid tsid"-error messages be caused by the fact that I have the IPTV network listed in the GUI (eventhough it is disabled)? I am not able to delete it but I guess I can remove it by manually editing some of the config files?
Updated by Crazy Fin over 10 years ago
Ah!
I am still on 3.9.385~g7d8d81a~precise but thanks to discussion in the topic https://tvheadend.org/issues/2059 and others about the "power save" which was previously called "keep FE open", I decided to test with Keep FE open ENABLED on all my 8 tuners (2 x quad CINE S2 cards) and voila!! Now my continuity counter errors (and minimal artifacts caused during this) are gone when the EPG process runs.
Wonderful! 
However, I still have the messages about "invalid tsid found" showing up in the log:
2014-04-18 22:33:37.014 eit: invalid tsid found tid 0x50, onid:tsid 1536:15708 != 1536:708
2014-04-18 22:33:37.014 eit: invalid tsid found tid 0x4E, onid:tsid 1536:15707 != 1536:707
2014-04-18 22:33:37.014 eit: invalid tsid found tid 0x4E, onid:tsid 1536:15707 != 1536:707
2014-04-18 22:33:43.936 eit: invalid tsid found tid 0x50, onid:tsid 1536:15709 != 1536:709
2014-04-18 22:33:43.937 eit: invalid tsid found tid 0x50, onid:tsid 1536:15709 != 1536:709
2014-04-18 22:33:43.937 eit: invalid tsid found tid 0x50, onid:tsid 1:1001 != 1:1
2014-04-18 22:33:45.093 eit: invalid tsid found tid 0x50, onid:tsid 1:1001 != 1:1
2014-04-18 22:33:45.095 eit: invalid tsid found tid 0x50, onid:tsid 1536:15709 != 1536:709
2014-04-18 22:33:45.095 eit: invalid tsid found tid 0x50, onid:tsid 1536:15709 != 1536:709
There are actually a LOT more of these on the same time stamp in the log but I removed like 80% of the messages to keep my comment short.
Updated by Adam Sutton over 10 years ago
- Status changed from New to Fixed
I've come to the conclusion that issues caused by stale data (which was my main concern) are not the problem here and that there are genuinely dodgy data streams out there (no surprise) so I've simply hidden the messages.
Adam