Alert: Don't Use Hotmail Email Accounts for registration

**gpaolobvt** · 11-30-2013, 06:57 AM

Re: How to made check script for CCcam 64-bit ?

Hello,
i think the problem is not in the script.

Infact the script just check if CCcam.x86 is present in the list of process that are active.

Ps command create this list.
Grep browse in the list, created by PS, check if CCcam.x86 exist.

So, the problem is that the 64bit version of this program may have a different name (maybe CCcam.x64 or like so).

In case you can connect to the system with telnet, you can manually start your CCCam, then by typing the command "ps auxwww" or simply ps, you will see the list...

Then you can find in the list what is the name of the process, and enter it in your script.

You can also change the script to look for both version (32 and 64)

Then, when executing the script, it browses the process and look for its existence.

Bye

**aplok** · 11-30-2013, 07:27 AM

Re: How to made check script for CCcam 64-bit ?

Originally posted by SatWaveDude

Can someone explaint how to made a check script for a 64-bit CCcam?

**SatWaveDude** · 12-01-2013, 07:58 PM

Re: How to made check script for CCcam 64-bit ?

Originally posted by gpaolobvt

Hello,
i think the problem is not in the script.

Infact the script just check if CCcam.x86 is present in the list of process that are active.

Ps command create this list.
Grep browse in the list, created by PS, check if CCcam.x86 exist.

So, the problem is that the 64bit version of this program may have a different name (maybe CCcam.x64 or like so).

In case you can connect to the system with telnet, you can manually start your CCCam, then by typing the command "ps auxwww" or simply ps, you will see the list...

Then you can find in the list what is the name of the process, and enter it in your script.

You can also change the script to look for both version (32 and 64)

Then, when executing the script, it browses the process and look for its existence.

Bye

I have check it and these are the namen of CCcam:

32-bit = CCcam.x86
64-bit = CCcam.x86_64

As the command "ps auxwww" gives me:

Code:

~# ps auxwww
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.0  10644   824 ?        Ss   Nov30   0:02 init [2]
root         2  0.0  0.0      0     0 ?        S    Nov30   0:00 [kthreadd]
root         3  0.0  0.0      0     0 ?        S    Nov30   0:04 [ksoftirqd/0]
root         6  0.0  0.0      0     0 ?        S    Nov30   0:00 [migration/0]
root         7  0.0  0.0      0     0 ?        S    Nov30   0:00 [watchdog/0]
root         8  0.0  0.0      0     0 ?        S    Nov30   0:00 [migration/1]
root        10  0.0  0.0      0     0 ?        S    Nov30   0:02 [ksoftirqd/1]
root        12  0.0  0.0      0     0 ?        S    Nov30   0:00 [watchdog/1]
root        13  0.0  0.0      0     0 ?        S<   Nov30   0:00 [cpuset]
root        14  0.0  0.0      0     0 ?        S<   Nov30   0:00 [khelper]
root        15  0.0  0.0      0     0 ?        S    Nov30   0:00 [kdevtmpfs]
root        16  0.0  0.0      0     0 ?        S<   Nov30   0:00 [netns]
root        17  0.0  0.0      0     0 ?        S    Nov30   0:00 [sync_supers]
root        18  0.0  0.0      0     0 ?        S    Nov30   0:00 [bdi-default]
root        19  0.0  0.0      0     0 ?        S<   Nov30   0:00 [kintegrityd]
root        20  0.0  0.0      0     0 ?        S<   Nov30   0:00 [kblockd]
root        21  0.0  0.0      0     0 ?        S    Nov30   0:00 [khungtaskd]
root        22  0.0  0.0      0     0 ?        S    Nov30   0:00 [kswapd0]
root        23  0.0  0.0      0     0 ?        SN   Nov30   0:00 [ksmd]
root        24  0.0  0.0      0     0 ?        SN   Nov30   0:00 [khugepaged]
root        25  0.0  0.0      0     0 ?        S    Nov30   0:00 [fsnotify_mark]
root        26  0.0  0.0      0     0 ?        S<   Nov30   0:00 [crypto]
root        98  0.0  0.0      0     0 ?        S    Nov30   0:00 [khubd]
root       121  0.0  0.0      0     0 ?        S<   Nov30   0:00 [ata_sff]
root       133  0.0  0.0      0     0 ?        S    Nov30   0:00 [scsi_eh_0]
root       134  0.0  0.0      0     0 ?        S    Nov30   0:00 [scsi_eh_1]
root       135  0.0  0.0      0     0 ?        S    Nov30   0:00 [scsi_eh_2]
root       136  0.0  0.0      0     0 ?        S    Nov30   0:00 [scsi_eh_3]
root       138  0.0  0.0      0     0 ?        S    Nov30   0:00 [kworker/u:2]
root       139  0.0  0.0      0     0 ?        S    Nov30   0:00 [kworker/u:3]
root       177  0.0  0.0      0     0 ?        S    Nov30   0:00 [jbd2/sda1-8]
root       178  0.0  0.0      0     0 ?        S<   Nov30   0:00 [ext4-dio-unwrit]
root       313  0.0  0.0  21632  1552 ?        Ss   Nov30   0:00 udevd --daemon
root       368  0.0  0.0  21628  1160 ?        S    Nov30   0:00 udevd --daemon
root       369  0.0  0.0  21628  1040 ?        S    Nov30   0:00 udevd --daemon
root       390  0.0  0.0      0     0 ?        S<   Nov30   0:00 [hd-audio0]
root       407  0.0  0.0      0     0 ?        S<   Nov30   0:00 [kpsmoused]
root      1185  0.0  0.0      0     0 ?        S    Nov30   0:00 [jbd2/sda9-8]
root      1186  0.0  0.0      0     0 ?        S<   Nov30   0:00 [ext4-dio-unwrit]
root      1187  0.0  0.0      0     0 ?        S    Nov30   0:00 [jbd2/sda8-8]
root      1188  0.0  0.0      0     0 ?        S<   Nov30   0:00 [ext4-dio-unwrit]
root      1189  0.0  0.0      0     0 ?        S    Nov30   0:00 [jbd2/sda5-8]
root      1190  0.0  0.0      0     0 ?        S<   Nov30   0:00 [ext4-dio-unwrit]
root      1191  0.0  0.0      0     0 ?        S    Nov30   0:03 [jbd2/sda6-8]
root      1192  0.0  0.0      0     0 ?        S<   Nov30   0:00 [ext4-dio-unwrit]
root      1209  0.0  0.0      0     0 ?        S    02:25   0:06 [kworker/0:1]
root      1452  0.0  0.0  18968   888 ?        Ss   Nov30   0:00 /sbin/rpcbind -w
statd     1485  0.0  0.0  23340  1340 ?        Ss   Nov30   0:00 /sbin/rpc.statd
root      1491  0.0  0.0      0     0 ?        S<   Nov30   0:00 [rpciod]
root      1493  0.0  0.0      0     0 ?        S<   Nov30   0:00 [nfsiod]
root      1500  0.0  0.0  25288   428 ?        Ss   Nov30   0:00 /usr/sbin/rpc.idmapd
root      1760  0.0  0.0  52932  1636 ?        Sl   Nov30   0:01 /usr/sbin/rsyslogd -c5
root      1838  0.0  0.0   4112   652 ?        Ss   Nov30   0:00 /usr/sbin/acpid
root      1874  0.0  0.2 132156 11636 ?        Ss   Nov30   0:03 /usr/sbin/apache2 -k start
root      1904  0.0  0.0  10408   816 ?        Ss   Nov30   0:02 /usr/sbin/inadyn
daemon    1933  0.0  0.0  16668   152 ?        Ss   Nov30   0:00 /usr/sbin/atd
106       1993  0.0  0.0  29800   464 ?        Ss   Nov30   0:00 /usr/bin/dbus-daemon --system
root      1995  0.0  0.0  20920   920 ?        Sl   Nov30   0:00 /usr/sbin/pcscd
root      1998  0.0  0.0  20404  1056 ?        Ss   Nov30   0:00 /usr/sbin/cron
101       2337  0.0  0.0  46804  1056 ?        Ss   Nov30   0:00 /usr/sbin/exim4 -bd -q30m
root      2387  0.0  0.0  16252   948 tty1     Ss+  Nov30   0:00 /sbin/getty 38400 tty1
root      2388  0.0  0.0  16252   944 tty2     Ss+  Nov30   0:00 /sbin/getty 38400 tty2
root      2389  0.0  0.0  16252   936 tty3     Ss+  Nov30   0:00 /sbin/getty 38400 tty3
root      2390  0.0  0.0  16252   948 tty4     Ss+  Nov30   0:00 /sbin/getty 38400 tty4
root      2391  0.0  0.0  16252   944 tty5     Ss+  Nov30   0:00 /sbin/getty 38400 tty5
root      2392  0.0  0.0  16252   940 tty6     Ss+  Nov30   0:00 /sbin/getty 38400 tty6
root      2396  0.0  0.0      0     0 ?        S    Nov30   0:01 [flush-8:0]
root      2409  0.0  0.0   9956  2576 ?        Ss   Nov30   0:00 dhclient -v -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases eth0
root      2450  0.0  0.0  49848  1200 ?        Ss   Nov30   0:00 /usr/sbin/sshd
root      3510  0.0  0.0      0     0 ?        S    Nov30   0:04 [kworker/1:2]
root      7397  0.0  0.0  71208  3652 ?        Ss   20:12   0:00 sshd: root@pts/0
root      7405  0.0  0.0  20496  3284 pts/0    Ss   20:12   0:00 -bash
root      7650  0.0  0.0  17416   356 ?        Ss   03:59   0:00 /usr/local/bin/oscam -b
root      7651  0.0  0.0  51264  2464 ?        Ssl  03:59   0:12 /usr/local/bin/CCcam.x86_64
root      7652  0.0  0.1 174848  6896 ?        S<l  03:59   0:47 /usr/local/bin/oscam -b
root      7827  0.0  0.0      0     0 ?        S    Nov30   0:01 [kworker/1:1]
root     10286  0.0  0.0  16832  1256 pts/0    R+   20:51   0:00 ps auxwww
www-data 17417  0.0  0.1 132180  6728 ?        S    06:25   0:00 /usr/sbin/apache2 -k start
www-data 17419  0.0  0.1 132180  6728 ?        S    06:25   0:00 /usr/sbin/apache2 -k start
www-data 17422  0.0  0.1 132180  6728 ?        S    06:25   0:00 /usr/sbin/apache2 -k start
www-data 17423  0.0  0.1 132180  6728 ?        S    06:25   0:00 /usr/sbin/apache2 -k start
www-data 17424  0.0  0.1 132180  6728 ?        S    06:25   0:00 /usr/sbin/apache2 -k start
proftpd  17434  0.0  0.0 101464  2044 ?        Ss   06:25   0:00 proftpd: (accepting connections)
root     25661  0.0  0.0      0     0 ?        S    16:38   0:02 [kworker/0:0]
root@oscam-server:~#

