July 20, 20232 yr On 7/18/2023 at 9:54 AM, binhex said: I'm on 6.11.5 Just to let you know, everything is working as expected, was a simple configuration issue.
July 20, 20232 yr Author Just now, ich777 said: Just to let you know, everything is working as expected, was a simple configuration issue. Ah cheers ich777, a good end result 🙂
August 5, 20232 yr Having issues with my Plex server all of a sudden. I left for vacation 2 days ago and everything was working fine. Even streamed a couple of shows and it worked perfectly. I come home and fire up the tv and go to start a TV Show and get the error "couldn't retrieve the play queue for this item. Please try again." It only does this on TV Shows. My Movies folder is working just fine. Running latest version of the docker container and latest version of Unraid. Literally nothing has changed, it just stopped working. I tried rolling back to older versions of the docker and I tried rebooting the server. Still nothing. In the logs I show a libusb_init failed under critical warnings. That's the only error I'm seeing. Edited August 5, 20232 yr by hahler2
August 5, 20232 yr Author 6 hours ago, hahler2 said: In the logs I show a libusb_init failed under critical warnings. yeah ignore this, its of no consequence, lets check for database corruption, see Q4 (yes i know plex is starting but lets rule it out):- https://github.com/binhex/documentation/blob/master/docker/faq/plex.md
August 5, 20232 yr Ok so I show multiple errors. And yes some of them say database corruption. Look like this Aug 05, 2023 04:38:07.995 [23069527477048] ERROR - SQLITE3:0x80000001, 11, database corruption at line 59420 of [a29f994989]
August 5, 20232 yr Fixed. I rolled back to a database from a week ago. Thank you for pointing me in the right direction.
August 25, 20232 yr Went to watch a little Plex and found the server to be unavailable. Checked Unraid, and Plex service stopped. Tried to start it, but got a SERVER ERROR message. Latest red entries from log file shown below. OSError: [Errno 5] Input/output error 2023-08-23 02:24:38,120 CRIT uncaptured python exception, closing channel <POutputDispatcher at 22663105671696 for <Subprocess at 22663099747408 with name plexmediaserver in state RUNNING> (stderr)> (<class 'OSError'>:[Errno 5] Input/output error [/usr/lib/python3.11/site-packages/supervisor/supervisord.py|runforever|218] [/usr/lib/python3.11/site-packages/supervisor/dispatchers.py|handle_read_event|276] [/usr/lib/python3.11/site-packages/supervisor/dispatchers.py|record_output|210] [/usr/lib/python3.11/site-packages/supervisor/dispatchers.py|_log|189] [/usr/lib/python3.11/site-packages/supervisor/loggers.py|log|345] [/usr/lib/python3.11/site-packages/supervisor/loggers.py|emit|227] [/usr/lib/python3.11/site-packages/supervisor/loggers.py|doRollover|264]) Any troubleshooting advice would be appreciated. Thanks.
August 25, 20232 yr 24 minutes ago, propman07 said: Went to watch a little Plex and found the server to be unavailable. Checked Unraid, and Plex service stopped. Tried to start it, but got a SERVER ERROR message. Latest red entries from log file shown below. OSError: [Errno 5] Input/output error 2023-08-23 02:24:38,120 CRIT uncaptured python exception, closing channel <POutputDispatcher at 22663105671696 for <Subprocess at 22663099747408 with name plexmediaserver in state RUNNING> (stderr)> (<class 'OSError'>:[Errno 5] Input/output error [/usr/lib/python3.11/site-packages/supervisor/supervisord.py|runforever|218] [/usr/lib/python3.11/site-packages/supervisor/dispatchers.py|handle_read_event|276] [/usr/lib/python3.11/site-packages/supervisor/dispatchers.py|record_output|210] [/usr/lib/python3.11/site-packages/supervisor/dispatchers.py|_log|189] [/usr/lib/python3.11/site-packages/supervisor/loggers.py|log|345] [/usr/lib/python3.11/site-packages/supervisor/loggers.py|emit|227] [/usr/lib/python3.11/site-packages/supervisor/loggers.py|doRollover|264]) Any troubleshooting advice would be appreciated. Thanks. Looks like the cache drive I was using for Plex has failed...here are some of the log entries for that drive: Aug 23 02:05:05 XXXTOWER kernel: XFS (sde1): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0x1e68a1f0 len 32 error 5 Aug 23 02:06:08 XXXTOWER kernel: ata4.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x0 Aug 23 02:06:08 XXXTOWER kernel: ata4.00: irq_stat 0x40000008 Aug 23 02:06:08 XXXTOWER kernel: ata4.00: failed command: READ FPDMA QUEUED Aug 23 02:06:08 XXXTOWER kernel: ata4.00: cmd 60/20:08:30:a2:68/00:00:1e:00:00/40 tag 1 ncq dma 16384 in Aug 23 02:06:08 XXXTOWER kernel: ata4.00: status: { DRDY ERR } Aug 23 02:06:08 XXXTOWER kernel: ata4.00: error: { UNC } Aug 23 02:06:08 XXXTOWER kernel: ata4.00: configured for UDMA/133 Aug 23 02:06:08 XXXTOWER kernel: sd 4:0:0:0: [sde] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s Aug 23 02:06:08 XXXTOWER kernel: sd 4:0:0:0: [sde] tag#1 Sense Key : 0x3 [current] Aug 23 02:06:08 XXXTOWER kernel: sd 4:0:0:0: [sde] tag#1 ASC=0x11 ASCQ=0x4 Aug 23 02:06:08 XXXTOWER kernel: sd 4:0:0:0: [sde] tag#1 CDB: opcode=0x28 28 00 1e 68 a2 30 00 00 20 00 Aug 23 02:06:08 XXXTOWER kernel: blk_update_request: I/O error, dev sde, sector 510173744 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0 Aug 23 02:06:08 XXXTOWER kernel: ata4: EH complete Aug 23 02:06:08 XXXTOWER kernel: XFS (sde1): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0x1e68a1f0 len 32 error 5 Aug 23 02:06:08 XXXTOWER kernel: XFS (sde1): xfs_do_force_shutdown(0x1) called from line 296 of file fs/xfs/xfs_trans_buf.c. Return address = 00000000814715b6 Aug 23 02:06:08 XXXTOWER kernel: XFS (sde1): I/O Error Detected. Shutting down filesystem Aug 23 02:06:08 XXXTOWER kernel: XFS (sde1): Please unmount the filesystem and rectify the problem(s) New drive on order....now if I could only remember how I set up Plex to use the cache drive.....and I assume that all of the images that were on the drive will now need to be re-created.... Edited August 25, 20232 yr by propman07
August 26, 20232 yr Very confused. Tonight I changed from Google Wifi (192.168.86.x) to a Ubiquiti Dream Machine Pro setup (192.168.1.x) and I cannot access binhex-plex. Clicking WebGUI in unRAID goes to the proper address of 192.168.1.174:32400, and double checked that the container config has this WebGUI parameter: http://[IP]:[PORT:32400]/web/index.html My other containers on .174:[port] are working properly. Getting this msg in container log: 2023-08-25 23:43:31,634 INFO reaped unknown pid 14 (exit status 0) 2023-08-25 23:43:31,824 DEBG 'plexmediaserver' stderr output: Failed to load preferences at /config/Plex Media Server/Preferences.xml 2023-08-25 23:43:32,825 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-08-25 23:43:33,824 DEBG 'plexmediaserver' stderr output: Failed to load preferences at /config/Plex Media Server/Preferences.xml Related or unrelated? note: I checked this Preferences.xml file and it is 0 byte empty. Edit: It's fixed....uhm....how weird. I deleted that 0b Preferences file and restarted the container, and now it's OK. Edited August 26, 20232 yr by Sanborn
August 26, 20232 yr On the 15 August 2023, I was able to track down the date that my library quit updating. looking at logs, Unraid 6.12.3 binhex plex docker, i was able to find the date. getting Critical: libusb_init failed. I have no usb devices associated with plex. I have shares setup in unraid that are local to array, plex app date folder on ssd drive. plex is working other than that that i can tell edit: looking through plex logs found this when scanning new movies: Caught exception while scanning Movies: sqlite3_statement_backend::loadOne: database disk image is malformed Edited August 26, 20232 yr by tank101
September 3, 20232 yr On 5/26/2023 at 9:19 AM, EvilTiger said: I just posted what appears to be the same issue with the "latest" tag docker image. Sorry for reposting, i didnt see this post prior to submitting mine. I've been able to workaround it by doing the same as you, using a specific version tag and not grabbing the latest version of the docker image. Following this thread now as well as mine ... Best regards, -Tiger 023-09-03 23:31:42,563 DEBG 'plexmediaserver' stdout output: No data written! 2023-09-03 23:31:49,111 DEBG 'plexmediaserver' stdout output: No data written! 2023-09-03 23:31:55,383 DEBG 'plexmediaserver' stdout output: No data written! 2023-09-03 23:32:02,289 DEBG 'plexmediaserver' stdout output: No data written! 2023-09-03 23:32:09,049 DEBG 'plexmediaserver' stdout output: No data written! 2023-09-03 23:32:15,327 DEBG 'plexmediaserver' stdout output: No data written! 2023-09-03 23:32:22,548 DEBG 'plexmediaserver' stdout output: I am getting this, latest version. I have it steup like this: I used the command to create the virtual ram disk etc for transcoding. in the plex app I have /transcode. I have tried using just an external SSD, or direct to ram, and I still get this, it thinks the transcoding location is full. I have actually tried the linuxserv.io and hotio containers and now this one, I get the problem on all. restarting the container fixes it again until it thinks the transcode location gets full. More than enough RAM for it, and the HDD locations do not get anywhere full if I use them. help please!
September 17, 20232 yr Latest Plex release broke hw transcoding (tone mapping) and in my case also PlexKodiConnect's ability to direct play. Are you considering downgrading to latest working release like some other docker publishers have done?
September 26, 20232 yr I am trying to repair a corrupt database on the latest version of Binhex-plex. 1. I am unable to stop plex from running inside the docker container. 2. I am not sure which file is the actual database. I am attempting to use https://github.com/ChuckPa/PlexDBRepair but I need to manually stop plex. I am newish to unraid and could use a little help. Thanks <a target="_blank" href="https://imageupload.io/kfoIuU1HTgiqkSd"><img src="https://imageupload.io/ib/uMNXNEaiiMKLKpL_1695770803.jpg" alt="Screenshot_20230926_190932_nzb360.jpg"/></a>
September 27, 20232 yr Author 12 hours ago, Coolin72 said: I am trying to repair a corrupt database on the latest version of Binhex-plex. 1. I am unable to stop plex from running inside the docker container. 2. I am not sure which file is the actual database. I am attempting to use https://github.com/ChuckPa/PlexDBRepair but I need to manually stop plex. I am newish to unraid and could use a little help. Thanks <a target="_blank" href="https://imageupload.io/kfoIuU1HTgiqkSd"><img src="https://imageupload.io/ib/uMNXNEaiiMKLKpL_1695770803.jpg" alt="Screenshot_20230926_190932_nzb360.jpg"/></a> you can give my repair script a run, see this post:- https://forums.unraid.net/topic/44142-support-binhex-plex-pass/?do=findComment&comment=1286021
October 30, 20232 yr On 9/4/2023 at 6:55 AM, sunwind said: 023-09-03 23:31:42,563 DEBG 'plexmediaserver' stdout output: No data written! 2023-09-03 23:31:49,111 DEBG 'plexmediaserver' stdout output: No data written! 2023-09-03 23:31:55,383 DEBG 'plexmediaserver' stdout output: No data written! 2023-09-03 23:32:02,289 DEBG 'plexmediaserver' stdout output: No data written! 2023-09-03 23:32:09,049 DEBG 'plexmediaserver' stdout output: No data written! 2023-09-03 23:32:15,327 DEBG 'plexmediaserver' stdout output: No data written! 2023-09-03 23:32:22,548 DEBG 'plexmediaserver' stdout output: I am getting this, latest version. I have it steup like this: I used the command to create the virtual ram disk etc for transcoding. in the plex app I have /transcode. I have tried using just an external SSD, or direct to ram, and I still get this, it thinks the transcoding location is full. I have actually tried the linuxserv.io and hotio containers and now this one, I get the problem on all. restarting the container fixes it again until it thinks the transcode location gets full. More than enough RAM for it, and the HDD locations do not get anywhere full if I use them. help please! same problem, Do you find any solution?
November 10, 20232 yr I am doing a little "house keeping" its been a long time since I setup my shares etc. Just for simplicity sake I wanted to change a few things around. My host path is /mnt/user/ Will I run into any issues if I want to set a new path that is /mnt/user/media then pop all of my folders into that one folder then change directories in binhex-plex config accordingly?
November 11, 20232 yr 1 hour ago, z0ki said: Will I run into any issues if I want to set a new path that is /mnt/user/media then pop all of my folders into that one folder then change directories in binhex-plex config accordingly? The should not cause any issues. I take it one step further. I have a share for each media type so my host paths are mnt/user/movies, mount/user/photos, mount/user/tv, etc. Of course, this requires a host path --> container path mapping for each share/media type. In the case you presented, you could have just one host--->container mapping like /mnt/user/media-->/media and then in Plex your library mappings would be /media/[media type folder name] e.g. /media/movies for movie content.
November 11, 20232 yr 1 hour ago, Hoopster said: The should not cause any issues. I take it one step further. I have a share for each media type so my host paths are mnt/user/movies, mount/user/photos, mount/user/tv, etc. Of course, this requires a host path --> container path mapping for each share/media type. In the case you presented, you could have just one host--->container mapping like /mnt/user/media-->/media and then in Plex your library mappings would be /media/[media type folder name] e.g. /media/movies for movie content. Perfect. Makes sense. thanks for that. I'll note my original paths down in case something goes pear shaped lol
November 12, 20232 yr Hi if I swap from binhex-pluspass to binhex-plex can I just point to the same 'app folder location' or will this fuck the library up? Thanks
November 26, 20232 yr EDIT: Corrupt DB rolled back to last back up and let PLEX rebuild. All is good. Any help with this would be appreciated. Everything has been running fine, no changes to the server or updates that I know of. The library will not update and I get this error. 2023-11-26 02:14:35,830 DEBG 'plexmediaserver' stderr output: ****** PLEX MEDIA SCANNER CRASHED, CRASH REPORT WRITTEN: /config/Plex Media Server/Crash Reports/1.32.7.7621-871adbd44/PLEX MEDIA SCANNER/b6a0bd04-7c62-42d5-2c0bfca1-74dfd278.dmp Log file attached b6a0bd04-7c62-42d5-2c0bfca1-74dfd278.dmp.log Edited November 26, 20232 yr by Juscuz17
November 28, 20232 yr On 10/30/2023 at 3:59 AM, danieland said: same problem, Do you find any solution? It eventually just went away. I am using /tmp for my transcode now and it's fine.
December 7, 20232 yr Anyone have any advice on how to enable Nvdia gpu transcode on plex in in this container? All the resources I can find reference linuxserver's image, which has different variables in the template. I have included --runtime=nvidia in extra parameters. can I just create the additional variables in the template for gpuid etc? Will that just work? Edited December 7, 20232 yr by ImBadAtThis
December 7, 20232 yr Author 14 minutes ago, ImBadAtThis said: Anyone have any advice on how to enable Nvdia gpu transcode on plex in in this container? All the resources I can find reference linuxserver's image, which has different variables in the template. I have included --runtime=nvidia in extra parameters. can I just create the additional variables in the template for gpuid etc? Will that just work? Q3:- https://github.com/binhex/documentation/blob/master/docker/faq/plex.md
December 28, 20232 yr Hey guys, i'm planning the following migration scenario from my debian/OMV with Plex (1.9.4.4325) to Unraid with latest binhex-plex. Sadly i'm unable to update my actual Plex version before migration. My Plex userdata is quite huge (metadata, collections, cover, etc.) Unraid, docker and binhex-plex are new to me, but from what i read until now here are my thoughts: - installing unraid - installing binhex-plex with tag "1.9.4.4325" to get my old Plex version running in the docker environment - migrate the plex data folders from the old to the new server - updating binhex-plex with tag "latest" Is that possible? Did i miss something? I'm uncertain if Plex is able to update from 1.9.4.4325 to the latest version in one step (at least around 6 years of development in between). Will the binhex-plex docker automatically start update scripts when running the latest version for the first time? Thanks!
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.