MVP Never Progresses past "Starting Application"

[MrApollinax]

Got my MVP in the mail yesterday and was excited to set it up in my network. Here is what I have:

P4 1.6 Ghz
1GB RAM
Plextor PX-TV402U
Window XP Pro
No Firewall
Router: DGL-4300
Switch: Dlink 5-port 1000/100/10
MVP is served a static DHCP address


So to test basic functionality I connect the MVP to my TV and connect the LAN cables to the switch. On my PC I install the Haup software package. I power up the MVP and the screens go through normal screen cycle and displays the Haup applicaiton on the TV screen. The router reports that DHCP has served my MVP the right IP address and I can ping it. I can even read the media and playback the files on my computer. Good Stuff!

As great as that is I bought this MVP and client licence for Sage to get the sage functionality on my TV. So i unistall the Haup software package and run ccleaner to clear out any straggling registry entries. I power down the MVP and I check sagetv.com and see a new release is available. So I install 4.1.4 and I load the client licence into my system. So far so good. I double check to make sure SageTV server and Media Extender Server are both "Enabled" and go power up my MVP.

So the screen starts up and I see the MVP get an IP address. The MVP then contacts the Media Boot Server and loads the program. Here is where my troubles start. The MVP stays at "Starting Application" and never progresses past that. If i go back to my Sage machine I can no longer ping the MVP. I never see anything other than the MVP startup screen with the the words "Starting Application" on the bottom.

Any help would be really appreciated.

[jquinlan]

Try to power cycle the MVP a couple more times if you have not. I heard SAGE wrote thier own Kernal for the MVP so it is a different application from the Haup software, but that worked so your MVP seems to be functioning properly.

[2FarGone]

I have been having the EXACT same problem:

http://forums.sagetv.com/forums/showthread.php?t=14771

I am starting to think that it might have something to do with the Dlink router (DGL-4300) or something.... I have ordered a new router and a new NIC card, so I am going to try that this weekend.

If you do find a solution please post it, since I know there are a few other people that are experiencing the same problem.

Thanks!
:goodjob:

[MrApollinax]

2FarGone:
I really don't think it has anything to do with the DGL-4300. On the LAN side it has no packet filtering at all. The SPI is only in place for traffic leaving the LAN to the WAN. But just in case I've given the MVP the same priority on my LAN as my Xbox. Another reason I don't think that the router is problem is because I can install the Haup software on the same box as SageTV and the MVP works as advertised with the Haup software. Since I'm not the only one having this issue I'm hoping someone out there is working on this as well.

jquinlan:
I've run through my scenario multiple times so I've power cycled my MVP many, many times. The MVP will always work with the Haup software package. I may try installing the plugin everyone is talking about in the other thread and try that out.


I've looked through all my router logs and cannot see any errors or discarded frames on the LAN. So I'm guessing there is a process that is not coming up within SageTV itself that is keeping this from working. Does anyone here know how I can open up a debug and see the process list as the kernel comes up? Something that I can look at and see where the process may be dying?

[BBCritical]

I have the same issues with the same router.... read 2FarGone's thread.

[MrApollinax]

I went to that thread and I think you guys may be chasing your tails with the ALG settings. ALG is used as a trigger to open up ports for certain applications to certain IPs on your LAN. It shouldn't do anything with LAN-to-LAN communications. Tonight I'm going to fire up ethereal to see if I can monitor what packets are being sent to and from the MVP. The biggest "gotcha" that i have with this is that my setup will work fine IF i use the Haup software package. This however means I'm not using the imbedded MVP support in SageTV 4.1.4

[_Demo_]

Could you check if the network connection is dropped on your router after it displays starting application and if it is reestablished soon after that?

Thanks

_Demo_

[MrApollinax]

I'll have to wait till I get home to try that. Is there anything else I should check?

[_Demo_]

You could also try to ping the mvp.

_Demo_

[MrApollinax]

If you see in my first post, once I'm in this state the MVP doesn't respond to ping. I'm pretty sure that my router stays up as none of my logs on the routers show any of the ports going down. I see pretty consistently the MVP gets the configured DHCP IP address everytime it turns on.

[_Demo_]

One possiblity is that the transfer is corrupted or your mvp.bin file is bad.

Which mvp model do you have? (under the mvp)

_Demo_

[MrApollinax]

I belive it is a D3A, I'll have to double check to be sure and the start screen shows version 1.0 underneath the MVP splash/logo

[flavius]

Try you guys try to use a switch - or at least a hub to connect it to the router?

[BBCritical]

