Группа 3 (grp3.3usd.tv)

Настройка оборудования и программ

Re: Группа 3 (grp3.3usd.tv)

Сообщение kovalchyk1983a » 15 сен 2017, 19:38

Спутнег 1 писал(а):ну и ? где от вас запросы на сервер?
что из вас все по ниточке нужно вытягивать?

это и весь запрос больше нету, со старта викарда на каналах 85*
новичок
kovalchyk1983a
 
Сообщения: 73
Зарегистрирован: 15 апр 2013, 17:12

Re: Группа 3 (grp3.3usd.tv)

Сообщение kovalchyk1983a » 15 сен 2017, 19:39

kovalchyk1983a писал(а):
Спутнег 1 писал(а):ну и ? где от вас запросы на сервер?
что из вас все по ниточке нужно вытягивать?

это и весь запрос больше нету, со старта викарда на каналах 85*

16:41:23 192.168.0.103 wicardd: wicardd-sh4 version 1.19 beelive (Dec 28 2015) http://wicard.tv

16:41:23 192.168.0.103 wicardd: Build options: [AutoConf] [TuxBox SCI] [DVBAPI] [STAPI] [WEBIF] [ExMLog] [TWIN]

16:41:23 192.168.0.103 wicardd: disabling internal CAS - -1

16:41:23 192.168.0.103 under_app_detect: procname: linuxrc, daemonize = 0

16:41:23 192.168.0.103 under_app_detect: PPID: 0

16:41:23 192.168.0.103 3usd: Filter object created.

16:41:23 192.168.0.103 3usd1: Filter object created.

16:41:23 192.168.0.103 name10000: activity_timeout = 9000 ms

16:41:23 192.168.0.103 name10000: using default secure key

16:41:23 192.168.0.103 name10000: not decoded cache initialized, size: 64, ttl: 3000

16:41:23 192.168.0.103 name10001: activity_timeout = 9000 ms

16:41:23 192.168.0.103 name10001: using default secure key

16:41:23 192.168.0.103 name10001: not decoded cache initialized, size: 64, ttl: 3000

16:41:23 192.168.0.103 name10002: activity_timeout = 9000 ms

16:41:23 192.168.0.103 name10000: reader thread started, pid 2726, tid 695997640

16:41:23 192.168.0.103 name10002: using default secure key

16:41:23 192.168.0.103 name10002: not decoded cache initialized, size: 64, ttl: 3000

16:41:23 192.168.0.103 name10001: reader thread started, pid 2727, tid 697046216

16:41:23 192.168.0.103 name10003: activity_timeout = 9000 ms

16:41:23 192.168.0.103 name10003: using default secure key

16:41:23 192.168.0.103 name10003: not decoded cache initialized, size: 64, ttl: 3000

16:41:23 192.168.0.103 name10002: reader thread started, pid 2728, tid 698094792

16:41:23 192.168.0.103 name10004: activity_timeout = 9000 ms

16:41:23 192.168.0.103 name10003: reader thread started, pid 2729, tid 699143368

16:41:23 192.168.0.103 name10004: using default secure key

16:41:23 192.168.0.103 name10004: not decoded cache initialized, size: 64, ttl: 3000

16:41:23 192.168.0.103 name10005: activity_timeout = 9000 ms

16:41:23 192.168.0.103 name10005: using default secure key

16:41:23 192.168.0.103 name10005: not decoded cache initialized, size: 64, ttl: 3000

16:41:23 192.168.0.103 name10006: activity_timeout = 9000 ms

16:41:23 192.168.0.103 name10006: using default secure key

16:41:23 192.168.0.103 name10004: reader thread started, pid 2730, tid 700191944

16:41:23 192.168.0.103 name10005: reader thread started, pid 2731, tid 701240520

16:41:23 192.168.0.103 name10006: not decoded cache initialized, size: 64, ttl: 3000

16:41:23 192.168.0.103 name10007: activity_timeout = 9000 ms

16:41:23 192.168.0.103 name10007: using default secure key

16:41:23 192.168.0.103 name10007: not decoded cache initialized, size: 64, ttl: 3000

16:41:23 192.168.0.103 name10006: reader thread started, pid 2732, tid 702289096

16:41:23 192.168.0.103 name10010: activity_timeout = 9000 ms

16:41:23 192.168.0.103 name10010: using default secure key

16:41:23 192.168.0.103 name10007: reader thread started, pid 2733, tid 703337672

