Having problems with HD300's connecting

[CptKirk]

Every now and then my USB Hauppauge HVR-1950 tuner stops changing channels and I have to reboot the computer.

But recently after doing the reboot my HD300's (I have two of them) do not connect to the server. They get stuck on the 'SageTV HD Theater is starting up'. I have to keep power cycling them over and over. Eventually, they have been able to connect.

I've been doing that for awhile now this morning and still have not had any luck in getting them connected yet.

I looked at the sagetv_0.txt log file see the following (both HD300's are sitting at the 'SageTV HD Theater is starting up' screen):

Thu 4/30 11:00:08.843 [SageTVDiscoveryServer@10be6dc] Error creating discovery socket:java.net.BindException: Address already in use: Cannot bind
Thu 4/30 11:00:20.152 [MiniUIServer@af01a6] Dropping old MiniPlayer connection because it's old from:0023a50010d8
Thu 4/30 11:00:20.154 [MiniUIServer@af01a6] MiniUI got connection from java.nio.channels.SocketChannel[connected local=/192.168.99.51:31099 remote=/192.168.99.118:33718]
Thu 4/30 11:00:20.154 [MiniUIServerConnection@1b19892] MiniPlayer is adding to its map:0023a50010d8
Thu 4/30 11:00:23.854 [SageTVDiscoveryServer@10be6dc] Error creating discovery socket:java.net.BindException: Address already in use: Cannot bind
Thu 4/30 11:00:30.155 [MiniUIServer@af01a6] Dropping old MiniPlayer connection because it's old from:0023a50011ba
Thu 4/30 11:00:30.156 [MiniUIServer@af01a6] MiniUI got connection from java.nio.channels.SocketChannel[connected local=/192.168.99.51:31099 remote=/192.168.99.110:59935]
Thu 4/30 11:00:30.156 [MiniUIServerConnection@1b19892] MiniPlayer is adding to its map:0023a50011ba
Thu 4/30 11:00:38.854 [SageTVDiscoveryServer@10be6dc] Error creating discovery socket:java.net.BindException: Address already in use: Cannot bind
Thu 4/30 11:00:50.179 [MiniUIServer@af01a6] Dropping old MiniPlayer connection because it's old from:0023a50010d8
Thu 4/30 11:00:50.181 [MiniUIServer@af01a6] MiniUI got connection from java.nio.channels.SocketChannel[connected local=/192.168.99.51:31099 remote=/192.168.99.118:33719]
Thu 4/30 11:00:50.181 [MiniUIServerConnection@1b19892] MiniPlayer is adding to its map:0023a50010d8
Thu 4/30 11:00:53.861 [SageTVDiscoveryServer@10be6dc] Error creating discovery socket:java.net.BindException: Address already in use: Cannot bind
Thu 4/30 11:01:00.194 [MiniUIServer@af01a6] Dropping old MiniPlayer connection because it's old from:0023a50011ba
Thu 4/30 11:01:00.196 [MiniUIServer@af01a6] MiniUI got connection from java.nio.channels.SocketChannel[connected local=/192.168.99.51:31099 remote=/192.168.99.110:59936]
Thu 4/30 11:01:00.196 [MiniUIServerConnection@1b19892] MiniPlayer is adding to its map:0023a50011ba
Thu 4/30 11:01:08.868 [SageTVDiscoveryServer@10be6dc] Error creating discovery socket:java.net.BindException: Address already in use: Cannot bind
Thu 4/30 11:01:20.224 [MiniUIServer@af01a6] Dropping old MiniPlayer connection because it's old from:0023a50010d8
Thu 4/30 11:01:20.225 [MiniUIServer@af01a6] MiniUI got connection from java.nio.channels.SocketChannel[connected local=/192.168.99.51:31099 remote=/192.168.99.118:33726]
Thu 4/30 11:01:20.226 [MiniUIServerConnection@1b19892] MiniPlayer is adding to its map:0023a50010d8
Thu 4/30 11:01:23.874 [SageTVDiscoveryServer@10be6dc] Error creating discovery socket:java.net.BindException: Address already in use: Cannot bind
Thu 4/30 11:01:30.239 [MiniUIServer@af01a6] Dropping old MiniPlayer connection because it's old from:0023a50011ba
Thu 4/30 11:01:30.240 [MiniUIServer@af01a6] MiniUI got connection from java.nio.channels.SocketChannel[connected local=/192.168.99.51:31099 remote=/192.168.99.110:59937]
Thu 4/30 11:01:30.241 [MiniUIServerConnection@1b19892] MiniPlayer is adding to its map:0023a50011ba
Thu 4/30 11:01:38.881 [SageTVDiscoveryServer@10be6dc] Error creating discovery socket:java.net.BindException: Address already in use: Cannot bind
Thu 4/30 11:01:49.317 [Ministry@114451b] Ministry is waiting for 180 sec

And that just keeps repeating after the 3 minute wait.

Is there something on the server that I need to clear/fix so that this does not happen?

Both HD300's are using firmware 20110506-0

Thanks

[CptKirk]

Rebooted the computer again, power cycled the HD300's again and was finally able to get them to connect.

Looking at the sagetv_0.txt log file I see the following when it connects:

Thu 4/30 11:33:39.782 [SageTVMiniDiscoveryServer@7301fe] Server got broadcast packet: java.net.DatagramPacket@1d5c645
Thu 4/30 11:33:39.825 [SageTVMiniDiscoveryServer@7301fe] Server sent back mini discovery data:java.net.DatagramPacket@1d5c645 to /192.168.99.110 8271
Thu 4/30 11:33:42.110 [SageTVDiscoveryServer@13e3f] Error creating discovery socket:java.net.BindException: Address already in use: Cannot bind
Thu 4/30 11:33:57.110 [SageTVDiscoveryServer@13e3f] Error creating discovery socket:java.net.BindException: Address already in use: Cannot bind
Thu 4/30 11:33:58.080 [MiniMVP@2ce189] Received mvp packet
Thu 4/30 11:33:58.125 [MiniMVP@2ce189] Sending mvp reply
Thu 4/30 11:34:01.034 [MiniUIServer@c65d2a] MiniUI got connection from java.nio.channels.SocketChannel[connected local=/192.168.99.51:31099 remote=/192.168.99.110:48860]
Thu 4/30 11:34:01.035 [MiniUIServerConnection@2df71] MiniPlayer is adding to its map:0023a50011ba
Thu 4/30 11:34:01.045 [MiniUIServer@c65d2a] MiniUI got connection from java.nio.channels.SocketChannel[connected local=/192.168.99.51:31099 remote=/192.168.99.110:48861]
Thu 4/30 11:34:01.045 [MiniUIServerConnection@2df71] MiniUI is adding to its map:0023a50011ba
Thu 4/30 11:34:01.045 [MiniUIServerConnection@2df71] Creating new UI for client:0023a50011ba
Thu 4/30 11:34:01.048 [MiniUIServerConnection@2df71] Creating-2 new UI for client:0023a50011ba UIManager:localhost@@0023a50011ba-da03da

Any suggestions on what to change/fix so that I can shortcut this from happening in the future when having to do computer reboots?

[CptKirk]

Happening again...

Anyone?

Please?

[KryptoNyte]

Is everything hard wired to the Sage Server? I have found nearly every time that an HD300 has had trouble connecting that it was a network issue. Last time I had an issue, I had an HD300 connected to a wireless extender and the extender was dying.

[KryptoNyte]

In the event that the issue is with the HD300 customized config, you could also try moving all the properties files out of the SageTV\SageTV\clients directory so that the file is recreated from scratch the next time the HD300 connects. You would of course unplug the HD300's, then stop the SageTV software/service.

[Striker:WG]

if its hardwired, try rebooting your network switch and/or router.

[CptKirk]

It's hardwired.

I looked at the logs I had captured again especially at "Address already in use: Cannot bind"

So I
1. Powered off the HD300
2. Powered off my SageTV computer
3. Powered on my SageTV computer
4. Powered on the HD300

Thinking that I could clear whatever address has been locked in place. Seemed to work since after I powered up the HD300 it immediately connected.

[sungod]

Once something like this happened to me and I did the following.

1. power off the sage device
2. let it rest a few minutes
3. disconnect the ethernet cord
4. power up sage - it will not connect
5. power off the device
6. let it rest a few minutes
7. connect the ethernet cord
8. device worked normally after that.

If this does not work then its a problem beyond my abilities to correct.

[fidget]

Have you tried using Wireshark to look at what is going out n the network? I found a subnet size mismatch oh my HDHomeRuns that way.

[wayner]

A few people here, including me, have instances where the extender hangs when starting up. One thing that seems to work is similar to waht sungod said. Power off the extender and remove the ethernet cable. Restore power to the extender and let it boot up. Then plug in the ethernet and manually select the SageTV server.

[sic0048]

Thanks everyone for post this and solutions.

I have never really had this problem before, but recently our power was out for a while and when it came back on all but one of my extenders would connect. I eventually got this one HD300 extender to connect after messing with it for way too long. I had to restart my Sage service on Saturday and this same HD300 gave me a lot of trouble reconnecting.

Long story short, I am going to try some of the solutions listed when this happens again. I have removed power from the extender for a long period of time, but I have never thought about disconnecting the ethernet cord. I bet this will clear it up.

[fidget]

One other thing: patch cables can go bad. If the only device having problems is the extender, try replacing its Ethernet cable. If that fixes the problem, destroy the bad cable, so you don’t accidentally reuse it.

[eopian]

I have found the network capability of the HD300's to be very weak. If I even touch my HD300, it can disconnect. Everything else about the HD300 makes it the best way to watch Sage for me. We have finally come to an understanding, but when the power goes out it can take two or three power cycles for it to connect. Once it connects it's good until the power goes out again (or I touch it in any way).

Also, order of rebooting matters. I shut everything down. I bring up the router, switch, cable modem, hdhr prime, sage server, then hd300 in that order.

Finally, using a quality netgear gs116 switch has made a big difference for me in the quality of my network.

The hd100's I have flat out work all the time in any condition (but they don't pass through video format or transmit dts or hd audio).