Tried to put another switch between the router and mvp... still got the same results :(

[flavius]

So, this http://forums.sagetv.com/forums/showthread.php?p=130629#post130629 does not help either, I assume?

[MrApollinax]

Could you check if the network connection is dropped on your router after it displays starting application and if it is reestablished soon after that?

Thanks

_Demo_

Okay, i was finally able to test this with a switch between the MVP and my router so I can watch the LEDs on the switch. I can confirm the above behavior. Soon after "Starting Application" is displayed on my TV I see the link LED on my switch for the MVP go out momentarily and then come back. I've also configured debug logging and here is the output for this issue:

Thu 12/22 23:05:12.021 PM currState=0 wakeupTime=Thu 12/22/2005 23:58:00.000
Thu 12/22 23:05:42.022 PM currState=0 wakeupTime=Thu 12/22/2005 23:58:00.000
Thu 12/22 23:06:01.198 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:303370235 nSeconds:100 flags:0
MAC: 00:0d:fe:00:33:6e
Thu 12/22 23:06:01.200 Matched request to client 0
Thu 12/22 23:06:01.200 Warning, request from 00:0d:fe:00:33:6e doesn't have IP.
Thu 12/22 23:06:11.652 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:303370235 nSeconds:100 flags:0
MAC: 00:0d:fe:00:33:6e
Thu 12/22 23:06:11.653 Matched request to client 0
Thu 12/22 23:06:11.654 Warning, request from 00:0d:fe:00:33:6e doesn't have IP.
Thu 12/22 23:06:15.061 PM currState=0 wakeupTime=Thu 12/22/2005 23:58:00.000
Thu 12/22 23:06:20.705 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:830038626 nSeconds:100 flags:0
MAC: 00:0d:fe:00:33:6e
Thu 12/22 23:06:20.706 Matched request to client 0
Thu 12/22 23:06:20.707 servername 192.168.0.129
Thu 12/22 23:06:20.840 Reading mvp.bin in mode octet
Thu 12/22 23:06:20.841 Opening file
Thu 12/22 23:06:33.881 At last block
Thu 12/22 23:06:45.063 PM currState=0 wakeupTime=Thu 12/22/2005 23:58:00.000
Thu 12/22 23:07:15.064 PM currState=0 wakeupTime=Thu 12/22/2005 23:58:00.000


Here is the log from my router to show that it served out an IP to the MVP:

[INFO] Thu Dec 22 23:12:22 2005 Previous message repeated 2 times
[INFO] Thu Dec 22 23:11:14 2005 Assigned new lease 192.168.0.177 to client 000DFE00336E

Note that 00:0d:fe:00:33:6e is the MAC of the MVP. Also my MVP is in fact a D3A.

[ckron]

Here is what I got in my log:


Fri 12/23 8:23:03.804 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 8:23:16.582 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:104989221 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:23:16.583 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:23:25.603 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:104989221 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:23:25.604 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:23:33.808 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 8:23:35.584 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:617999553 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:23:35.584 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:23:44.604 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:617999553 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:23:44.605 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:23:54.586 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:1131012511 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:23:54.587 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:24:03.810 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 8:24:05.375 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:1131012511 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:24:05.376 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:24:13.211 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:1131012511 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:24:13.212 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:24:26.591 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:1995037509 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:24:26.592 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:24:33.813 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 8:24:35.612 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:1995037509 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:24:35.613 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:24:45.594 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:-1786912291 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:24:45.595 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:24:54.615 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:-1786912291 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:24:54.616 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:25:03.816 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 8:25:04.597 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:-1273898630 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:25:04.598 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:25:13.618 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:-1273898630 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:25:13.619 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:25:23.600 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:-760883644 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:25:23.600 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:25:32.620 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:-760883644 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:25:32.621 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:25:33.819 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 8:25:42.602 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:-247869990 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:25:42.603 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:25:44.084 Ministry is waiting for 180 sec
Fri 12/23 8:25:51.623 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:-247869990 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:25:51.624 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:26:03.822 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 8:26:04.606 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:346147053 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:26:04.606 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:26:13.626 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:346147053 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:26:13.627 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:26:23.608 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:859162599 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:26:23.609 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:26:32.629 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:859162599 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:26:32.630 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:26:33.824 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 8:26:42.611 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:1372175686 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:26:42.612 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:26:51.632 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:1372175686 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:26:51.633 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:27:01.614 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:1885192048 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:27:01.615 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:27:03.827 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 8:27:10.635 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:1885192048 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:27:10.636 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:27:20.617 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:-1896762503 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:27:20.617 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:27:29.638 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:-1896762503 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:27:29.638 Couldn't match client 00:50:c2:24:5f:ff
Fri 12/23 8:27:33.830 PM currState=0 wakeupTime=Fri 12/23/2005 16:58:00.000
Fri 12/23 8:27:44.620 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:-1248744005 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Fri 12/23 8:27:44.621 Couldn't match client 00:50:c2:24:5f:ff


My MVP stops at contacting media boot server

[MrApollinax]

Until someone can help me find a viable solution to this issue I want to try and use Matt's MVP plugin instead. I have a Media extender license right now for the MVP. Can I use this license for Matt's MVP plugin as well?

[2FarGone]

I don't believe the Media Extender License will work as a Client License, but you should still be able to install the Trial Version of the Client Software. Which would give you 15 days to test it out. Not a perfect solution, but hopefully there will be a fix in the next week or so.

:goodjob:

[ckron]

Has anyone considered that Java might be the cuprit? I noticed that the latest version of Matt's plugin requires version=1.4.2_07 or later. I am running version=1.4.2_04-b05 which might explain my issues with this latest version of Matt's client. Does anyone know what version is required for SageTV Media Extender support?

[MrApollinax]

I'm not sure if java would be the culprit or not. But at this point I'm willing to try anything. Here is my java version:

java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05
Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode, sharing)


