Can0n Posted February 13, 2019 Share Posted February 13, 2019 (edited) 19 hours ago, binhex said: ok this is going to have to go to the plex team for them to fix, i have no idea why there is a reference to jenkins in this but i would say their last build was bad, if i were you i would roll back to the previous build, if you want to know how to do this then follow this Q12 in the following link:- https://forums.unraid.net/topic/44108-support-binhex-general/?tab=comments#comment-433612 ok tried that it broke the image and i can only remove it now...tried tag binhex/plexpass:1.14.1.5488 which is the current non beta version as per the plex official one *edit i see what i did wrong Edited February 13, 2019 by Can0nfan Quote Link to comment
3d24rd0 Posted February 17, 2019 Share Posted February 17, 2019 Hello, in the last week plex is not recognizing me the last episodes, the problem is due to a custom complement to scan anime that was failing concretely in supervisord.log. I found this error: It is possible that in the latest versions the library has been omitted. Is possible include it again? Quote Link to comment
chrissi5120 Posted February 18, 2019 Share Posted February 18, 2019 (edited) Greetings, the last update ruined Transcoding completely: docker logs: Feb 18 20:29:33 storageserver kernel: Plex Transcoder[17238]: segfault at 20 ip 00001545a9bbd126 sp 00007ffe2729d770 error 4 in libavformat.so.58[1545a9b56000+4a9000] plex console: Feb 18, 2019 20:33:16.000 [0x14c09f9fc700] Fehler — [Transcoder] [eac3_eae @ 0x7f5380] EAE timeout! EAE not running, or wrong folder? Could not read '/tmp/pms-130a3668-5040-431d-b66a-de6554188549/EasyAudioEncoder/Convert to WAV (to 8ch or less)/3cczi7tbenbteicmmnzdvm5x_624-0-49.wav' Feb 18, 2019 20:33:16.001 [0x14c0e5dc1700] Fehler — [Transcoder] [eac3_eae @ 0x7f5380] error reading output Feb 18, 2019 20:33:16.002 [0x14c0e4b37700] Fehler — [Transcoder] Error while decoding stream #0:1: Input/output error i tried to use different versions of the container already but the problem persists.. any ideas ? i tried: latest 1.15.0.647-2-01 1.14.1.5488-1-01 edit: tried setting 777 permissions for all files with no luck Edited February 18, 2019 by chrissi5120 additional information Quote Link to comment
Fiala06 Posted February 19, 2019 Share Posted February 19, 2019 So I recently decided to move my plex metadata to its own SSD which isn't in the array since its getting huge. Fix Common Problems started giving me an error: Event: Fix Common Problems - UNRAID Subject: Errors have been found with your server (UNRAID). Description: Investigate at Settings / User Utilities / Fix Common Problems Importance: alert **** Docker application binhex-plexpass has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option **** Now I've done some searching and seems I need to change the access mode for the dir. Unfortunately I can't do that for this dir as there is no edit/options. Any ideas? Quote Link to comment
binhex Posted February 19, 2019 Author Share Posted February 19, 2019 19 minutes ago, Fiala06 said: So I recently decided to move my plex metadata to its own SSD which isn't in the array since its getting huge. Fix Common Problems started giving me an error: Event: Fix Common Problems - UNRAID Subject: Errors have been found with your server (UNRAID). Description: Investigate at Settings / User Utilities / Fix Common Problems Importance: alert **** Docker application binhex-plexpass has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option **** Now I've done some searching and seems I need to change the access mode for the dir. Unfortunately I can't do that for this dir as there is no edit/options. Any ideas? toggle "advanced view" top right Quote Link to comment
Fiala06 Posted February 19, 2019 Share Posted February 19, 2019 3 minutes ago, binhex said: toggle "advanced view" top right Wow.. I feel dumb now. Thanks again! Quote Link to comment
binhex Posted February 19, 2019 Author Share Posted February 19, 2019 On 2/17/2019 at 12:05 AM, 3d24rd0 said: It is possible that in the latest versions the library has been omitted. Is possible include it again? not by me, nope, but i guess potentially it might of been missed/deprecated by the plex team, your best bet is to ask on their support forum. Quote Link to comment
binhex Posted February 19, 2019 Author Share Posted February 19, 2019 19 hours ago, chrissi5120 said: '/tmp/pms-130a3668-5040-431d-b66a-de6554188549/EasyAudioEncoder/Convert to WAV (to 8ch or less)/3cczi7tbenbteicmmnzdvm5x_624-0-49.wav' it looks like you are transcoding to RAM, is that the case?, if so check you arent running out of ram, as a test try switching transcoding back to ssd/hd. Quote Link to comment
chrissi5120 Posted February 21, 2019 Share Posted February 21, 2019 (edited) Feb 21, 2019 20:15:50.638 [0x14b508a37700] Warnung — LongPoll: Got error, closing. Feb 21, 2019 20:15:56.915 [0x14b4f8be5700] Fehler — QueryParser: Invalid field 'onlyTransient' found, ignoring. Feb 21, 2019 20:15:56.918 [0x14b4f8be5700] Fehler — QueryParser: Invalid field 'onlyTransient' found, ignoring. Feb 21, 2019 20:15:56.921 [0x14b4f8be5700] Fehler — QueryParser: Invalid field 'onlyTransient' found, ignoring. Feb 21, 2019 20:15:56.925 [0x14b4f8be5700] Fehler — QueryParser: Invalid field 'onlyTransient' found, ignoring. Feb 21, 2019 20:15:57.429 [0x14b4f9bed700] Fehler — [Transcoder] [dash @ 0x68fb80] Unable to open http://127.0.0.1:32400/video/:/transcode/session/ex2slwcqrdqgn7pdab7xd1qa/1f44db67-46c5-4140-986d-8e3de8efdba9/manifest?X-Plex-Http-Pipeline=infinite for writing Feb 21, 2019 20:15:57.429 [0x14b4f87e3700] Fehler — [Transcoder] av_interleaved_write_frame(): Broken pipe Feb 21, 2019 20:15:57.512 [0x14b4fb1f8700] Warnung — Transcode runner appears to have died. Feb 21, 2019 20:15:57.516 [0x14b4f85e2700] Warnung — Transcode runner appears to have died. Feb 21, 2019 20:15:57.533 [0x14b4f87e3700] Warnung — [CompanionPlayer] We already have a handler, overwriting. Feb 21, 2019 20:16:09.927 [0x14b4f87e3700] Fehler — [FFMPEG] - Cannot load libcuda.so.1 Feb 21, 2019 20:16:09.927 [0x14b4f87e3700] Warnung — avcodec_open2 returned -1313558101 for encoder 'h264_nvenc' Feb 21, 2019 20:16:09.927 [0x14b4f87e3700] Fehler — [FFMPEG] - No VA display found for device: /dev/dri/renderD128. Feb 21, 2019 20:16:09.927 [0x14b4f87e3700] Fehler — [FFMPEG] - Cannot load libcuda.so.1 Feb 21, 2019 20:16:09.927 [0x14b4f87e3700] Warnung — avcodec_open2 returned -1313558101 for encoder 'h264_nvenc' Feb 21, 2019 20:16:09.927 [0x14b4f87e3700] Fehler — [FFMPEG] - No VA display found for device: /dev/dri/renderD128. Feb 21, 2019 20:16:09.928 [0x14b4f87e3700] Fehler — [FFMPEG] - Cannot load libcuda.so.1 Feb 21, 2019 20:16:09.928 [0x14b4f87e3700] Warnung — avcodec_open2 returned -1313558101 for encoder 'h264_nvenc' Feb 21, 2019 20:16:09.928 [0x14b4f87e3700] Fehler — [FFMPEG] - No VA display found for device: /dev/dri/renderD128. Feb 21, 2019 20:16:09.928 [0x14b4f87e3700] Fehler — [FFMPEG] - Cannot load libcuda.so.1 Feb 21, 2019 20:16:09.928 [0x14b4f87e3700] Warnung — avcodec_open2 returned -1313558101 for encoder 'h264_nvenc' Feb 21, 2019 20:16:09.929 [0x14b4f87e3700] Fehler — [FFMPEG] - No VA display found for device: /dev/dri/renderD128. Feb 21, 2019 20:16:09.929 [0x14b4f87e3700] Fehler — [FFMPEG] - Cannot load libcuda.so.1 Feb 21, 2019 20:16:09.929 [0x14b4f87e3700] Warnung — avcodec_open2 returned -1313558101 for encoder 'h264_nvenc' Feb 21, 2019 20:16:09.929 [0x14b4f87e3700] Fehler — [FFMPEG] - No VA display found for device: /dev/dri/renderD128. Feb 21, 2019 20:16:09.930 [0x14b4f87e3700] Fehler — [FFMPEG] - Cannot load libcuda.so.1 Feb 21, 2019 20:16:09.930 [0x14b4f87e3700] Warnung — avcodec_open2 returned -1313558101 for encoder 'h264_nvenc' Feb 21, 2019 20:16:09.930 [0x14b4f87e3700] Fehler — [FFMPEG] - No VA display found for device: /dev/dri/renderD128. Feb 21, 2019 20:16:12.354 [0x14b508635700] Fehler — [Transcoder] [dash @ 0x690fc0] Unable to open http://127.0.0.1:32400/video/:/transcode/session/ctk8seunc6cf3eif9iqc9cm7/664430a9-d468-47ed-aefd-43fdd7bb9f12/manifest?X-Plex-Http-Pipeline=infinite for writing Feb 21, 2019 20:16:12.354 [0x14b4f87e3700] Fehler — [Transcoder] av_interleaved_write_frame(): Broken pipe Feb 21, 2019 20:16:12.422 [0x14b4f85e2700] Warnung — Transcode runner appears to have died. Feb 21, 2019 20:16:12.425 [0x14b4f9bed700] Warnung — Transcode runner appears to have died. I was transcoding to RAM all the time, no issues the last update broke everything.. i tried to set transcoding dir back to SSD with no success, same log output Edited February 21, 2019 by chrissi5120 Quote Link to comment
DannyG Posted February 22, 2019 Share Posted February 22, 2019 Hi guys, I've been running unraid for the past 3 months, and so far I've been loving it. Yesterday I ran into my first issue. I can't connect to my plex server. My Logs say the following: 2019-02-22 08:14:50.091360 [info] System information Linux UnRaidServer 4.18.20-unRAID #1 SMP Fri Nov 23 11:38:16 PST 2018 x86_64 GNU/Linux 2019-02-22 08:14:50.122694 [info] PUID defined as '99' 2019-02-22 08:14:50.267939 [info] PGID defined as '100' 2019-02-22 08:14:50.408576 [info] UMASK defined as '000' 2019-02-22 08:14:50.441054 [info] Permissions already set for volume mappings 2019-02-22 08:14:50.471165 [info] TRANS_DIR defined as '/config/transcode' 2019-02-22 08:14:50.561746 [info] Starting Supervisor... 2019-02-22 08:14:51,011 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing 2019-02-22 08:14:51,012 INFO Set uid to user 0 succeeded 2019-02-22 08:14:51,014 INFO supervisord started with pid 8 2019-02-22 08:14:52,016 INFO spawned: 'plexmediaserver' with pid 54 2019-02-22 08:14:52,017 INFO reaped unknown pid 9 2019-02-22 08:14:52,119 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23029063375328 for <Subprocess at 23029063375256 with name plexmediaserver in state STARTING> (stdout)> 2019-02-22 08:14:52,119 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23029063375616 for <Subprocess at 23029063375256 with name plexmediaserver in state STARTING> (stderr)> 2019-02-22 08:14:52,119 INFO exited: plexmediaserver (exit status 255; not expected) 2019-02-22 08:14:52,119 DEBG received SIGCLD indicating a child quit 2019-02-22 08:14:53,122 INFO spawned: 'plexmediaserver' with pid 59 2019-02-22 08:14:53,159 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23029063375832 for <Subprocess at 23029063375256 with name plexmediaserver in state STARTING> (stdout)> 2019-02-22 08:14:53,159 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23029063375904 for <Subprocess at 23029063375256 with name plexmediaserver in state STARTING> (stderr)> 2019-02-22 08:14:53,159 INFO exited: plexmediaserver (exit status 255; not expected) 2019-02-22 08:14:53,159 DEBG received SIGCLD indicating a child quit 2019-02-22 08:14:55,162 INFO spawned: 'plexmediaserver' with pid 64 2019-02-22 08:14:55,199 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23029063376120 for <Subprocess at 23029063375256 with name plexmediaserver in state STARTING> (stdout)> 2019-02-22 08:14:55,199 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23029063375616 for <Subprocess at 23029063375256 with name plexmediaserver in state STARTING> (stderr)> 2019-02-22 08:14:55,199 INFO exited: plexmediaserver (exit status 255; not expected) 2019-02-22 08:14:55,199 DEBG received SIGCLD indicating a child quit 2019-02-22 08:14:58,203 INFO spawned: 'plexmediaserver' with pid 69 2019-02-22 08:14:58,240 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23029063376192 for <Subprocess at 23029063375256 with name plexmediaserver in state STARTING> (stdout)> 2019-02-22 08:14:58,240 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23029063375904 for <Subprocess at 23029063375256 with name plexmediaserver in state STARTING> (stderr)> 2019-02-22 08:14:58,240 INFO exited: plexmediaserver (exit status 255; not expected) 2019-02-22 08:14:58,240 DEBG received SIGCLD indicating a child quit 2019-02-22 08:14:59,241 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly Here are my configs: The only change I did that's related was I installed Tautuli, which installed correctly. any help would be greatly appreciated! Dan Quote Link to comment
tazire Posted February 23, 2019 Share Posted February 23, 2019 I'm starting to run into a strange issue. I can no longer play media on the Web browser. I haven't tested this fully as I'm not at home. But I literally went through a big upgrade. Now a Ryzen 7 1700 with 32gb of ram and a p4000 I have the whole lot up and running and the transcoding works as best it can using the p4000. But when I try play anything with the we player I get this error in the logs. usr/lib/plexmediaserver/Plex DLNA Server: relocation error: /usr/lib64/libssl.so.1.0.0: symbol ENGINE_init version OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 with link time reference Just FYI I have changed from transcoding to an SSD to ram. I'm not sure if that has anything to do with it. Sorry I'm not at home to give full logs right now. Quote Link to comment
mdipinto Posted February 24, 2019 Share Posted February 24, 2019 I'm not completely sure if this is something about the docker or a personal problem. In the plex web client, under settings - general it says that it's version 3.83.1 and I'm not sure how that goes in comparison with Windows and other Linux build versions. But I'm trying to upload my phone's camera roll to my server tho plex. It seems to upload all the pictures no problem, but the videos(i took a few quick videos and clicked to sync) doesn't seem to be uploading, it showed to be uploading the 3 new videos uploading, and it finished rather quick, but none of the videos were actually uploaded(checked the destination folder). I looked in the Plex forums to make sure, and it seems that by now it should of been uploading videos and showing them on the photo library. Anyone has any input about this? Quote Link to comment
bshep Posted February 25, 2019 Share Posted February 25, 2019 On 2/23/2019 at 11:14 AM, tazire said: I'm starting to run into a strange issue. I can no longer play media on the Web browser. I haven't tested this fully as I'm not at home. But I literally went through a big upgrade. Now a Ryzen 7 1700 with 32gb of ram and a p4000 I have the whole lot up and running and the transcoding works as best it can using the p4000. But when I try play anything with the we player I get this error in the logs. usr/lib/plexmediaserver/Plex DLNA Server: relocation error: /usr/lib64/libssl.so.1.0.0: symbol ENGINE_init version OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 with link time reference Just FYI I have changed from transcoding to an SSD to ram. I'm not sure if that has anything to do with it. Sorry I'm not at home to give full logs right now. i had a similar issue dowgraded from latest to version below: binhex/arch-plexpass:1.14.1.5488-1-01 thats the most recent build that works for me Quote Link to comment
BBLV Posted February 26, 2019 Share Posted February 26, 2019 I just started getting an odd error when trying to start playing a new video, happening on both AppleTV (transcoding) and Nvidia Shield (direct play): "Playback was terminated by the server. Not enough disk space to convert this item." Any thoughts? I tried restarting the docker and it just hung on me. Had to restart the server to get the spinning green arrows to clear to a red square. There's an update for my PlexPass Docker available, but that's also hanging on install right now... Quote Link to comment
Rhynri Posted February 26, 2019 Share Posted February 26, 2019 (edited) The latest Plex container would not scan for, nor detect changes to, my library items. Manual scans would immediately terminate, and manual scanning was not required prior to the latest un-tagged versions. Rolling back to 1.14.1.5488-1-01 immediately rectified the problem and found the library items I've added since updating to the 'latest' version. I'm available for debugging purposes if you are interested @binhex. Judging by responses on the official Plex forums this may be an issue in the official release, but most of the threads I'm finding are referencing the Mac OSX version. Edit: Your container has been excellent one for many moons for me though. Just wanted to give my praise as well. Edited February 26, 2019 by Rhynri <3 Quote Link to comment
binhex Posted February 26, 2019 Author Share Posted February 26, 2019 1 hour ago, Rhynri said: The latest Plex container would not scan for, nor detect changes to, my library items. Manual scans would immediately terminate, and manual scanning was not required prior to the latest un-tagged versions. Rolling back to 1.14.1.5488-1-01 immediately rectified the problem and found the library items I've added since updating to the 'latest' version. I'm available for debugging purposes if you are interested @binhex. Judging by responses on the official Plex forums this may be an issue in the official release, but most of the threads I'm finding are referencing the Mac OSX version. Edit: Your container has been excellent one for many moons for me though. Just wanted to give my praise as well. ok so there are two changes that have happened, firstly a base image bump, this updates packages included in the base image, and secondly obviously plex pass. so to rule out the base being the issue i just built a test tagged image with the newer base and the older working version of plex, added a movie, noticed it scanned in fine, deleted the movie, noticed it got removed from plex, no crashes that i can see. so this does look to be a plex pass issue (at the end of the day plex pass = plex beta) so this will have to be resolved by the plex team, nothing further i can do im afraid at this point. Quote Link to comment
Rhynri Posted February 26, 2019 Share Posted February 26, 2019 51 minutes ago, binhex said: so this does look to be a plex pass issue (at the end of the day plex pass = plex beta) so this will have to be resolved by the plex team, nothing further i can do im afraid at this point. Firstly, thank you for your response. Second, I appreciate the education; I wasn't aware plex pass was a form of beta, but that makes sense now that you've said it. I'll see what I can do through official channels, but thank you again for your time and providing this great container in the first place. Quote Link to comment
DJ Callyman Posted February 27, 2019 Share Posted February 27, 2019 8 hours ago, Rhynri said: The latest Plex container would not scan for, nor detect changes to, my library items. Manual scans would immediately terminate, and manual scanning was not required prior to the latest un-tagged versions. Rolling back to 1.14.1.5488-1-01 immediately rectified the problem and found the library items I've added since updating to the 'latest' version. I'm available for debugging purposes if you are interested @binhex. Judging by responses on the official Plex forums this may be an issue in the official release, but most of the threads I'm finding are referencing the Mac OSX version. Edit: Your container has been excellent one for many moons for me though. Just wanted to give my praise as well. I'm having this very issue. Have tried rolling back a few versions and can't get my media libraries to update. Any ideas on how to deal with this while we what for Plex to sort it out? Quote Link to comment
binhex Posted February 27, 2019 Author Share Posted February 27, 2019 7 hours ago, DJ Callyman said: I'm having this very issue. Have tried rolling back a few versions and can't get my media libraries to update. Any ideas on how to deal with this while we what for Plex to sort it out? you will need to go back to this tag "1.14.1.5488-1-01", if you dont know how to do that then check Q12 in the following link:- https://forums.unraid.net/topic/44108-support-binhex-general/?tab=comments#comment-433612 Quote Link to comment
BBLV Posted February 28, 2019 Share Posted February 28, 2019 I still haven't been able to get my Plex docker back up and running. Tried removing it again and re-adding, but now it doesn't even finish the download and gives me this error: "Error: failed to register layer: ApplyLayer exit status 1 stdout: stderr: archive/tar: invalid tar header". In addition, my binhex DelugeVPN docker won't start up now. Something must be related, but I have no idea where to start. I'm getting so frustrated at the constant problems with this unRAID setup.... PLEASE HELP Quote Link to comment
binhex Posted February 28, 2019 Author Share Posted February 28, 2019 12 hours ago, BBLV said: I still haven't been able to get my Plex docker back up and running. Tried removing it again and re-adding, but now it doesn't even finish the download and gives me this error: "Error: failed to register layer: ApplyLayer exit status 1 stdout: stderr: archive/tar: invalid tar header". In addition, my binhex DelugeVPN docker won't start up now. Something must be related, but I have no idea where to start. I'm getting so frustrated at the constant problems with this unRAID setup.... PLEASE HELP this sounds like your docker image file is full, go to the dashboard and check the percentage utilisation shown for the "flash log docker" (3rd bar), i would assume it will be close to 100% thus stopping you downloading/starting any containers. Quote Link to comment
binhex Posted March 1, 2019 Author Share Posted March 1, 2019 (edited) other people with plex pass issues - comforting for me that its not something related to the docker image ive built, not so comforting for those who have plex natively installed and cant roll back easily:- https://www.reddit.com/r/PleX/comments/auo6jd/new_beta_pms_version_available_1151710ece95b3a1/ Edited March 1, 2019 by binhex 2 Quote Link to comment
Rhynri Posted March 1, 2019 Share Posted March 1, 2019 1 minute ago, binhex said: comforting for me that its not something related to the docker image I've built, not so comforting for those who have plex natively installed and cant roll back easily:- https://www.reddit.com/r/PleX/comments/auo6jd/new_beta_pms_version_available_1151710ece95b3a1/ Ouch. Yeah, I'm very happy with your docker image and knowing we can roll back easily is just icing on the cake. 1 Quote Link to comment
mdipinto Posted March 1, 2019 Share Posted March 1, 2019 Anyone using the camera upload feature? I been trying to to get it to upload the videos, tried 3 phone (2 Android and 1 iPhone). All the same, only uploads the pictures. Quote Link to comment
Fredrick Posted March 2, 2019 Share Posted March 2, 2019 Access to my server via apps (Android, Libreelec) are somehow gone and I cant figure out what I can do to fix it. I can access the server fine through webui, both local and WAN. The server has green checkmark under network. I cant see anything in the log for the container, and not sure where the logs are for Android app. Maybe I could get a log for libreelec? I've tried disabling SSL on the server to rule that out, I've tried downgrading PMS and I've tried rebooting pretty much everything multiple times. Any ideas? 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.