Server Version#: 1.20.2.3370
Player Version#: 4.43.1
Can you help me ? I sometimes find myself with this kind of error, which fills my server RAM, which becomes unusable!
Error :
Sep 27, 2020 23:13:31.683 [0x7f37177fe700] DEBUG - [TranscodeOutputStream] Changed instance plex-transcode-6jc3hze5s0mfjaerwiue9rf4-b5af3835-cf06-426d-964b-c3b5b39a07c1 which had to -1; was at chunk -1 with offset -1.000000 now at chunk -1
Installing in Docker - DSM 6.2.3
Look : Plex Media Server.5.log
I have to restart the docker for this to stop and the RAM to stop increasing.
On the plex dashboard, the RAM is not seen as used by Plex, but by the "system"Plex Media Server Logs_2020-09-28_16-45-34.zip (3,9 Mo)
Where are /config and all the other Plex directories outside the container mapped?
Are they on NAS / network storage or is everything resident on the machine?
Are you 100% certain that file is correct and you’re not running out of space?
All 5 rollover logs are filled with the same thing:
Nov 02, 2020 11:44:54.929 [0x7fe35874c700] INFO - Plex Media Server v1.20.4.3517-ab5e1197c - Docker Docker Container (LinuxServer.io) x86_64 - build: linux-x86_64 debian - GMT 00:00
Nov 02, 2020 11:44:55.119 [0x7fe35874c700] INFO - Linux version: 4.4.59+, language: en-US
Nov 02, 2020 11:44:55.323 [0x7fe35874c700] INFO - Processor Intel(R) Core(TM) i5-8600K CPU @ 3.60GHz
Nov 02, 2020 11:44:55.323 [0x7fe35874c700] INFO - /usr/lib/plexmediaserver/Plex Media Server
Nov 02, 2020 11:44:17.696 [0x7fe2e9ffb700] DEBUG - [TranscodeOutputStream] Changed instance plex-transcode-uyvbvg71ykoppku3m9r882wc-d93cd175-fad7-448b-b10a-856883f62544 which had to -1; was at chunk -1 with offset -1.000000 now at chunk -1
Nov 02, 2020 11:44:17.696 [0x7fe2e9ffb700] DEBUG - [TranscodeOutputStream] Changed instance plex-transcode-uyvbvg71ykoppku3m9r882wc-d93cd175-fad7-448b-b10a-856883f62544 which had to -1; was at chunk -1 with offset -1.000000 now at chunk -1
Nov 02, 2020 11:44:17.696 [0x7fe2e9ffb700] DEBUG - [TranscodeOutputStream] Changed instance plex-transcode-uyvbvg71ykoppku3m9r882wc-d93cd175-fad7-448b-b10a-856883f62544 which had to -1; was at chunk -1 with offset -1.000000 now at chunk -1
Nov 02, 2020 11:44:17.696 [0x7fe2e9ffb700] DEBUG - [TranscodeOutputStream] Changed instance plex-transcode-uyvbvg71ykoppku3m9r882wc-d93cd175-fad7-448b-b10a-856883f62544 which had to -1; was at chunk -1 with offset -1.000000 now at chunk -1
Nov 02, 2020 11:44:17.696 [0x7fe2e9ffb700] DEBUG - [TranscodeOutputStream] Changed instance plex-transcode-uyvbvg71ykoppku3m9r882wc-d93cd175-fad7-448b-b10a-856883f62544 which had to -1; was at chunk -1 with offset -1.000000 now at chunk -1
Nov 02, 2020 11:44:17.696 [0x7fe2e9ffb700] DEBUG - [TranscodeOutputStream] Changed instance plex-transcode-uyvbvg71ykoppku3m9r882wc-d93cd175-fad7-448b-b10a-856883f62544 which had to -1; was at chunk -1 with offset -1.000000 now at chunk -1
Nov 02, 2020 11:44:17.696 [0x7fe2e9ffb700] DEBUG - [TranscodeOutputStream] Changed instance plex-transcode-uyvbvg71ykoppku3m9r882wc-d93cd175-fad7-448b-b10a-856883f62544 which had to -1; was at chunk -1 with offset -1.000000 now at chunk -1
Nov 02, 2020 11:44:17.696 [0x7fe2e9ffb700] DEBUG - [TranscodeOutputStream] Changed instance plex-transcode-uyvbvg71ykoppku3m9r882wc-d93cd175-fad7-448b-b10a-856883f62544 which had to -1; was at chunk -1 with offset -1.000000 now at chunk -1
Nov 02, 2020 11:44:17.696 [0x7fe2e9ffb700] DEBUG - [TranscodeOutputStream] Changed instance plex-transcode-uyvbvg71ykoppku3m9r882wc-d93cd175-fad7-448b-b10a-856883f62544 which had to -1; was at chunk -1 with offset -1.000000 now at chunk -1
Nov 02, 2020 11:44:17.696 [0x7fe2e9ffb700] DEBUG - [TranscodeOutputStream] Changed instance plex-transcode-uyvbvg71ykoppku3m9r882wc-d93cd175-fad7-448b-b10a-856883f62544 which had to -1; was at chunk -1 with offset -1.000000 now at chunk -1
Nov 02, 2020 11:44:17.696 [0x7fe2e9ffb700] DEBUG - [TranscodeOutputStream] Changed instance plex-transcode-uyvbvg71ykoppku3m9r882wc-d93cd175-fad7-448b-b10a-856883f62544 which had to -1; was at chunk -1 with offset -1.000000 now at chunk -1
Nov 02, 2020 11:44:17.696 [0x7fe2e9ffb700] DEBUG - [TranscodeOutputStream] Changed instance plex-transcode-uyvbvg71ykoppku3m9r882wc-d93cd175-fad7-448b-b10a-856883f62544 which had to -1; was at chunk -1 with offset -1.000000 now at chunk -1
Nov 02, 2020 11:44:17.696 [0x7fe2e9ffb700] DEBUG - [TranscodeOutputStream] Changed instance plex-transcode-uyvbvg71ykoppku3m9r882wc-d93cd175-fad7-448b-b10a-856883f62544 which had to -1; was at chunk -1 with offset -1.000000 now at chunk -1
Nov 02, 2020 11:44:17.696 [0x7fe2e9ffb700] DEBUG - [TranscodeOutputStream] Changed instance plex-transcode-uyvbvg71ykoppku3m9r882wc-d93cd175-fad7-448b-b10a-856883f62544 which had to -1; was at chunk -1 with offset -1.000000 now at chunk -1
Might have just found a damaged file that FFMPEG/transcoder doesn’t know how to handle.
Yes, that’s the next logical piece of the puzzle.
Is there any way to find out what that person was doing - what was observed at time of failure?
For the trick – Can it be recreated ?
If so, would you care to make your log file retention longer so we might be able to see the start of the failure?
Not going to be super helpful, but just want to add/let you know I actually experienced a similar issue and it involved 1 user that was using Chrome and my memory would fill up and then Plex would basically crash. I took a slightly extreme route by using Tautulli to trigger a kill stream script when that user started playing something using Chrome (and I put a message saying there was an issue with the Chrome player and to download Plex for [their OS] and use that instead. That user hasn’t used Plex Web on Chrome since (as I can see when the script is triggered) and I haven’t had the issue. I realize it’s kind of extreme, but honestly for me, I would prefer my users to use Plex for [their OS] because it is going to handle more codecs vs Plex Web as well as it should be able to handle some transcoding on their side (I can’t confirm that just speculation on my end).
All that was to let you know that I have seen this issue before, but I “can’t” reproduce it any longer because I got the user to stop using Plex Web for Chrome. Also, I know that user has logged into their account for a couple family members so I don’t actually know who was using it during the crash.
the user was playing a video lowering the quality to 2Mbps.
After the transcoder failure, the container restarts, and sometimes after several tries, the reading proceeds correctly.
This only seems to happen with the user’s computer, I was not able to reproduce it with my machine.
Also, it is not always possible to reproduce it, sometimes playing multiple episodes does not report bugs. (even when re-playing a video that previously caused a crash)
Thank you for your answer, indeed, the solution seems to be not to read via Plex Web and Chrome! But banning it via Tautulli is a bit “radical”, I would like not to come to that even if I will have to do it if there is no solution because regular crashes are very penalizing for other users.
If it comes to it where you need to setup the script and you already have Tautulli installed, I will be glad to help you get the script up and running.
However, hopefully you will be able to get logs for Chuck that will help show the issue and allow it to be resolved.
I don’t know if this is similar but I am having a memory issue as well. I am using Plex Version 1.20.4.3517 in a LXC container in Proxmox. I am having stead memory usage increase over time.
11/12/20 11:49 — 61.3% 2.45GB of 4GB of ram…
11/13/20 09:12 — 70.15% 2.81GB of 4GB ram…
Im not sure what logs you need. I used proxmox’s menu to see if memory is released, it might happen a little bit but it continues throughout the day. I do have a GPU pass-through, and I do use trans-coding while I DVR from my HDHomeRun. If I can provide any information to help diagnose the problem as well let me know.
