Connection Loop

[Lindsay]

For a long time now I quite often get the situation where the mvpmc dongle just loops from pinging to rebuilding to pinging......... It seems to happen if the recording service is stopped and restarted. I had to unplug the mvp to reload the dongle before it would connect again.

This happened today and I got the looping at 08:07:44. The attached log shows an error at the time in question.

[mvallevand]

It looks like gbpvr is having trouble the weather plugin a couple of times. I would turn off mvpmc and change the <MVPLoadPluginsEarlier> setting to true to see if the weather plugin is working.

Martin

[psycik]

yeah i get that sometimes as well. And I end up just pulling the plug. I've never thought to look at the logs to see if a plugin was having a problem.

[Lindsay]

Bit late getting back but today I changed the config setting re mvploadplugins as you suggested, Martin, and my log showed no errors and I had no problem with the looping. I'll try a few more times tomorrow to see how consistent it is.

[Lindsay]

Yep, seems to have fixed the problem. I presume it is OK to leave the config setting to true, now, Martin?

[mvallevand]

I don't use this setting since the only plugin I have is ML2 I haven't seen the problem you showed but the impact is negligible The more plugins the worse the negative side effects are but only when your mvp is off. If your mvp is on a lot or you have a dedicated server it's not much of an issue. I did ask sub about this setting earlier and here is his opinion http://forums.nextpvr.com/showthread.php?t=31161

I know the weather plugin can use a lot of system resources and I avoid it. I didn't need the plugin to tell me how much snow had fallen overnight last night but maybe it could have told me how stupid I was trying to drive in it today! I couldn't even maneuver my car from my street and it's parked at a neighbours until the roads are cleared, so no work today. This plugin will also tell me there is 25 cm more to follow today, something I'm wanting to ignore.

Also, what I proposed isn't really a solution it's a workaround and ideally the plugin author should try and prevent this crash if you are seeing it regularly.

Martin