Bug #5579
mpegts: too much queued table input data (over 2MB)
0%
Description
Hi,
I'm still getting following errors with 4.3-1784~g3f0c6b1e2.
Bugfix on ticket #4851 didn't help with my case.
I don't have OTA EPG -grabbers enabled, only internal XML grabber.
When this is happening, tvheadend stops responging and there is 100% IO with zero bytes written / read. After restarting tvheadend everything works ok for a some period of time.
Mar 15 20:30:42 tv tvheadend[12571]: mpegts: too much queued table input data (over 2MB) for TurboSight TBS 6205 DVB-T/T2/C #3 : DVB-T #0, discarding new Mar 15 20:30:51 tv tvheadend[12571]: mpegts: too much queued table input data (over 2MB) for TurboSight TBS 6205 DVB-T/T2/C #1 : DVB-T #0, discarding new Mar 15 20:30:52 tv tvheadend[12571]: mpegts: too much queued table input data (over 2MB) for TurboSight TBS 6205 DVB-T/T2/C #3 : DVB-T #0, discarding new Mar 15 20:31:01 tv tvheadend[12571]: mpegts: too much queued table input data (over 2MB) for TurboSight TBS 6205 DVB-T/T2/C #1 : DVB-T #0, discarding new Mar 15 20:31:02 tv tvheadend[12571]: mpegts: too much queued table input data (over 2MB) for TurboSight TBS 6205 DVB-T/T2/C #3 : DVB-T #0, discarding new Mar 15 20:31:11 tv tvheadend[12571]: mpegts: too much queued table input data (over 2MB) for TurboSight TBS 6205 DVB-T/T2/C #1 : DVB-T #0, discarding new Mar 15 20:31:12 tv tvheadend[12571]: mpegts: too much queued table input data (over 2MB) for TurboSight TBS 6205 DVB-T/T2/C #3 : DVB-T #0, discarding new Mar 15 20:31:15 tv tvheadend[12571]: mpegts: too much queued table input data (over 2MB) for TurboSight TBS 6205 DVB-T/T2/C #2 : DVB-T #0, discarding new Mar 15 20:31:21 tv tvheadend[12571]: mpegts: too much queued table input data (over 2MB) for TurboSight TBS 6205 DVB-T/T2/C #1 : DVB-T #0, discarding new Mar 15 20:31:22 tv tvheadend[12571]: mpegts: too much queued table input data (over 2MB) for TurboSight TBS 6205 DVB-T/T2/C #3 : DVB-T #0, discarding new Mar 15 20:31:25 tv tvheadend[12571]: mpegts: too much queued table input data (over 2MB) for TurboSight TBS 6205 DVB-T/T2/C #2 : DVB-T #0, discarding new Mar 15 20:31:31 tv tvheadend[12571]: mpegts: too much queued table input data (over 2MB) for TurboSight TBS 6205 DVB-T/T2/C #1 : DVB-T #0, discarding new Mar 15 20:31:32 tv tvheadend[12571]: mpegts: too much queued table input data (over 2MB) for TurboSight TBS 6205 DVB-T/T2/C #3 : DVB-T #0, discarding new Mar 15 20:31:35 tv tvheadend[12571]: mpegts: too much queued table input data (over 2MB) for TurboSight TBS 6205 DVB-T/T2/C #2 : DVB-T #0, discarding new Mar 15 20:31:41 tv tvheadend[12571]: mpegts: too much queued table input data (over 2MB) for TurboSight TBS 6205 DVB-T/T2/C #1 : DVB-T #0, discarding new Mar 15 20:31:42 tv tvheadend[12571]: mpegts: too much queued table input data (over 2MB) for TurboSight TBS 6205 DVB-T/T2/C #3 : DVB-T #0, discarding new Mar 15 20:31:45 tv tvheadend[12571]: mpegts: too much queued table input data (over 2MB) for TurboSight TBS 6205 DVB-T/T2/C #2 : DVB-T #0, discarding new
History
Updated by Jarmo Kivirinta over 5 years ago
saen acro wrote:
Descrambling used?
No descrabling used.
Flole Systems wrote:
Use GDB to figure out what's going on there
I'll try this next time process freezes and post results
Updated by Flole Systems over 5 years ago
You can also get a coredump then so you don't have to leave it in stucked state, I know that situation very well: Sometimes you really want to watch something and don't have time to debug at that moment, using gdb to generate a coredump and load it later on to look at when was going on there.