Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £99! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £149! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

[VU+ Solo2] Mgcamds keeps stopping

  • Thread starter Thread starter Philjobooboo
  • Start date Start date
Hi again,still doing it tried the suggestions. I'm using vix image installed by wos when I bought the box last week, and mgcamds 1.35a. I've noticed for example that if you switch to radio, then back to tv I have to restart camds. It's not a huge problem just annoying. cheers all Phil
 
Mine seems fine now. A lot more stable since I've stopped going into deep standby at night.
 
Do you have logging enabled? I found that with option enabled for me it would randomly stop. Disabled logging and the random stops stopped.

Sent from my GT-I9505 using Tapatalk
 
I'm having Mgcamd problems on my solo2 and Technomate nano oe since upgrading them both to Zeus, i'm going to try re-installing and a using a different config file.
p.s. the N lines are seem fine in Cccam, just tried them.
 
Noticed it's been stopping quite often this morning. Not to the extent that I need to go into softcam manager but it's stopping for a good few seconds.
 
Yea it's awful today. Freezing every few seconds. Nothing changed since last night either. Sounds like something wrong with MgCamd.
 
I rebooted the router and it's a lot better now. Might have to get in touch with BT. Says it's connected at 78mbps but every now and again it's so bloody slow.
 
I rebooted the router and it's a lot better now. Might have to get in touch with BT. Says it's connected at 78mbps but every now and again it's so bloody slow.

I am getting the same problem with my internet getting killed since using mgcamd.1.35a (and soon as I disconnect my solo2 from the router I get internet again!) I'm going to downgrade to 1.35 and see what happens.
 
You are probably using the logging option with a wrong IP. Easiest solution is to use the configs by Mr Mister
 
I can't take credit for this (Ronand gave me this info).... in your mg_cfg file I changed "L: { 03 } 172.16.1.1 28007 /tmp/mgcamd.log" to "0: { 03 } 172.16.1.1 28007 /tmp/mgcamd.log" (this is default IP in the config file).

I did an update and it did not kill my router, I'll see how I get on during the overnight update.

I also kept 1.35a on as well.
 
I can't take credit for this (Ronand gave me this info).... in your mg_cfg file I changed "L: { 03 } 172.16.1.1 28007 /tmp/mgcamd.log" to "0: { 03 } 172.16.1.1 28007 /tmp/mgcamd.log" (this is default IP in the config file).

I did an update and it did not kill my router, I'll see how I get on during the overnight update.

I also kept 1.35a on as well.

not really sure what you mean by over night update as the image does not auto update, you have to physically tell it to update, maybe you mean ABM ? or your EPG ?.
 
not really sure what you mean by over night update as the image does not auto update, you have to physically tell it to update, maybe you mean ABM ? or your EPG ?.

Yes I do meant that. But, I was thinking L to a 0 thing is more to do with it killing my router (while doing the updates).

I think I may have taken this thread off topic. Sorry about that.

But keeping it on topic... My Mgcamds still stops tho!
 
Last edited by a moderator:
I was thinking L to a 0 thing is more to do with it killing my router

Constantly trying to send a log file to a box that doesn't exist is bound to cause problems on your network...
 
It should be

Code:
L: { 00 }
not
Code:
0: { 03 } 172.16.1.1 28007 /tmp/mgcamd.log"

Best thing,
Use mgcamd form openvix site.
Use these configs.
http://www.world-of-satellite.com/showthread.php?24555-original-vu-duo&p=182712#post182712

I've gone the configs from the link. I was using a PDF guide that I downloaded from here (and that is how I got those setting for the L part)

with the mg_cfg file I have just left as is. That is the correct thing to do yeah?

Cheers guys.
 
I had a similar problem, I changed the mg_cfg file settings. This section; I changed to 06 and saved the file and ftp back into Var - Keys
# box type
# 00 autodetect, change only if you think wrong type detected.
# 01 dbox2
# 02 dreambox
# 03 triple-dragon
# 04 relook
# 05 openbox
# 06 dreambox/mips
# 08 stapi/kathrein
# 09 stapi/ipbox
# 11 stapi/openbox
B: { 06 }

I would like to confirm that this fixed my issue
 

OpenViX Feeds Status

Back
Top