Upgraded from v3 to v6... now my MVP's don't work.

[hufnagel]

So I finally decided to upgrade to v6.0.19.120 tonight after getting tired of dealing with the more frequent crashes of Sage v3 and my MVP's. The transition seemed to go fine and I can see all of my recordings and schedules fine. I followed the instructions to activate Media Extender but now none of my MVPs are working and I cannot find the log file(s) people mention looking for. I have no idea where to start to solve this so....

HELP!

addendum:
no idea if the following will help but...
I'm currently running v6 in trial mode until I get at least 1 MVP tested and running
the MVP nearest me has listed on the bottom "model 86001 Rev E1 Lot 1105R". when it "boots" it shows "Rev1.0"
I have no Hauppauge software installed on my machine... never needed it before.

[AngelofDeth]

What happens when you try to boot the MVP? What screen does it get to? Are you running a DHCP server? You might also want to turn off the firewall on your sage server box just to eliminate that as a possible problem.

[hufnagel]

Originally Posted by AngelofDeth

What happens when you try to boot the MVP? What screen does it get to?

I get the initial MediaMVP screen that shows Rev1.0 and the 5 white rectangles. It immediately goes to 3 blue, 2 white and sits there indefinitely.
I turned on debugging and get the following in the log...

Fri 3/16 23:50:02.650 Received bootp request
Fri 3/16 23:50:02.651 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:43886724 nSeconds:100 flags:0
MAC: 00:0d:fe:00:74:b8
Fri 3/16 23:50:02.651 Matched request to client 0
Fri 3/16 23:50:02.651 servername 192.168.1.71
Fri 3/16 23:50:02.651 Sending bootp reply

Originally Posted by AngelofDeth

Are you running a DHCP server?

Yes, under Microsoft Windows Server 2003 SP1. I have all 4 MVPs setup in DHCP as reservations for IPs in the same subnet as the PVR machine (which also has a reservation.)

Originally Posted by AngelofDeth

You might also want to turn off the firewall on your sage server box just to eliminate that as a possible problem.

The Windows Firewall has been disabled for nearly a year on this machine. The only web site this box ever visits is sagetv.com

[hufnagel]

Noticed something else as I was doing more research...
when I run the "Register SageTV Media Extender or Placeshifter License" program it indicates that my trial has NOT started. something tells me that's part of the problem.

[hufnagel]

AH HAH!!!
Got it!

I'll post up the fix shortly...

For the old setup (v3) to work I had to set one of the parameters in DHCP... namely '066 Boot Server Host Name' to a value of 'pvr.home' (which is the FQDN of my PVR machine). Having that setting enabled causes the MVP's to NOT boot properly.

Well, I got 1 MVP working. Can I only use 1 MVP while in trial mode?

[hufnagel]

Well, I let everything sit overnight (it was 2am when I finally went to bed ) and when I woke up all 4 MVPs had started the SageTV interface

Watched a couple shows on various TVs, decided I like the way it works and forked over the cash for the pre v4 to v6 upgrade and 4 Media Extender licenses. All I need to do now is learn how to alter some of the remote button commands (specifically 'go', and 'menu' work totally backwards), spend at least a week playing with it, get the WAF (and tweaks), and I can finally get the setup designed and installed for a client of mine who has been DYING to get this at his house... and he's only seen it running v3!! v6 will blow him away.

[hufnagel]

Ok. My happiness has turned to pain. I had to restart the machine SageTV runs on. Now NONE of the MVPs work again. It's been 10 hours now and they refuse to restart. I even tried installing the latest beta 6.1.4 and no go. Here's the log file. I need some advice.

[BobPhoenix]

Sorry don't have any advise other that to contact SageTV Support directly. Since you have the beta installed you should probably go here to report a problem otherwise if you've reverted back to 6.0.19 then maybe here. But either would probably be fine. Also someone else here may have an idea as well but I would definitely start the support request. You can always tell them you have fixed it - if you do fix it before they get back to you.

[hufnagel]

Yea. The part that's really annoying is I've gone from v3.0 where I needed to restart 6 programs (service, local client, 4 MVP clients) every couple of days (and have a brutal memory hog at over 1GB of used memory) to having a fantastic running system with beautiful services (the visible fast forward/rewind is great and the response times to remote commands are lightyears better) that will be totally useless for at least a couple hours if you need to restart it for any reason.

