Bug #1839
EIT grab is spamming the syslog
100%
Description
When selecting the internal EPG grabber to module EIT grabber and saving it TVH doesn't show it when reloading the page, the selectionbox says "disabled". However, it does seem to be enabled since it is really spamming my syslog:
Nov 20 21:17:12 mediacenter tvheadend882: eit: grab started
Nov 20 21:17:56 mediacenter tvheadend882: eit: grab complete
Nov 20 21:17:56 mediacenter tvheadend882: subscription: "epggrab" unsubscribing
Nov 20 21:18:02 mediacenter tvheadend882: eit: grab started
Nov 20 21:18:02 mediacenter tvheadend882: mpegts: 274000 - starting for 'epggrab' (weight 2)
Nov 20 21:18:02 mediacenter tvheadend882: mpegts: 274000 - tuning on /dev/dvb/adapter0/frontend0
Nov 20 21:18:02 mediacenter tvheadend882: subscription: 'epggrab' subscribing to mux, weight: 2, adapter: '/dev/dvb/adapter0/frontend0', network: 'Caiway Gouda', mux: '274000'
Nov 20 21:18:45 mediacenter tvheadend882: eit: grab started
Nov 20 21:19:20 mediacenter tvheadend882: eit: grab started
Nov 20 21:19:52 mediacenter tvheadend882: epgdb: saved
Nov 20 21:19:52 mediacenter tvheadend882: epgdb: brands 0
Nov 20 21:19:52 mediacenter tvheadend882: epgdb: seasons 0
Nov 20 21:19:52 mediacenter tvheadend882: epgdb: episodes 24158
Nov 20 21:19:52 mediacenter tvheadend882: epgdb: broadcasts 24158
Nov 20 21:19:55 mediacenter tvheadend882: eit: grab started
Nov 20 21:21:15 tvheadend882: last message repeated 13 times
Nov 20 21:22:15 tvheadend882: last message repeated 14 times
Nov 20 21:23:00 mediacenter tvheadend882: eit: grab started
Nov 20 21:23:26 mediacenter tvheadend882: eit: grab started
Nov 20 21:24:49 mediacenter tvheadend882: eit: grab started
Nov 20 21:26:01 mediacenter tvheadend882: eit: grab started
Nov 20 21:27:12 tvheadend882: last message repeated 4 times
Nov 20 21:28:45 mediacenter tvheadend882: eit: grab started
Nov 20 21:29:20 mediacenter tvheadend882: eit: grab started
Nov 20 21:30:31 tvheadend882: last message repeated 11 times
History
Updated by Adam Sutton almost 11 years ago
Updated by - Status changed from New to Accepted
Sounds plausible, I think the EPG grab configuration is a bit "broken", someone pointed out the fact the grabbers are listed in the wrong places!
Updated by Carlo Landmeter almost 11 years ago
Updated by Adam Sutton wrote:
Sounds plausible, I think the EPG grab configuration is a bit "broken", someone pointed out the fact the grabbers are listed in the wrong places!
I wonder who that was 
(subscribed)
Updated by Dimitris Kazakos almost 11 years ago
Updated by I was wondering about the EPG grab configuration after the DVB rewrite merge, too...
Is it totally broken (ie. not worth playing with the configuration), or is there some unconventional way to change the settings until it is fixed?
Updated by Hanspeter Müller almost 11 years ago
Updated by I'm seeing a similar message, several hundred entries per minute when the eit-grabber runs (UPC DVB-C):
Dec 12 21:55:26 tvheadend721: eit: invalid tsid found tid 0x50, onid:tsid 1:58 != 1:79
Dec 12 21:55:26 tvheadend721: eit: invalid tsid found tid 0x50, onid:tsid 1:70 != 1:77
Dec 12 21:55:26 tvheadend721: eit: invalid tsid found tid 0x50, onid:tsid 1:55 != 1:71
Dec 12 21:55:26 tvheadend721: eit: invalid tsid found tid 0x50, onid:tsid 1:70 != 1:77
Dec 12 21:55:26 tvheadend721: eit: invalid tsid found tid 0x50, onid:tsid 1:58 != 1:71
Is this related/the same problem, or is there something f*****d up on UPC's EPG...?
Updated by Adam Sutton almost 11 years ago
Can you provide me a muxdump from that UPC network, I don't quite understand what is happening there. The warning is there as it can imply that stale data has go into the pipeline, but possibly there is something else going on here.
As for the general spam I'll remove that in a bit.
Adam
Updated by Adam Sutton almost 11 years ago
- Status changed from Accepted to Fixed
- % Done changed from 0 to 100
Applied in changeset tvheadend|commit:8d7839f43a782244e49c66b4f59cf91e397133d7.