It seems to me that Oscam is running twice or is this normal?

The idea of an check script that looks for both versions would be nice for automated install scripts!

Originally posted by aplok

I just want to check if CCcam is runing and if not it start again, that is what that script schould do but it is for 32-bit and I need it for 64-bit.

The commands you give me gave a huge list, do you need all of that?

**gpaolobvt** · 12-01-2013, 09:43 PM

Re: How to made check script for CCcam 64-bit ?

OK.

Now lets change your original script:

#!/bin/sh
process=`ps auxwww | grep CCcam.x86_64 | grep -v grep | awk '{print $1}'`
if [ -z "$process" ]; then
echo "Couldn't find CCcam.x86 running. Restarting server-binary" >> /var/cccamlog/cccam.check
echo && date >>/var/cccamlog/cccam.check
/usr/local/bin/ CCcam.x86_64 -d >> /var/cccamlog/CCcam.log &
else echo "CCcam.x86 is still OK!" >> /var/cccamlog/cccam.check
fi

If the script find the CCcam.x86_64 in the list proces, then update the log and let's execute it with -d parameter.

Remember also to set the 755 flags to this script with the chmod command, to let this script executable.

About double oscam....

Normally, in a system may be more than on processes with the same name. Their number may depend on the scripts that may be execute more than one time, or the same process can fork to a child (same binary, same name).

This last feature depend on how the program itself has been designed by the programmers. In the next day, i will collect some information on it, and i will give you feedback.

Bye

