PLEX showing on two ports netstat

Status
Not open for further replies.

Rhys_O

Dabbler
Joined
Jan 11, 2016
Messages
17
Hi,

I have been having problems with a very slow FreeNAS box which has come out of the blue after 6 months or so of smooth sailing.

I notice it most in plex, so I will start there.

System specs:
System is virtualised on Proxmox
TS140
Xeon 1226 v3
24GB ECC RAM
4x 3TB WD RED running in Raid 10 in a HP MSA 60 - Raid card: reflashed Dell PERC H310

CPU isn't taxed, plenty of RAM, no rogue processes as far as I can see. Once a stream starts, it's absolutely fine. I was watching a show at 9mbps with no issues at all however it took forever to navigate to it via any platform inc. LG TV, web browser, Android app etc.

The only thing I can find that is causing me any concern is a netstat output showing two FreeNAS ports routing to the same plex IP:

tcp4 0 0 192.168.1.150.47657 192.168.1.148.32400 ESTABLISHED

tcp4 0 0 192.168.1.150.47652 192.168.1.148.32400 ESTABLISHED

Could this be the cause of the issue? Is it a case of conflicting routes causing packet loss? If so, where to from here?
 

Nick2253

Wizard
Joined
Apr 21, 2014
Messages
1,633
I doubt your problem has anything to do with multiple ports. Many services connect over multiple ports, and I would imagine that Plex is one of them.

First off, virtualizing FreeNAS is prone to a number of problems. I noticed that you said "Raid 10"; is the RAID card forwarded to the FreeNAS VM, and is FreeNAS handling the drives directly? Can you elaborate on your setup here?

My guess is that your hardware is not set up correctly, which is causing problems for FreeNAS accessing the drives. What other VMs do you have running? What drive(s) are you using for your Proxmox datastore?
 

Rhys_O

Dabbler
Joined
Jan 11, 2016
Messages
17
So I tried a few things out and got it sorted. I'm not going to pretend I understand what I've done or why it worked, but simply put, I turned on auto-tune and everything just started functioning better.

My guess is that there was too much RAM being held for ZFS, but that is the guess of someone with absolutely no experience of these things.

Just in case someone comes to the thread looking for answers, here are the autotune features that have been added
 

Attachments

  • Screen Shot 2016-09-02 at 09.14.54.png
    Screen Shot 2016-09-02 at 09.14.54.png
    121.5 KB · Views: 202
Status
Not open for further replies.
Top