Frage: Oscam + ffdecsawrapper + dvbapi? Verständnisproblem

[zaphod_muc]

Hallo!

Seit ca. 3 Wochen habe ich auf meinem Ubuntu Server oscam (mit easymouse2 und weißer HD+ Karte) am laufen mit ffdecsawrapper (über newcamd Protokoll verbunden), um an zwei DVB-S2 Karten HD+ zu entschlüsseln.

Ich habe das Problem, das Aufnahmen oft Aussetzer haben (ca. 20 Sekunden lang), mit folgendem Output in der ffdecsawrapper.log:

Spoiler

Jun 17 16:40:24.568 CSA: Got command(2): O idx: 1 pid: 0 key: 1729...11
Jun 17 16:40:50.147 CAM(core.net): socket: select timed out (20000 ms)
Jun 17 16:40:50.147 CAM(cardclient.core): recv error. reconnecting...
Jun 17 16:40:50.147 CAM(cardclient.newcamd): failed to read message length
Jun 17 16:40:50.147 CAM(cardclient.newcamd): unexpected server response (code 0)
Jun 17 16:40:50.147 CAM(cardclient.core): client Newcamd (192.168.0.1:10002) ECM failed (20020 ms)
Jun 17 16:40:50.148 CAM(cardclient.core): cc-loop
Jun 17 16:40:50.148 CAM(core.ecm): 0.2: filter flush (elapsed 20021)
Jun 17 16:40:50.148 CAM(core.ecm): 0.2: lost sync (period 7002, elapsed 26728)
Jun 17 16:40:50.147 CAM(general.error): action logger 0/0 read: Buffer overflow
Jun 17 16:40:50.148 CAM(general.error): action logger 0/1 read: Buffer overflow
Jun 17 16:40:50.148 CAM(core.net): connecting to 192.168.0.1:10002/tcp (192.168.0.1)
Jun 17 16:40:50.151 CAM(cardclient.login): Newcamd: CaID=1830 admin=1 srvUA=0000000048BCB112 provider 008011/0000000048BC0000 <unhandled> 000000/0000000048BC0000 <unhandled> 003411/0000000048BC0000 <unhandled>
Jun 17 16:40:50.434 CAM(cardclient.core): Tue Jun 17 16:40:50 2014: lagged cw 19158 ms (Newcamd)
Jun 17 16:40:50.434 CSA: Got command(2): E idx: 1 pid: 0 key: 7f26...d0
Jun 17 16:40:50.434 CAM(general.error): action ecmhandler 0/0 read: Buffer overflow
Jun 17 16:40:50.731 CSA: Got command(2): E idx: 2 pid: 0 key: b087...95
Jun 17 16:40:50.731 CSA: Got command(2): O idx: 2 pid: 0 key: bc9e...45
Jun 17 16:40:50.731 CAM(core.ecm): 0.2: correct key found

Dieses Problem geht weg, wenn ich in der oscam.conf dvbapi einschalte durch:

Spoiler

[dvbapi]
enabled = 1
user = mythtv
group = mythtv

Und hier habe ich mein Verständnisproblem: DVB, Zugriff auf die Devices, Entschlüsselung wird doch eigentlich durch ffdecsawrapper gemacht. Außerdem könnte ich ja oscam auch auf einer ganz anderen Box laufen haben als ffdecsawrapper, und die dvbapi macht ja wohl nur sinn, wenn oscam lokal bei den DVB Adaptern läuft...

Also ist mein Verdacht, dass die Aussetzer nur zufällig durch den start der dvbapi weggehen und ich eigentlich noch einen Fehler in meiner Konfiguration habe... liege ich da falsch? Ich kopiere meine Konfiguration mal ganz unten rein.