I may just turn off the servers in Sage and use the Haup software as is until this is resolved. I've tried two different nics with the same behavior. I only have D-Link routers here since I've never had problems with the brand. Since the Haup software works I can only guess that the issue is with the Sage implemtation. I've tried everyone's suggestions and I still can't get it to work. Thanks everyone for your help!

[ckron]

I'm not sure if java would be the culprit or not. But at this point I'm willing to try anything. Here is my java version:

java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05
Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode, sharing)


I may just turn off the servers in Sage and use the Haup software as is until this is resolved. I've tried two different nics with the same behavior. I only have D-Link routers here since I've never had problems with the brand. Since the Haup software works I can only guess that the issue is with the Sage implemtation. I've tried everyone's suggestions and I still can't get it to work. Thanks everyone for your help!


I just upgraded to this version which appears to be the latest. Matt's client now connects perfectly everytime. SageTV Media Extender now logs Java errors:

Sat 12/24 11:19:43.299 Seeker awoken
Sat 12/24 11:19:43.300 MARK 1 currRecord=null enc=Hauppauge WinTV PVR PCI II Capture #2 clients=[] ir=false
Sat 12/24 11:19:43.301 Seeker in AUTOMATIC mode nextRecord=A[52628,52432,"Time Zone Watches",14948@1225.01:00,120] nextTTA=49216700
Sat 12/24 11:19:43.302 newRecord=null
Sat 12/24 11:19:43.303 NOTHING TO RECORD FOR NOW...
Sat 12/24 11:19:43.303 MARK 1 currRecord=null enc=Hauppauge WinTV PVR PCI II Capture clients=[] ir=false
Sat 12/24 11:19:43.304 Seeker in AUTOMATIC mode nextRecord=null nextTTA=9223372036854775807
Sat 12/24 11:19:43.305 newRecord=null
Sat 12/24 11:19:43.305 NOTHING TO RECORD FOR NOW...
Sat 12/24 11:19:43.616 Seeker clearing unwanted and partial files...
Sat 12/24 11:19:43.624 Seeker waiting for 815 mins.
Sat 12/24 11:20:12.444 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:97179016 nSeconds:100 flags:0
MAC: 00:50:c2:24:5f:ff
Sat 12/24 11:20:12.445 Matched request to client 0
Sat 12/24 11:20:12.445 servername 192.168.0.124
Sat 12/24 11:20:12.578 Reading mvp.bin in mode octet
Sat 12/24 11:20:12.579 Opening file
Sat 12/24 11:20:13.012 PM currState=0 wakeupTime=Sun 12/25/2005 0:58:00.000
Sat 12/24 11:20:13.093 Ministry is waiting for 180 sec
Sat 12/24 11:20:21.767 At last block
Sat 12/24 11:20:43.053 PM currState=0 wakeupTime=Sun 12/25/2005 0:58:00.000
Sat 12/24 11:21:13.056 PM currState=0 wakeupTime=Sun 12/25/2005 0:58:00.000
Sat 12/24 11:21:28.990 Seeker.finishWatch(/127.0.0.1:2380@@SAGETV_PROCESS_LOCAL_UI)
Sat 12/24 11:21:28.997 Seeker.finishWatch(/127.0.0.1:2380@@SAGETV_PROCESS_LOCAL_UI)
Sat 12/24 11:21:31.108 Error communicating with server:java.io.EOFException
Sat 12/24 11:21:31.108 Cleaning up c/s connection
Sat 12/24 11:21:31.109 NetworkManager CommunicationFailure : /127.0.0.1:2380 type=1
Sat 12/24 11:21:31.110 NetworkClient fullCleanup /127.0.0.1:2380
Sat 12/24 11:21:31.111 Cleaning up c/s connection
Sat 12/24 11:21:31.112 Cleaning up c/s connection
Sat 12/24 11:21:31.113 Seeker awoken
Sat 12/24 11:21:31.114 MARK 1 currRecord=null enc=Hauppauge WinTV PVR PCI II Capture #2 clients=[] ir=false
Sat 12/24 11:21:31.115 Seeker in AUTOMATIC mode nextRecord=A[52628,52432,"Time Zone Watches",14948@1225.01:00,120] nextTTA=49108886
Sat 12/24 11:21:31.115 newRecord=null
Sat 12/24 11:21:31.120 NOTHING TO RECORD FOR NOW...
Sat 12/24 11:21:31.120 MARK 1 currRecord=null enc=Hauppauge WinTV PVR PCI II Capture clients=[] ir=false
Sat 12/24 11:21:31.121 Seeker in AUTOMATIC mode nextRecord=null nextTTA=9223372036854775807
Sat 12/24 11:21:31.123 MsgRecv thread is terminating for /127.0.0.1:2380
Sat 12/24 11:21:31.124 newRecord=null
Sat 12/24 11:21:31.125 NOTHING TO RECORD FOR NOW...
Sat 12/24 11:21:31.164 Seeker clearing unwanted and partial files...
Sat 12/24 11:21:31.167 Seeker waiting for 813 mins.
Sat 12/24 11:21:33.162 Error with c/s comm:java.lang.NullPointerException
Sat 12/24 11:21:33.162 NetworkManager CommunicationFailure : /127.0.0.1:2380 type=2
Sat 12/24 11:21:33.163 NetworkManager CommunicationFailure : /127.0.0.1:2380 type=2
Sat 12/24 11:21:43.060 PM currState=0 wakeupTime=Sun 12/25/2005 0:58:00.000
Sat 12/24 11:21:44.000 Error communicating with server:java.lang.NullPointerException
Sat 12/24 11:21:44.001 Cleaning up c/s connection
Sat 12/24 11:21:44.002 NetworkManager CommunicationFailure : /127.0.0.1:2380 type=1
Sat 12/24 11:21:44.003 MsgSend thread terminating for /127.0.0.1:2380
Sat 12/24 11:22:06.306 Sage.exit() called.
Sat 12/24 11:22:06.306 Cleaning up servers
Sat 12/24 11:22:06.311 Error w/SageTV client connection:java.net.SocketException: socket closed
Sat 12/24 11:22:06.313 Cleaning up PM
Sat 12/24 11:22:06.315 PM currState=0 wakeupTime=Sun 12/25/2005 0:58:00.000
Sat 12/24 11:22:06.316 Killed Carny.
Sat 12/24 11:22:06.317 Killed Scheduler.
Sat 12/24 11:22:06.318 Ministry is shutting down....destroying the converts in progress
Sat 12/24 11:22:06.319 Killed Seeker.
Sat 12/24 11:22:06.320 Killed EPG.
Sat 12/24 11:22:06.322 stopEncoding0 called
Sat 12/24 11:22:06.323 Stopped graph res=0x0
Sat 12/24 11:22:06.323 teardownGraph0 called for device=Hauppauge WinTV PVR PCI II Capture
java.net.SocketException: socket closed
Sat 12/24 11:22:06.329 MiniInput ServerSocket died from:java.net.SocketException: socket closed
Sat 12/24 11:22:06.330 MiniUI ServerSocket died from:java.net.SocketException: socket closed
Sat 12/24 11:22:06.331 MiniPlayer ServerSocket died from:java.net.SocketException: socket closed
java.net.SocketException: socket closed
Sat 12/24 11:22:06.426 stopEncoding0 called
Sat 12/24 11:22:06.427 Stopped graph res=0x0
Sat 12/24 11:22:06.427 teardownGraph0 called for device=Hauppauge WinTV PVR PCI II Capture
Sat 12/24 11:22:06.529 Killed MMC.
Sat 12/24 11:22:06.530 Killed UIManager.



