Вход в биллинг - Billing entrance - www.CardsharingServer.com

English forum section

Автор Тема: How Log-file shall look like?  (Прочитано 3632 раз)

suma

  • Модератор
  • Ветеран
  • *****
  • Сообщений: 9487
  • Keep trying!
How Log-file shall look like?
« : 07 Сентября 2014, 14:45:35 »
Frequently, administration is asking users for log-file. How it looks like?

1. If your settings are OK and your receiver gets a response from the server, your login and password are accepted by the server, your log-file shall look like this:

Sep 07 16:29:15 192.168.1.33 tuxbox mgcamd v1.35a by mixvt (compiled Jan 26 2010 15:59:20)
Sep 07 16:29:15 192.168.1.33 [mg] Net:1:7:0:1s Show ecm:1, emm:0 Up:1 Au:3 Dir:0 Osd:no:80:0 Cache:0 Log:3:192.168.1.35:514 Reread:0
Sep 07 16:29:15 192.168.1.33 [mg] Ecm cache time: 0
Sep 07 16:29:15 192.168.1.33 Box type: mips dreambox (dm7025, dm800)
Sep 07 16:29:17 192.168.1.33 Conax.Key error 2: No such file or directory
Sep 07 16:29:17 192.168.1.33 Keys readed
Sep 07 16:29:17 192.168.1.33 AutoRoll.Key error 2: No such file or directory
Sep 07 16:29:17 192.168.1.33 Conax.Key error 2: No such file or directory
Sep 07 16:29:17 192.168.1.33 ignore prov 0500:050C00
Sep 07 16:29:17 192.168.1.33 ignore prov 0500:050900
Sep 07 16:29:17 192.168.1.33 priority prov 0600:000043
Sep 07 16:29:17 192.168.1.33 priority prov 0600:000013
Sep 07 16:29:17 192.168.1.33 [config] newcamd route = your login:servXX:XXXX3 server cardserv
Sep 07 16:29:17 192.168.1.33 [config] newcamd route = your login:servXX:XXXX8 server cardserv
Sep 07 16:29:17 192.168.1.33 [config] newcamd route = your login:servXX:XXXX9 server cardserv
Sep 07 16:29:17 192.168.1.33 [config] newcamd route = your login:servXX:XXX12 server cardserv
Sep 07 16:29:17 192.168.1.33 [config] newcamd route = your login:servXX:XXX21 server cardserv
Sep 07 16:29:17 192.168.1.33 [config] newcamd route = your login:servXX:XXX24 server cardserv
Sep 07 16:29:17 192.168.1.33 [config] newcamd route = your login:servXX:XXX26 server cardserv
Sep 07 16:29:17 192.168.1.33 newcamd keep alive: 300, incoming port: 0
Sep 07 16:29:17 192.168.1.33 [mgcam] emm thread started
Sep 07 16:29:17 192.168.1.33 [newcamd] Connecting to servXX:XXX12...
Sep 07 16:29:17 192.168.1.33 [newcamd] Connecting to servXX:XXX21...
Sep 07 16:29:17 192.168.1.33 [newcamd] Connecting to servXX:XXX24...
Sep 07 16:29:17 192.168.1.33 [newcamd] Connecting to servXX:XXX26...
Sep 07 16:29:17 192.168.1.33 [newcamd] Connecting to servXX:XXX15...
Sep 07 16:29:17 192.168.1.33 [newcamd] Connecting to servXX:XXX29...
Sep 07 16:29:18 192.168.1.33 Client <- Server: -- Sun Sep  7 16:29:17 2014
Sep 07 16:29:18 192.168.1.33  Server: -- Sun Sep  7 16:29:17 2014
Sep 07 16:29:18 192.168.1.33 [newcamd] Login to servXX:XXX03 as your login accepted (106ms)
Sep 07 16:29:18 192.168.1.33 Client <- Server: -- Sun Sep  7 16:29:17 2014
Sep 07 16:29:18 192.168.1.33 [newcamd] Login to servXX:XXX12 as your login accepted (106ms)
Sep 07 16:29:21 192.168.1.33 [mg0] <- CW from newcamd server name:port (376ms)
Sep 07 16:29:21 192.168.1.33 [mg0] 376 msec -- Sun Sep  7 16:29:21 2014
Sep 07 16:29:21 192.168.1.33 ===== Irdeto ECM on CaID 0x0602, pid 0x0259 ======
Sep 07 16:29:21 192.168.1.33 prov: 000000
Sep 07 16:29:21 192.168.1.33 cw0:0 CC 15 FE DF 99 20 88 41
Sep 07 16:29:21 192.168.1.33 cw1:0 DC 31 CA D7 53 82 8A 5F
Sep 07 16:29:21 192.168.1.33 [mg0] irdeto using chid 0013 version 45
Sep 07 16:29:21 192.168.1.33 [mgcamd] emm started
Sep 07 16:29:21 192.168.1.33  CaPID: 0x01F4 ProvID: 000000
Sep 07 16:29:21 192.168.1.33  CaPID: 0x01F5 ProvID: 000000

The main things you can see here are: your login to the server was accepted, and the keys from the server received.

2. If your settings are not OK and you have black-screen, it means that your login cannot be accepted, and consequently, keys from the server will not be received.

Sep 07 16:43:17 192.168.1.33 [mg0] network can't decode
Sep 07 16:43:17 192.168.1.33 [mg0] pid 0x0524 failed to decode.
Sep 07 16:43:17 192.168.1.33 [mg0] network can't decode
Sep 07 16:43:17 192.168.1.33 [mg0] pid 0x0624 failed to decode.
Sep 07 16:43:17 192.168.1.33 [mg0] No viaccess key(s) found for id 32A00 keynr 03
Sep 07 16:43:17 192.168.1.33 [mg0] network can't decode
Sep 07 16:43:17 192.168.1.33 [mg0] pid 0x0924 failed to decode.
Sep 07 16:43:17 192.168.1.33 [mg0] No nagra2 key(s) found for id 7 keynr 01
Sep 07 16:43:17 192.168.1.33 [mg0] network can't decode
Sep 07 16:43:17 192.168.1.33 [mg0] pid 0x0724 failed to decode.
Sep 07 16:43:17 192.168.1.33 [mg0] No seca key(s) found for id 68 keynr 0c
Sep 07 16:43:17 192.168.1.33 [mg0] network can't decode
Sep 07 16:43:17 192.168.1.33 [mg0] pid 0x0724 failed to decode.
Sep 07 16:43:18 192.168.1.33 [mg0] No conax key(s) found for id 0 keynr 21
Sep 07 16:43:18 192.168.1.33 [mg0] network can't decode
Sep 07 16:43:18 192.168.1.33 [mg0] pid 0x0824 failed to decode.
Sep 07 16:43:18 192.168.1.33 [mgcamd] emm started
Sep 07 16:43:18 192.168.1.33  CaPID: 0x0083 ProvID: 000000
Sep 07 16:43:18 192.168.1.33  CaPID: 0x0086 ProvID: 000000
Sep 07 16:43:18 192.168.1.33 [mgcamd] emm stopped
VU+Zero. 13E, 82.5E, 56E, Vip All, OpenPLI 6.0 image, OSCam: 1.20-unstable_svn. ALL POSTS WITHOUT SIGNATURE AND LOG-FILE will be ignored and deleted!1.mg_cfg here http://www.cardsharing.cc/index.php?topic=23717.msg58140#msg58140
2. ignore-priority.lists here http://www.cardsharing.cc/index.php?topic