Oscam CS 4Wochen vor Vetragsende down? Ratlos....

[Bias999]

Hallo.
Seit 5 Tagen ist mein CS down. Lief nun knapp ein Jahr alles fehlerfrei.

Nun die Frage? Hat es was damit zu tun, dass mein Vertrag in einem Monat ausläuft(VollAbo),
oder ist es doch eher ne Config ANgelegenheit?(easymouse wird jedenfalls erkannt, karte auch)

Hardware: Fritzbox mit Freetz, Easymouse 2 und ne V14Karte., CLients nutzen CCCam, Server ist OScam

Anbei nen Screen meines Oscam WebIf, oscam.server stelle ich auch ein(weiss nur nicht was davon ich
unkenntlich machen muss)

Vielen Dank im voraus,
wollte mein Abo eigentlich verlänger, natürlich nur wenn es wieder funzt.

oscam.server

Spoiler

[reader]
label = sky
protocol = mouse
device=/dev/ttyUSB0
caid = 098C
boxid = 12345678
detect = CD
mhz = 357
cardmhz = 357
group = 1
emmcache = 1,3,2
lb_weight = 100
ndsversion = 2

OscamWebif:

Spoiler

s services reloaded: 0 services freed, 4 services loaded, rejected 0
s userdb reloaded: 9 accounts loaded, 0 expired, 0 disabled
s signal handling initialized (type=sysv)
XXXXX service-id's loaded in 376ms
WARNING: You risk high CPU load and high ECM times with more than 2000 service-id´s!
s HINT: --> use optimized lists from

Sie müssen registriert sein, um Links zu sehen.

s 116 tier-id's loaded
s 3 provid's loaded
s 22 lengths for caid guessing loaded
s monitor: disabled
s camd35: disabled
s cs378x: disabled
s newcamd: disabled
s cccam: initialized (fd=7, port=5678, ip=192.168.178.1, crypted)
s radegast: disabled
s http thread started
h HTTP Server listening on port 5XX4
s reader check thread started
s check thread started
s creating thread for device /dev/ttyUSB0
s loadbalancer: can't read from file /tmp/.oscam/stat
s waiting for local card init
r reader sky initialized (device=/dev/ttyUSB0, detect=cd, mhz=357, cardmhz=357)
s init for all local cards done

 

[supraracer]

AW: Oscam CS 4Wochen vor Vetragsende down? Ratlos....

Du blockst lt. deiner oscam.server keine EMM, evtl. wurde deine Karte gepairt.
Payload auslesen um zu sehen was los ist: OScam WebIF LiveLog auf 2+4 klicken, Reader neu starten, im Log nach 0F 06 suchen und die ganze Zeile hier mal posten.
Vielleicht hattest du auch ganz viel glück, AU hat nicht funktioniert und die Entitlements sind nur abgelaufen. Auch das erkennt man am Payload.
Poste auch noch alle deine anderen Configs im Spoiler.

-supraracer

 

[dodo83]

AW: Oscam CS 4Wochen vor Vetragsende down? Ratlos....

um ein Screen einzustellen musst du es über einen externen Hoster machen

poste mal bitte alle Configs (in SPOILERN)
und das log ab start der OScam bis zur Sender Abfrage
Entitlements noch vorhanden?

 

[Bias999]

AW: Oscam CS 4Wochen vor Vetragsende down? Ratlos....

Was muss ich den unkenntlich machen in der oscam.config, oscam.server, oscam.services ??

Wo finde ich die Oscam.log? auf dem stick ist die gespeichert oder?

danke

 

[dodo83]

AW: Oscam CS 4Wochen vor Vetragsende down? Ratlos....

eigentlich nur öffentliche Ip´s im log
WebIF -> Files -> logfile

wenn es speicherst, weiß man nicht da man deine Config nicht kennt, in der oscam.conf steht der Pfad oder im WebIF unter CONFIG

 

[Bias999]

AW: Oscam CS 4Wochen vor Vetragsende down? Ratlos....

ok, danke
hier der log aus dem WebIf:

Spoiler

