minisatip and satip-receiver and oscam

Support forum for minisatip
woec007
Posts: 12
Joined: Mon Jun 19, 2017 7:25 pm

Re: minisatip and satip-receiver and oscam

Post by woec007 »

Hi,

after some days of operation, I can tell the following observations:
setting dvbapi_offset on the vdr client seems to work - no further access problems running two clients on oscam server (at least by using vdr clients). It seems that this parameter does not work when set in minisatip.

Despite this, I have crashes of minisatip after some time running, tail of log before crash shows:
.....
[12/07 19:55:51.342 main]: reply -> 11 (192.168.129.8:59878) CL:0 [sock_id 11]:
[12/07 19:55:51.344 AD0]: Start streaming for stream 0, len 1316 to handle 10 => 192.168.129.8:45950
[12/07 19:55:51.672 signal]: BW 1273KB/s, Total BW: 2669 MB, ns/read 2314, r: 375, w: 1013 fw: 0, tt: 868 ms
RECEIVED SIGNAL 11 - SP=0 IP=0
Obtained 0 stack frames.

Further point: is it possible to reduce the log intensity? - the log file crows quite fast when clients are running (without any -l options set)

Thanks,
woec
cata
Site Admin
Posts: 768
Joined: Tue May 12, 2015 1:01 am

Re: minisatip and satip-receiver and oscam

Post by cata »

HI,

yes I will reduce it if u do not need -l.

About the crash, run:

gdb --args ./minisatip .....


and the when it breaks, run:

bt
thread apply all bt

Thanks
woec007
Posts: 12
Joined: Mon Jun 19, 2017 7:25 pm

Re: minisatip and satip-receiver and oscam

Post by woec007 »

Hi,

I tried to run by gdb, but I get an error - see below:

gdb --args /usr/local/bin/minisatip -H 1:5 -b 4042752 -B 10000 -o 127.0.0.1:2000 -s 192.168.129.20 -s 192.168.129.20 -R /usr/local/src/minisatip-0.7-ca/html -t
GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
Type "show configuration" for configuration details.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/local/bin/minisatip...done.
(gdb) run
Starting program: /usr/local/bin/minisatip -H 1:5 -b 4042752 -B 10000 -o 127.0.0.1:2000 -s 192.168.129.20 -s 192.168.129.20 -R /usr/local/src/minisatip-0.7-ca/html -t
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Cannot access memory at address 0x0

Program received signal SIGILL, Illegal instruction.
0xb6ebbe68 in ?? () from /usr/lib/arm-linux-gnueabihf/libcrypto.so.1.0.0
(gdb) quit

Further, I noticed you modified the 0.7-ca branch of the git repository. So I tried the actual branch checkout, but dvbapi (use of oscam) does not work at all with this version.

Thank you,

woec
cata
Site Admin
Posts: 768
Joined: Tue May 12, 2015 1:01 am

Re: minisatip and satip-receiver and oscam

Post by cata »

Compile again minisatip:

make clean
make DVBAES=0

Then run the command again

Thank you
woec007
Posts: 12
Joined: Mon Jun 19, 2017 7:25 pm

Re: minisatip and satip-receiver and oscam

Post by woec007 »

Hi,

I did it as you adviced.
After crash of minisatip I executed bt and thread apply all bt.
The message of the debugger was: No stack.
Below the session sequence:
(gdb) run
Starting program: /usr/local/bin/minisatip -H 1:5 -b 4042752 -B 10000 -o 127.0.0.1:2000 -s 192.168.129.20 -s 192.168.129.20 -R /usr/local/src/minisatip-0.7-ca/html -t
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[27/07 10:46:56.501 main]: Could not ignore signal SIGPIPE
[27/07 10:46:56.501 main]: running minisatip in background and logging to /tmp/minisatip.log
[Inferior 1 (process 31393) exited normally]
(gdb) bt
No stack.
(gdb) thread apply all bt

Please give me additional advice.
Thanks
cata
Site Admin
Posts: 768
Joined: Tue May 12, 2015 1:01 am

Re: minisatip and satip-receiver and oscam

Post by cata »

Hi,

Use -f as well

Thanks
woec007
Posts: 12
Joined: Mon Jun 19, 2017 7:25 pm

Re: minisatip and satip-receiver and oscam

Post by woec007 »

Hi,

