MVP lockout on LAN failure

[bgowland]

I restarted my router a little earlier not realising my wife was watching a recorded programme on the MVP.

After the router restarted, the MVP continued to flash a 'broken connection' symbol and I couldn't put it into standby from remote. I power-cycled it but it never managed to download the dongle (I waited quite a few minutes).

I then used task manager to kill the pvrx2 mvp process, the rec. service created a new one but still no dongle download (the MVP was powered up at the time).

In the end, I had to unplug power on the MVP, kill the pvrx2 mvp process again then power up the MVP at which point it recovered.

There's an exception logged in the -3 log at the time I rebooted the router. I was wondering if this caused the lockout and prevented the MVP from recovering.

Cheers,
Brian

[sub]

Usually if the network connection is broken the app will restart the MVP server. Restarting the router should have triggered this, and I cant think of any reason it wouldnt have.

If its just a one-off problem though, its probably not worth investing any time to look into it.

[mvallevand]

I would guess the recovery had a problem because the IP changed which forces you to unplug it.

Martin

[bgowland]

Usually if the network connection is broken the app will restart the MVP server. Restarting the router should have triggered this, and I cant think of any reason it wouldnt have.

If its just a one-off problem though, its probably not worth investing any time to look into it.

I've seen it before and I 'think' it's only when the MVP is playing a video - if it's sitting at a menu etc., I think it recovers. I'll do some tests and let you know if I can reproduce it consistently.

I would guess the recovery had a problem because the IP changed which forces you to unplug it.

I can see how things could get confused but the IP address of the MVP wouldn't change. On reboot, the DHCP server in the router wouldn't attempt to 'push' new IP addresses out to connected machines (obviously) and unless the DHCP lease time allocated by the DHCP server is very short, the MVP shouldn't have tried to request a renewal - besides, I have static allocations for all my regular devices.

Hmmm, - OK thanks both. I expect this is MVP dongle logic - it lost connection at the Datalink, Network and Transport layers, the pvrx2 MVP process restarted faster than the router rebooted and the MVP didn't have a clue what to do next. The root of the problem seems to be that I wasn't able to put the MVP into standby using the remote. If I'd been able to do this, I could have brought it out of standby again and it would've established a new connection to the pvrx2 MVP process.

Cheers,
Brian

[mvallevand]

I can see how things could get confused but the IP address of the MVP wouldn't change. On reboot, the DHCP server in the router wouldn't attempt to 'push' new IP addresses out to connected machines (obviously) and unless the DHCP lease time allocated by the DHCP server is very short, the MVP shouldn't have tried to request a renewal - besides, I have static allocations for all my regular devices.

If you had been using mvpmc it would have gone back to the main menu with the Hauppauge dongle it does release the IP. There are definite log entries from an MVP with no IP

Code:

2008-07-20 20:35:44.393    VERBOSE    [5]    Received BOOTP request from client. bytesReceived: 300  address: 0.0.0.0
2008-07-20 20:35:53.424    VERBOSE    [5]    Received BOOTP request from client. bytesReceived: 300  address: 0.0.0.0
2008-07-20 20:36:02.893    VERBOSE    [5]    Received BOOTP request from client. bytesReceived: 300  address: 172.16.1.34

(I'm surprised you are writing email, I'd probably have had to take my wife out to dinner.)

Martin