Bug #4071
Sometimes oscam answer ecm request but tvheadend says descrambler: cannot decode packets for service
0%
Description
Sometimes oscam answer ecm request but tvheadend says descrambler: cannot decode packets for service
check logs
Files
History
Updated by Joe User about 8 years ago
I do not have time to fully examine the logs, but a few things I noticed are:
1. you are descrambling multiple channels at the same time - is this always the case when it happens? If not can you provide the logs with only one channel so it is easier to follow?
2. It appears you have the same channel twice with slightly different names??
2016-11-05 16:18:50.044 [ TRACE]:descrambler: Obtained keys 0000000000000000:9F37EFC5C7973B99 from capmt-/tmp/camd.socket for service "SPORT TV 1 HD"
2016-11-05 16:18:50.044 [ TRACE]:descrambler: Obtained keys 0000000000000000:9F37EFC5C7973B99 from capmt-/tmp/camd.socket for service "Sport TV 1 HD"
3. have you tried using mode 5 (network connection) to oscam?
4. Does the channel stop descrambling completely, or is it an intermittent problem?
Updated by Jaroslav Kysela about 8 years ago
TVH didn't receive keys from oscam when decoding does not work. As suggested - try to use the 127.0.0.1 network connection, it appears from other reports that the socket mode (/tmp/camd.socket) is somewhat broken in latest oscam.
Updated by Ricardo Rocha almost 8 years ago
Jaroslav Kysela wrote:
TVH didn't receive keys from oscam when decoding does not work. As suggested - try to use the 127.0.0.1 network connection, it appears from other reports that the socket mode (/tmp/camd.socket) is somewhat broken in latest oscam.
ok i will try...
Updated by Ricardo Rocha almost 8 years ago
Joe User wrote:
I do not have time to fully examine the logs, but a few things I noticed are:
1. you are descrambling multiple channels at the same time - is this always the case when it happens? If not can you provide the logs with only one channel so it is easier to follow?
2. It appears you have the same channel twice with slightly different names??
2016-11-05 16:18:50.044 [ TRACE]:descrambler: Obtained keys 0000000000000000:9F37EFC5C7973B99 from capmt-/tmp/camd.socket for service "SPORT TV 1 HD"
2016-11-05 16:18:50.044 [ TRACE]:descrambler: Obtained keys 0000000000000000:9F37EFC5C7973B99 from capmt-/tmp/camd.socket for service "Sport TV 1 HD"3. have you tried using mode 5 (network connection) to oscam?
4. Does the channel stop descrambling completely, or is it an intermittent problem?
1 - yes i am opening multiple channels... but this happen with a single descramble or when doing multiple ones.
2 - those are the same channel from different provider and different caid so guess the problem is not that.
3 - never used it... will try... what about mode 6?
4 - when this happen the channel never came back... restart needed to descramble again
Updated by Joe User almost 8 years ago
mode was referring to Tvheadend mode: http://docs.tvheadend.org/webui/config_caclient/
In CA tab set:
Mode: OSCam net protocol (rev >= 10389)
Camd.socket filename / IP Address (TCP mode): 127.0.0.1
Listen / Connect port: 9000
In oscam use:
boxtype = pc
pmt_mode = 4
listen_port = 9000
Updated by Ricardo Rocha almost 8 years ago
Joe User wrote:
mode was referring to Tvheadend mode: http://docs.tvheadend.org/webui/config_caclient/
In CA tab set:
Mode: OSCam net protocol (rev >= 10389)
Camd.socket filename / IP Address (TCP mode): 127.0.0.1
Listen / Connect port: 9000
In oscam use:
boxtype = pc
pmt_mode = 4
listen_port = 9000
after a few days with that setup the problem still not solved.... however it happens a lot less than with previous one.
any other hint?
Updated by piotr galek almost 8 years ago
i hade some problem and nothing help
in log oscam i have perfect eveything all DW shiped to Tvheaded (no any late key, or timeout - all time from local card 250ms)
But tvheadend say - key odd late or something smillar after that even after some time start working recording only growing into big number of errors in stream
Updated by Jaroslav Kysela almost 8 years ago
When I analyzed the logs, the problem was on the oscam side - although oscam handled (and logged) the right ECM reply, it was lost in the dvbapi module (in oscam). Tvheadend has not received the reply.
You can debug this using '--trace descrambler,capmt' in tvheadend and 'debug 128' log in oscam and compare the logs from both sides (you may also attach this here or create a new issue).
Updated by Ricardo Rocha almost 8 years ago
i can confirm also the behaviour continues even with last oscam 11289... perexg do you need more logs?
Updated by Jaroslav Kysela almost 8 years ago
Yes, provide logs from tvh and oscam as described in comment 8 (only around time when things are not working 60 seconds before and 60 seconds after).
Updated by piotr galek almost 8 years ago
im tried switch mode from net on no-dmx etc. but nothing help
please look
http://pastebin.com/jDZVbDGi
http://pastebin.com/KuSeHKCC
and compare times from both - logs
2016-12-20 19:06:03.988 descrambler: ECM - key late (17614 ms) (17 sec ??? )
some ECM just gone somewhere ...
Updated by Joe User almost 8 years ago
You need to provide oscam log with debug level set to 128 and use the trace options for tvheadend...
Updated by piotr galek almost 8 years ago
@Ricardo Rocha do you using tvheadend build with libdvbcsa ?
becuase we had 2 diffrent system LE and Ubuntu - and same issue - and only we ... im interested why ...
Yesterday im builded without libdvbcsa, like defaut tvheadend with FFdcsa so far - no any issue ... but i will keep test 2-3 days more ...
Updated by piotr galek almost 8 years ago
Hi Jaroslav Kysela im on #hts irc with logs, please catch me there