ok, here is the debugger output on crash:
Program received signal SIGSEGV, Segmentation fault.
0xb6eeac2e in strlen () from /lib/arm-linux-gnueabihf/libc.so.6
(gdb) bt
#0 0xb6eeac2e in strlen () from /lib/arm-linux-gnueabihf/libc.so.6
#1 0xb6ec60c2 in vfprintf () from /lib/arm-linux-gnueabihf/libc.so.6
#2 0xb6ee0244 in vsnprintf () from /lib/arm-linux-gnueabihf/libc.so.6
#3 0x0002512c in _log (file=0x40930 "utils.c", line=1186,
fmt=0x412e4 "%s:%d Locked %p after %ld ms, previously locked at: %s, line %d") at utils.c:640
#4 0x000274e4 in mutex_lock1 (FILE=0x3dd98 "socketworks.c", line=423, mutex=0x68ce0) at utils.c:1186
#5 0x00017e78 in sockets_lock (ss=0x68768) at socketworks.c:423
#6 0x00018b1c in select_and_execute (arg=0x0) at socketworks.c:671
#7 0x00016892 in main (argc=17, argv=0xbefff6f4) at minisatip.c:1607
(gdb) thread apply all bt

Thread 3 (Thread 0xb61232c0 (LWP 15084)):
#0 0xb6fc1544 in __libc_do_syscall () from /lib/arm-linux-gnueabihf/libpthread.so.0
#1 0xb6fbf1c0 in __lll_lock_wait () from /lib/arm-linux-gnueabihf/libpthread.so.0
#2 0xb6fbb996 in pthread_mutex_lock () from /lib/arm-linux-gnueabihf/libpthread.so.0
#3 0x000273fc in mutex_lock1 (FILE=0x3ed5c "stream.c", line=1178, mutex=0x68ce0) at utils.c:1171
#4 0x0001debe in lock_streams_for_adapter (aid=0) at stream.c:1178
#5 0x0001d6ea in read_dmx (s=0x685d8) at stream.c:1054
#6 0x00018f86 in select_and_execute (arg=0x671c0) at socketworks.c:744
#7 0xb6fb9f88 in start_thread () from /lib/arm-linux-gnueabihf/libpthread.so.0
#8 0xb6f270fc in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 2 (Thread 0xb6e912c0 (LWP 15083)):
#0 0xb6f208d0 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
#1 0xb6f208ca in poll () from /lib/arm-linux-gnueabihf/libc.so.6
#2 0x00000000 in ?? ()

Thread 1 (Thread 0xb6ff0000 (LWP 15080)):
#0 0xb6eeac2e in strlen () from /lib/arm-linux-gnueabihf/libc.so.6
#1 0xb6ec60c2 in vfprintf () from /lib/arm-linux-gnueabihf/libc.so.6
#2 0xb6ee0244 in vsnprintf () from /lib/arm-linux-gnueabihf/libc.so.6
#3 0x0002512c in _log (file=0x40930 "utils.c", line=1186,
fmt=0x412e4 "%s:%d Locked %p after %ld ms, previously locked at: %s, line %d") at utils.c:640
#4 0x000274e4 in mutex_lock1 (FILE=0x3dd98 "socketworks.c", line=423, mutex=0x68ce0) at utils.c:1186
#5 0x00017e78 in sockets_lock (ss=0x68768) at socketworks.c:423
#6 0x00018b1c in select_and_execute (arg=0x0) at socketworks.c:671
#7 0x00016892 in main (argc=17, argv=0xbefff6f4) at minisatip.c:1607
(gdb)

Maybe it helps to find the problem ...

Thanks,
woec
cata
Site Admin
Posts: 768
Joined: Tue May 12, 2015 1:01 am

Re: minisatip and satip-receiver and oscam

Post by cata »

Yes it does help.

Thanks
woec007
Posts: 12
Joined: Mon Jun 19, 2017 7:25 pm

Re: minisatip and satip-receiver and oscam

Post by woec007 »

Hi,

today I tried the actual 0.7-ca branch (assuming you implemented some improvements solving the crash problem) - but without success.
FTA channels work, but using oscam server over dvbapi does not (dark screen).
Below I enclose the logfile (created with options -l satipc,http).
I noticed, that the executeable file of this compile is significant smaller than the older (which works with oscam)

Thanks,
woec
Attachments
minisatip-log.tgz
(45.25 KiB) Downloaded 395 times
Post Reply