HD 300 slugish

[stuckless]

Originally Posted by graywolf

How does this look?
What is the difference between errors and dropped?
I assume the stats reset after a hard power (unplugged) recycle instead of just turning the unit off (via remote)?

tango3[~]# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:23:A5:00:01:2E
          inet addr:xxx.xxx.xxx.xxx  Bcast:xxx.xxx.xxx.xxx  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:175900285 errors:127 dropped:0 overruns:0 frame:127
          TX packets:101797152 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:256
          RX bytes:2928254339 (2.7 GiB)  TX bytes:1908118250 (1.7 GiB)
          Interrupt:46

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:124349 errors:0 dropped:0 overruns:0 frame:0
          TX packets:124349 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:90557834 (86.3 MiB)  TX bytes:90557834 (86.3 MiB)

tango3[~]# uptime
 05:20:19 up 11 days, 13:20, load average: 0.00, 0.00, 0.00

There's some errors and it's odd to see any, but, not enough that I would think would cause any amount of slowdown. My server has been up for 34 days... 0 errors.

        RX packets 459949500  bytes 410791176045 (382.5 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 397350022  bytes 257723559652 (240.0 GiB)

[Doubledose]

I am not familiar with the ifconfig command. I tried to use the run command with it and also dos command and it says cannot find ifconfig. How do I make this work?
Thanks
Wayne

[graywolf]

sftp to your HDx00 (I use putty)

Then you will be prompted for login, answer with: root
then at the cmd prompt type: ifconfig -a
then to quit the sftp session, type: exit

Example:

tango3 login: root
tango3[~]# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:23:A5:00:01:2E
          inet addr:192.168.254.145  Bcast:192.168.254.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:191333722 errors:135 dropped:0 overruns:0 frame:135
          TX packets:110442404 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:256
          RX bytes:3430347435 (3.1 GiB)  TX bytes:2431347967 (2.2 GiB)
          Interrupt:46

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:148707 errors:0 dropped:0 overruns:0 frame:0
          TX packets:148707 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:108381658 (103.3 MiB)  TX bytes:108381658 (103.3 MiB)

tango3[~]# exit

[graywolf]

Also:

ifconfig is for Unix systems
ipconfig is for Windows systems

[Doubledose]

I was able to get connected, here is what my hd 300 looks like.
Thanks for the logon help
Wayne

tango3 login: root
tango3[~]# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:23:A5:00:05:1E
          inet addr:172.20.20.192  Bcast:172.20.20.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:18260305 errors:149 dropped:0 overruns:0 frame:149
          TX packets:10559899 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:256
          RX bytes:2243280906 (2.0 GiB)  TX bytes:651787152 (621.5 MiB)
          Interrupt:46

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:5933289 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5933289 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:432801861 (412.7 MiB)  TX bytes:432801861 (412.7 MiB)

tango3[~]#
tango3[~]#

[Doubledose]

Stuckless
I used the WD software to check the drive. The long and short showed no problems. I will see if I can get placeshifter going.
Thanks
Wayne

[Doubledose]

Forgot to paste java info
Thanks
Wayne

[KeithAbbott]

Originally Posted by Doubledose

I was able to get connected, here is what my hd 300 looks like.
Thanks for the logon help
Wayne

tango3 login: root
tango3[~]# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:23:A5:00:05:1E
          inet addr:172.20.20.192  Bcast:172.20.20.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:18260305 errors:149 dropped:0 overruns:0 frame:149
          TX packets:10559899 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:256
          RX bytes:2243280906 (2.0 GiB)  TX bytes:651787152 (621.5 MiB)
          Interrupt:46

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:5933289 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5933289 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:432801861 (412.7 MiB)  TX bytes:432801861 (412.7 MiB)

tango3[~]#
tango3[~]#

Seems like a high amount of traffic on the Local Loopback, compared to the traffic on my own HD300s and the other examples in this thread. No idea whether this could be contributing to your issue or not.

[Doubledose]

Just got placeshifter working on another computer. If I hold mouse button on the down arrow key it scrolls a lot faster then the hd 300 but has some stopping for a second every so often. But I see a lot of spinning circles when scrolling down. It almost looks like they correspond to the channel icons being loaded. If I hold down the up button it does scroll up pretty decent but once in a while stalls for a second. I have never used placeshifter, so I have no idea what to compare it to. But it definitely is faster than the hd-300.
Thanks
Wayne

[KeithAbbott]

Is the new server any more responsive if you completely power-down the old server? I'm wondering if the two servers aren't playing nicely together.

[KryptoNyte]

Expanding on what Keith mentioned - do you have either or both of the machines set up with a static IP, and are they (2) different static IP's?

Do you have an extra network interface card around you could throw in that machine temporarily for testing, and disable the on-board network adapter?

[Doubledose]

Originally Posted by KeithAbbott

Is the new server any more responsive if you completely power-down the old server? I'm wondering if the two servers aren't playing nicely together.

I shut the old one down and rebooted the new one and the hd-300. It made no difference.

Originally Posted by KryptoNyte

Expanding on what Keith mentioned - do you have either or both of the machines set up with a static IP, and are they (2) different static IP's?

Do you have an extra network interface card around you could throw in that machine temporarily for testing, and disable the on-board network adapter?

My old machine had a static ip and the new machine was still dhcp, so I assigned a static ip to new machine and rebooted both. That still does not seem to have made any difference.
I do not have an extra nic card.
Thanks
Wayne

[Doubledose]

I also just put my driver disk in and updated the network driver. it told me there was a newer version and installed it. That did not make any difference either.
Wayne

[stuckless]

So I think if I understand the tests so far...

| hd300 | placeshifter | new server | old server | PASS | FAIL |
|-------|--------------|------------|------------|------|------|
|   x   |              |     x      |            |      |  x   |
|-------|--------------|------------|------------|------|------|
|   x   |              |            |     x      |  x   |      |
|-------|--------------|------------|------------|------|------|
|       |      x       |     x      |            |      |  x?  |
|-------|--------------|------------|------------|------|------|
|       |      x       |            |     x      |  ?   |      |
|-------|--------------|------------|------------|------|------|

Same HD300 used in both tests, using the same cable
Same Placeshifter used in both tests, using the same cable

I would sort of consider the placeshifter a failure just because you are seeing spinning circles, and I would not expect to see that. Could you test the placeshifter connecting to the old server and see if youget the same results?

If the above chart is accurate, then I think you are looking at either a
* NIC issue on the server, cable issue on the server, or switch port for the server
* Java issue (ie, excessive garbage collection
* HD issue on the server

Based on what you are saying with the placeshifter, I'd be looking for at Java or HD. ie, spinning while trying to load images could be java having to free and allocate memory. It could also be a slow drive access (ie, the drive spun down, or some windows process like a virus scanner is intercepting the file request and doing some work before allowing it to be accessed). Unfortunately I'm not a windows person, so I don't know how to troubleshoot those 2 things.

The server NIC is the easiest to test... ie, new card, then new cable, then port on the switch.

The Frame errors on the HD300 is interesting. I checked every linux device on my network and I have 0 errors and 0 frame errors. I don't have a HD300 (or sagetv server) hooked up at the moment. Frame errors can indicate a bad, nic, cable, or port, and not necessarily on the HD300 itself. Just means that somewhere from went he packet was created and the HD300 got it, there was an error. It could have originated on the server.

You can try this....
unplug HD300, plug it in, telnet to it, and run the ifconfig command and check for error.
connect to your OLD sagetv server, do some operations, and then check the ifconfig command again, see if you have errors.

Repeat those steps (ie, unplug, plug in, etc) while connecting to the NEW server.

If you are seeing frame errors in BOTH tests then we can ignore those. if you are seeing frame errors in just the new server, I think it points to a server nic/cable/port issue.

[KeithAbbott]

Originally Posted by Doubledose

I have not transferred anything from old machine yet. I wanted this to be working before bringing anything over. I have tried to run as a service and just run the normal sage and it does the same thing. I am pretty sure the server is loaded and installed as I can choose between the 2 machines in the hd300 setup.
I have also increased the heap again and it now shows used 494mb Total 647mb Max7457mb
I am not sure what fanart is.
I do not do any importing of pictures or video. This is sage tv only for me.
I think it plays the shows fine from what I have watched them, but the program guide and the recorded shows guide are where it is real sluggish. the old machine scrolls right thru them and this one jumps a line at a time and then stall and then maybe 2 lines. it is real erratic. On the server box all is good, no problems.

Thanks
Wayne

You say "On the server box all is good, no problems." So you are not experiencing this issue when you bring up the gui on the server itself, which would eliminate the server hardware/software (excluding the networking part of the server) from being the problem. You have also stated that the HD300s work fine when they are pointed to your old server, but are slow when connected to the new server. Since they are working fine with the old server, that would seem to eliminate the HD300 from being the problem. So what we are left with is a networking issue somewhere between the new server and the HD300s. I think you also said that watching recorded or live shows works fine, it is just the navigation of the EPG listing and the recorded shows listing that is slow. Which seems strange, if it was a networking issue I would expect that watching a show would be as bad or worse than navigating the EPG. Have you tried deleting the HD300 property files on the server, and letting the extender/server recreate them?

Also, with two servers and five HDx00s connected, I'm assuming you have some sort of switch that these devices are all connected together with. Maybe a description of how your network is put together might help solve the puzzle.

[stuckless]

Originally Posted by KeithAbbott

if it was a networking issue I would expect that watching a show would be as bad or worse than navigating the EPG.

Actually video is usually ok because of the amount of buffering that happens, ie, a bad packet is dropped and then requested, and sent before the video has a chance to know there was a bad packet. But the sagetv UI is real-time, any latency due to network or IO is immediately visible. I had this exact same problem (twice) with the same switch. Videos were smooth, but actions like moving around the UI we sluggish. In my case(s) I had bad ports on an 8 port switch.

[sic0048]

I know from personal experience that a bad file/recording can freeze the GUI when you are browsing recordings. Specifically, if that bad recording appears in a list of recordings on the GUI it will cause the GUI to stall for a long time before recovering. However that shouldn't have any effect on the playback of recordings (unless you are trying to playback the bad recording), so I don't think this is entirely your problem. However since you seem to be having GUI slowness on multiple clients, you might see if there is any consistency in what you are experiencing - if so that probably points to a couple of bad recordings. Deleting the bad recordings should will fix the GUI freezing issue caused by them.

[Doubledose]

Here is new server and old server HD 300 ifconfig's. I don't see any errors on either. I run the program guide up and down a couple of times, tuned into a couple of watch live shows, tuned into a couple of recorded shows on both and scrolled the recorded shows.

Originally Posted by stuckless

You can try this....
unplug HD300, plug it in, telnet to it, and run the ifconfig command and check for error.
connect to your OLD sagetv server, do some operations, and then check the ifconfig command again, see if you have errors.

Repeat those steps (ie, unplug, plug in, etc) while connecting to the NEW server.

If you are seeing frame errors in BOTH tests then we can ignore those. if you are seeing frame errors in just the new server, I think it points to a server nic/cable/port issue.

New Server

tango3 login: root
tango3[~]# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:23:A5:00:05:1E
          inet addr:172.20.20.192  Bcast:172.20.20.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1122044 errors:0 dropped:0 overruns:0 frame:0
          TX packets:609845 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:256
          RX bytes:1516105613 (1.4 GiB)  TX bytes:40627358 (38.7 MiB)
          Interrupt:46

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:3228 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3228 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2191508 (2.0 MiB)  TX bytes:2191508 (2.0 MiB)

tango3[~]#



Old server

tango3 login: root
tango3[~]# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:23:A5:00:05:1E
          inet addr:172.20.20.192  Bcast:172.20.20.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1427341 errors:0 dropped:0 overruns:0 frame:0
          TX packets:757151 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:256
          RX bytes:1926661833 (1.7 GiB)  TX bytes:50826090 (48.4 MiB)
          Interrupt:46

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:5059 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5059 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3308717 (3.1 MiB)  TX bytes:3308717 (3.1 MiB)

tango3[~]#

[Doubledose]

Originally Posted by KeithAbbott

You say "On the server box all is good, no problems." So you are not experiencing this issue when you bring up the gui on the server itself, which would eliminate the server hardware/software (excluding the networking part of the server) from being the problem. You have also stated that the HD300s work fine when they are pointed to your old server, but are slow when connected to the new server. Since they are working fine with the old server, that would seem to eliminate the HD300 from being the problem. So what we are left with is a networking issue somewhere between the new server and the HD300s. I think you also said that watching recorded or live shows works fine, it is just the navigation of the EPG listing and the recorded shows listing that is slow. Which seems strange, if it was a networking issue I would expect that watching a show would be as bad or worse than navigating the EPG. Have you tried deleting the HD300 property files on the server, and letting the extender/server recreate them?

Also, with two servers and five HDx00s connected, I'm assuming you have some sort of switch that these devices are all connected together with. Maybe a description of how your network is put together might help solve the puzzle.

Yes, server box and sage work good just like they should. Yes, live shows and recordings are fine.
My network consist of a UBNT edgerouter 6P router and (2) netgear GSS116E gig switches.

[KeithAbbott]

Your motherboard looks like it is intended for gaming usage. It has a "Gaming GbE LAN" ethernet port onboard. It looks like Gigabyte has a free LAN Optimizer software that you can download and install. By default, I think the ethernet port operates in Auto Mode, maybe try to set it to Stream Mode or Browser Mode with the LAN Optimizer software and see if that makes any difference?