![]() |
|
SageTV Media Extender Discussion related to any SageTV Media Extender used directly by SageTV. Questions, issues, problems, suggestions, etc. relating to a SageTV supported media extender should be posted here. Use the SageTV HD Theater - Media Player forum for issues related to using an HD Theater while not connected to a SageTV server. |
![]() |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
|||
|
|||
Problem with sage7 and hd300/hd100
I am having problems with sage7 on windows xp where over the internet when watched on an hd300 or placeshifter the devices turn off after 10 minutes. On the local network the hd300 works fine. I have sent my log file that I made of just the hd300 playing a recorded show and turning off after 10 minutes and sagetv told me that there was no disconnect in the file and that i should send another one. Is there someone who can look at the file and tell me if there are any problems. I see that there are errors or the word error in the file but I do not know what it means. I am looking for any changes that I need to make on the server to make this work. My internet connection is .94 up and 11 down.
I have tried to upload the sage file in a zip file. Last edited by ripplingj; 01-07-2011 at 07:56 PM. |
#2
|
|||
|
|||
Have you tried zipping the log up and uploading the zip file?
|
#3
|
|||
|
|||
Thank you I have uploaded in a zip file.
|
#4
|
|||
|
|||
It looks like here is where the connection to the server is lost:
Code:
Sat 1/1 14:04:47.193 [FinalRender-0023a5000723@574ac1] ERROR: MiniUIClient receiver timed out waiting for response from the MiniClient! Sat 1/1 14:04:47.194 [KillUIMgr@1041911] Killing UIMgr UIManager:localhost@@0023a5000723-7a7501 Sat 1/1 14:04:47.194 [FinalRender-0023a5000723@574ac1] MiniUI client error23:java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0 Sat 1/1 14:04:47.195 [FinalRender-0023a5000723@574ac1] java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0 Sat 1/1 14:04:47.195 [FinalRender-0023a5000723@574ac1] java.util.Vector.remove(Unknown Source) Sat 1/1 14:04:47.195 [FinalRender-0023a5000723@574ac1] sage.bp$d.do(Unknown Source) Sat 1/1 14:04:47.195 [FinalRender-0023a5000723@574ac1] sage.bp$d.new(Unknown Source) Sat 1/1 14:04:47.195 [FinalRender-0023a5000723@574ac1] sage.bp.W(Unknown Source) Sat 1/1 14:04:47.196 [FinalRender-0023a5000723@574ac1] sage.bp.a(Unknown Source) Sat 1/1 14:04:47.196 [FinalRender-0023a5000723@574ac1] sage.bs.a(Unknown Source) Sat 1/1 14:04:47.196 [FinalRender-0023a5000723@574ac1] sage.bs.new(Unknown Source) Sat 1/1 14:04:47.196 [FinalRender-0023a5000723@574ac1] sage.bs$1.run(Unknown Source) Sat 1/1 14:04:47.196 [KillUIMgr@1041911] Killed UI Timers Sat 1/1 14:04:47.217 [Pusher@12b3afd] Client Buffer size=2067712 estimRateKbps=1361 avgRateKbps=1256 rateKbps=1189 estimStreamRateKbps=1802 avgStreamRateKbps=357 Sat 1/1 14:04:47.218 [Pusher@12b3afd] Adjusted bitrate UP to : 1208 Sat 1/1 14:04:47.252 [Fork-BASE-55376@cc344d] Stopping Disk Space Bar thread since the UI context "0023a5000723" no longer exists. AllUIContexts = [] Sat 1/1 14:04:47.253 [Fork-BASE-55376@cc344d] Shutting down Disk Space Bar Updater Thread: Thread[Fork-BASE-55376,1,main], for UI context 0023a5000723 Sat 1/1 14:04:47.806 [KillUIMgr@1041911] Updated:Watched[id=472178 Airing=A[95978,95902,"Criminal Minds",11261@1117.21:00,60], WatchStart=Wed 11/17 21:00:00.004, WatchEnd=Wed 11/17 21:16:37.155, RealStart=Sat 1/1 13:46:30.540, RealEnd=Sat 1/1 14:04:47.641] Sat 1/1 14:04:47.807 [KillUIMgr@1041911] VF logFileWatch doneAir=A[95978,95902,"Criminal Minds",11261@1117.21:00,60] theTime=Wed 11/17 21:16:37.155 recTime=Wed 11/17 21:00:00.004 Sat 1/1 14:04:49.500 [Pusher@12b3afd] Client Buffer size=2069760 estimRateKbps=1322 avgRateKbps=1278 rateKbps=1208 estimStreamRateKbps=983 avgStreamRateKbps=437 Sat 1/1 14:04:49.500 [Pusher@12b3afd] Adjusted bitrate UP to : 1230 Sat 1/1 14:04:49.892 [KillUIMgr@1041911] stopPush0() Sat 1/1 14:04:50.047 [KillUIMgr@1041911] Closing down MiniPlayer Sat 1/1 14:04:50.047 [KillUIMgr@1041911] closeDriver0() Sat 1/1 14:04:50.238 [KillUIMgr@1041911] Seeker.finishWatch(UIManager:localhost@@0023a5000723-7a7501) Sat 1/1 14:04:50.238 [KillUIMgr@1041911] Killed VideoFrame Sat 1/1 14:04:50.238 [KillUIMgr@1041911] Killed EventRouter From the log, it looks like maybe the server timed out waiting for communication from your extender. If that is the case, then it's probably not a problem with your Internet connection at your home, it's more likely to be a poor Internet connection at your extender side of the setup. This is more likely at large busy hotels and other WiFi hotspots where wireless interference and network latency can be extremely high or wireless signals at your extender are too weak and can cause the extender connection to your SageTV server to drop because the communication between the client and server is taking too long.
__________________
--Jason Server Hardware: GIGABYTE GA-EP45-UD3R, Intel Q9550 CPU 2.83GHz, 11GB RAM, 1xHDHR, 1xHVR1600, 1xHVR2250 29TB Server Storage: 1TB SSD (OS), 1TB (data), 2x6TB+2x10TB (22TB FlexRaid storage pool), 2x2TB (recordings), 1x750GB (VMs). Server Software: Win10 Pro x64 OS, SageTV 64bit v9.2.0.441, Java 1.8 u241, PlayOn, Comskip (Donator) v0.82.003, WampServer v2.5. Clients: 3xHD300s, 2xHD100, 2xPlaceshifters |
#5
|
||||
|
||||
One thing that gets overlooked a lot is to make sure that the Power Management settings for the network adapter on your Sage server has "Allow the computer to turn off this device to save power" UNCHECKED. (Under device manager in Windows)
Usually when the Internet connection drops out (even for a moment) you will get errors like this: java.io.IOException: An existing connection was forcibly closed by the remote host
__________________
blog: www.iamwhen.com |
#6
|
|||
|
|||
When you file is to big then try dropbox "public link"
http://www.groovypost.com/howto/free...-public-links/ |
#7
|
|||
|
|||
Quote:
This is at another home DSL connection for Fairpoint communications. The internet speed there is 3.0 Mbps down 512k up. The sage extender hd300 is connection wired to the router at this location. |
#8
|
|||
|
|||
Quote:
|
#9
|
|||
|
|||
The sagetv server is connected to a netgear router attached to timewarner cable internet this is a wired conneciton.
|
#10
|
|||
|
|||
Other than a possible flaky DSL connection, I would think that setup would be about as stable as you can get. It might be worthwhile to run some extended ping tests and ping your server from the remote location to see if there are any high latency returns or lost packets. If ping tests are normal, I would continue to press SageTV Support to investigate further since it could be a firmware bug on the extender when in Placeshifter mode. I would point out that section of the log I quoted and see if they can tell you what might cause that particular timeout error...that might help determine which side of the network connection to focus on if it is a network problem and not a SageTV software or firmware problem. That error seems to indicate the connection isn't being dropped due to network failures, but the server is killing the UI context that belongs to the extender due to some kind of communication timeout with the extender. If it happens remotely (WAN), but not locally (LAN), it might possibly be caused by dropped/corrupt network packets or high network/Internet latency where the SageTV server isn't getting the data it is expecting within the timeframe it is expecting it in.
__________________
--Jason Server Hardware: GIGABYTE GA-EP45-UD3R, Intel Q9550 CPU 2.83GHz, 11GB RAM, 1xHDHR, 1xHVR1600, 1xHVR2250 29TB Server Storage: 1TB SSD (OS), 1TB (data), 2x6TB+2x10TB (22TB FlexRaid storage pool), 2x2TB (recordings), 1x750GB (VMs). Server Software: Win10 Pro x64 OS, SageTV 64bit v9.2.0.441, Java 1.8 u241, PlayOn, Comskip (Donator) v0.82.003, WampServer v2.5. Clients: 3xHD300s, 2xHD100, 2xPlaceshifters |
#11
|
|||
|
|||
This helps out a lot in trouble shooting i have contacted the dsl provider at the remote location and have initiated a trouble shooting initiative from their end to see if they can fix the poor latency on the remote connection.
|
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Audio sync problem with HD300 | rdefino | SageTV Media Extender | 2 | 01-03-2011 02:36 PM |
HD300 Flac problem rears its ugly head again | gdippel | SageTV Beta Test Software | 2 | 01-01-2011 11:15 AM |
hd300 problem | ripplingj | SageTV Media Extender | 0 | 12-06-2010 08:13 PM |
HD300 vs. HD100 | Skybolt | SageTV HD Theater - Media Player | 9 | 10-19-2010 07:03 PM |
HD100 died. Any HD300 rumors? | GollyJer | SageTV HD Theater - Media Player | 13 | 04-19-2010 12:54 PM |