@ChuckPA said:
You are NOT protected . There is no locking.local_lock=none
You are getting NFS version 4 but your NAS vendor/ computer cannot negotiate
posixlocking.You must resolve this first. If not, you need to use the alternative and use a
/home/plexdirmethod to have more space. I have a created instructions for this as well
What exactly the benefits of the home directory method? I have to store my files directly in my vm. What is bad on the original position of the plex files?
There is nothing wrong with the default installation location for PMS. In recent versions of Ubuntu (a very common Linux distribution), they have decided to make it as small as possible. Some are only 16 GB. This is barely enough for the operating system and some utilities. It is not enough to add 5-10 GB of metadata for a medium sized Library.
In a VM, all linux installers will use the size of the HD you created for the VM. I always allocate 64 GB or more to a VM. It will only use the disk space it actually needs on demand (allocate-as-needed and copy-on-write). You may declare the maximum size as 128 GB, Linux will report this in the VM. When you examine the actual VDI / VMDK, you will often see 4-8 GB used where Linux reports 126 GB free. This is normal
When you install Linux, you can customize the installation and change all the filesystem (partition) sizes as well. This is what Ubuntu has changed. They default to a ‘small root’ model. Changing PMS’s default directory at this point only to support Ubuntu would cause chaos. This justified the creation of how to relocate the Plex ‘Library’. In the Tips, I suggest use of /home because is almost always the larger file system by default. Some do not use /home and allocate the space directly to /. The choice is entirely yours.
If you use /home in your VM, the metadata is in the VM unless you map a Host OS directory to the VM guest and use it. This is known as ‘shared folder pass through’. It allows the VM to remain small and the data to reside anywhere you like on the Host OS. It has all the benefits of file locking as provided by the host without all the troubles
@ChuckPA said:
There is nothing wrong with the default installation location for PMS. In recent versions of Ubuntu (a very common Linux distribution), they have decided to make it as small as possible. Some are only 16 GB. This is barely enough for the operating system and some utilities. It is not enough to add 5-10 GB of metadata for a medium sized Library.In a VM, all linux installers will use the size of the HD you created for the VM. I always allocate 64 GB or more to a VM. It will only use the disk space it actually needs on demand (allocate-as-needed and copy-on-write). You may declare the maximum size as 128 GB, Linux will report this in the VM. When you examine the actual VDI / VMDK, you will often see 4-8 GB used where Linux reports 126 GB free. This is normal
When you install Linux, you can customize the installation and change all the filesystem (partition) sizes as well. This is what Ubuntu has changed. They default to a ‘small root’ model. Changing PMS’s default directory at this point only to support Ubuntu would cause chaos. This justified the creation of how to relocate the Plex ‘Library’. In the Tips, I suggest use of
/homebecause is almost always the larger file system by default. Some do not use/homeand allocate the space directly to/. The choice is entirely yours.If you use
/homein your VM, the metadata is in the VM unless you map a Host OS directory to the VM guest and use it. This is known as ‘shared folder pass through’. It allows the VM to remain small and the data to reside anywhere you like on the Host OS. It has all the benefits of file locking as provided by the host without all the troubles
OK, so I have to try this… I will follow your instructions in the Linux forum. One… I hope last question… How to map a OS directory to the vm? At the moment I have my Metadata on my freenas mapped with nfs
Thaths all very complicated 
I do not know your VM. The documentation for it should show you this
@ChuckPA said:
I do not know your VM. The documentation for it should show you this
Hello,
I guess I have found the reason for my issues. It seems it is the Serie (Star wars rebels) of my son. If he looks this, a short time later plex dies. Other files work without any problems. Is it possible to verify my thoughts? What I have to looking for.?
If you can generate a sample of one file and upload it here (15-20 MB), I will look at it and see what is happening.
https://support.plex.tv/hc/en-us/articles/201035968-Generating-Sample-Files-from-Media
Also, please start playback and capture Plex log files (Settings - Server - Help - Download Logs) 15 seconds after failure. The sample and the log files will help me see the exact problem you are having.
We can the correct the root problem
@ChuckPA said:
If you can generate a sample of one file and upload it here (15-20 MB), I will look at it and see what is happening.
https://support.plex.tv/hc/en-us/articles/201035968-Generating-Sample-Files-from-MediaAlso, please start playback and capture Plex log files (Settings - Server - Help - Download Logs) 15 seconds after failure. The sample and the log files will help me see the exact problem you are having.
We can the correct the root problem
Hello,
please find attached the sample file and the log file. I hope the log file will help you, because I have to restart the plexserver (service plexmediaserver restart) before I am able to do the download.
Thanks again a lot for your help.
Andreas,
I am seeing two videos being played concurrently. “Der Klang der Stille” und “Das Dunkelschwert”. Stimmt?
I do not see obvious error in the sample you gave. May I have a sample of the other?
I also see the transcoder working. It goes to sleep (buffer full) . I next see the playback is terminated by the player (Samsung ?).
Which players are active? I see the Samsung TV clearly.
Would it be possible to have only one active when capturing this failure?
Yes, it’s a Samsung UE32J4570 television playing the plex app 2.008 The other is a LG with webos 3.10.23-p 13.biscayne.Im14a.6 I will try to get an error with only the Samsung playing and I will send a test file of the other playback
Thank you. I understand how it can be to ‘schedule’ television time. Whenever it is convenient, I will be available.
@ChuckPA said:
Thank you. I understand how it can be to ‘schedule’ television time. Whenever it is convenient, I will be available.
Please find attached the sample of the second movie. But I guess the problem will only appear if there are two playbacks at the same time. I will try to force the error on the samsung tv
Doesn’t sound related, but the latest Plex Pass version crashes on my Ubuntu physical box too.
@plexcloudgeek said:
Doesn’t sound related, but the latest Plex Pass version crashes on my Ubuntu physical box too.
May I see your log files immediately after a crash too please?
@ChuckPA said:
Thank you. I understand how it can be to ‘schedule’ television time. Whenever it is convenient, I will be available.
Hello,
here comes the logfile only for the Samsung TV
I hope you can find the problem. It is very frustating
Andreas,
Can you advise me please on which devices are 192.168.1.249 and 192.168.1.98 ? Also, what is 192.168.1.248? It arrives later in the logs (reboot?)
This statement: Jul 26, 2017 12:28:03.209 [0x7f0f577fe700] DEBUG - WebSocket: client initiated close tells me the player (.1.249) is exiting the Plex app.
Jul 26, 2017 12:27:50.316 [0x7f0f577fe700] DEBUG - Auth: We found auth token (xxxxxxxxxxxxxxxxxxxx), enabling token-based authentication.
Jul 26, 2017 12:27:50.316 [0x7f0f577fe700] DEBUG - Auth: authenticated user 1 as andreas.frank1971@t-online.de
Jul 26, 2017 12:27:50.316 [0x7f0f577fe700] DEBUG - Auth: Came in with a super-token, authorization succeeded.
Jul 26, 2017 12:27:50.316 [0x7f0f56ffd700] DEBUG - Request: [192.168.1.249:54210 (Subnet)] GET /player/proxy/poll?deviceClass=pc&protocolVersion=1&protocolCapabilities=timeline%2Cplayback%2Cnavigation%2Cmirror%2Cplayqueues&timeout=1 (13 live) TLS GZIP Signed-in Token (andreas.frank1971@t-online.de)
Jul 26, 2017 12:27:50.317 [0x7f0f56ffd700] DEBUG - Beginning read from two-way stream.
Jul 26, 2017 12:28:03.203 [0x7f0f577fe700] DEBUG - handleStreamRead code 335544539: short read
Jul 26, 2017 12:28:03.203 [0x7f0f577fe700] WARN - LongPoll: Got error, closing.
Jul 26, 2017 12:28:03.209 [0x7f0f577fe700] DEBUG - WebSocket: client initiated close
Jul 26, 2017 12:28:03.209 [0x7f0f577fe700] DEBUG - handleStreamRead code 335544539: short read
Jul 26, 2017 12:28:03.209 [0x7f0f577fe700] DEBUG - NotificationStream: Removing because of error
Jul 26, 2017 12:28:05.504 [0x7f0f54fff700] DEBUG - [CompanionProxy] player 61754e86-a575-41e6-9669-3e02aec8ecf4 was last refreshed 10 seconds ago
Jul 26, 2017 12:28:15.504 [0x7f0f55fff700] DEBUG - [CompanionProxy] player 61754e86-a575-41e6-9669-3e02aec8ecf4 was last refreshed 20 seconds ago
Jul 26, 2017 12:28:25.504 [0x7f0f3f7ff700] DEBUG - [CompanionProxy] player 61754e86-a575-41e6-9669-3e02aec8ecf4 was last refreshed 30 seconds ago
Jul 26, 2017 12:28:35.504 [0x7f0f54fff700] DEBUG - [CompanionProxy] player 61754e86-a575-41e6-9669-3e02aec8ecf4 was last refreshed 40 seconds ago
Jul 26, 2017 12:28:35.505 [0x7f0f54fff700] DEBUG - [CompanionProxy] player 61754e86-a575-41e6-9669-3e02aec8ecf4 was not refreshed for over 30 seconds, dropping it.
Jul 26, 2017 12:29:16.961 [0x7f0f54fff700] DEBUG - EPG[onconnect]: Purging 5 airings which completed in the past.
Jul 26, 2017 12:29:17.037 [0x7f0f54fff700] DEBUG - Destroying metadata item 1547 (Episode 07-26)
Jul 26, 2017 12:29:55.508 [0x7f0f4ebff700] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.1.1 (http://192.168.1.1:1990/WFADevice.xml)
Jul 26, 2017 12:29:55.508 [0x7f0f55fff700] DEBUG - HTTP requesting GET http://192.168.1.1:1990/WFADevice.xml
Jul 26, 2017 12:29:55.509 [0x7f0f55fff700] DEBUG - HTTP 200 response from GET http://192.168.1.1:1990/WFADevice.xml
Jul 26, 2017 12:29:57.912 [0x7f0f56ffd700] DEBUG - [PlexRelay] Transferred: sent 6744, received 4496 bytes, in 323.9 seconds
Jul 26, 2017 12:29:57.913 [0x7f0f3d7ff700] DEBUG - [PlexRelay] Bytes per second: sent 20.8, received 13.9
Jul 26, 2017 12:29:57.913 [0x7f0f53fff700] ERROR - JobManager: child process returned: 255 (Unknown error 255)
Jul 26, 2017 12:30:01.339 [0x7f0f3f7ff700] DEBUG - EPG[onconnect]: Next thing to start/end is at 2017-07-26 10:35:00 (in 300 seconds)
... removed 12:30:17 ... was BPQ Garbage Collection ...
Jul 26, 2017 12:31:32.507 [0x7f0f4ebff700] DEBUG - NetworkServiceBrowser: PLAYER departed after not being seen for 181.999729 seconds: 127.0.0.1
Jul 26, 2017 12:32:58.746 [0x7f0f577fe700] DEBUG - handleStreamRead code 104: Connection reset by peer
Jul 26, 2017 12:32:58.746 [0x7f0f577fe700] DEBUG - NotificationStream: Removing because of error
Jul 26, 2017 12:32:58.749 [0x7f0f57fff700] DEBUG - handleStreamRead code 104: Connection reset by peer
Jul 26, 2017 12:32:58.749 [0x7f0f57fff700] DEBUG - NotificationStream: Removing because of error
@ChuckPA said:
Andreas,
Can you advise me please on which devices are 192.168.1.249 and 192.168.1.98 ? Also, what is 192.168.1.248? It arrives later in the logs (reboot?)This statement:
Jul 26, 2017 12:28:03.209 [0x7f0f577fe700] DEBUG - WebSocket: client initiated closetells me the player (.1.249) is exiting the Plex app.Jul 26, 2017 12:27:50.316 [0x7f0f577fe700] DEBUG - Auth: We found auth token (xxxxxxxxxxxxxxxxxxxx), enabling token-based authentication. Jul 26, 2017 12:27:50.316 [0x7f0f577fe700] DEBUG - Auth: authenticated user 1 as andreas.frank1971@t-online.de Jul 26, 2017 12:27:50.316 [0x7f0f577fe700] DEBUG - Auth: Came in with a super-token, authorization succeeded. Jul 26, 2017 12:27:50.316 [0x7f0f56ffd700] DEBUG - Request: [192.168.1.249:54210 (Subnet)] GET /player/proxy/poll?deviceClass=pc&protocolVersion=1&protocolCapabilities=timeline%2Cplayback%2Cnavigation%2Cmirror%2Cplayqueues&timeout=1 (13 live) TLS GZIP Signed-in Token (andreas.frank1971@t-online.de) Jul 26, 2017 12:27:50.317 [0x7f0f56ffd700] DEBUG - Beginning read from two-way stream. Jul 26, 2017 12:28:03.203 [0x7f0f577fe700] DEBUG - handleStreamRead code 335544539: short read Jul 26, 2017 12:28:03.203 [0x7f0f577fe700] WARN - LongPoll: Got error, closing. Jul 26, 2017 12:28:03.209 [0x7f0f577fe700] DEBUG - WebSocket: client initiated close Jul 26, 2017 12:28:03.209 [0x7f0f577fe700] DEBUG - handleStreamRead code 335544539: short read Jul 26, 2017 12:28:03.209 [0x7f0f577fe700] DEBUG - NotificationStream: Removing because of error Jul 26, 2017 12:28:05.504 [0x7f0f54fff700] DEBUG - [CompanionProxy] player 61754e86-a575-41e6-9669-3e02aec8ecf4 was last refreshed 10 seconds ago Jul 26, 2017 12:28:15.504 [0x7f0f55fff700] DEBUG - [CompanionProxy] player 61754e86-a575-41e6-9669-3e02aec8ecf4 was last refreshed 20 seconds ago Jul 26, 2017 12:28:25.504 [0x7f0f3f7ff700] DEBUG - [CompanionProxy] player 61754e86-a575-41e6-9669-3e02aec8ecf4 was last refreshed 30 seconds ago Jul 26, 2017 12:28:35.504 [0x7f0f54fff700] DEBUG - [CompanionProxy] player 61754e86-a575-41e6-9669-3e02aec8ecf4 was last refreshed 40 seconds ago Jul 26, 2017 12:28:35.505 [0x7f0f54fff700] DEBUG - [CompanionProxy] player 61754e86-a575-41e6-9669-3e02aec8ecf4 was not refreshed for over 30 seconds, dropping it. Jul 26, 2017 12:29:16.961 [0x7f0f54fff700] DEBUG - EPG[onconnect]: Purging 5 airings which completed in the past. Jul 26, 2017 12:29:17.037 [0x7f0f54fff700] DEBUG - Destroying metadata item 1547 (Episode 07-26) Jul 26, 2017 12:29:55.508 [0x7f0f4ebff700] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.1.1 (http://192.168.1.1:1990/WFADevice.xml) Jul 26, 2017 12:29:55.508 [0x7f0f55fff700] DEBUG - HTTP requesting GET http://192.168.1.1:1990/WFADevice.xml Jul 26, 2017 12:29:55.509 [0x7f0f55fff700] DEBUG - HTTP 200 response from GET http://192.168.1.1:1990/WFADevice.xml Jul 26, 2017 12:29:57.912 [0x7f0f56ffd700] DEBUG - [PlexRelay] Transferred: sent 6744, received 4496 bytes, in 323.9 seconds Jul 26, 2017 12:29:57.913 [0x7f0f3d7ff700] DEBUG - [PlexRelay] Bytes per second: sent 20.8, received 13.9 Jul 26, 2017 12:29:57.913 [0x7f0f53fff700] ERROR - JobManager: child process returned: 255 (Unknown error 255) Jul 26, 2017 12:30:01.339 [0x7f0f3f7ff700] DEBUG - EPG[onconnect]: Next thing to start/end is at 2017-07-26 10:35:00 (in 300 seconds) ... removed 12:30:17 ... was BPQ Garbage Collection ... Jul 26, 2017 12:31:32.507 [0x7f0f4ebff700] DEBUG - NetworkServiceBrowser: PLAYER departed after not being seen for 181.999729 seconds: 127.0.0.1 Jul 26, 2017 12:32:58.746 [0x7f0f577fe700] DEBUG - handleStreamRead code 104: Connection reset by peer Jul 26, 2017 12:32:58.746 [0x7f0f577fe700] DEBUG - NotificationStream: Removing because of error Jul 26, 2017 12:32:58.749 [0x7f0f57fff700] DEBUG - handleStreamRead code 104: Connection reset by peer Jul 26, 2017 12:32:58.749 [0x7f0f57fff700] DEBUG - NotificationStream: Removing because of error
Hi Chuck,
192.168.1.98 is a handy
192.168.1.248 is also a handy
192.168.1.249 is my windows10 vm
The statement you are talking about was the TV of my son. But it was an another series. Not star wars rebels. Will it be possible that the Samsung television do the problem. The plex app is the one for smart TV(no Tizen TV)
The file I have send to you was from a crash 4 hours later. I have to restart plex via cmd. And it takes very long to finish the command (about a minute)
Andreas,
Thank you for the information.
I believe the Samsung is the problem but it is not yet clear.
You use Windows 10 with Ubuntu in VM? Do you know you can use PMS on Windows 10 direct? It is much better and faster without the VM.
@ChuckPA said:
Andreas,
Thank you for the information.
I believe the Samsung is the problem but it is not yet clear.You use Windows 10 with Ubuntu in VM? Do you know you can use PMS on Windows 10 direct? It is much better and faster without the VM.
Chuck,
no I dont use Ubuntu vm with windows10. Both are semperated from each other and running on a esxi host.
What can we do to be sure that the samsung will be the problem? Whats your thought about the problem:
(The TV is strait byside my router. Just one wall are betwenn router and tv. The distance is < 1m)=
Andreas,
Are you using the VMNET3 ethernet adapter with LRO (Large Receive Offload) enabled? If so, this will cause Ubuntu & PMS to crash. It is a Ubuntu driver bug. Changing the ESXi adapter name to e1000e will resolve the issue completely.
@ChuckPA said:
Andreas,
Are you using the VMNET3 ethernet adapter with LRO (Large Receive Offload) enabled? If so, this will cause Ubuntu & PMS to crash. It is a Ubuntu driver bug. Changing the ESXi adapter name toe1000ewill resolve the issue completely.
I cant find this setting on my esxi host. Can you give me some advice pleas Sorry :…
Edit: Have found it. I will tell you whats happend 