I never got these errors before updating Java!

[flavius]

Did you send this thru the official support channel? I would.

[MrApollinax]

SageTV Media Extender now logs Java errors:

I never got these errors before updating Java!

I also get java errors in my logs.

[MrApollinax]

okay, i've downgraded to java version 1.4.2_10-b03. I', still running into the same problem:

Sun 12/25 11:56:47.646 NetworkManager CommunicationFailure : /127.0.0.1:1034 type=1
Sun 12/25 11:56:47.647 MsgSend thread terminating for /127.0.0.1:1034
Sun 12/25 11:56:59.981 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:303370222 nSeconds:100 flags:0
MAC: 00:0d:fe:00:33:6e
Sun 12/25 11:56:59.982 Added MVP client to our bootp list 00:0d:fe:00:33:6e
Sun 12/25 11:56:59.983 Warning, request from 00:0d:fe:00:33:6e doesn't have IP.
Sun 12/25 11:57:00.573 PM currState=0 wakeupTime=Sun 12/25/2005 14:28:00.000
Sun 12/25 11:57:09.001 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:303370222 nSeconds:100 flags:0
MAC: 00:0d:fe:00:33:6e
Sun 12/25 11:57:09.002 Matched request to client 0
Sun 12/25 11:57:09.007 Warning, request from 00:0d:fe:00:33:6e doesn't have IP.
Sun 12/25 11:57:18.053 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:791340774 nSeconds:100 flags:0
MAC: 00:0d:fe:00:33:6e
Sun 12/25 11:57:18.055 Matched request to client 0
Sun 12/25 11:57:18.057 servername 192.168.0.108
Sun 12/25 11:57:18.189 Reading mvp.bin in mode octet
Sun 12/25 11:57:18.190 Opening file
Sun 12/25 11:57:19.744 TFTP timeout
Sun 12/25 11:57:29.535 At last block