16:41:23 192.168.0.103 name10010: not decoded cache initialized, size: 64, ttl: 3000

16:41:23 192.168.0.103 wicardd: creating default balancer.

16:41:23 192.168.0.103 default: [balancer] chain key missed, creating default chain including all readers.

16:41:23 192.168.0.103 default: balancer object created, 1 stage(s).

16:41:23 192.168.0.103 name10010: reader thread started, pid 2734, tid 704386248

16:41:23 192.168.0.103 DVB: Detected API: DVBAPI3

16:41:24 192.168.0.103 DVB0[DVBAPI3]: starting camd.socket handler thread

16:41:24 192.168.0.103 wicardd: registered 2 filter(s), 9 reader(s), 1 balancer(s), 0 tuner(s) and 0 server(s)

16:41:24 192.168.0.103 wicardd: loaded 0 user account(s)

16:41:24 192.168.0.103 wicardd: ECM cache size = 0

16:41:24 192.168.0.103 DVB0[DVBAPI3]: DVB handler thread started, pid 2735, tid 705930440

16:41:24 192.168.0.103 wicardd: main thread, pid 2725, tid 694947840

16:41:24 192.168.0.103 wicardd: Discovery thread terminated.

16:41:24 192.168.0.103 name10000: connect to [scrubbed]

16:41:24 192.168.0.103 name10001: connect to [scrubbed]

16:41:24 192.168.0.103 name10002: connect to [scrubbed]

16:41:24 192.168.0.103 name10003: connect to [scrubbed]

16:41:24 192.168.0.103 name10004: connect to [scrubbed]

16:41:24 192.168.0.103 name10005: connect to [scrubbed]

16:41:24 192.168.0.103 name10006: connect to [scrubbed]

16:41:24 192.168.0.103 name10007: connect to [scrubbed]

16:41:24 192.168.0.103 name10010: connect to [scrubbed]

16:41:24 192.168.0.103 name10001: Server detected: WiCard

16:41:24 192.168.0.103 name10002: Server detected: WiCard

16:41:24 192.168.0.103 name10000: Server detected: WiCard

16:41:24 192.168.0.103 name10005: Server detected: WiCard

16:41:24 192.168.0.103 name10003: Server detected: WiCard

16:41:24 192.168.0.103 name10007: Server detected: WiCard

16:41:24 192.168.0.103 name10004: Server detected: WiCard

16:41:24 192.168.0.103 name10006: Server detected: WiCard

16:41:24 192.168.0.103 name10001: CAID 4AE0, providers 2, UA 0000000000000000

16:41:24 192.168.0.103 name10001: provider 0: id 000000, SA 0000000000000000

16:41:24 192.168.0.103 name10001: provider 1: id 000015, SA 0000000000000000

16:41:24 192.168.0.103 name10001: auto update disabled

16:41:24 192.168.0.103 name10002: CAID 0000, providers 1, UA 0000000000000000

16:41:24 192.168.0.103 name10002: provider 0: id 000000, SA 0000000000000000

16:41:24 192.168.0.103 name10002: auto update disabled

16:41:24 192.168.0.103 name10002: provider data updated

16:41:24 192.168.0.103 name10001: provider data updated

16:41:24 192.168.0.103 name10001: reconnecting... connected

16:41:24 192.168.0.103 name10002: reconnecting... connected

16:41:24 192.168.0.103 name10005: CAID 1843, providers 1, UA 0000000000000000

16:41:24 192.168.0.103 name10005: provider 0: id 000000, SA 0000000000000000

16:41:24 192.168.0.103 name10005: auto update disabled

16:41:24 192.168.0.103 name10006: CAID 1834, providers 1, UA 0000000000000000

16:41:24 192.168.0.103 name10006: provider 0: id 000000, SA 0000000000000000

16:41:24 192.168.0.103 name10007: CAID 1722, providers 1, UA 0000000000000000

16:41:24 192.168.0.103 name10007: provider 0: id 000000, SA 0000000000000000

16:41:24 192.168.0.103 name10007: auto update disabled

16:41:24 192.168.0.103 name10004: CAID 098C, providers 1, UA 0000000000000000

16:41:24 192.168.0.103 name10004: provider 0: id 000000, SA 0000000000000000

16:41:24 192.168.0.103 name10004: auto update disabled

16:41:24 192.168.0.103 name10004: provider data updated