[wayner]

The touching effect sounds like a grounding issue. But I think I have seen this myself. I wonder if there is a way to fix this by attaching attaching the case to a ground on the circuit board?

[wayner]

And look what I posted three years ago: https://forums.sagetv.com/forums/sho...d.php?p=613026

[jpwegas]

Originally Posted by wayner

And look what I posted three years ago: https://forums.sagetv.com/forums/sho...d.php?p=613026

I wonder if this is different between HD300s, maybe a different production run?

Because our "main" HD300 has been running basically 24/7 for years and regularly gets touched, including by young kids, and I have never experienced this.

--John

[eopian]

Originally Posted by fidget

Have you tried using Wireshark to look at what is going out n the network? I found a subnet size mismatch oh my HDHomeRuns that way.

I'm fairly competent, but I have no idea what any of this means. I'm having an HDHR issue right now. Is Wireshark software? Does it give findings that one can act on to fix, or is it like staring into the matrix code?

[wayner]

Originally Posted by eopian

I'm fairly competent, but I have no idea what any of this means. I'm having an HDHR issue right now. Is Wireshark software? Does it give findings that one can act on to fix, or is it like staring into the matrix code?

Wireshark is network monitoring software. But I don't think it is easy to troubleshoot issues like this unless you are a network expert.