**aplok** · 12-01-2013, 09:54 PM

Re: How to made check script for CCcam 64-bit ?

hi

your cccam 64 is running under /usr/local/bin/CCcam.x86_64

Code:

~# ps auxwww
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root      7651  0.0  0.0  51264  2464 ?        Ssl  03:59   0:12 /usr/local/bin/CCcam.x86_64

I just want to check if CCcam is runing
ps aux |grep CCcam.x86_64

and if not it start again, that is what that script schould do but it is for 32-bit and I need it for 64-bit

try this:
ps aux |grep -q CCcam.x86_64 || /usr/local/bin/CCcam.x86_64 &

**SatWaveDude** · 12-03-2013, 02:40 AM

Re: How to made check script for CCcam 64-bit ?

Originally posted by aplok

try this:
ps aux |grep -q CCcam.x86_64 || /usr/local/bin/CCcam.x86_64 &

Where do I have to put that line?

**aplok** · 12-03-2013, 05:04 AM

Re: How to made check script for CCcam 64-bit ?

Originally posted by SatWaveDude

Where do I have to put that line?

hi,

try this recipy :

Code:

fsh=/var/bin/my.cccam.restart.sh
#
touch $fsh
chown root:root $fsh
chmod 755 $fsh
ls -la $fsh

here is the file /var/bin/my.cccam.restart.sh

Code:

#!/bin/ash 
# - 
cmd=/usr/local/bin/CCcam.x86_64
tempo=60
# -
cbn=$( basename $cmd)
fchk=/tmp/$cbn.check
flog=/tmp/$cbn.log
# -
while [ . ]; do
	process=`ps aux | grep $cbn | grep -v grep | awk '{print $1}'`
	if [ -z "$process" ]; then
		echo  $( date '+%Y%m%d.%H%M') $cbn not running: restart >> $fchk
		$cmd -d >> $flog &
		else 
			echo $( date '+%Y%m%d.%H%M') $cbn ok >> $fchk
		fi
	sleep $tempo
	done
#

start it manually:

/var/bin/my.cccam.restart.sh

check if it runs:

ps aux |grep my.cccam.restart.sh

kill it:

kill -9 process_id_of_my.cccam.restart.sh

killall my.cccam.restart.sh

start it manually, backgrounded:

/var/bin/my.cccam.restart.sh &

start it at boot:

add the line

/var/bin/my.cccam.restart.sh &

in at the end of an executed script at boot located in

/var/etc/init.d

enjoy !

**uttnls** · 12-13-2013, 09:39 PM

Re: How to made check script for CCcam 64-bit ?

Originally posted by aplok

hi,

try this recipy :

Code:

fsh=/var/bin/my.cccam.restart.sh
#
touch $fsh
chown root:root $fsh
chmod 755 $fsh
ls -la $fsh

here is the file /var/bin/my.cccam.restart.sh

Code:

#!/bin/ash 
# - 
cmd=/usr/local/bin/CCcam.x86_64
tempo=60
# -
cbn=$( basename $cmd)
fchk=/tmp/$cbn.check
flog=/tmp/$cbn.log
# -
while [ . ]; do
	process=`ps aux | grep $cbn | grep -v grep | awk '{print $1}'`
	if [ -z "$process" ]; then
		echo  $( date '+%Y%m%d.%H%M') $cbn not running: restart >> $fchk
		$cmd -d >> $flog &
		else 
			echo $( date '+%Y%m%d.%H%M') $cbn ok >> $fchk
		fi
	sleep $tempo
	done
#

start it manually:

/var/bin/my.cccam.restart.sh

check if it runs:

ps aux |grep my.cccam.restart.sh

kill it:

kill -9 process_id_of_my.cccam.restart.sh

killall my.cccam.restart.sh

start it manually, backgrounded:

/var/bin/my.cccam.restart.sh &

start it at boot:

add the line

/var/bin/my.cccam.restart.sh &

in at the end of an executed script at boot located in

/var/etc/init.d

enjoy !

I would rather use the crontab than keeping the script in an infinite while loop

**aplok** · 12-13-2013, 09:55 PM

Re: How to made check script for CCcam 64-bit ?

hi,

if you prefer the crontab trigger
try this recipy :
( inhibit the while-sleep command)

