Tvheadend

It seems that the tuner currently in use is still running when tvheadend is droping tuners. So if 1 tuner is in use and the other 2 is in idle only idle tuners is droped. To recover from this issue the tvheadend process need to be restarted.

It looks like a driver issue. Try to enable the powersave option which ensure that the file descriptor for the linuxdvb frontend is re-opened in each tune request.

i dont see how this could be a driver issue. server has been running for 1 year with debian 7 and backport kernel, (standard wheezy kernel has some bugs regarding the firmware that is fixed in backport) this issue staqrted to occure after upgrading to latest unstable version of tvheadend.

currently powersave is turned of and i dont see any reasons to turn it on either, i need idle scanning 24/7 .
by the way how does powersave work?

I tried to enable powersave without effect..

tvheadend fails with this logged:

Aug 19 22:59:43 tv rsyslogd-2177: imuxsock lost 90 messages from pid 2477 due to rate-limiting
Aug 19 23:01:43 tv rsyslogd-2177: imuxsock begins to drop messages from pid 2477 due to rate-limiting
Aug 19 23:01:56 tv rsyslogd-2177: imuxsock lost 202 messages from pid 2477 due to rate-limiting
Aug 19 23:19:14 tv kernel: [ 5306.946245] TCP: TCP: Possible SYN flooding on port 9981. Sending cookies. Check SNMP counters.
Aug 19 23:44:09 tv kernel: [ 6801.807074] cx88-mpeg driver manager 0000:01:08.2: DVB: adapter 2 frontend 0 frequency 9640010 out of range (950000..2150000)
Aug 19 23:44:13 tv kernel: [ 6805.806993] cx88-mpeg driver manager 0000:02:06.2: DVB: adapter 0 frontend 0 frequency 9640010 out of range (950000..2150000)
Aug 19 23:44:56 tv kernel: [ 6848.966514] cx88-mpeg driver manager 0000:01:06.2: DVB: adapter 1 frontend 0 frequency 9640010 out of range (950000..2150000)

i belive pid 2477 is the tvheadend process

Aug 20 01:29:48 tv rsyslogd-2177: imuxsock begins to drop messages from pid 2477 due to rate-limiting
Aug 20 01:31:34 tv kernel: [13246.920089] perf samples too long (2524 > 2500), lowering kernel.perf_event_max_sample_rate to 50000

this is what tvheand logs:

2014-08-20 03:53:09.024 [ ERROR]:linuxdvb: Conexant CX24116/CX24118 : DVB-S #0 - failed to tune [e=Invalid argument]

i belive its the same case, i use the 28.2e, 1w and 5e possition with idle scan so that can probably be the reason. reverting back to some older release fixes the issue.

i will test with that mux deactivated.

Raymond Paulsen wrote:

i belive its the same case, i use the 28.2e, 1w and 5e possition with idle scan so that can probably be the reason. reverting back to some older release fixes the issue.

i will test with that mux deactivated.

mux 19999.99H is deactivated, lets se how long it takes before tuners are droped again, and if that is the case

It had no effect disabling mux 19999.99H on 28.2e

Aug 20 17:07:07 tv rsyslogd-2177: imuxsock lost 37 messages from pid 23032 due to rate-limiting
Aug 20 18:11:54 tv kernel: [73266.831416] cx88-mpeg driver manager 0000:01:06.2: DVB: adapter 1 frontend 0 frequency 9640010 out of range (950000..2150000)
Aug 20 18:14:43 tv kernel: [73435.977223] cx88-mpeg driver manager 0000:01:08.2: DVB: adapter 2 frontend 0 frequency 9640010 out of range (950000..2150000)

this time only the idle tuners 2 of 3 went down, the 3 tuner was still working as it has been subscribed to.

but i think this error is not long way from the other one

i noticed a malformed mux on 5e onid 86 also. it might be this that is cousing the lockout for my case

2014-08-20 18:14:43.194 [ INFO]:mpegts: 109.99H in 5e - Viasat - Onid 86 - tuning on Conexant CX24116/CX24118 : DVB-S #2
2014-08-20 18:14:43.194 [ ERROR]:linuxdvb: Conexant CX24116/CX24118 : DVB-S #2 - failed to tune [e=Invalid argument]

109.99H

Ok it seems the problem is related to those malformed muxes.

I disabled mux 19999.99H (28.2e) and 109.99H (5e) and that seems to fix the issue.