The part that really pains me is THIS is the version I've been waiting for. I have a half-dozen (at least) customers for my computer consulting biz that have seen my setup when running v3.0 and are clambering for it. They'll be insanely happier with v6 by far.

I installed the latest beta in hopes that it might cure the problem... it doesn't. I'll downgrade back to 6.0 if needed.

I'll throw out some technical info to make life easier for those who read this, and for future reference...

Server IP: 192.168.1.71
MVP1 Client IP: 192.168.1.65 MAC: 00:0d:fe:00:3e:17
MVP2 Client IP: 192.168.1.66 MAC: 00:0d:fe:00:a2:c6
MVP3 Client IP: 192.168.1.67 MAC: 00:0d:fe:00:74:b8
MVP4 Client IP: 192.168.1.68 MAC: 00:0d:fe:00:76:9e

relevant sections of the attached log file...

...
Sun 3/18 0:30:43.632 Received bootp request
Sun 3/18 0:30:43.633 Op:1 hwtype:1 hwaddrlen:6hopcount:0 transaction:-496150990 nSeconds:100 flags:0 MAC: 00:0d:fe:00:74:b8
Sun 3/18 0:30:43.633 Added MVP client to our bootp list 00:0d:fe:00:74:b8
Sun 3/18 0:30:43.633 servername 192.168.1.71
Sun 3/18 0:30:43.633 Sending bootp reply
Sun 3/18 0:31:10.354 Received bootp request
Sun 3/18 0:31:10.354 Op:1 hwtype:1 hwaddrlen:6hopcount:0 transaction:-996671691 nSeconds:100 flags:0 MAC: 00:0d:fe:00:76:9e
Sun 3/18 0:31:10.355 Added MVP client to our bootp list 00:0d:fe:00:76:9e
Sun 3/18 0:31:10.355 servername 192.168.1.71
Sun 3/18 0:31:10.355 Sending bootp reply
Sun 3/18 0:31:10.487 Received tftp packet
Sun 3/18 0:31:10.506 Reading mvp.bin in mode octet
Sun 3/18 0:31:10.507 Opening file
Sun 3/18 0:31:10.641 TFTP timeout
Sun 3/18 0:31:13.907 TFTP timeout
Sun 3/18 0:31:16.253 At last block
Sun 3/18 0:31:28.203 Server got broadcast packet: java.net.DatagramPacket@1209d1b
Sun 3/18 0:31:28.924 Server sent back mini discovery data:java.net.DatagramPacket@1209d1b to /192.168.1.68 3072
Sun 3/18 0:31:28.943 MiniUI got connection from Socket[addr=/192.168.1.68,port=3199,localport=31099]
Sun 3/18 0:31:28.944 MiniUI is adding to its map:000dfe00769e
Sun 3/18 0:31:28.944 Creating new UI for client:000dfe00769e
Sun 3/18 0:31:28.976 Creating-2 new UI for client:000dfe00769e UIManager:localhost@@000dfe00769e-2a865a
Sun 3/18 0:31:29.273 MiniUI established for 000dfe00769e
...
Sun 3/18 0:32:39.499 Received bootp request
Sun 3/18 0:32:39.499 Op:1 hwtype:1 hwaddrlen:6hopcount:0 transaction:78397013 nSeconds:100 flags:0 MAC: 00:0d:fe:00:3e:17
Sun 3/18 0:32:39.499 Matched request to client 0
Sun 3/18 0:32:39.500 servername 192.168.1.71
Sun 3/18 0:32:39.500 Sending bootp reply
Sun 3/18 0:33:23.622 Ministry is waiting for 180 sec
Sun 3/18 0:33:36.600 Received bootp request
Sun 3/18 0:33:36.601 Op:1 hwtype:1 hwaddrlen:6hopcount:0 transaction:1673604337 nSeconds:100 flags:0 MAC: 00:0d:fe:00:a2:c6
Sun 3/18 0:33:36.601 Added MVP client to our bootp list 00:0d:fe:00:a2:c6
Sun 3/18 0:33:36.601 servername 192.168.1.71
Sun 3/18 0:33:36.602 Sending bootp reply
..
Sun 3/18 7:25:52.942 Received tftp packet
Sun 3/18 7:25:52.944 Reading mvp.bin in mode octet
Sun 3/18 7:25:52.944 Opening file
Sun 3/18 7:25:53.393 TFTP timeout
Sun 3/18 7:25:56.810 TFTP timeout
Sun 3/18 7:25:57.537 TFTP timeout
Sun 3/18 7:25:58.823 At last block
Sun 3/18 7:26:10.603 Server got broadcast packet: java.net.DatagramPacket@165e7a5
Sun 3/18 7:26:10.900 Server sent back mini discovery data:java.net.DatagramPacket@165e7a5 to /192.168.1.66 3072
Sun 3/18 7:26:10.919 MiniUI got connection from Socket[addr=/192.168.1.66,port=3595,localport=31099]
Sun 3/18 7:26:10.920 MiniUI is adding to its map:000dfe00a2c6
Sun 3/18 7:26:10.920 Creating new UI for client:000dfe00a2c6
Sun 3/18 7:26:11.080 Creating-2 new UI for client:000dfe00a2c6 UIManager:localhost@@000dfe00a2c6-14b3397
Sun 3/18 7:26:11.367 MiniUI established for 000dfe00a2c6
...
Sun 3/18 7:59:15.285 Received tftp packet
Sun 3/18 7:59:15.286 Received tftp packet
Sun 3/18 7:59:15.288 Reading mvp.bin in mode octet
Sun 3/18 7:59:15.289 Opening file
Sun 3/18 7:59:15.290 Reading mvp.bin in mode octet
Sun 3/18 7:59:15.290 Opening file
Sun 3/18 7:59:16.689 TFTP timeout
Sun 3/18 7:59:18.852 TFTP timeout
Sun 3/18 7:59:19.655 TFTP timeout
Sun 3/18 7:59:19.655 TFTP timeout
Sun 3/18 7:59:20.973 TFTP timeout
Sun 3/18 7:59:21.002 At last block
Sun 3/18 7:59:21.061 At last block
Sun 3/18 7:59:32.398 Server got broadcast packet: java.net.DatagramPacket@229c98
Sun 3/18 7:59:32.695 Server sent back mini discovery data:java.net.DatagramPacket@229c98 to /192.168.1.65 3072
Sun 3/18 7:59:32.695 Server got broadcast packet: java.net.DatagramPacket@56c668
Sun 3/18 7:59:32.714 MiniUI got connection from Socket[addr=/192.168.1.65,port=4050,localport=31099]
Sun 3/18 7:59:32.715 MiniUI is adding to its map:000dfe003e17
Sun 3/18 7:59:32.715 Creating new UI for client:000dfe003e17
Sun 3/18 7:59:32.740 Creating-2 new UI for client:000dfe003e17 UIManager:localhost@@000dfe003e17-fbd70b
Sun 3/18 7:59:33.276 Server sent back mini discovery data:java.net.DatagramPacket@56c668 to /192.168.1.67 3072
Sun 3/18 7:59:33.280 MiniUI established for 000dfe003e17
...
Sun 3/18 7:59:36.490 MiniUI got connection from Socket[addr=/192.168.1.67,port=3667,localport=31099]
Sun 3/18 7:59:36.491 MiniUI is adding to its map:000dfe0074b8
Sun 3/18 7:59:36.491 Creating new UI for client:000dfe0074b8
Sun 3/18 7:59:36.499 Creating-2 new UI for client:000dfe0074b8 UIManager:localhost@@000dfe0074b8-1f14b06
...
Sun 3/18 7:59:36.788 MiniUI established for 000dfe0074b8
...

breakdown of events.

| MVP # | PowerUp @        | bin file xfer @  | MiniUI established @ |
|   1   | 3/18 0:32:39.499 | 3/18 7:59:15.288 | 3/18 7:59:33.280     |
|   2   | 3/18 0:33:36.601 | 3/18 7:25:52.942 | 3/18 7:26:11.367     |
|   3   | 3/18 0:30:43.633 | 3/18 7:59:15.290 | 3/18 7:59:36.788     |
|   4   | 3/18 0:31:10.354 | 3/18 0:31:10.506 | 3/18 0:31:29.273     |

You can see that other than #4 all of them took 7 hours or more to actually start.

I do not use any SageTV Clients on PCs or on the server. My method of playback is exclusively the MVPs.

I'll give this until Monday night at which point I'll submit for support.