The only thing different now is that the logs are reporting that TFTP is timing out.

[Jason]

okay, i've downgraded to java version 1.4.2_10-b03. I', still running into the same problem:

Sun 12/25 11:56:47.646 NetworkManager CommunicationFailure : /127.0.0.1:1034 type=1
Sun 12/25 11:56:47.647 MsgSend thread terminating for /127.0.0.1:1034
Sun 12/25 11:56:59.981 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:303370222 nSeconds:100 flags:0
MAC: 00:0d:fe:00:33:6e
Sun 12/25 11:56:59.982 Added MVP client to our bootp list 00:0d:fe:00:33:6e
Sun 12/25 11:56:59.983 Warning, request from 00:0d:fe:00:33:6e doesn't have IP.
Sun 12/25 11:57:00.573 PM currState=0 wakeupTime=Sun 12/25/2005 14:28:00.000
Sun 12/25 11:57:09.001 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:303370222 nSeconds:100 flags:0
MAC: 00:0d:fe:00:33:6e
Sun 12/25 11:57:09.002 Matched request to client 0
Sun 12/25 11:57:09.007 Warning, request from 00:0d:fe:00:33:6e doesn't have IP.
Sun 12/25 11:57:18.053 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:791340774 nSeconds:100 flags:0
MAC: 00:0d:fe:00:33:6e
Sun 12/25 11:57:18.055 Matched request to client 0
Sun 12/25 11:57:18.057 servername 192.168.0.108
Sun 12/25 11:57:18.189 Reading mvp.bin in mode octet
Sun 12/25 11:57:18.190 Opening file
Sun 12/25 11:57:19.744 TFTP timeout
Sun 12/25 11:57:29.535 At last block


The only thing different now is that the logs are reporting that TFTP is timing out.

Just jumping in here, but most of the problems I have seen are from the communication side of things... Are you going througha single switch/router? If not, try it out (single router...) and see if things get better.

-Jason

[ckron]

Just jumping in here, but most of the problems I have seen are from the communication side of things... Are you going througha single switch/router? If not, try it out (single router...) and see if things get better.

-Jason

I have tried this even though I fail to see how it could be the problem when Matt's plugin works flawlessly.

[SprDtyF350]

You know, I will probably get bashed for this but who cares. For something that has been touted as being a plug it in, turn on the MVP server in Sage and it will work this has from what I can tell been a big joke. I love Sage, and have used it for a long time. I just fail to see how something can be sold as "Plug and Play" in the simplest form and yet be such a pain for what seems to be so many people. I have not, and have no plans to switch from what I have been using considering the fact that I see no significant difference in functionality but a huge difference in the headache to get it to work department. I understand the desire for Sage to make a buck, but what would be wrong with putting something out there that actually does what it says it will?

Sorry for the rant, then again... actually no I'm not.

Randy

[MrApollinax]

Since the nerd in me couldn't let this one go I decided to do a little more investigation. I've done two ethereal captures of the MVP and my server communicating. One of the Haup software and the other the SageTV server. It seems that the two pieces of software handle the image upload slightly different.

When using the Haup software the MVP sends out a broadcast on port 16868. The capture shows a source/destination of 0.0.0.0/255.255.255.255. However drilling down into to the packet (EthernetII level) I see the packet source is actully coming from IP 192.168.0.2 with the MAC address of my MVP. This is strange since my router shows that it served that MAC an IP address of 192.168.0.149. Anyway my server ARPs for 192.168.0.2 and the MVP replies and a UDP exchange happens on ports 2803/3909 while the application is "Loading." At this point I see the MVP send out a DHCP Discover (BOOTP), my router responds with an Offer and my MVP sends out a Request which is ACKed by my router. Then i see an ARP request for 192.168.0.149 from my server get ACKed by the MVP and at this point the Haup interface is displayed on the screen of my monitor.