16:41:24 192.168.0.103 name10007: provider data updated

16:41:24 192.168.0.103 name10007: reconnecting... connected

16:41:24 192.168.0.103 name10006: auto update disabled

16:41:24 192.168.0.103 name10006: provider data updated

16:41:24 192.168.0.103 name10006: reconnecting... connected

16:41:24 192.168.0.103 name10005: provider data updated

16:41:24 192.168.0.103 name10005: reconnecting... connected

16:41:24 192.168.0.103 name10004: reconnecting... connected

16:41:24 192.168.0.103 name10000: CAID 0500, providers 10, UA 0000000000000000

16:41:24 192.168.0.103 name10000: provider 0: id 024700, SA 0000000000000000

16:41:24 192.168.0.103 name10000: provider 1: id 032500, SA 0000000000000000

16:41:24 192.168.0.103 name10000: provider 2: id 041200, SA 0000000000000000

16:41:24 192.168.0.103 name10000: provider 3: id 041700, SA 0000000000000000

16:41:24 192.168.0.103 name10000: provider 4: id 042200, SA 0000000000000000

16:41:24 192.168.0.103 name10003: CAID 0602, providers 11, UA 0000000000000000

16:41:24 192.168.0.103 name10003: provider 0: id 00000B, SA 0000000000000000

16:41:24 192.168.0.103 name10003: provider 1: id 000011, SA 0000000000000000

16:41:24 192.168.0.103 name10003: provider 2: id 000027, SA 0000000000000000

16:41:24 192.168.0.103 name10000: provider 5: id 042300, SA 0000000000000000

16:41:24 192.168.0.103 name10000: provider 6: id 042700, SA 0000000000000000

16:41:24 192.168.0.103 name10000: provider 7: id 043800, SA 0000000000000000

16:41:24 192.168.0.103 name10000: provider 8: id 060A00, SA 0000000000000000

16:41:24 192.168.0.103 name10000: provider 9: id 060C00, SA 0000000000000000

16:41:24 192.168.0.103 name10003: provider 3: id 00002F, SA 0000000000000000

16:41:24 192.168.0.103 name10003: provider 4: id 000042, SA 0000000000000000

16:41:24 192.168.0.103 name10003: provider 5: id 00004C, SA 0000000000000000

16:41:24 192.168.0.103 name10003: provider 6: id 00008D, SA 0000000000000000

16:41:24 192.168.0.103 name10000: auto update disabled

16:41:24 192.168.0.103 name10000: provider data updated

16:41:24 192.168.0.103 name10000: reconnecting... connected

16:41:25 192.168.0.103 name10003: provider 7: id 00008E, SA 0000000000000000

16:41:25 192.168.0.103 name10003: provider 8: id 000091, SA 0000000000000000

16:41:25 192.168.0.103 name10003: provider 9: id 0000BD, SA 0000000000000000

16:41:25 192.168.0.103 name10003: provider 10: id 00FFFF, SA 0000000000000000

16:41:25 192.168.0.103 name10003: auto update disabled

16:41:25 192.168.0.103 name10003: provider data updated

16:41:25 192.168.0.103 name10003: reconnecting... connected

16:41:25 192.168.0.103 name10010: Server detected: WiCard

16:41:25 192.168.0.103 name10010: CAID 0B01, providers 1, UA 0000000000000000

16:41:26 192.168.0.103 name10010: provider 0: id 000000, SA 0000000000000000

16:41:26 192.168.0.103 name10010: auto update disabled

16:41:26 192.168.0.103 name10010: provider data updated

16:41:26
новичок
kovalchyk1983a
 
Сообщения: 73
Зарегистрирован: 15 апр 2013, 17:12

Re: Группа 3 (grp3.3usd.tv)

Сообщение kovalchyk1983a » 15 сен 2017, 21:24

18:28:04 192.168.0.103 wicardd: wicardd-sh4 version 1.19 beelive (Dec 28 2015) http://wicard.tv

18:28:04 192.168.0.103 wicardd: Build options: [AutoConf] [TuxBox SCI] [DVBAPI] [STAPI] [WEBIF] [ExMLog] [TWIN]

18:28:04 192.168.0.103 wicardd: disabling internal CAS - -1

18:28:04 192.168.0.103 under_app_detect: procname: linuxrc, daemonize = 0

18:28:04 192.168.0.103 under_app_detect: PPID: 0

18:28:04 192.168.0.103 3usd: Filter object created.

18:28:04 192.168.0.103 3usd1: Filter object created.

18:28:04 192.168.0.103 name10000: activity_timeout = 9000 ms

18:28:04 192.168.0.103 name10000: using default secure key

18:28:04 192.168.0.103 name10000: not decoded cache initialized, size: 64, ttl: 3000

18:28:04 192.168.0.103 name10001: activity_timeout = 9000 ms

18:28:04 192.168.0.103 name10001: using default secure key

18:28:04 192.168.0.103 name10001: not decoded cache initialized, size: 64, ttl: 3000

18:28:04 192.168.0.103 name10002: activity_timeout = 9000 ms

18:28:04 192.168.0.103 name10002: using default secure key

18:28:04 192.168.0.103 name10002: not decoded cache initialized, size: 64, ttl: 3000

18:28:04 192.168.0.103 name10000: reader thread started, pid 1425, tid 695997640

18:28:04 192.168.0.103 name10001: reader thread started, pid 1426, tid 697046216

18:28:04 192.168.0.103 name10003: activity_timeout = 9000 ms

18:28:04 192.168.0.103 name10003: using default secure key

18:28:04 192.168.0.103 name10003: not decoded cache initialized, size: 64, ttl: 3000

18:28:04 192.168.0.103 name10002: reader thread started, pid 1427, tid 698094792

18:28:04 192.168.0.103 name10004: activity_timeout = 9000 ms

18:28:04 192.168.0.103 name10004: using default secure key

18:28:04 192.168.0.103 name10004: not decoded cache initialized, size: 64, ttl: 3000

18:28:04 192.168.0.103 name10003: reader thread started, pid 1428, tid 699143368

18:28:04 192.168.0.103 name10005: activity_timeout = 9000 ms

18:28:04 192.168.0.103 name10005: using default secure key

18:28:04 192.168.0.103 name10005: not decoded cache initialized, size: 64, ttl: 3000

18:28:04 192.168.0.103 name10004: reader thread started, pid 1429, tid 700191944

18:28:04 192.168.0.103 name10006: activity_timeout = 9000 ms

18:28:04 192.168.0.103 name10006: using default secure key

18:28:04 192.168.0.103 name10006: not decoded cache initialized, size: 64, ttl: 3000

18:28:04 192.168.0.103 name10005: reader thread started, pid 1430, tid 701240520

18:28:04 192.168.0.103 name10006: reader thread started, pid 1431, tid 702289096

18:28:04 192.168.0.103 name10007: activity_timeout = 9000 ms

18:28:04 192.168.0.103 name10007: using default secure key

18:28:04 192.168.0.103 name10007: not decoded cache initialized, size: 64, ttl: 3000

18:28:04 192.168.0.103 name10010: activity_timeout = 9000 ms

18:28:04 192.168.0.103 name10010: using default secure key

18:28:04 192.168.0.103 name10010: not decoded cache initialized, size: 64, ttl: 3000

18:28:04 192.168.0.103 wicardd: creating default balancer.

18:28:04 192.168.0.103 name10007: reader thread started, pid 1432, tid 703337672

18:28:04 192.168.0.103 default: [balancer] chain key missed, creating default chain including all readers.

18:28:04 192.168.0.103 default: balancer object created, 1 stage(s).

18:28:04 192.168.0.103 name10010: reader thread started, pid 1433, tid 704386248

18:28:04 192.168.0.103 DVB: Detected API: DVBAPI3

18:28:04 192.168.0.103 DVB0[DVBAPI3]: starting camd.socket handler thread

18:28:04 192.168.0.103 wicardd: registered 2 filter(s), 9 reader(s), 1 balancer(s), 0 tuner(s) and 0 server(s)

18:28:04 192.168.0.103 wicardd: loaded 0 user account(s)

18:28:04 192.168.0.103 wicardd: main thread, pid 1424, tid 694947840

18:28:04 192.168.0.103 DVB0[DVBAPI3]: DVB handler thread started, pid 1434, tid 705930440

18:28:04 192.168.0.103 wicardd: Discovery thread terminated.

18:28:05 192.168.0.103 name10000: connect to [scrubbed]

18:28:05 192.168.0.103 name10001: connect to [scrubbed]

18:28:05 192.168.0.103 name10002: connect to [scrubbed]

18:28:05 192.168.0.103 name10003: connect to [scrubbed]