Code:

fsh=/var/bin/my.cccam.restart.crontab.sh
#
touch $fsh
chown root:root $fsh
chmod 755 $fsh
ls -la $fsh

here is the file /var/bin/my.cccam.restart.crontab.sh

Code:

#!/bin/ash 
cmd=/usr/local/bin/CCcam.x86_64
cmd=ls 
# tempo=60
# -
cbn=$( basename $cmd)
fchk=/tmp/$cbn.check
flog=/tmp/$cbn.log
# -
# while [ . ]; do
	process=`ps aux | grep $cbn | grep -v grep | awk '{print $1}'`
	if [ -z "$process" ]; then
		echo  $( date '+%Y%m%d.%H%M') $cbn not running: restart >> $fchk
		$cmd -d >> $flog &
		else 
			echo $( date '+%Y%m%d.%H%M') $cbn ok >> $fchk
		fi
#	sleep $tempo
#	done
#

start it manually:

/var/bin/my.cccam.restart.crontab.sh

check if it runs:

ps aux |grep my.cccam.restart.crontab.sh

kill it:

kill -9 process_id_of_my.cccam.restart.crontab.sh

killall my.cccam.restart.crontab.sh

ask crontab to trig it:
start crontab editor,
edit this line (each minute , every 5 minutes, every 1 hour )

crontab -e

# m h dom mon dow command
* * * * * /var/bin/my.cccam.restart.crontab.sh
# 5 * * * * /var/bin/my.cccam.restart.crontab.sh
# 0 1 * * * /var/bin/my.cccam.restart.crontab.sh

check if crontab is running

ps aux |grep crontab

wait 1 min ( or 5 min, 1 hour ...) and check if it is ok

enjoy

**SatWaveDude** · 12-14-2013, 12:36 AM

Re: How to made check script for CCcam 64-bit ?

What is the difference between both situations?

Can you explain a little more please.

**aplok** · 12-14-2013, 01:28 AM

Re: How to made check script for CCcam 64-bit ?

Originally posted by SatWaveDude

a little more please.

cron is a deamon to execute scheduled commands (Vixie Cron),
specified in a command files,
edited by the tool crontab -e
under the format

min hour dayofmonth dayfoweek command

it is commonly used by linux os itself for periodic processes
and by linux admin for periodic process (as backup, purge /tmp; ...)

--

differences:
my.cccam.restart.sh
my.cccam.restart.crontab.sh

my.cccam.restart.sh
while [ . ]; do
...
done

my.cccam.restart.crontab.sh

# while [ . ]; do
...
# done

my.cccam.restart.sh is launched manually

my.cccam.restart.crontab.sh is lauched by the cron deamon

cron deamon:
cron - daemon to execute scheduled commands (Vixie Cron)

those commands are specified in a file, exclusively edited by the command crontab

cron searches its spool area (/var/spool/cron/crontabs) for crontab files
crontabs found are loaded into memory.
Note that crontabs in this directory should not be accessed directly -
the <crontab> command should be used to access and update them.

crontab file syntax:

crontab -e

#m h dom mon dow command
#min hour DayOfMnth DayOfWeek command
* * * * * /var/bin/my.cccam.restart.crontab.sh
#5 * * * * /var/bin/my.cccam.restart.crontab.sh
#0 1 * * * /var/bin/my.cccam.restart.crontab.sh
#

more info
__http://askubuntu.com/questions/2368/how-do-i-set-up-a-cron-job
__https://help.ubuntu.com/community/CronHowto

**SatWaveDude** · 12-14-2013, 04:06 AM

Re: How to made check script for CCcam 64-bit ?

You are awsome dude!!!

I wish I had that Linux knoledge like you do

>>>>RESPECT<<<<

**aplok** · 12-14-2013, 08:52 AM

Re: How to made check script for CCcam 64-bit ?

Originally posted by SatWaveDude

... I wish I had that Linux knowledge

try these entries:

__https://help.ubuntu.com/13.10/ubuntu-help/index.html

__http://debian-handbook.info/browse/stable/

enjoy

Welcome!

Alert: Don't Use Hotmail Email Accounts for registration

How to made check script for CCcam 64-bit ?

How to made check script for CCcam 64-bit ?

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment