ET 4000 als OScam Server Probleme

[agms]

Hallo zusammen,

habe seit ein paar Wochen einen ET als Server laufen.Bis jetzt war alles Super. Seit dem ich vorgestern das Softwareupdate hab ich laufend freezer auf den Clients. Habe jetzt mal auf OPEN ATV gewechselt aber keine Besserung in Sicht.
Ich versteh die Welt nicht mehr alles lief super sauber und jetzt.
Verwende Oscam auf dem Server und Oscam und cccam auf den Clients( verschieden). Habe nach dem Neuflash die configs von OScam wieder so eingespielt wie vorher.
Ich hoffe es hat jemand Rat für mich.

 

[Mäx2.5]

AW: ET 4000 als OScam Server Probleme

fastmode aktiviert?

 

[agms]

AW: ET 4000 als OScam Server Probleme

ich denke ja

Spoiler

[reader]
label = V13
enable = 1
protocol = internal
device = /dev/sci0
caid = 09C4
services=SkyGermany
boxid = 12345678
detect = CD
mhz = 357
cardmhz = 357
group = 1
emmcache = 1,1,2
ins7e11=15
ndsversion=2

ist das der richtige teil??

 

[Mäx2.5]

AW: ET 4000 als OScam Server Probleme

ja ,das scheint zu passen, wie sind den die ECM -Zeiten im Web IF?

 

[agms]

AW: ET 4000 als OScam Server Probleme

[TABLE="class: status"]
[TR="class: c"]
[TD="class: statuscol14"]by V13 (120ms)[/TD]
[TD="class: statuscol10"]26.09.13 16:05:05[/TD]
[TD="class: statuscol11"]00:59:35[/TD]
[TD="class: statuscol15"]00:00:04[/TD]
[TD="class: statuscol16"]OK
[/TD]
[/TR]
[TR="class: c"]
[TD="class: statuscol0"]

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

[/TD]
[TD="class: statuscol5"][/TD]
[TD="class: statuscol7"][/TD]
[TD="class: statuscol8"][/TD]
[TD="class: statuscol9"]
[/TD]
[TD="class: statuscol12"][/TD]
[TD="class: statuscol13"][/TD]
[TD="class: statuscol14"][/TD]
[/TR]
[/TABLE]
meinst du das hier

 

[Mäx2.5]

AW: ET 4000 als OScam Server Probleme

ja sieht eigentlich gut aus.
Wie sind die Zeiten wenn freezer auftreten?

 

[agms]

AW: ET 4000 als OScam Server Probleme

wo sehe ich das

im log steht das

Spoiler

2013/09/26 16:05:05 5172A8 c opa disconnected from 92.78.145.232
2013/09/26 16:05:05 532D28 c encrypted cccam-client 92.78.145.232 granted (opa, au=off)

bei nem ganz kurzen freezer seh ich nix aussergewöhnliches

grad wieder kurz still stand 120ms

 

[Mäx2.5]

AW: ET 4000 als OScam Server Probleme

evtl. ist das Netzwerk oder die Box überlastet?
kannst mit telnet auf die Box und

top

eingeben

 

[agms]

AW: ET 4000 als OScam Server Probleme

komm irgendwie nicht drauf mit telnet habs eingeschalten bei windows

telnet(ip) oder??

habs bin drin und nun??

 

[Mäx2.5]

AW: ET 4000 als OScam Server Probleme

Benutze immer Putty, evtl. ip:23

 

[agms]

sorry ist jetzt offen

was ist da wichtig von den vielen daten??

hier nch ein log

Spoiler