18:28:05 192.168.0.103 name10004: connect to [scrubbed]

18:28:05 192.168.0.103 name10005: connect to [scrubbed]

18:28:05 192.168.0.103 name10006: connect to [scrubbed]

18:28:05 192.168.0.103 name10007: connect to [scrubbed]

18:28:05 192.168.0.103 name10010: connect to [scrubbed]

18:28:05 192.168.0.103 name10000: Server detected: WiCard

18:28:05 192.168.0.103 name10005: Server detected: WiCard

18:28:05 192.168.0.103 name10010: Server detected: WiCard

18:28:05 192.168.0.103 name10006: Server detected: WiCard

18:28:05 192.168.0.103 name10007: Server detected: WiCard

18:28:05 192.168.0.103 name10001: Server detected: WiCard

18:28:05 192.168.0.103 name10003: Server detected: WiCard

18:28:05 192.168.0.103 name10002: Server detected: WiCard

18:28:05 192.168.0.103 name10004: Server detected: WiCard

18:28:05 192.168.0.103 name10000: CAID 0500, providers 10, UA 0000000000000000

18:28:05 192.168.0.103 name10000: provider 0: id 024700, SA 0000000000000000

18:28:05 192.168.0.103 name10000: provider 1: id 032500, SA 0000000000000000

18:28:05 192.168.0.103 name10000: provider 2: id 041200, SA 0000000000000000

18:28:05 192.168.0.103 name10000: provider 3: id 041700, SA 0000000000000000

18:28:05 192.168.0.103 name10000: provider 4: id 042200, SA 0000000000000000

18:28:05 192.168.0.103 name10000: provider 5: id 042300, SA 0000000000000000

18:28:05 192.168.0.103 name10000: provider 6: id 042700, SA 0000000000000000

18:28:05 192.168.0.103 name10000: provider 7: id 043800, SA 0000000000000000

18:28:05 192.168.0.103 name10000: provider 8: id 060A00, SA 0000000000000000

18:28:05 192.168.0.103 name10000: provider 9: id 060C00, SA 0000000000000000

18:28:05 192.168.0.103 name10000: auto update disabled

18:28:05 192.168.0.103 name10000: provider data updated

18:28:05 192.168.0.103 name10000: reconnecting... connected

18:28:05 192.168.0.103 name10002: CAID 0000, providers 1, UA 0000000000000000

18:28:05 192.168.0.103 name10002: provider 0: id 000000, SA 0000000000000000

18:28:05 192.168.0.103 name10002: auto update disabled

18:28:05 192.168.0.103 name10010: CAID 0B01, providers 1, UA 0000000000000000

18:28:05 192.168.0.103 name10004: CAID 098C, providers 1, UA 0000000000000000

18:28:05 192.168.0.103 name10004: provider 0: id 000000, SA 0000000000000000

18:28:05 192.168.0.103 name10004: auto update disabled

18:28:05 192.168.0.103 name10004: provider data updated

18:28:05 192.168.0.103 name10010: provider 0: id 000000, SA 0000000000000000

18:28:05 192.168.0.103 name10010: auto update disabled

18:28:05 192.168.0.103 name10010: provider data updated

18:28:05 192.168.0.103 name10010: reconnecting... connected

18:28:05 192.168.0.103 name10002: provider data updated

18:28:05 192.168.0.103 name10002: reconnecting... connected

18:28:05 192.168.0.103 name10007: CAID 1722, providers 1, UA 0000000000000000

18:28:05 192.168.0.103 name10007: provider 0: id 000000, SA 0000000000000000

18:28:05 192.168.0.103 name10007: auto update disabled

18:28:05 192.168.0.103 name10007: provider data updated

18:28:05 192.168.0.103 name10007: reconnecting... connected

18:28:05 192.168.0.103 name10004: reconnecting... connected

18:28:05 192.168.0.103 name10006: CAID 1834, providers 1, UA 0000000000000000

18:28:05 192.168.0.103 name10006: provider 0: id 000000, SA 0000000000000000

18:28:05 192.168.0.103 name10006: auto update disabled

18:28:05 192.168.0.103 name10006: provider data updated

18:28:05 192.168.0.103 name10006: reconnecting... connected

18:28:05 192.168.0.103 name10005: CAID 1843, providers 1, UA 0000000000000000

18:28:05 192.168.0.103 name10005: provider 0: id 000000, SA 0000000000000000

