Reply With QuoteDe ce nu bagi inainte de restart si :"killall oscam" ? Ca sa te asiguri ca nu iti raman instante de la cel vechi ?
Ca aici http://sateliti.info/showthread.php?...l=1#post155389
oscam #4794 pe ubuntu 10.10 - multiple instante?
salutare!
pe un ubuntu 10.10 am urmatoarea problema: scriptul de verificare al functionarii oscam-ului imi porneste mai multe instante:
scriptul este urmatorul:
ceva idei? multumesc anticipat!Code:#!/bin/sh if ps x |grep -v grep |grep -c oscam.x86 >/dev/null then echo "oscam... ok" else date=`date` echo "Restarting OScam : $date" >> /tmp/checkoscam.log echo "oscam... restarting" /usr/local/bin/oscam.x86 -c /var/etc/ -d 64 >>/tmp/oscam.log & fi
succesuri!
De ce nu bagi inainte de restart si :"killall oscam" ? Ca sa te asiguri ca nu iti raman instante de la cel vechi ?
Ca aici http://sateliti.info/showthread.php?...l=1#post155389
2-3 cutii cu linucsi hw:mips si sh4;sw: openwrt si tidegloE2
am pus. acelasi rezultat. ideea este ca, din diverse motive, scriptul il porneste de 2 ori. dupa 8 ore, raman doar 2 instante. nu stiu ce sa cred.
succesuri!
incearca cu "killall -9 oscam" modifica timpii din cron sa nu coincida: verificare oscam cu multips
Azbox HD with OpenSPA 3.0 powered by OSCam
UE46F8000 powered by SamyGO_OSCam
nicio modificare in comportament. ce-i si mai dubios: doar am inlocuit executabilul oscam-ului; din 40xy in 4794. si atat. in aceeasi configuratie, serverul a mers fara probleme. nu se manifesta altfel. il las asa. vad ce si cum pana maine seara. daca-s probleme, revin la versiunea veche.
succesuri!
---------- Post added at 20:23 ---------- Previous post was at 20:17 ----------
L.E. pornit manual, oscam-ul se comporta le fel. se pare ca-i "de la ei". m-am lamurit. nu scriptul e de vina.
succesuri!
Ca sugestie, pune binu' in /usr/bin si configurile in /usr/local/etc.
Pe Ubuntu si acum pe debian n-am avut probleme cu mai multe vers de oscam si cu scriptul acesta:
si cu linia asta in cron n-ai treaba:#!/bin/sh
if ps x |grep -v grep |grep -c oscam.x86 >/dev/null
then
echo "oscam... ok"
else
date=`date`
echo "Restarting oscam : $date" >> /tmp/checkoscam.log
echo "oscam... restarting"
/usr/bin/oscam.x86 -b >>/tmp/logoscam.txt &
fi
Scriptul e in /var/scripts*/1 * * * * /var/scripts/./checkoscam.sh >>/tmp/checkoscam.log 2>&1
Doi mari vrăjmași are românul: mila pentru străini și ura pentru ai lui - Grigore Vieru
multumesc pentru sugestii! maine ma apuc sa-l modific.
succesuri!
eu acum am vazut bine primul post ( de... cafeaua!!),vad ca si la mine sunt o gramada de pid-uri, si nu cred ca e de la script, asa aveam si inainte de a baga oscam in crond.Originally Posted by techcenter
salutare!
pe un ubuntu 10.10 am urmatoarea problema: scriptul de verificare al functionarii oscam-ului imi porneste mai multe instante:
ceva idei? multumesc anticipat!
succesuri!
aici si logul:Check_Oscam.log in uptime de 2 zile nu am vazut vreo urma de restart cauzata de scripturi.Code:AZBox HD[~]$ ps | grep oscam 10034 root 340 S /EMU/OpenXCAS/oscamCAS/oscam 10040 root 7256 S < /EMU/OpenXCAS/oscamCAS/oscam 10043 root 7256 S < /EMU/OpenXCAS/oscamCAS/oscam 10044 root 7256 S < /EMU/OpenXCAS/oscamCAS/oscam 10047 root 7256 S < /EMU/OpenXCAS/oscamCAS/oscam 10048 root 7256 S < /EMU/OpenXCAS/oscamCAS/oscam 10049 root 7256 S < /EMU/OpenXCAS/oscamCAS/oscam 10050 root 7256 S < /EMU/OpenXCAS/oscamCAS/oscam 10051 root 7256 S < /EMU/OpenXCAS/oscamCAS/oscam 10052 root 7256 S < /EMU/OpenXCAS/oscamCAS/oscam 10053 root 7256 S < /EMU/OpenXCAS/oscamCAS/oscam 10054 root 7256 S < /EMU/OpenXCAS/oscamCAS/oscam 10055 root 7256 S < /EMU/OpenXCAS/oscamCAS/oscam 10056 root 7256 S < /EMU/OpenXCAS/oscamCAS/oscam 10057 root 7256 S < /EMU/OpenXCAS/oscamCAS/oscam 10060 root 7256 S < /EMU/OpenXCAS/oscamCAS/oscam 10062 root 7256 S < /EMU/OpenXCAS/oscamCAS/oscam 10730 root 7256 S < /EMU/OpenXCAS/oscamCAS/oscam 12232 root 7256 S < /EMU/OpenXCAS/oscamCAS/oscam 12236 root 332 S grep oscam
si aici din cygiwn(cu care mai testez r.oscam-oscam-1 reader+1user)Code:Mon Mar 7 06:40:02 UTC 2011 --> (20<40) = OscamPS OK Mon Mar 7 06:42:03 UTC 2011 Oscam working Mon Mar 7 06:45:05 UTC 2011 --> (20<40) = OscamPS OK Mon Mar 7 06:45:05 UTC 2011 Oscam working Mon Mar 7 06:48:03 UTC 2011 Oscam working Mon Mar 7 06:50:04 UTC 2011 --> (20<40) = OscamPS OK Mon Mar 7 06:51:03 UTC 2011 Oscam working Mon Mar 7 06:54:02 UTC 2011 Oscam working Mon Mar 7 06:55:02 UTC 2011 --> (20<40) = OscamPS OK Mon Mar 7 06:57:03 UTC 2011 Oscam working Mon Mar 7 07:00:04 UTC 2011 --> (21<40) = OscamPS OK Mon Mar 7 07:00:04 UTC 2011 Oscam working Mon Mar 7 07:03:05 UTC 2011 Oscam working Mon Mar 7 07:05:03 UTC 2011 --> (20<40) = OscamPS OK Mon Mar 7 07:06:03 UTC 2011 Oscam working Mon Mar 7 07:09:03 UTC 2011 Oscam working Mon Mar 7 07:10:05 UTC 2011 --> (20<40) = OscamPS OK Mon Mar 7 07:12:02 UTC 2011 Oscam working Mon Mar 7 07:15:03 UTC 2011 Oscam working Mon Mar 7 07:15:03 UTC 2011 --> (21<40) = OscamPS OK Mon Mar 7 07:18:03 UTC 2011 Oscam working Mon Mar 7 07:20:03 UTC 2011 --> (20<40) = OscamPS OK
oscam.version:
Version: 1.00-unstable_svn Rev. 4733
Maxpid: UNLIMITED
Last edited by qwess; 07-03-11 at 11:24. Reason: completare
Azbox HD with OpenSPA 3.0 powered by OSCam
UE46F8000 powered by SamyGO_OSCam
La mine pe server sunt 2 procese, dar vad ca asa trebuie.
Mai intai, ma uit la PIDs si vad ca unul e pornit din celalalt (parent-child):
Confirmare cu pstree:Code:% sudo ps -ef | grep oscam | grep -v grep root 15524 1 0 Mar13 ? 00:00:00 ./oscam -b root 21278 15524 0 Mar13 ? 00:03:18 ./oscam -b
Adica avem doua procese. Primul, PID 15524, este parent pentru al doilea, PID 21278.Code:% sudo pstree | grep oscam |-oscam---oscam---6*[{oscam}]
Al doilea are 6 threads, ceea ce inseamna ca, pe langa un reader si cele 2 thread-uri principale (server si monitor), am 3 clienti activi.
Iata:
In concluzie: These aren't the droids you're looking for. Move along!Code:GET "http://localhost:8888/oscamapi.html?part=status" | grep "<client" <client type="s" name="root" protocol="server" protocolext="" au="0"> <client type="h" name="root" protocol="monitor" protocolext="" au="0"> <client type="r" name="omnikey" protocol="pcsc" protocolext="" au="0"> <client type="c" name="dm500be" protocol="camd35" protocolext="" au="-1"> <client type="c" name="tm800" protocol="camd35" protocolext="" au="-1"> <client type="c" name="dm500fe" protocol="camd35" protocolext="" au="-1">
asa este. asa apar si la mine. asta m-a suparat: ca pleaca cu 2 procese, inca de la inceput. vad ca asa trebuie 9asa cum am scris si mai devreme). la killall, mor amandoua.
succesuri!
Posting Permissions
