sauso

Found a weird little bug that made for some interesting troubleshooting. I created a script with an exclamation point at the start. User scripts did not like this. Started throwing errors in the console. wouldn't allow me to delete so I removed from console. Lesson learnt, don't start scripts with a !

This has nothing to do with mono. must be your config. The reason i needed mono updated was because i use rclone in a merge and it was downloading items from google when i tried to set the air date. New version of mono stops that.

Legend as always!

Hey @binhex. Any chance you can upgrade Mono in Sonarr as well. Working a treat for Radarr. Just realised Sonarr is also having issues.

Just a follow up that Binhex has updated the base image to include the latest version of Mono. Issue is resolved.

Legend. Will buy you a Coffee

Guys thought I might post a problem I was having. I spun up a GCP server to download some backlog content quickly. Basically i wrote SAB post processing script to upload the file to my gdrive downloads directory. As the gdrive is part of my mergerfs location locally it should just move to the correct folder and rename. Well this wasn't happening for some reason. Turns out the version of Mono that binhex-radarr is using is 6.4 which has a bug that prevents renaming and moving. What it was doing was downloading each file locally rather than keeping it in the mount. (not ideal if you are downloading old content and want to download it direct to cloud) Upgrading Mono in the binhex-radarr fixed it and it now works a treat. I've asked binhex if we can upgrade mono in the container so this works correctly.

Hey @binhex, I'm having an issue with the version of Mono installed in the container. When i try and rename movies on my g drive mount it downloads them locally rather than doing a rename. If i rename the file in the container console it works perfectly. I upgraded Mono in the container to 6.10 and that fixes the issue. Any chance this can be updated in the dcoker image? Thanks, Sauso

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.

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.

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.

Actually this could be it. https://forums.plex.tv/t/1-19-1-2589-not-working-on-freenas-after-upgrade/565650

https://forums.plex.tv/t/libraries-and-settings-gone-after-upgrade-to-1-19/566527/18 This might possibly be the reason.

Will give that a shot

I should add. If i pull the updated container and use a fresh DB it works fine. It just corrupts with my existing install.