Vielleicht bekomme ich von den Experten hier ja einen Tip - ich weiß ehrlich gesagt nicht bei allem, was ich mir da zusammenkopiert habe, was es bedeutet :-(

Vielen Dank & Viele Grüße

Zaphod

Meine Konfiguration:
oscam.conf

Spoiler

#
# main configuration
#

[global]
nice = -1
WaitForCards = 1
preferlocalcards = 1
#lb_mode = 1
#lb_save = 150
maxlogsize = 2000
ecmfmt = c&p/d/s/l:h
ecmcache = 0

# logging

logfile = /var/log/oscam/oscam.log
usrfile = /var/log/oscam/oscamuser.log
cwlogdir = /var/log/oscam/cw

# monitor

[monitor]
port = 988
aulow = 120
monlevel = 1

# web interface

[webif]
httpport = 3001
httpuser = mythtv
httppwd = mythtv
httpallowed = 127.0.0.1,192.168.0.0-192.168.0.255,::1

# anti-cascading

[anticasc]
enabled = 1
numusers = 1
sampletime = 2
samples = 5
penalty = 1
aclogfile = /var/log/oscam/aclog.log
denysamples = 9

# protocols

[newcamd]
key = 0102030405060708091011121314
port = 10002@1830:003411

#[radegast]
#port = 20000
#user = user1
#allowed = 192.168.0.0-192.168.0.255

#[cs378x]
#port = 30000@0100:FFFFFF;30001@0200:FFF000,FFFF00;30002@0300:FFFFFF

#[cccam]
#port = 40000
#version = 1.2.3
#build = 1234
#reshare = 2

#[gbox]
#hostname = host.example.com
#port = 50000
#password = password1

#[serial]
#device = user2@/dev/ttyS0?delay=1&timeout=300;user3@192.160.0.10,2006?delay=1&timeout=5000

[dvbapi]
enabled = 1
user = mythtv
group = mythtv
#boxtype = PC
#au = 1

oscam.dvbapi

Spoiler

#
# dvbapi configuration
#
# types:
# P - Priority
# format:
# P: <caid>:[<provider>]:[<srvid>]:[<ecmpid>]:[<irdeto chid>]
# I - Ignore
# format:
# I: <caid>:[<provider>]:[<srvid>]:[<ecmpid>]:[<irdeto chid>]
# M - Map
# format:
# M: <caid>:[<provider>]:[<srvid>]:[<ecmpid>] <target caid >:[<target provider>]
# D - Delay
# format:
# D: <caid>:[<provider>]:[<srvid>]:[<ecmpid>] <delay (ms)>
#
#

# HDplus HD01 Card (white)
#M: 1830 1830:003411
P: 1830:000000
I: 1834:000000

oscam.server

Spoiler

#---Oscam Config Creator---

[reader]

Label = HDplus
Protocol = mouse
Device = /dev/ttyUSB0
#Mhz = 600
#cardmhz = 600
Detect = CD
Group = 1
CAID = 1830
EMMCache = 1,3,2
rsakey = BF_dieserTeilgelöscht_D5
boxkey = A_dieserTeilauch_C
blockemm-unknown = 1
blockemm-g = 1
dropbadcws = 1
ecmcache = 0

oscam.services

Spoiler

[hdplus]
caid=1830
provid=000000,003411,008011
srvid=277E,EF10,EF11,EF14,EF15,EF74,EF75,EF76,EF77

oscam.user

Spoiler

[account]
user = mythtv
pwd = mythtv
group = 1
au = 1

und schliesslich, /etc/default/ffdecsawrapper:

Spoiler

# Run as <username>, don't run as root.
# USER must be member of the video group in order to get access to adapters
# Do: usermod -a -G video <username> to add USER to the video group.

USER="ffdecsawrapper"



# Number of real adapters installed in your system
# Count starts at 0 (zero), so if you have 2, choose 1

ADAPTERS="2"

# Number of adapters dedicated to ffdecsawrapper
# Maximum is 4 because max 8 adapters are permitted in your system.
# (4 real + 4 loopback) If you need more, like me, recompile your kernel.
# So if you have 2 adapters, you need to set "-j a:c -j b:d" in JOIN=" "
# In this case, count starts at 1. I know, it's a bit confusing...

NUMADAPTERS="2"

# Number of seconds delay you need before (re)loading dvbloopback and other components.
# On Debian 2 or 3 is fine

DELAY="3"

# How nice we are. (must be positive or 0, we don't run as root
# Setting it to a positive value makes sure that your system will be
# accessible, even when things go wrong.

NICE="5"

IONICE="real-time:5"

# Combine (some of) your real adapters with loopback adapters
# Example: assuming you have 5 real adapters installed in your system
# The first two of them are in use with Tvheadend or some other program
# Number 3, 4 and 5 will be used by MythTV
# Then you should set: -j 2:5 -j 3:6 -j 4:7

JOIN='--join 0:2 --join 1:3'


# We are going to check if the dvbloopback module is loaded before we start ffdecsawrapper.
# If it is not loaded, we are attempting to load the module several times again.
# Max times to try

RUNLOOP="10"

# Time between two attempts to load dvbloopback module (in seconds)
# Reccomended minimum is 5 secs

SECLOOP="5"

# The directory in which you have placed the cam files needed
# to communicate with Oscam or other cardserver

CAMDIR="/etc/ffdecsawrapper"


# Other options to pass to ffdecsawrapper
# N.B.: One user reported that --buffer 8M works, and --buffer 16M crashes ffdecsawrapper.
# This probably has something to do with the (lack of) 'vmalloc' settings in /etc/default/grub.
# But I did not test it yet.

#OPTS="--cam-budget --sid-allpid --sid-filt 20 --buffer 16M " #--debug 1006633791"
OPTS="--cam-budget --sid-allpid --sid-filt 20 --buffer 16M --debug 0"
# Pid dir

PIDDIR="/var/run/ffdecsawrapper"

# Pid file

PID="ffdecsawrapper.pid"

# ffdecsawrapper logfile

LOG="ffdecsawrapper.log"

# where to put the ffdecsawrapper log

LOGDIR="/var/log/ffdecsawrapper"

# Name of the database for MythTV

DATABASENAME="mythconverg"

# Set this to 1 once you are done configuring.
ENABLED="1"