The Sage implementation differs where my MVP broadcasts the IP that my router served it instead of 192.168.0.2 in the intial broadcast packet onport 16868. The UDP exchange happens on the same ports as the Haup software but with the router served addresses of 192.168.0.149 (MVP) and 192.168.0.108 (SageTV Server). Now here i see the MVP send out a DHCP Discover as before, but with the "correct" IP of 192.168.0.149. My router sends out a DHCP Offer like before with the Haup software but this time the MVP never responds with a DHCP request. This will cycle continuously as my MVP displays "Starting Application" on my monitor.

This really doesn't get me any closer to fixing my problem but at least i know that there are some differences between the way the imbedded SageTV support handles things compared to the Haup implementaion.

[blade]

You know, I will probably get bashed for this but who cares. For something that has been touted as being a plug it in, turn on the MVP server in Sage and it will work this has from what I can tell been a big joke. I love Sage, and have used it for a long time. I just fail to see how something can be sold as "Plug and Play" in the simplest form and yet be such a pain for what seems to be so many people. I have not, and have no plans to switch from what I have been using considering the fact that I see no significant difference in functionality but a huge difference in the headache to get it to work department. I understand the desire for Sage to make a buck, but what would be wrong with putting something out there that actually does what it says it will?

Sorry for the rant, then again... actually no I'm not.

Randy

For many people it has been plug and play. There are literally millions of combinations of hardware configurations possible. Anytime something new is released it's to be expected that there are going to be some bugs to work out because it's impossible to have tested it with every possible combination.

There is indeed a functional difference between Matt's client and the integrated support. Most everyone that's used it agrees that they see a significant improvement.

I don't think it's simply about making a buck. Sage knows that in order to compete with MCE and other apps they have to provide a media extender. People on this forum have desired media extender support for quite some time. This is Sage's first step towards giving users what they've been wanting. The MVP is nice, but what's really encouraging is that once they get all the bugs worked out we can start looking foward to a HD extender.

I agree that ideally it would work perfectly on the first release, but I also understand that Sage isn't a huge corporation spending millions of dollars on R&D to add media extender support so I'm a little more forgiving than I would be of someone like Microsoft.

[ckron]

Since the nerd in me couldn't let this one go I decided to do a little more investigation. I've done two ethereal captures of the MVP and my server communicating. One of the Haup software and the other the SageTV server. It seems that the two pieces of software handle the image upload slightly different.

When using the Haup software the MVP sends out a broadcast on port 16868. The capture shows a source/destination of 0.0.0.0/255.255.255.255. However drilling down into to the packet (EthernetII level) I see the packet source is actully coming from IP 192.168.0.2 with the MAC address of my MVP. This is strange since my router shows that it served that MAC an IP address of 192.168.0.149. Anyway my server ARPs for 192.168.0.2 and the MVP replies and a UDP exchange happens on ports 2803/3909 while the application is "Loading." At this point I see the MVP send out a DHCP Discover (BOOTP), my router responds with an Offer and my MVP sends out a Request which is ACKed by my router. Then i see an ARP request for 192.168.0.149 from my server get ACKed by the MVP and at this point the Haup interface is displayed on the screen of my monitor.

The Sage implementation differs where my MVP broadcasts the IP that my router served it instead of 192.168.0.2 in the intial broadcast packet onport 16868. The UDP exchange happens on the same ports as the Haup software but with the router served addresses of 192.168.0.149 (MVP) and 192.168.0.108 (SageTV Server). Now here i see the MVP send out a DHCP Discover as before, but with the "correct" IP of 192.168.0.149. My router sends out a DHCP Offer like before with the Haup software but this time the MVP never responds with a DHCP request. This will cycle continuously as my MVP displays "Starting Application" on my monitor.

This really doesn't get me any closer to fixing my problem but at least i know that there are some differences between the way the imbedded SageTV support handles things compared to the Haup implementaion.


Thanks for your hard work! I for one am sticking with Matt's plugin for now. His latest version is quite an improvement over the older version I was using and it is FREE. I will probably spend my hard earned cash on getting commercial skipping up and running. I read that showanalyzer is doing very well and it is only $10.

:corn:

[flavius]

Matt's client was using a version of the VNC protocol, just as the hauppauge software does, whereas Sage has now implemented their proprietary protocol.

[MrApollinax]

I would say that the application interface with the Haup software is a VNC protocol yes, but I'm talking about the image upload to the MVP. The Haup software uploads using 192.168.0.2 (MVP) and 192.168.0.108 (my PC) on UDP ports 2803/3909 for the image upload. Once the image is on my MVP it then initiates communication with my PC via port 5906 which is probably VNC.

