MVP Never Progresses past "Starting Application" - Page 2

MrApollinax · #21 12-24-2005, 10:44 AM

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 · #22 12-24-2005, 11:44 AM

Quote:

Originally Posted by 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!

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 · #23 12-24-2005, 11:50 AM

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

MrApollinax · #24 12-24-2005, 01:56 PM

Quote:

Originally Posted by ckron

SageTV Media Extender now logs Java errors:

I never got these errors before updating Java!

I also get java errors in my logs.

MrApollinax · #25 12-25-2005, 12:11 PM

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 · #26 12-25-2005, 12:22 PM

Quote:

Originally Posted by 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.

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 · #27 12-25-2005, 02:32 PM

Quote:

Originally Posted by Jason

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 · #28 12-25-2005, 10:18 PM

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 · #29 12-25-2005, 10:30 PM

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 · #30 12-26-2005, 05:48 AM

Quote:

Originally Posted by 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

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 · #31 12-26-2005, 08:06 AM

Quote:

Originally Posted by 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.

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.

flavius · #32 12-26-2005, 08:10 AM

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 · #33 12-26-2005, 10:10 AM

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:

Quote:

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 · #34 12-26-2005, 10:14 AM

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 · #35 12-26-2005, 12:36 PM

Quote:

Originally Posted by blade

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 · #36 12-28-2005, 10:28 PM

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!!!

MrApollinax · #37 12-29-2005, 08:22 AM

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 · #38 12-29-2005, 03:59 PM

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 · #39 12-29-2005, 04:13 PM

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

2FarGone · #40 12-29-2005, 05:34 PM

Quote:

Originally Posted by 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.

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.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)