[1970/01/01 01:00:14, 0] nmbd/nmbd.c:main(723)
Netbios nameserver version 3.0.37 started.
Copyright Andrew Tridgell and the Samba Team 1992-2009
[1970/01/01 01:00:14, 0] nmbd/nmbd_subnetdb.c:create_subnets(190)
create_subnets: No non-loopback local interfaces !
[1970/01/01 01:00:14, 0] nmbd/nmbd_subnetdb.c:create_subnets(191)
create_subnets: Waiting for an interface to appear ...
[1970/01/01 01:00:19, 0] nmbd/nmbd.c:main(723)
Netbios nameserver version 3.0.37 started.
Copyright Andrew Tridgell and the Samba Team 1992-2009
[1970/01/01 01:00:20, 0] /home/factory/nightly/build-enviroment/builds/openatv/et9x00/tmp/work/mips32el-oe-linux/samba-3.0.37-r10/samba-3.0.37/source/lib/pidfile.cidfile_create(112)
ERROR: nmbd is already running. File /var/run/nmbd.pid exists and process id 253 is running.
[1970/01/01 01:00:23, 0] nmbd/nmbd.c:main(723)
Netbios nameserver version 3.0.37 started.
Copyright Andrew Tridgell and the Samba Team 1992-2009
[1970/01/01 01:00:23, 0] nmbd/nmbd.c:main(742)
standard input is not a socket, assuming -D option
[1970/01/01 01:00:23, 0] /home/factory/nightly/build-enviroment/builds/openatv/et9x00/tmp/work/mips32el-oe-linux/samba-3.0.37-r10/samba-3.0.37/source/lib/pidfile.cidfile_create(112)
ERROR: nmbd is already running. File /var/run/nmbd.pid exists and process id 253 is running.
[2013/09/26 15:46:33, 0] nmbd/nmbd_packets.crocess_browse_packet(1067)
process_browse_packet: Discarding datagram from IP 192.168.178.33. Source name ET4X00<00> is one of our names !
[2013/09/26 15:51:34, 0] nmbd/nmbd_packets.crocess_browse_packet(1067)
process_browse_packet: Discarding datagram from IP 192.168.178.33. Source name ET4X00<00> is one of our names !
[2013/09/26 16:41:40, 0] nmbd/nmbd_packets.crocess_browse_packet(1067)
process_browse_packet: Discarding datagram from IP 192.168.178.33. Source name ET4X00<00> is one of our names !
[2013/09/26 16:44:36, 0] nmbd/nmbd_packets.crocess_browse_packet(1067)
process_browse_packet: Discarding datagram from IP 192.168.178.33. Source name ET4X00<00> is one of our names !
[2013/09/26 16:49:27, 0] nmbd/nmbd_packets.crocess_browse_packet(1067)
process_browse_packet: Discarding datagram from IP 192.168.178.33. Source name ET4X00<00> is one of our names !
[2013/09/26 16:54:34, 0] nmbd/nmbd_packets.crocess_browse_packet(1067)
process_browse_packet: Discarding datagram from IP 192.168.178.33. Source name ET4X00<00> is one of our names !
[2013/09/26 16:59:37, 0] nmbd/nmbd_packets.crocess_browse_packet(1067)
process_browse_packet: Discarding datagram from IP 192.168.178.33. Source name ET4X00<00> is one of our names !
[2013/09/26 17:04:43, 0] nmbd/nmbd_packets.crocess_browse_packet(1067)
process_browse_packet: Discarding datagram from IP 192.168.178.33. Source name ET4X00<00> is one of our names !
[2013/09/26 17:09:51, 0] nmbd/nmbd_packets.crocess_browse_packet(1067)
process_browse_packet: Discarding datagram from IP 192.168.178.33. Source name ET4X00<00> is one of our names !
[2013/09/26 17:14:56, 0] nmbd/nmbd_packets.crocess_browse_packet(1067)
process_browse_packet: Discarding datagram from IP 192.168.178.33. Source name ET4X00<00> is one of our names !
[2013/09/26 17:19:55, 0] nmbd/nmbd_packets.crocess_browse_packet(1067)
process_browse_packet: Discarding datagram from IP 192.168.178.33. Source name ET4X00<00> is one of our names !
[2013/09/26 17:25:04, 0] nmbd/nmbd_packets.crocess_browse_packet(1067)
process_browse_packet: Discarding datagram from IP 192.168.178.33. Source name ET4X00<00> is one of our names !
[2013/09/26 17:30:09, 0] nmbd/nmbd_packets.crocess_browse_packet(1067)
process_browse_packet: Discarding datagram from IP 192.168.178.33. Source name ET4X00<00> is one of our names !
[2013/09/26 17:35:18, 0] nmbd/nmbd_packets.crocess_browse_packet(1067)
process_browse_packet: Discarding datagram from IP 192.168.178.33. Source name ET4X00<00> is one of our names !
[2013/09/26 17:40:20, 0] nmbd/nmbd_packets.crocess_browse_packet(1067)
process_browse_packet: Discarding datagram from IP 192.168.178.33. Source name ET4X00<00> is one of our names !
[2013/09/26 17:45:21, 0] nmbd/nmbd_packets.crocess_browse_packet(1067)
process_browse_packet: Discarding datagram from IP 192.168.178.33. Source name ET4X00<00> is one of our names !
[2013/09/26 17:50:29, 0] nmbd/nmbd_packets.crocess_browse_packet(1067)
process_browse_packet: Discarding datagram from IP 192.168.178.33. Source name ET4X00<00> is one of our names !
[2013/09/26 17:55:36, 0] nmbd/nmbd_packets.crocess_browse_packet(1067)
process_browse_packet: Discarding datagram from IP 192.168.178.33. Source name ET4X00<00> is one of our names !
[2013/09/26 18:00:40, 0] nmbd/nmbd_packets.crocess_browse_packet(1067)
process_browse_packet: Discarding datagram from IP 192.168.178.33. Source name ET4X00<00> is one of our names !
[2013/09/26 18:05:48, 0] nmbd/nmbd_packets.crocess_browse_packet(1067)
process_browse_packet: Discarding datagram from IP 192.168.178.33. Source name ET4X00<00> is one of our names !
[2013/09/26 18:10:54, 0] nmbd/nmbd_packets.crocess_browse_packet(1067)
process_browse_packet: Discarding datagram from IP 192.168.178.33. Source name ET4X00<00> is one of our names !
[2013/09/26 18:16:02, 0] nmbd/nmbd_packets.crocess_browse_packet(1067)
process_browse_packet: Discarding datagram from IP 192.168.178.33. Source name ET4X00<00> is one of our names !
[2013/09/26 18:21:06, 0] nmbd/nmbd_packets.crocess_browse_packet(1067)
process_browse_packet: Discarding datagram from IP 192.168.178.33. Source name ET4X00<00> is one of our names !
[2013/09/26 18:26:10, 0] nmbd/nmbd_packets.crocess_browse_packet(1067)
process_browse_packet: Discarding datagram from IP 192.168.178.33. Source name ET4X00<00> is one of our names !

 

[Mäx2.5]

AW: ET 4000 als OScam Server Probleme

Hast du im Netzwerk 2 ET4x00?

 

[agms]

AW: ET 4000 als OScam Server Probleme

ja 1x server 1x client

soll das das problem sein

 

[Mäx2.5]

AW: ET 4000 als OScam Server Probleme

ändere mal bei einer den Netzwerknamen

 

[agms]

AW: ET 4000 als OScam Server Probleme

hab ich gemacht