The Sage software uses the correct DHCP served address for the MVP, 192.168.0.149, to communicate with my PC. The image upload to the MVP is nearly identical using UDP ports 2809/3909. However where SageTV stops is where I describe it in my previous post:

Now here i see the MVP send out a DHCP Discover as before, but with the "correct" IP of 192.168.0.149. My router sends out a DHCP Offer like before with the Haup software but this time the MVP never responds with a DHCP request. This will cycle continuously as my MVP displays "Starting Application" on my monitor.

So i never get to the application interface with my PC using the imbedded Sage client. It never initiates at all, thus my monitor always displaying "Starting Application." I'm not trying to bad mouth Sage at all. I want this to work. I do not want to convert my media files to WMV/MP3 to view them via my Xbox360 nor do i wish to purchase another old Xbox and mod it to play streamed media. I want to use the MVP with SageTV because of the clean UI and front end. This is a much cheaper and scalable solution for me.

[MrApollinax]

And yes I have sent a message to SageTV support with the info found in this thread as well as a link to this thread for more information. Hopefully I have given enough information to start troubleshooting this problem I'm having. I'm posting this info here since I'm seem to be getting more response from the forum right now than from support due to the holidays. I understand that people deserve vacations so I've posted this here in hopes that someone else may know what is happening or have a possible solution. Thanks everyone for your responses and i hope you are having a good holiday season!

[SprDtyF350]

For many people it has been plug and play. There are literally millions of combinations of hardware configurations possible. Anytime something new is released it's to be expected that there are going to be some bugs to work out because it's impossible to have tested it with every possible combination.

There is indeed a functional difference between Matt's client and the integrated support. Most everyone that's used it agrees that they see a significant improvement.

I don't think it's simply about making a buck. Sage knows that in order to compete with MCE and other apps they have to provide a media extender. People on this forum have desired media extender support for quite some time. This is Sage's first step towards giving users what they've been wanting. The MVP is nice, but what's really encouraging is that once they get all the bugs worked out we can start looking foward to a HD extender.

I agree that ideally it would work perfectly on the first release, but I also understand that Sage isn't a huge corporation spending millions of dollars on R&D to add media extender support so I'm a little more forgiving than I would be of someone like Microsoft.

Yes, I agree that when I wrote this I was in a pretty non patient mood. I have never had a problem with Sage and so far they have always done right by me. I just think that next time something gets released maybe some thinking should go into the "just plug it in and it will magically work type advertising". Not everyone has a Grandma with a computer science degree. All they want to do is watch TV. There are many of us out here that would gladly beta test something like this for them as we have in the past. No reason to put something out with such a bold statement when it hasn't really been put through the torture test of a normal user.

See ya, and good luck....

Randy

[2FarGone]

I am not sure if you have gotten your "Starting Application..." freezing problem fixed yet, however I found a solution to mine:

http://forums.sagetv.com/forums/showthread.php?t=14771


I hope this helps your problem too!!!
:goodjob:

[MrApollinax]

I'm really glad you were able to get your situation resolved. I'm working with Support and they've forwarded my issue up the food chain. I'm hoping that they will be able to fix this issuse. I'm very reluctant to go out and buy a new router especially since the 4300 is a bit pricey when it comes to SOHO routers. Do you know how to take an ethernet capture of your network? I'm curious to see how your MVP behaves differently with the MIMO router vs the DGL. I do a lot of gaming and the DGL has met everyone of my expectations on that point. So far SageTV is the only thing that hasn't worked with this router. I'm hoping Sage will have this figured out soon.

[LostInSpace]

Java seems to be one of the problems. My MVP did not start (I had SageTV boot screen for a few second then... black screen)
Until I switched to Java v1.4.2_06.
It's working fine now.

Regards

Ferdinand

[MrApollinax]

I forgot to mention that I downgraded my JRE to 1.4 already. It didn't solve my particular issue.

[2FarGone]

I'm really glad you were able to get your situation resolved. I'm working with Support and they've forwarded my issue up the food chain. I'm hoping that they will be able to fix this issuse. I'm very reluctant to go out and buy a new router especially since the 4300 is a bit pricey when it comes to SOHO routers. Do you know how to take an ethernet capture of your network? I'm curious to see how your MVP behaves differently with the MIMO router vs the DGL. I do a lot of gaming and the DGL has met everyone of my expectations on that point. So far SageTV is the only thing that hasn't worked with this router. I'm hoping Sage will have this figured out soon.



I haven't ever taken an ethernet capture, however I would be happy to try. Just let me know what programs to install. I am hoping that I can install the programs on an extra laptop that I have, because I am not crazy about installing any software on the SageTV server.

