binhex Posted April 3, 2020 Author Share Posted April 3, 2020 Anyone else having issues with release 1.19.1.2589-1-01? Every time i attempt to update my docker it corrupts my database and i have to restore it.Running unraid 6.7.x by any chance?Sent from my CLT-L09 using Tapatalk Quote Link to comment
sauso Posted April 3, 2020 Share Posted April 3, 2020 2 minutes ago, binhex said: Running unraid 6.7.x by any chance? Sent from my CLT-L09 using Tapatalk Nah 6.8.2. 1.18.9.2578-1-01 works perfectly but as soon as i update the DB corrupts no soup for me. Quote Link to comment
sauso Posted April 3, 2020 Share Posted April 3, 2020 (edited) I should add. If i pull the updated container and use a fresh DB it works fine. It just corrupts with my existing install. Edited April 3, 2020 by sauso Quote Link to comment
binhex Posted April 3, 2020 Author Share Posted April 3, 2020 25 minutes ago, sauso said: I should add. If i pull the updated container and use a fresh DB it works fine. It just corrupts with my existing install. ok, well i guess it could be a db upgrade bug, after all plex pass is beta edition of pms. Have you tried posting the issue on plex forums to see if its a known issue?. 1 Quote Link to comment
sauso Posted April 3, 2020 Share Posted April 3, 2020 9 minutes ago, binhex said: ok, well i guess it could be a db upgrade bug, after all plex pass is beta edition of pms. Have you tried posting the issue on plex forums to see if its a known issue?. Will give that a shot Quote Link to comment
sauso Posted April 3, 2020 Share Posted April 3, 2020 https://forums.plex.tv/t/libraries-and-settings-gone-after-upgrade-to-1-19/566527/18 This might possibly be the reason. Quote Link to comment
sauso Posted April 3, 2020 Share Posted April 3, 2020 Actually this could be it. https://forums.plex.tv/t/1-19-1-2589-not-working-on-freenas-after-upgrade/565650 Quote Link to comment
drdebian Posted April 4, 2020 Share Posted April 4, 2020 2020-04-04 04:15:46.138925 [info] PUID defined as '99' 2020-04-04 04:15:46.299542 [info] PGID defined as '100' 2020-04-04 04:15:46.847706 [info] UMASK defined as '000' 2020-04-04 04:15:46.889934 [info] Permissions already set for volume mappings 2020-04-04 04:15:46.914962 [info] TRANS_DIR defined as '/config/transcode' 2020-04-04 04:15:47.627790 [info] Deleting files in /tmp (non recursive)... 2020-04-04 04:15:48.468482 [info] Starting Supervisor... 2020-04-04 04:15:54,129 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing 2020-04-04 04:15:54,129 INFO Set uid to user 0 succeeded 2020-04-04 04:15:54,151 INFO supervisord started with pid 6 2020-04-04 04:15:55,152 INFO spawned: 'plexmediaserver' with pid 55 2020-04-04 04:15:55,153 INFO reaped unknown pid 7 2020-04-04 04:15:56,154 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2020-04-04 04:16:25,146 DEBG 'plexmediaserver' stderr output: connect: Connection timed out 2020-04-04 04:16:31,162 DEBG 'plexmediaserver' stderr output: connect: Connection timed out 2020-04-04 04:16:37,178 DEBG 'plexmediaserver' stderr output: connect: Connection timed out 2020-04-04 04:16:37,178 DEBG 'plexmediaserver' stderr output: connect: Connection timed out 2020-04-04 04:16:43,194 DEBG 'plexmediaserver' stderr output: connect: Connection timed out Is this also due to the version upgrade? How to get it working again? Quote Link to comment
sauso Posted April 4, 2020 Share Posted April 4, 2020 deffinately some sort of problem with the Database upgrade portion. Moved my settings over to the linuxserver.io container to test and can see the upgrade occur but then the same crashes after. [cont-init.d] 10-adduser: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 45-plex-claim: executing... [cont-init.d] 45-plex-claim: exited 0. [cont-init.d] 50-gid-video: executing... [cont-init.d] 50-gid-video: exited 0. [cont-init.d] 60-plex-update: executing... Atempting to upgrade to: 1.19.1.2621-b249be3b0 2020-04-04 15:37:16 URL:https://downloads.plex.tv/plex-media-server-new/1.19.1.2621-b249be3b0/debian/plexmediaserver_1.19.1.2621-b249be3b0_amd64.deb [91119418/91119418] -> "/tmp/plexmediaserver_1.19.1.2621-b249be3b0_amd64.deb" [1] (Reading database ... 10446 files and directories currently installed.) Preparing to unpack .../plexmediaserver_1.19.1.2621-b249be3b0_amd64.deb ... PlexMediaServer install: Pre-installation Validation. PlexMediaServer install: Docker detected. Preinstallation validation not required. Unpacking plexmediaserver (1.19.1.2621-b249be3b0) over (1.18.9.2578-513b381af) ... Setting up plexmediaserver (1.19.1.2621-b249be3b0) ... PlexMediaServer install: Docker detected. Postinstallation tasks not required. Continuing. Processing triggers for libc-bin (2.27-3ubuntu1) ... [cont-init.d] 60-plex-update: exited 0. [cont-init.d] 99-custom-scripts: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-scripts: exited 0. [cont-init.d] done. [services.d] starting services Starting Plex Media Server. [services.d] done. ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.19.1.2621-b249be3b0/PLEX MEDIA SERVER/25fef65b-2e88-3706-424a2f9d-08e97f82.dmp Starting Plex Media Server. Error starting framework core for /usr/lib/plexmediaserver/Resources/Plug-ins-b249be3b0/PlexMusic.bundle. ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.19.1.2621-b249be3b0/PLEX MEDIA SERVER/4b063399-5431-8024-0ec2f67c-1e3d0ab0.dmp Starting Plex Media Server. ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.19.1.2621-b249be3b0/PLEX MEDIA SERVER/1e27924b-fccb-9594-4478833a-6b75cabd.dmp Starting Plex Media Server. There are some rumblings on the plex forums about it but i doubt the vast majority of users will be running this new version so it may not get much traction until then. Only thing i can think of doing (if they don't fix it) is to export my watch settings and start fresh. Quote Link to comment
sauso Posted April 4, 2020 Share Posted April 4, 2020 Thought i would try and Dump my DB into a fresh one just in case but didn't seem to make a differnce. I've spun up another plex server with my library and will attempt the upgrade with that and see how it goes. If worst comes to worst i will just export my watch settings and start fresh. Quote Link to comment
sauso Posted April 5, 2020 Share Posted April 5, 2020 Ended up giving up on making my current DB work and just built up a new container and migrated my watched status. Must have been a decent amount of crud in my DB because the old one was 85mb and the new ones is 53mb. I also went from having 7gb of metadata to 2.7. Quote Link to comment
drdebian Posted April 8, 2020 Share Posted April 8, 2020 How would I go about adding Handbrake in this container, so I can use HandbrakeCLI to automatically transcode my DVR recordings to H.265 using Plex's "postprocessing script" feature? Any ideas? Quote Link to comment
Knh68 Posted April 11, 2020 Share Posted April 11, 2020 Hi guys I've got a problem with my binhex plex pass........ I recently cancelled my tidal hifi subscription which i linked to plexpass...... I later changed my mind after contemplating going to a competitor. I carried on my subscription to tidal hifi /plexpass....... I've relinked my tidal to plexpass my tidal doesn't show in plex only the preview! I've tried unlinking and relinking still nothing.! I've restarted the docker container still nothing.. Any ideas.? I hope I've got this in the correct thread by the way my apologies if not.. Quote Link to comment
trurl Posted April 11, 2020 Share Posted April 11, 2020 4 hours ago, Knh68 said: I hope I've got this in the correct thread Sounds like a question for the plex forums Quote Link to comment
Knh68 Posted April 11, 2020 Share Posted April 11, 2020 37 minutes ago, trurl said: Sounds like a question for the plex forums Thanks for the help 👍 Quote Link to comment
njdowdy Posted April 15, 2020 Share Posted April 15, 2020 I'm experience a strange problem. Whenever I try to play .m4a files through the browser (chrome & firefox), transcode fails and playback does not start. Logs say: "DEBG 'plexmediaserver' stderr output: Jobs: failed with chdir, errno=2" However, if I use the plex android app, the files play fine. FLAC/mp3/etc formats work fine in browser and in app. What could be going wrong? Quote Link to comment
binhex Posted April 15, 2020 Author Share Posted April 15, 2020 4 hours ago, njdowdy said: I'm experience a strange problem. Whenever I try to play .m4a files through the browser (chrome & firefox), transcode fails and playback does not start. Logs say: "DEBG 'plexmediaserver' stderr output: Jobs: failed with chdir, errno=2" However, if I use the plex android app, the files play fine. FLAC/mp3/etc formats work fine in browser and in app. What could be going wrong? this also sounds like a question for the plex forums, please post your question there. Quote Link to comment
Duggie264 Posted April 19, 2020 Share Posted April 19, 2020 Hi, just started getting this crash today, any ideas? 2020-04-19 15:23:48.353687 [info] System information Linux ################# 4.19.107-Unraid #1 SMP Thu Mar 5 13:55:57 PST 2020 x86_64 GNU/Linux 2020-04-19 15:23:48.383161 [info] PUID defined as '99' 2020-04-19 15:23:48.415129 [info] PGID defined as '100' 2020-04-19 15:23:48.918075 [info] UMASK defined as '000' 2020-04-19 15:23:48.945899 [info] Permissions already set for volume mappings 2020-04-19 15:23:48.972882 [warn] TRANS_DIR not defined,(via -e TRANS_DIR), defaulting to '/config/tmp' 2020-04-19 15:23:49.004719 [info] Deleting files in /tmp (non recursive)... 2020-04-19 15:23:49.030933 [info] Starting Supervisor... 2020-04-19 15:23:49,197 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing 2020-04-19 15:23:49,197 INFO Set uid to user 0 succeeded 2020-04-19 15:23:49,199 INFO supervisord started with pid 6 2020-04-19 15:23:49.004719 [info] Deleting files in /tmp (non recursive)... 2020-04-19 15:23:49.030933 [info] Starting Supervisor... 2020-04-19 15:23:49,197 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing 2020-04-19 15:23:49,197 INFO Set uid to user 0 succeeded 2020-04-19 15:23:49,199 INFO supervisord started with pid 6 2020-04-19 15:23:50,202 INFO spawned: 'plexmediaserver' with pid 55 2020-04-19 15:23:50,202 INFO reaped unknown pid 7 2020-04-19 15:23:50,437 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 139734334410080 for <Subprocess at 139734334410224 with name plexmediaserver in state STARTING> (stdout)> 2020-04-19 15:23:50,438 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 139734334410368 for <Subprocess at 139734334410224 with name plexmediaserver in state STARTING> (stderr)> 2020-04-19 15:23:50,438 INFO exited: plexmediaserver (exit status 255; not expected) 2020-04-19 15:23:50,438 DEBG received SIGCHLD indicating a child quit 2020-04-19 15:23:51,441 INFO spawned: 'plexmediaserver' with pid 60 2020-04-19 15:23:51,731 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 139734335288080 for <Subprocess at 139734334410224 with name plexmediaserver in state STARTING> (stdout)> 2020-04-19 15:23:51,731 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 139734333605152 for <Subprocess at 139734334410224 with name plexmediaserver in state STARTING> (stderr)> 2020-04-19 15:23:51,731 INFO exited: plexmediaserver (exit status 255; not expected) 2020-04-19 15:23:51,732 DEBG received SIGCHLD indicating a child quit 2020-04-19 15:23:53,736 INFO spawned: 'plexmediaserver' with pid 65 2020-04-19 15:23:54,021 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 139734334119840 for <Subprocess at 139734334410224 with name plexmediaserver in state STARTING> (stdout)> 2020-04-19 15:23:54,021 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 139734334410368 for <Subprocess at 139734334410224 with name plexmediaserver in state STARTING> (stderr)> 2020-04-19 15:23:54,021 INFO exited: plexmediaserver (exit status 255; not expected) 2020-04-19 15:23:54,021 DEBG received SIGCHLD indicating a child quit 2020-04-19 15:23:54,021 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 139734334119840 for <Subprocess at 139734334410224 with name plexmediaserver in state STARTING> (stdout)> 2020-04-19 15:23:54,021 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 139734334410368 for <Subprocess at 139734334410224 with name plexmediaserver in state STARTING> (stderr)> 2020-04-19 15:23:54,021 INFO exited: plexmediaserver (exit status 255; not expected) 2020-04-19 15:23:54,021 DEBG received SIGCHLD indicating a child quit 2020-04-19 15:23:57,027 INFO spawned: 'plexmediaserver' with pid 70 2020-04-19 15:23:57,323 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 139734335288080 for <Subprocess at 139734334410224 with name plexmediaserver in state STARTING> (stdout)> 2020-04-19 15:23:57,323 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 139734333605056 for <Subprocess at 139734334410224 with name plexmediaserver in state STARTING> (stderr)> 2020-04-19 15:23:57,324 INFO exited: plexmediaserver (exit status 255; not expected) 2020-04-19 15:23:57,324 DEBG received SIGCHLD indicating a child quit 2020-04-19 15:23:58,325 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly 2020-04-19 15:23:58,325 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly Quote Link to comment
Tabraxis Posted April 19, 2020 Share Posted April 19, 2020 Hey All, Have 2 weird issues: 1) Has anyone else's Plex switched ownership from the last update? For some reason my Plex is signed in as my user email instead of the Plexpass email? All the administration are now under my home user (same as the signed in email account) and I cant find a way to swap it back. My friends outside my network have lost access too. 2) Docker seems to be running on host instead of bridged. When I change it to bridged, I cannot access the docker? I surmise its the same cause Tautulli cannot access it. Anyone have any thoughts? Quote Link to comment
Jhp612 Posted April 20, 2020 Share Posted April 20, 2020 I’ve lost access to the UI locally but can access it over the wan. Network still shows host . Strange.... Quote Link to comment
binhex Posted April 20, 2020 Author Share Posted April 20, 2020 17 hours ago, Duggie264 said: Hi, just started getting this crash today, any ideas? 2020-04-19 15:23:48.353687 [info] System information Linux ################# 4.19.107-Unraid #1 SMP Thu Mar 5 13:55:57 PST 2020 x86_64 GNU/Linux 2020-04-19 15:23:48.383161 [info] PUID defined as '99' 2020-04-19 15:23:48.415129 [info] PGID defined as '100' 2020-04-19 15:23:48.918075 [info] UMASK defined as '000' 2020-04-19 15:23:48.945899 [info] Permissions already set for volume mappings 2020-04-19 15:23:48.972882 [warn] TRANS_DIR not defined,(via -e TRANS_DIR), defaulting to '/config/tmp' 2020-04-19 15:23:49.004719 [info] Deleting files in /tmp (non recursive)... 2020-04-19 15:23:49.030933 [info] Starting Supervisor... 2020-04-19 15:23:49,197 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing 2020-04-19 15:23:49,197 INFO Set uid to user 0 succeeded 2020-04-19 15:23:49,199 INFO supervisord started with pid 6 2020-04-19 15:23:49.004719 [info] Deleting files in /tmp (non recursive)... 2020-04-19 15:23:49.030933 [info] Starting Supervisor... 2020-04-19 15:23:49,197 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing 2020-04-19 15:23:49,197 INFO Set uid to user 0 succeeded 2020-04-19 15:23:49,199 INFO supervisord started with pid 6 2020-04-19 15:23:50,202 INFO spawned: 'plexmediaserver' with pid 55 2020-04-19 15:23:50,202 INFO reaped unknown pid 7 2020-04-19 15:23:50,437 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 139734334410080 for <Subprocess at 139734334410224 with name plexmediaserver in state STARTING> (stdout)> 2020-04-19 15:23:50,438 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 139734334410368 for <Subprocess at 139734334410224 with name plexmediaserver in state STARTING> (stderr)> 2020-04-19 15:23:50,438 INFO exited: plexmediaserver (exit status 255; not expected) 2020-04-19 15:23:50,438 DEBG received SIGCHLD indicating a child quit 2020-04-19 15:23:51,441 INFO spawned: 'plexmediaserver' with pid 60 2020-04-19 15:23:51,731 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 139734335288080 for <Subprocess at 139734334410224 with name plexmediaserver in state STARTING> (stdout)> 2020-04-19 15:23:51,731 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 139734333605152 for <Subprocess at 139734334410224 with name plexmediaserver in state STARTING> (stderr)> 2020-04-19 15:23:51,731 INFO exited: plexmediaserver (exit status 255; not expected) 2020-04-19 15:23:51,732 DEBG received SIGCHLD indicating a child quit 2020-04-19 15:23:53,736 INFO spawned: 'plexmediaserver' with pid 65 2020-04-19 15:23:54,021 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 139734334119840 for <Subprocess at 139734334410224 with name plexmediaserver in state STARTING> (stdout)> 2020-04-19 15:23:54,021 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 139734334410368 for <Subprocess at 139734334410224 with name plexmediaserver in state STARTING> (stderr)> 2020-04-19 15:23:54,021 INFO exited: plexmediaserver (exit status 255; not expected) 2020-04-19 15:23:54,021 DEBG received SIGCHLD indicating a child quit 2020-04-19 15:23:54,021 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 139734334119840 for <Subprocess at 139734334410224 with name plexmediaserver in state STARTING> (stdout)> 2020-04-19 15:23:54,021 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 139734334410368 for <Subprocess at 139734334410224 with name plexmediaserver in state STARTING> (stderr)> 2020-04-19 15:23:54,021 INFO exited: plexmediaserver (exit status 255; not expected) 2020-04-19 15:23:54,021 DEBG received SIGCHLD indicating a child quit 2020-04-19 15:23:57,027 INFO spawned: 'plexmediaserver' with pid 70 2020-04-19 15:23:57,323 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 139734335288080 for <Subprocess at 139734334410224 with name plexmediaserver in state STARTING> (stdout)> 2020-04-19 15:23:57,323 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 139734333605056 for <Subprocess at 139734334410224 with name plexmediaserver in state STARTING> (stderr)> 2020-04-19 15:23:57,324 INFO exited: plexmediaserver (exit status 255; not expected) 2020-04-19 15:23:57,324 DEBG received SIGCHLD indicating a child quit 2020-04-19 15:23:58,325 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly 2020-04-19 15:23:58,325 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly make sure its not Q3, if so read on to Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/plex.md Quote Link to comment
binhex Posted April 20, 2020 Author Share Posted April 20, 2020 11 hours ago, Tabraxis said: Docker seems to be running on host instead of bridged. When I change it to bridged, I cannot access the docker? its designed to run in host mode not bridged. Quote Link to comment
Tabraxis Posted April 20, 2020 Share Posted April 20, 2020 5 hours ago, binhex said: its designed to run in host mode not bridged. Ok, noted. Any idea as to why the ownership has changed from the update? Quote Link to comment
binhex Posted April 20, 2020 Author Share Posted April 20, 2020 1 hour ago, Tabraxis said: Ok, noted. Any idea as to why the ownership has changed from the update? no idea on that one, you are best asking on the plex forum and see if they are having any issues with authentication, def nothing that is controlled by this docker image. Quote Link to comment
kavo Posted April 24, 2020 Share Posted April 24, 2020 Is anyone running a DVR post-processing script to re-encode the DVR recordings? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.