>> OSCam << cardserver started at Fri Nov 21 11:28:42 2014
-------------------------------------------------------------------------------
2014/11/21 11:28:42 5AD188 s >> OSCam << cardserver started, version 1.20 -DEB-Freetz--Prof.Linux- , build #5781 (mipsel-router-linux-uclibc931)
2014/11/21 11:28:42 5AD188 s version=1.20 -DEB-Freetz--Prof.Linux- , build #5781, system=mipsel-router-linux, nice=-1
2014/11/21 11:28:42 5AD188 s client max. idle=120 sec, debug level=0
2014/11/21 11:28:42 5AD188 s max. logsize=1000 Kb, loghistorysize=4096 bytes
2014/11/21 11:28:42 5AD188 s client timeout=5000 ms, fallback timeout=2000 ms, cache delay=120 ms
2014/11/21 11:28:42 5AD188 s services reloaded: 0 services freed, 4 services loaded, rejected 0
2014/11/21 11:28:42 5AD188 s userdb reloaded: 9 accounts loaded, 0 expired, 0 disabled
2014/11/21 11:28:42 5AD188 s signal handling initialized (type=sysv)
2014/11/21 11:28:42 5AD188 s 11590 service-id's loaded in 376ms
2014/11/21 11:28:42 5AD188 s WARNING: You risk high CPU load and high ECM times with more than 2000 service-id´s!
2014/11/21 11:28:42 5AD188 s HINT: --> use optimized lists from

Sie müssen registriert sein, um Links zu sehen.

2014/11/21 11:28:42 5AD188 s 116 tier-id's loaded
2014/11/21 11:28:42 5AD188 s 3 provid's loaded
2014/11/21 11:28:42 5AD188 s 22 lengths for caid guessing loaded
2014/11/21 11:28:42 5AD188 s monitor: disabled
2014/11/21 11:28:42 5AD188 s camd35: disabled
2014/11/21 11:28:42 5AD188 s cs378x: disabled
2014/11/21 11:28:42 5AD188 s newcamd: disabled
2014/11/21 11:28:42 5AD188 s cccam: initialized (fd=7, port=5678, ip=XXXXXXXXXXX, crypted)
2014/11/21 11:28:42 5AD188 s radegast: disabled
2014/11/21 11:28:42 5AD188 s http thread started
2014/11/21 11:28:42 6BC9B8 h HTTP Server listening on port 5454
2014/11/21 11:28:42 5AD188 s reader check thread started
2014/11/21 11:28:42 5AD188 s check thread started
2014/11/21 11:28:42 5AD188 s creating thread for device /dev/ttyUSB0
2014/11/21 11:28:42 5AD188 s loadbalancer: can't read from file /tmp/.oscam/stat
2014/11/21 11:28:42 5AD188 s waiting for local card init
2014/11/21 11:28:45 6BE090 r reader sky initialized (device=/dev/ttyUSB0, detect=cd, mhz=357, cardmhz=357)
2014/11/21 11:28:46 5AD188 s init for all local cards done

 

[supraracer]

AW: Oscam CS 4Wochen vor Vetragsende down? Ratlos....

Damit lässt sich nicht viel anfangen, #2 noch mal lesen und die geforderten Infos liefern, erst dann kann geholfen werden.

-supraracer

 

[Bias999]

AW: Oscam CS 4Wochen vor Vetragsende down? Ratlos....

ALso von 2auf4 hab ich umgestellt, Oscam neu gestartet, in der logfile steht nun auch nix anderes als vorher..
Was mach ich falsch? danke

 

[dodo83]

AW: Oscam CS 4Wochen vor Vetragsende down? Ratlos....

das einzige

- OScam zu Alt
- Reader wird nicht erkannt laut log

 

[Bias999]

AW: Oscam CS 4Wochen vor Vetragsende down? Ratlos....

Oscam ist 1.2, "reader sky initialized " heisst ja das der Reader erkannt wurde oder?
Bei mir kommt nirgends im Log 0F 06..

 

[mrwong]

AW: Oscam CS 4Wochen vor Vetragsende down? Ratlos....

psoten doch mal das log wie dir befohlen

 

[phili76]

AW: Oscam CS 4Wochen vor Vetragsende down? Ratlos....

Hi,