If I can monitor the network with another machine, will I be able to do it by plugging directly into the router/switch? Or will I need to come off the router/switch with a hub and then connect everything into the hub?

Also, I know what you mean about the DGL-4300, that is one of the best routers I have ever had. I do not believe I have ever had to reboot one or anything!! Hopefully they will get this problem solved so I can start using mine again.

Other Notes: I have tried a very cheap AirLink router and the MediaMVP's work fine with it too. So I am starting to think that it might be just that one particular router, chipset or something.

[TripleTapper]

If this is a router specific problem, I would think it would be pretty easy for tech support to nail and get a fix for it. I really hope this will be resolved quickly....the wife baught me the MVP for my b-day and is not too happy about it just sitting next to the tv like a brick, :(

[MrApollinax]

I'm working with support on this still and hopefully this will be straightened out. As soon as I know something useful for you guys I'll update here.

[MrApollinax]

I've worked with Sage support and I am testing an alpha load that has a work around for this issue. My system now works as advertised and I couldn't be happier with the setup. Once SageTV supports DivX natively my setup will be perfect! Thanks _Demo_ for all the help!

[LSHorwitz]

This problem we are all experiencing is not specific to a particular router.

I have exactly the same problem using a Linksys router, and it works perfectly fine with the standard MVP firmware and Matt's client.

IMHO the Sage mvp.bin is the application with a bug, and fooling with routers, NICs, etc. will apparently only solve this problem for some users but not others (unfortunately myself included).

I have also send a request to support for their assistance,

Larry

[MrApollinax]

One of the cardinal rules for support is that the more info you have the better off you will be when it comes to any type of problem. So in this post I'm going to explain how to use Ethereal (http://ethereal.com/) to troubleshoot the communications between your SageTV server and the Hauppage MediaMVP. I used this to troubleshoot the problem described in this thread and provided the info in order to help SageTV narrow down the possible causes for my problem. I'm very familiar with the program and am very comfortable using it. If you feel that this is something you do not wish to pursue then disregard the rest of this post. Otherwise continue below:

I. Install Programs
1. Install ethereal on your system (or on a PC on the same network segment as your MVP and SageTV server)
a. Installation procedures for all supported OSes can be found at the Ethereal (http://ethereal.com/) website

2. install Winpcap (http://www.winpcap.org/). This will allow you to capture the ethernet information and save it to files on your HDD

II. Prepare your setup for captures
1. Enable debug logging for SageTV
a. Add the following line to the sage.properties file. This is a case sensitive command input it as shown here:
debug_logging=TRUE
2. Power down your Media MVP
3. Ensure Media Extender and Server services are running for SageTV

III. Capturing Packets
1. Run Ethereal
a. In the top left corner there is a button just below the "File" menu. This will display all interfaces available for capture
b. From that menu locate the LAN interface that your SageTV server and MVP communicate on.
c. Click on the "Capture" button. A window will appear with a list of "Captured Packets showing that Ethereal is capturing packets.
a. I strongly recommend that you stop all other programs using IP communications ie Internet Apps etc.
2. Power MediaMVP back on
3. Watch as the screens load in squence
4. Where the sequence stops wait 30 seconds to a minute
5. In Ethereal click on "Stop"
6. Captured packets are displayed in the main Ethreal window.
7. Goto File >> Save As and save the capture.

IV. Gather your info
1. Locate the sage_log file under your %\sagetv\ directory
2. Locate your ethernet capture
3. Send the info via email to support if asked.
a. *Warning* Ethereal captures can become quite large

Now to most people the information provided by Ethereal is pretty useless. But for those who can read the capture it can provide a lot of valuable information about TCP/IP communication between your MediaMVP and SageTV. If you wish to learn more about the information in the captures I recommend finding a good TCP/IP book and reading about the numerous protocols and applications that work within the TCP/IP stack.

[BBCritical]

Now that we have fixed Horowitz's problem are we any closer to fixing the original DGL issue?

[MrApollinax]

Now that we have fixed Horowitz's problem are we any closer to fixing the original DGL issue?

I've worked with Sage support and I am testing an alpha load that has a work around for this issue. My system now works as advertised and I couldn't be happier with the setup. Once SageTV supports DivX natively my setup will be perfect! Thanks _Demo_ for all the help!

The fix will be included in the next beta build.

[flavius]

The fix will be included in the next beta build.

Is that one imminent? I know that's in general quite fruitless to ask - but I'll get my MVP this coming Friday. Would be nice, if I could install it over the weekend
Of course, I can always try to get the alpha..

[MrApollinax]

Ask and ye shall recieve!

http://forums.sagetv.com/forums/showthread.php?t=15161

[flavius]

Excellent!