18:28:05 192.168.0.103 name10005: auto update disabled

18:28:05 192.168.0.103 name10005: provider data updated

18:28:05 192.168.0.103 name10005: reconnecting... connected

18:28:05 192.168.0.103 name10001: CAID 4AE0, providers 2, UA 0000000000000000

18:28:05 192.168.0.103 name10001: provider 0: id 000000, SA 0000000000000000

18:28:05 192.168.0.103 name10001: provider 1: id 000015, SA 0000000000000000

18:28:05 192.168.0.103 name10001: auto update disabled

18:28:05 192.168.0.103 name10001: provider data updated

18:28:05 192.168.0.103 name10001: reconnecting... connected

18:28:05 192.168.0.103 name10003: CAID 0602, providers 11, UA 0000000000000000

18:28:05 192.168.0.103 name10003: provider 0: id 00000B, SA 0000000000000000

18:28:05 192.168.0.103 name10003: provider 1: id 000011, SA 0000000000000000

18:28:05 192.168.0.103 name10003: provider 2: id 000027, SA 0000000000000000

18:28:05 192.168.0.103 name10003: provider 3: id 00002F, SA 0000000000000000

18:28:05 192.168.0.103 name10003: provider 4: id 000042, SA 0000000000000000

18:28:05 192.168.0.103 name10003: provider 5: id 00004C, SA 0000000000000000

18:28:05 192.168.0.103 name10003: provider 6: id 00008D, SA 0000000000000000

18:28:05 192.168.0.103 name10003: provider 7: id 00008E, SA 0000000000000000

18:28:05 192.168.0.103 name10003: provider 8: id 000091, SA 0000000000000000

18:28:05 192.168.0.103 name10003: provider 9: id 0000BD, SA 0000000000000000

18:28:05 192.168.0.103 name10003: provider 10: id 00FFFF, SA 0000000000000000

18:28:05 192.168.0.103 name10003: auto update disabled

18:28:05 192.168.0.103 name10003: provider data updated

18:28:05
новичок
kovalchyk1983a
 
Сообщения: 73
Зарегистрирован: 15 апр 2013, 17:12

Re: Группа 3 (grp3.3usd.tv)

Сообщение Спутнег 1 » 15 сен 2017, 22:19

ну как нет, если вы скидываете время от следующей строки
18:28:05 192.168.0.103 name10003: provider data updated
18:28:05

с таким логом и количеством предоставляемой вами информации, мне вам нечем помочь
Спутнег 1
 
Сообщения: 5113
Зарегистрирован: 25 авг 2011, 21:31

Re: Группа 3 (grp3.3usd.tv)

Сообщение tyomka » 16 сен 2017, 19:41

Посмотрите пожалуйста soroka77, приехал на выходные, тюнер был выключен из розетки, немного поработало и отвалилось.
Поменял пароль, все равно не работает. Перед тем, как ковыряться дальше, может меня за что-то забанили.
tyomka
 
Сообщения: 90
Зарегистрирован: 22 ноя 2011, 20:53

Re: Группа 3 (grp3.3usd.tv)

Сообщение tyomka » 16 сен 2017, 19:51

Как-то так, не могу понять.