oscam ist zwar 1.2 aber die SVN Version 5781 ist vom März 2011..

 

[Bias999]

AW: Oscam CS 4Wochen vor Vetragsende down? Ratlos....

Wie gesagt da steht nix neues drin:

Spoiler

-------------------------------------------------------------------------------
>> OSCam << cardserver started at Thu Jan 1 01:01:29 1970
-------------------------------------------------------------------------------
1970/01/01 1:01:29 5AD188 s >> OSCam << cardserver started, version 1.20 -DEB-Freetz--Prof.Linux- , build #5781 (mipsel-router-linux-uclibc931)
1970/01/01 1:01:29 5AD188 s version=1.20 -DEB-Freetz--Prof.Linux- , build #5781, system=mipsel-router-linux, nice=-1
1970/01/01 1:01:29 5AD188 s client max. idle=120 sec, debug level=0
1970/01/01 1:01:29 5AD188 s max. logsize=1000 Kb, loghistorysize=4096 bytes
1970/01/01 1:01:29 5AD188 s client timeout=5000 ms, fallback timeout=2000 ms, cache delay=120 ms
1970/01/01 1:01:29 5AD188 s The current system time is smaller than the build date (Aug 4 2011). Waiting 5s for time to correct...
1970/01/01 1:01:34 5AD188 s The current system time is smaller than the build date (Aug 4 2011). Waiting 5s for time to correct...
1970/01/01 1:01:39 5AD188 s The current system time is smaller than the build date (Aug 4 2011). Waiting 5s for time to correct...
2014/11/21 13:08:49 5AD188 s services reloaded: 0 services freed, 4 services loaded, rejected 0
2014/11/21 13:08:49 5AD188 s userdb reloaded: 9 accounts loaded, 0 expired, 0 disabled
2014/11/21 13:08:49 5AD188 s signal handling initialized (type=sysv)
2014/11/21 13:08:49 5AD188 s 11590 service-id's loaded in 463ms
2014/11/21 13:08:49 5AD188 s WARNING: You risk high CPU load and high ECM times with more than 2000 service-id´s!
2014/11/21 13:08:49 5AD188 s HINT: --> use optimized lists from

Sie müssen registriert sein, um Links zu sehen.

