Bad glitching recently

[dazirl]

go into softcam manager cccam info then server info. It will tell you in there.
But it won't tell me in MGcamd.

incorrect mate, it can be done by telnet

Open your mg_cfg and find the following

# Log option, summ of:
# 00 off
# 01 network udp log
# 02 log to console
# 04 file, appended ! delete it by yourself, before it eat all your hdd
# + IP udp-port log-file-name
L: { 00 } 172.16.1.1 28007 /tmp/mgcamd.log

change it to

# Log option, summ of:
# 00 off
# 01 network udp log
# 02 log to console
# 04 file, appended ! delete it by yourself, before it eat all your hdd
# + IP udp-port log-file-name
L: { 02 } 172.16.1.1 28007 /tmp/mgcamd.log

that allows mgcamd to log all info to telnet console.

now reupload your mg_cfg to your stb

now open telnet and connect to the box and run the following 3 commands (dependent on version of mgcamd you use, if you use mgcamd 1.38 just change mgcamd_1.35a to mgcamd_1.38)

cd /usr/bin
killall mgcamd_1.35a -9
mgcamd_1.35a -d

now keep a eye on telnet as the line reconnects, it will show all caids on server and amount of so called cards but dont forget that depending on what software server uses, cache connectors can show as cards with a little black magic

after line connects and it shows you all caids under it you will see something like got xx (the xx is amount of so called cards)

 

[river4ever]

Will give that a try and see if it says something different from checking softcam manager.

 

[jfish]

or use a syslog server on a PC to log this info

download this on PC

Downloads

the free edition - run it on PC - ensure firewall allows port 514

then in mg_cfg edit above line as follows

L: {01} 192.168.0.5 514

change IP to address of computer running the syslog server

 

[jfish]

just to confirm the above logging to a syslog file works for me as I have just configured my mgcamd and it is logging everything to my syslog server

 

[jfish]

this taken from another forum - may explain the current issues

I suspect the many servers out there have not updated their cache timeout from say 400ms to 1000ms after the reported Sky ECM timeout change (probably because of the WiFi latency with their new Sky Q service)..

If the timeout is too short, the cache will be of no use and you get enforced glitching (as opposed to glitching due card shortage)