I have tried using Wireshark in the past to do stuff like reverse engineer smarthome device apps but it isn't easy to figure out what is going on.

[tvmaster2]

Originally Posted by eopian

I have found the network capability of the HD300's to be very weak. If I even touch my HD300, it can disconnect. Everything else about the HD300 makes it the best way to watch Sage for me. We have finally come to an understanding, but when the power goes out it can take two or three power cycles for it to connect. Once it connects it's good until the power goes out again (or I touch it in any way).

Also, order of rebooting matters. I shut everything down. I bring up the router, switch, cable modem, hdhr prime, sage server, then hd300 in that order.

Finally, using a quality netgear gs116 switch has made a big difference for me in the quality of my network.

The hd100's I have flat out work all the time in any condition (but they don't pass through video format or transmit dts or hd audio).

You’re not alone. ALL my HD300’s have been network un-friendly since Narflex made changes to the system in July I think it was. I’m not sure what he did had anything to do with it, but that’s when it all went to hell for me. HD200’s are rock-solid. There is no logical fix I’ve found, after firmware changes, switch changes, router changes. Something was changed, and HD300’s don’t like it.

[wayner]

Was something changed in the HD300 firmware? Many of these problems described are even before the system connects to your server so this would have to be a hardware issue or a firmware issue that precedes the HD300's connection to the server.