2014/11/21 13:08:49 5AD188 s 116 tier-id's loaded
2014/11/21 13:08:49 5AD188 s 3 provid's loaded
2014/11/21 13:08:49 5AD188 s 22 lengths for caid guessing loaded
2014/11/21 13:08:49 5AD188 s monitor: Bind request failed, waiting another 119 seconds
2014/11/21 13:08:50 5AD188 s monitor: Bind request failed, waiting another 118 seconds
2014/11/21 13:08:51 5AD188 s monitor: Bind request failed, waiting another 117 seconds
2014/11/21 13:08:52 5AD188 s monitor: Bind request failed, waiting another 116 seconds
2014/11/21 13:08:53 5AD188 s monitor: Bind request failed, waiting another 115 seconds
2014/11/21 13:08:54 5AD188 s monitor: Bind request failed, waiting another 114 seconds
2014/11/21 13:08:55 5AD188 s monitor: Bind request failed, waiting another 113 seconds
2014/11/21 13:08:56 5AD188 s monitor: Bind request failed, waiting another 112 seconds
2014/11/21 13:08:57 5AD188 s monitor: Bind request failed, waiting another 111 seconds
2014/11/21 13:08:58 5AD188 s monitor: Bind request failed, waiting another 110 seconds
2014/11/21 13:08:59 5AD188 s monitor: Bind request failed, waiting another 109 seconds
2014/11/21 13:09:00 5AD188 s monitor: Bind request failed, waiting another 108 seconds
2014/11/21 13:09:01 5AD188 s monitor: Bind request failed, waiting another 107 seconds
2014/11/21 13:09:02 5AD188 s monitor: Bind request failed, waiting another 106 seconds
2014/11/21 13:09:03 5AD188 s monitor: Bind request failed, waiting another 105 seconds
2014/11/21 13:09:04 5AD188 s monitor: Bind request failed, waiting another 104 seconds
2014/11/21 13:09:05 5AD188 s monitor: Bind request failed, waiting another 103 seconds
2014/11/21 13:09:06 5AD188 s monitor: Bind request failed, waiting another 102 seconds
2014/11/21 13:09:07 5AD188 s monitor: Bind request failed, waiting another 101 seconds
2014/11/21 13:09:08 5AD188 s monitor: Bind request failed, waiting another 100 seconds
2014/11/21 13:09:09 5AD188 s monitor: Bind request failed, waiting another 99 seconds
2014/11/21 13:09:10 5AD188 s monitor: Bind request failed, waiting another 98 seconds
2014/11/21 13:09:11 5AD188 s monitor: Bind request failed, waiting another 97 seconds
2014/11/21 13:09:12 5AD188 s monitor: Bind request failed, waiting another 96 seconds
2014/11/21 13:09:13 5AD188 s monitor: Bind request failed, waiting another 95 seconds
2014/11/21 13:09:14 5AD188 s monitor: Bind request failed, waiting another 94 seconds
2014/11/21 13:09:15 5AD188 s monitor: Bind request failed, waiting another 93 seconds
2014/11/21 13:09:16 5AD188 s monitor: Bind request failed, waiting another 92 seconds
2014/11/21 13:09:17 5AD188 s monitor: Bind request failed, waiting another 91 seconds
2014/11/21 13:09:18 5AD188 s monitor: Bind request failed, waiting another 90 seconds
2014/11/21 13:09:19 5AD188 s monitor: Bind request failed, waiting another 89 seconds
2014/11/21 13:09:20 5AD188 s monitor: Bind request failed, waiting another 88 seconds
2014/11/21 13:09:21 5AD188 s monitor: Bind request failed, waiting another 87 seconds
2014/11/21 13:09:22 5AD188 s monitor: Bind request failed, waiting another 86 seconds
2014/11/21 13:09:23 5AD188 s monitor: Bind request failed, waiting another 85 seconds
2014/11/21 13:09:24 5AD188 s monitor: Bind request failed, waiting another 84 seconds
2014/11/21 13:09:25 5AD188 s monitor: Bind request failed, waiting another 83 seconds
2014/11/21 13:09:26 5AD188 s monitor: Bind request failed, waiting another 82 seconds
2014/11/21 13:09:27 5AD188 s monitor: Bind request failed, waiting another 81 seconds
2014/11/21 13:09:28 5AD188 s monitor: Bind request failed, waiting another 80 seconds
2014/11/21 13:09:29 5AD188 s monitor: Bind request failed, waiting another 79 seconds
2014/11/21 13:09:30 5AD188 s monitor: Bind request failed, waiting another 78 seconds
2014/11/21 13:09:31 5AD188 s monitor: Bind request failed, waiting another 77 seconds
2014/11/21 13:09:32 5AD188 s monitor: Bind request failed, waiting another 76 seconds
2014/11/21 13:09:33 5AD188 s monitor: Bind request failed, waiting another 75 seconds
2014/11/21 13:09:34 5AD188 s monitor: Bind request failed, waiting another 74 seconds
2014/11/21 13:09:35 5AD188 s monitor: Bind request failed, waiting another 73 seconds
2014/11/21 13:09:36 5AD188 s monitor: Bind request failed, waiting another 72 seconds
2014/11/21 13:09:37 5AD188 s monitor: Bind request failed, waiting another 71 seconds
2014/11/21 13:09:38 5AD188 s monitor: Bind request failed, waiting another 70 seconds
2014/11/21 13:09:39 5AD188 s monitor: Bind request failed, waiting another 69 seconds
2014/11/21 13:09:40 5AD188 s monitor: Bind request failed, waiting another 68 seconds
2014/11/21 13:09:41 5AD188 s monitor: Bind request failed, waiting another 67 seconds
2014/11/21 13:09:42 5AD188 s monitor: Bind request failed, waiting another 66 seconds
2014/11/21 13:09:43 5AD188 s monitor: Bind request failed, waiting another 65 seconds
2014/11/21 13:09:44 5AD188 s monitor: Bind request failed, waiting another 64 seconds
2014/11/21 13:09:45 5AD188 s monitor: Bind request failed, waiting another 63 seconds
2014/11/21 13:09:46 5AD188 s monitor: Bind request failed, waiting another 62 seconds
2014/11/21 13:09:47 5AD188 s monitor: Bind request failed, waiting another 61 seconds
2014/11/21 13:09:48 5AD188 s monitor: Bind request failed, waiting another 60 seconds
2014/11/21 13:09:49 5AD188 s monitor: Bind request failed, waiting another 59 seconds
2014/11/21 13:09:50 5AD188 s monitor: Bind request failed, waiting another 58 seconds
2014/11/21 13:09:51 5AD188 s monitor: Bind request failed, waiting another 57 seconds
2014/11/21 13:09:52 5AD188 s monitor: Bind request failed, waiting another 56 seconds
2014/11/21 13:09:53 5AD188 s monitor: Bind request failed, waiting another 55 seconds
2014/11/21 13:09:54 5AD188 s monitor: Bind request failed, waiting another 54 seconds
2014/11/21 13:09:55 5AD188 s monitor: Bind request failed, waiting another 53 seconds
2014/11/21 13:09:56 5AD188 s monitor: Bind request failed, waiting another 52 seconds
2014/11/21 13:09:57 5AD188 s monitor: Bind request failed, waiting another 51 seconds
2014/11/21 13:09:58 5AD188 s monitor: Bind request failed, waiting another 50 seconds
2014/11/21 13:09:59 5AD188 s monitor: Bind request failed, waiting another 49 seconds
2014/11/21 13:10:00 5AD188 s monitor: Bind request failed, waiting another 48 seconds
2014/11/21 13:10:01 5AD188 s monitor: Bind request failed, waiting another 47 seconds
2014/11/21 13:10:02 5AD188 s monitor: Bind request failed, waiting another 46 seconds
2014/11/21 13:10:03 5AD188 s monitor: Bind request failed, waiting another 45 seconds
2014/11/21 13:10:04 5AD188 s monitor: Bind request failed, waiting another 44 seconds
2014/11/21 13:10:05 5AD188 s monitor: Bind request failed, waiting another 43 seconds
2014/11/21 13:10:06 5AD188 s monitor: Bind request failed, waiting another 42 seconds
2014/11/21 13:10:07 5AD188 s monitor: Bind request failed, waiting another 41 seconds
2014/11/21 13:10:08 5AD188 s monitor: Bind request failed, waiting another 40 seconds
2014/11/21 13:10:09 5AD188 s monitor: Bind request failed, waiting another 39 seconds
2014/11/21 13:10:10 5AD188 s monitor: Bind request failed, waiting another 38 seconds
2014/11/21 13:10:11 5AD188 s monitor: Bind request failed, waiting another 37 seconds
2014/11/21 13:10:12 5AD188 s monitor: Bind request failed, waiting another 36 seconds
2014/11/21 13:10:13 5AD188 s monitor: Bind request failed, waiting another 35 seconds
2014/11/21 13:10:14 5AD188 s monitor: Bind request failed, waiting another 34 seconds
2014/11/21 13:10:15 5AD188 s monitor: Bind request failed, waiting another 33 seconds
2014/11/21 13:10:16 5AD188 s monitor: Bind request failed, waiting another 32 seconds
2014/11/21 13:10:17 5AD188 s monitor: Bind request failed, waiting another 31 seconds
2014/11/21 13:10:18 5AD188 s monitor: Bind request failed, waiting another 30 seconds
2014/11/21 13:10:19 5AD188 s monitor: Bind request failed, waiting another 29 seconds
2014/11/21 13:10:20 5AD188 s monitor: Bind request failed, waiting another 28 seconds
2014/11/21 13:10:21 5AD188 s monitor: Bind request failed, waiting another 27 seconds
2014/11/21 13:10:22 5AD188 s monitor: Bind request failed, waiting another 26 seconds
2014/11/21 13:10:23 5AD188 s monitor: Bind request failed, waiting another 25 seconds
2014/11/21 13:10:24 5AD188 s monitor: Bind request failed, waiting another 24 seconds
2014/11/21 13:10:25 5AD188 s monitor: Bind request failed, waiting another 23 seconds
2014/11/21 13:10:26 5AD188 s monitor: Bind request failed, waiting another 22 seconds
2014/11/21 13:10:27 5AD188 s monitor: Bind request failed, waiting another 21 seconds
2014/11/21 13:10:28 5AD188 s monitor: Bind request failed, waiting another 20 seconds
2014/11/21 13:10:29 5AD188 s monitor: Bind request failed, waiting another 19 seconds
2014/11/21 13:10:30 5AD188 s monitor: Bind request failed, waiting another 18 seconds
2014/11/21 13:10:31 5AD188 s monitor: Bind request failed, waiting another 17 seconds
2014/11/21 13:10:32 5AD188 s monitor: Bind request failed, waiting another 16 seconds
2014/11/21 13:10:33 5AD188 s monitor: Bind request failed, waiting another 15 seconds
2014/11/21 13:10:34 5AD188 s monitor: Bind request failed, waiting another 14 seconds
2014/11/21 13:10:35 5AD188 s monitor: Bind request failed, waiting another 13 seconds
2014/11/21 13:10:36 5AD188 s monitor: Bind request failed, waiting another 12 seconds
2014/11/21 13:10:37 5AD188 s monitor: Bind request failed, waiting another 11 seconds
2014/11/21 13:10:38 5AD188 s monitor: Bind request failed, waiting another 10 seconds
2014/11/21 13:10:39 5AD188 s monitor: Bind request failed, waiting another 9 seconds
2014/11/21 13:10:40 5AD188 s monitor: Bind request failed, waiting another 8 seconds
2014/11/21 13:10:41 5AD188 s monitor: Bind request failed, waiting another 7 seconds
2014/11/21 13:10:42 5AD188 s monitor: Bind request failed, waiting another 6 seconds
2014/11/21 13:10:43 5AD188 s monitor: Bind request failed, waiting another 5 seconds
2014/11/21 13:10:44 5AD188 s monitor: Bind request failed, waiting another 4 seconds
2014/11/21 13:10:45 5AD188 s monitor: Bind request failed, waiting another 3 seconds
2014/11/21 13:10:46 5AD188 s monitor: Bind request failed, waiting another 2 seconds
2014/11/21 13:10:47 5AD188 s monitor: Bind request failed, waiting another 1 seconds
2014/11/21 13:10:48 5AD188 s monitor: Bind request failed, giving up
2014/11/21 13:10:48 5AD188 s camd35: disabled
2014/11/21 13:10:48 5AD188 s cs378x: disabled
2014/11/21 13:10:48 5AD188 s newcamd: disabled
2014/11/21 13:10:48 5AD188 s cccam: initialized (fd=6, port=5678, ip=192.168.178.1, crypted)
2014/11/21 13:10:48 5AD188 s radegast: disabled
2014/11/21 13:10:48 5AD188 s http thread started
2014/11/21 13:10:48 5AD188 s reader check thread started
2014/11/21 13:10:48 5AD188 s check thread started
2014/11/21 13:10:48 5AD188 s creating thread for device /dev/ttyUSB0
2014/11/21 13:10:48 5AD188 s loadbalancer: can't read from file /tmp/.oscam/stat
2014/11/21 13:10:48 5AD188 s waiting for local card init
2014/11/21 13:10:48 6BE090 h HTTP Server listening on port 5454
2014/11/21 13:10:50 6BC9B8 r reader sky initialized (device=/dev/ttyUSB0, detect=cd, mhz=357, cardmhz=357)
2014/11/21 13:10:52 5AD188 s init for all local cards done

 

[phili76]

AW: Oscam CS 4Wochen vor Vetragsende down? Ratlos....

könnte sein das die oscam mehrfach rennt. Fehler Bind request failed, oder ein schon belegter Port verwendet wird. wartet sonst immer 2 Minuten bis es weitergeht. Hast Du eine andere oscam.config genommen?

 

[Thommy_dd]

AW: Oscam CS 4Wochen vor Vetragsende down? Ratlos....

Was machst du denn mit sovielen Service-id's? Läuft da noch ein anderer Prozess, der deine Karten beansprucht? Wie ist dein Oscam config? Oscam unbedingt auf aktuelle Version updaten!