Sep 16 14:54:04 192.168.1.104 DVB0[DVBAPI3]: ECM81 (0500:060A00/89C.0) 'HTB+:MATCh! HD' not decoded by 3usd10000
Sep 16 14:54:14 192.168.1.104 3usd10000: 5 ECM80 (0500:060C00/89C.0) for DVB0[DVBAPI3] not decoded (563/563/563 ms)
Sep 16 14:54:14 192.168.1.104 DVB0[DVBAPI3]: ECM80 (0500:060C00/89C.0) 'HTB+:MATCh! HD' not decoded by 3usd10000
Sep 16 14:54:14 192.168.1.104 3usd10000: 5 ECM80 (0500:060A00/89C.0) for DVB0[DVBAPI3] not decoded (463/463/464 ms)
Sep 16 14:54:14 192.168.1.104 DVB0[DVBAPI3]: ECM80 (0500:060A00/89C.0) 'HTB+:MATCh! HD' not decoded by 3usd10000
Sep 16 14:54:20 192.168.1.104 3usd10000: 5 ECM80 (0500:060C00/3EE.0) for DVB0[DVBAPI3] not decoded (76/76/76 ms)
Sep 16 14:54:20 192.168.1.104 DVB0[DVBAPI3]: ECM80 (0500:060C00/3EE.0) 'N/A' not decoded by 3usd10000
Sep 16 14:54:20 192.168.1.104 3usd10000: 5 ECM80 (0500:060A00/3EE.0) for DVB0[DVBAPI3] not decoded (140/140/140 ms)
Sep 16 14:54:20 192.168.1.104 DVB0[DVBAPI3]: ECM80 (0500:060A00/3EE.0) 'N/A' not decoded by 3usd10000
Sep 16 14:54:27 192.168.1.104 3usd10000: 5 ECM81 (0500:060C00/3EE.0) for DVB0[DVBAPI3] not decoded (1025/1025/1025 ms)
Sep 16 14:54:27 192.168.1.104 DVB0[DVBAPI3]: ECM81 (0500:060C00/3EE.0) 'N/A' not decoded by 3usd10000
Sep 16 14:54:27 192.168.1.104 3usd10000: 5 ECM81 (0500:060A00/3EE.0) for DVB0[DVBAPI3] not decoded (922/925/925 ms)
Sep 16 14:54:27 192.168.1.104 DVB0[DVBAPI3]: ECM81 (0500:060A00/3EE.0) 'N/A' not decoded by 3usd10000
Sep 16 14:54:37 192.168.1.104 3usd10000: 5 ECM80 (0500:060C00/3EE.0) for DVB0[DVBAPI3] not decoded (806/806/806 ms)
Sep 16 14:54:37 192.168.1.104 DVB0[DVBAPI3]: ECM80 (0500:060C00/3EE.0) 'HTB+:Rossiya 24' not decoded by 3usd10000
Sep 16 14:54:37 192.168.1.104 3usd10000: 5 ECM80 (0500:060A00/3EE.0) for DVB0[DVBAPI3] not decoded (708/708/708 ms)
tyomka
 
Сообщения: 90
Зарегистрирован: 22 ноя 2011, 20:53

Re: Группа 3 (grp3.3usd.tv)

Сообщение krovla2 » 16 сен 2017, 21:25

Спутнег 1 писал(а):ну конечно, шарой пользуются одни честные и правильные люди =)

Не одни, но и в том числе.
У меня, например, бывает что на одном канале рес висит и по двое суток. Но это не значит, что я каскад куда-то сливаю. Просто выключается тв, а включиться он может и через день, и через два.
Спутнег 1 писал(а):в виду большого кол-ва каскадеров, пришлось ввести новое ограничение, за простой на одном канале более суток, будет банить
достаточно переключить канал и просмотр продолжиться
А сказать об этом до "плясок с бубном" юзеров что-то не позволило?
krovla2
 
Сообщения: 91
Зарегистрирован: 26 мар 2012, 17:17

Re: Группа 3 (grp3.3usd.tv)

Сообщение tyomka » 16 сен 2017, 21:44

В квартире постоянно не живем (soroka77), тюнер из розетки не всегда выключаю.
У меня 8180, если моргнул свет, может включенный и неделю простоять.
Теперь буду знать, что за это могут забанить. Буду всегда выключать из розетки перед отъездом, раз такие дела.
tyomka
 
Сообщения: 90
Зарегистрирован: 22 ноя 2011, 20:53

Re: Группа 3 (grp3.3usd.tv)

Сообщение alexeywk » 17 сен 2017, 08:15

Спутнег 1 писал(а):
alexeywk писал(а):Спасибо. Теперь понятно.

Только простоя более суток обычно не бывает. Максимум пол дня. Обычно днём каналы переключаются.
И после включения утром помогает только отключение ресивера от сети и несколько минут ожидания. Простое переключение каналов не помогает.

попробуете как будет сегодня, завтра
внесли изменения

Пока все ОК. Второй день полет нормальный. Ещё не блокировался.
новичок
alexeywk
 
Сообщения: 6
Зарегистрирован: 16 апр 2013, 13:17

Re: Группа 3 (grp3.3usd.tv)

Сообщение bobby » 17 сен 2017, 16:05

Сообщайте если что не так. И причину обязательно. стояло так так то, столько то времени итд
Суппорт проекта
bobby
 
Сообщения: 201
Зарегистрирован: 17 авг 2011, 02:54

Пред.След.

Вернуться в Работа сервиса

Кто сейчас на конференции

Сейчас этот форум просматривают: нет зарегистрированных пользователей и гости: 29