Opened 11 years ago

Closed 11 years ago

#3024 closed defect (fixed)

OSCAM shut down after SIGHUP signal

Reported by: gorro Owned by:
Priority: minor Component: General
Severity: low Keywords:
Cc: Sensitive: no

Description

Revision

oscam-1.20-unstable_svn-r8021

Issue Description

OSCAM shut down after SIGHUP signal

When the issue occurs

after send
killall -SIGHUP oscam

i not show any oscam prosess in ps

Change History (9)

comment:1 by ni hao, 11 years ago

too less info

comment:2 by ni hao, 11 years ago

Priority: majorminor
Resolution: invalid
Severity: mediumlow
Status: newclosed

comment:3 by gorro, 11 years ago

Resolution: invalid
Status: closedreopened

i now use this latest Oscam binary:

http://www.streamboard.tv/wbb2/attachment.php?attachmentid=36275
from
http://www.streamboard.tv/wbb2/thread.php?postid=443749#post443749

and use FBF7390 (128MB RAM) with latest stocking INTL firmware (kernel 2.6.28.10 #1 Fri Apr 20 12:19:44 CEST 2012 mips GNU/Linux), all work well...

After i send via telnet command:

killall -SIGHUP oscam

then oscam kill instead of reload settings. Then i not know, where is bug?

Here is some info from OS:

# killall --help
BusyBox v1.18.5 (2011-10-27 16:00:43 CEST) multi-call binary.
# killall -l
HUP
INT
QUIT
ILL
TRAP
ABRT
FPE
KILL
BUS
SEGV
SYS
PIPE
ALRM
TERM
USR1
USR2
CHLD
PWR
WINCH
URG
POLL
STOP
TSTP
CONT
TTIN
TTOU
VTALRM
PROF
XCPU
XFSZ

Then signal HUP is supported, i think. Maybe is this busybox bugged?


Now i use for restart:

killall -9 oscam;oscam

but i think, somewhere is bug about ...

If anyone know better cfg reloading method for oscam, then please note me, thx.

Last edited 11 years ago by gorro (previous) (diff)

comment:4 by Admin, 11 years ago

If you don't kill with killall but with a specific process id: Does it also crash?

comment:5 by gorro, 11 years ago

but i have more PIDs:
ps

4095 root 4024 S ./oscam -r 2 -Sbc cfg -d 255
4096 root 5176 S < ./oscam -r 2 -Sbc cfg -d 255
4097 root 5176 S < ./oscam -r 2 -Sbc cfg -d 255
4098 root 5176 S < ./oscam -r 2 -Sbc cfg -d 255
4099 root 5176 S < ./oscam -r 2 -Sbc cfg -d 255
4100 root 5176 S < ./oscam -r 2 -Sbc cfg -d 255
4101 root 5176 S < ./oscam -r 2 -Sbc cfg -d 255
4102 root 5176 S < ./oscam -r 2 -Sbc cfg -d 255
4103 root 5176 S < ./oscam -r 2 -Sbc cfg -d 255
4106 root 5176 S < ./oscam -r 2 -Sbc cfg -d 255

10303 root 5176 S < ./oscam -r 2 -Sbc cfg -d 255
13176 root 5176 S < ./oscam -r 2 -Sbc cfg -d 255

how is recomended syntax for reload cfg ?

comment:6 by Admin, 11 years ago

Just try a bit (I would try the lowest pid and the second-lowest one) if that would fix it and if so we can maybe fix it in a way that killall will work in the future.

comment:7 by gorro, 11 years ago

Please write me what exactly do I send the console to try out, thanks.

comment:8 by Admin, 11 years ago

You did the "ps" and that got a list of pids. Now try what happens if you kill the lowest pid, so in your example

kill 4095

The next time you startup you will get other pids. Just try to kill the second lowest one, so in your example

kill 4096

comment:9 by gf, 11 years ago

Resolution: fixed
Status: reopenedclosed
killall -HUP oscam

Once we have pidfile (see ticket #3079) you can use

kill -HUP `cat oscam.pid`

If you have problems, please open other tickets (or ask in the forum) because this ticket is fixed.

Note: See TracTickets for help on using tickets.