Unable to access the plex server / content. Preferences.xml is corrupted.
Sometimes a server hard reset introduce some corruption in the container configuration files.
This is the case for plex which restarted normally but showed a blank page.
A quick look, at the logs to learn that the Preferences.xml file could not be read.
Container is started.
docker psdocker exec -it <container_id> /bin/bashcd /config/Library/Application Support/Plex Media Serverls -lh to check Preferences.xml sizeAfter everything is running again, don't forget to remove the old devices in settings > authorized devices > then filter on server.
error message: Too many packets buffered for output stream 0:1.
solution: add -max_muxing_queue_size 9999 after the ffmepg command somewhere in the faulty plugin
source: https://github.com/HaveAGitGat/Tdarr/issues/101
You need to copy the community plugin to a local plugin and then edit the
local plugin to add the ffmpeg command-line option. Each plugin is
different so the code is slightly different, but all plugins will create a
string for the ffmpeg command-line. Here's an example
from Tdarr_Plugin_MC93_Migz2CleanTitle:
// Convert file if convert variable is set to true.
if (convert === true) {
response.infoLog += '☒File has title metadata. Removing \n';
response.preset = `,${ffmpegCommandInsert} -c copy -map 0
-max_muxing_queue_size 9999`;
response.reQueueAfter = true;
response.processFile = true;
} else {
response.infoLog += '☑File has no title metadata \n';
}
return response;
}
There a command you can run that will take the radarr db and dump it to a text SQL file. Edit the file with vi or whatever and the another command to create a new db from that file.
Process will go something like this. Not sure what the db file is named:
STOP radarr:
echo .dump | sqlite3 nzbdrone.db > nzbdrone.sql
BACKUP DB IMPORTANT IF YOU SCREW IT UP:
mv nzbdrone. nzbdrone.db.backup
Edit/fix the SQL file with text editor of choice. Then restore db from sql file:
sqlite3 -init nzbdrone.sql nzbdrone.db
Start radarr
You'll have to figure out where/what the db file in question is. It's down in the Application Data dir somewhere.