hello everyone,
so after an abrupt shutdown caused power outage, the server now is unavailable after starting the docker.
how to get the one (top with lists of libraries) running again?
Server Version#: 1.41.9.9961-46083195d
Player Version#: 4.148.0
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>
The database may have been corrupted so I would try to restore a database backup
To add to Bigwheel,
The server can also become unclaimed.
Look at Preferences.xml. Confirm it’s not zero length / chopped.
Before restoring a database, I would look at the Plex Media Server.log and see if it states the DB is “malformed”
unfortunately, tried this just now and there’s no change at all.
the Preferences.xml file is indeed zero length, but nothing in the log states db is malformed.
I need you to open the terminal / console,
go to where you mapped /config into the filesystem,
drill down into Plex’s data until you find the “Logs” directory.
Now make a tar.gz of the “Logs” directory and attach it here.
here you go
Logs.tar.gz (2.0 MB)
DNS lookup failures
Mar 05, 2025 14:45:40.403 [22674155715384] WARN - [HttpClient/HCl#19cb] HTTP error requesting GET undefined (6, Couldn't resolve host name) (Could not resolve host: undefined)
Mar 05, 2025 14:45:40.545 [22674155715384] WARN - [HttpClient/HCl#19cd] HTTP error requesting GET undefined (6, Couldn't resolve host name) (Could not resolve host: undefined)
Mar 05, 2025 14:45:40.832 [22674155715384] WARN - [HttpClient/HCl#19ce] HTTP error requesting GET undefined (6, Couldn't resolve host name) (Could not resolve host: undefined)
Mar 05, 2025 14:45:50.522 [22674155715384] WARN - [HttpClient/HCl#19cf] HTTP error requesting GET undefined (6, Couldn't resolve host name) (Could not resolve host: undefined)
Mar 05, 2025 14:45:50.533 [22674155715384] WARN - [HttpClient/HCl#19d0] HTTP error requesting GET undefined (6, Couldn't resolve host name) (Could not resolve host: undefined)
Mar 05, 2025 14:45:50.534 [22674155715384] WARN - [HttpClient/HCl#19d1] HTTP error requesting GET undefined (6, Couldn't resolve host name) (Could not resolve host: undefined)
Mar 05, 2025 14:45:50.597 [22674155715384] WARN - [HttpClient/HCl#19d2] HTTP error requesting GET undefined (6, Couldn't resolve host name) (Could not resolve host: undefined)
Mar 05, 2025 14:45:50.597 [22674155715384] WARN - [HttpClient/HCl#19d3] HTTP error requesting GET undefined (6, Couldn't resolve host name) (Could not resolve host: undefined)
Mar 05, 2025 14:45:50.598 [22674155715384] WARN - [HttpClient/HCl#19d4] HTTP error requesting GET undefined (6, Couldn't resolve host name) (Could not resolve host: undefined)
I cannot tell if Preferences.xml is ok or not due to DNS failures.
This is a damaged DB
Apr 04, 2025 02:04:40.955 [23191689272120] INFO - [Database optimization/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 17, statement aborts at 60: [select * from metadata_items limit 1] database schema has changed
Apr 04, 2025 02:04:40.957 [23191689272120] INFO - [Database optimization/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 17, statement aborts at 60: [select * from metadata_items limit 1] database schema has changed
Apr 04, 2025 02:04:40.958 [23191689272120] INFO - [Database optimization/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 17, statement aborts at 60: [select * from metadata_items limit 1] database schema has changed
Apr 04, 2025 02:04:40.960 [23191689272120] INFO - [Database optimization/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 17, statement aborts at 60: [select * from metadata_items limit 1] database schema has changed
Apr 04, 2025 02:04:40.962 [23191689272120] INFO - [Database optimization/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 17, statement aborts at 60: [select * from metadata_items limit 1] database schema has changed
Apr 04, 2025 02:04:40.964 [23191689272120] INFO - [Database optimization/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 17, statement aborts at 60: [select * from metadata_items limit 1] database schema has changed
Apr 04, 2025 02:04:40.965 [23191689272120] INFO - [Database optimization/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 17, statement aborts at 60: [select * from metadata_items limit 1] database schema has changed
Apr 04, 2025 02:04:40.967 [23191689272120] INFO - [Database optimization/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 17, statement aborts at 60: [select * from metadata_items limit 1] database schema has changed
Apr 04, 2025 02:04:40.969 [23191689272120] INFO - [Database optimization/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 17, statement aborts at 60: [select * from metadata_items limit 1] database schema has changed
Apr 04, 2025 02:04:40.970 [23191689272120] INFO - [Database optimization/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 17, statement aborts at 60: [select * from metadata_items limit 1] database schema has changed
Apr 04, 2025 02:04:40.972 [23191689272120] INFO - [Database optimization/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 17, statement aborts at 60: [select * from metadata_items limit 1] database schema has changed
Apr 04, 2025 02:04:40.973 [23191689272120] INFO - [Database optimization/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 17, statement aborts at 60: [select * from metadata_items limit 1] database schema has changed
Apr 04, 2025 02:04:40.975 [23191689272120] INFO - [Database optimization/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 17, statement aborts at 60: [select * from metadata_items limit 1] database schema has changed
Apr 04, 2025 02:04:40.977 [23191689272120] INFO - [Database optimization/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 17, statement aborts at 60: [select * from metadata_items limit 1] database schema has changed
Apr 04, 2025 02:04:40.978 [23191689272120] INFO - [Database optimization/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 17, statement aborts at 60: [select * from metadata_items limit 1] database schema has changed
Apr 04, 2025 02:04:40.980 [23191689272120] INFO - [Database optimization/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 17, statement aborts at 60: [select * from metadata_items limit 1] database schema has changed
Apr 04, 2025 02:04:40.981 [23191689272120] INFO - [Database optimization/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 17, statement aborts at 60: [select * from metadata_items limit 1] database schema has changed
Apr 04, 2025 02:04:40.983 [23191689272120] INFO - [Database optimization/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 17, statement aborts at 60: [select * from metadata_items limit 1] database schema has changed
Apr 04, 2025 02:04:40.984 [23191689272120] INFO - [Database optimization/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 17, statement aborts at 60: [select * from metadata_items limit 1] database schema has changed
Apr 04, 2025 02:04:40.995 [23191689272120] INFO - Running migrations. (EPG 0)
Apr 04, 2025 02:04:44.564 [23191689272120] INFO - SQLITE3:0x80000001, 17, statement aborts at 60: [select * from metadata_items limit 1] database schema has changed
Apr 04, 2025 02:05:04.665 [23191689272120] INFO - SQLITE3:0x80000001, 17, statement aborts at 14: [SELECT bl.`id` FROM blobs bl WHERE (bl.`linked_type`=:C1 AND bl.`linked_id`=:C2 AND bl.`blob_type`=:C3)] database schema has changed
Apr 04, 2025 02:14:25.153 [23191878351672] WARN - [HttpClient/HCl#465d] HTTP error requesting GET https://77-69-130-103.ea1ae628a1a6477eb1ca1ede4dec4397.plex.direct:19346/identity (7, Couldn't connect to server) (Failed to connect to 77-69-130-103.ea1ae628a1a6477eb1ca1ede4dec4397.plex.direct port 19346 after 2994 ms: Couldn't connect to server)
Apr 04, 2025 02:29:17.328 [23191714585400] INFO - It's been 86400 seconds, so we're starting scheduled library update for section 2 (TV Shows)
Apr 04, 2025 02:29:17.361 [23191685053240] WARN - [Req#902f6] QueryParser: Invalid field 'sectionID' found, ignoring.
Apr 04, 2025 02:29:17.376 [23191685053240] WARN - [Req#902f6] QueryParser: Invalid field 'sectionID' found, ignoring.
Apr 04, 2025 02:29:18.175 [23191693491000] WARN - [Req#90320] QueryParser: Invalid field 'sectionID' found, ignoring.
Apr 04, 2025 02:29:18.187 [23191693491000] WARN - [Req#90320] QueryParser: Invalid field 'sectionID' found, ignoring.
Apr 04, 2025 03:14:24.731 [23191878351672] WARN - [HttpClient/HCl#4661] HTTP error requesting GET https://77-69-130-103.ea1ae628a1a6477eb1ca1ede4dec4397.plex.direct:19346/identity (7, Couldn't connect to server) (Failed to connect to 77-69-130-103.ea1ae628a1a6477eb1ca1ede4dec4397.plex.direct port 19346 after 2998 ms: Couldn't connect to server)
Apr 04, 2025 04:14:24.764 [23191878351672] WARN - [HttpClient/HCl#4667] HTTP error requesting GET https://77-69-130-103.ea1ae628a1a6477eb1ca1
Recommend using DBRepair to “Replace” this DB with a known good backup (which it will check for you)
just had a go at it but now the older two servers are not there as options (i hope that i’ve not lost my main), and it defaulted on the new one that was created after reinstalling docker first time after power outage as a try for fixing.
here’s a new Logs, and also has pulled a Preferences.xml file from an old pack up since the one after power outage was zero length (no text at all).
Logs.tar.gz (2.0 MB)
Looking at your account.
From your logs:
This is posted using the Unraid tag.
Do you have the Appdata Backup plugin installed? If so, have you tried using it to restore your last backup prior to the outage? Once restored then you can try addressing the DB corruption.
the second instance was created, i believe, because after running the server up again for the first time, i was unable to have access to the webui. so ended up deleting the docker+image, then reinstalling. and for some reason it prompted a new plex setup and i went ahead with it (mistake ig).
i’ve zero knowledge about why logs are not matching.
is there any way i could go back to the first instance at least? i’m unsure about how to proceed.
unfortunately, i was not running it, because if i remember correctly, i updated the server entirely beginning of the year and forgot to set it up again. i do have a legacy backup from last year, but it’s an old one dating to (02/2024)
managed to restore an old backup, but after doing so, and accessing webui for the first time, i’m getting this page again.
attaching the logs as well
Logs.tar.gz (1.4 MB)
At this point you might be hitting a more general problem with the latest version of plexmediaserver that many people are having right now. Plex says they are working on it.
I am in a similar situation as you. A power outage last week ended up with my linux PMS server having an empty Preferences.xml resulting in my whole server & libraries being unavailable. Sqlite DBs checked out OK, so I tinkered around with the Preferences.XML file last week but no luck, and gave up for a while. Lucky me, today I updated the the latest PMS, and started working on it again, only to hit the same error as everyone else, which you will undoubtedly see after clicking “Got It!” in your screen above: “A problem has been detected with a core component of Plex Media Server.” Dead end for now. I guess we wait.
Assume nothing until we see the logs.
Get into the unraid file system where Plex is stored.
My main array is called main.
It all looks like this.
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 16364612 827760 15536852 6% /
tmpfs 131072 868 130204 1% /run
/dev/sdb1 60556768 1323392 59233376 3% /boot
overlay 16364612 827760 15536852 6% /usr
overlay 16364612 827760 15536852 6% /lib
tmpfs 131072 328 130744 1% /var/log
devtmpfs 8192 0 8192 0% /dev
tmpfs 16382572 0 16382572 0% /dev/shm
efivarfs 128 55 69 45% /sys/firmware/efi/efivars
tmpfs 1024 0 1024 0% /mnt/disks
tmpfs 1024 0 1024 0% /mnt/remotes
tmpfs 1024 0 1024 0% /mnt/addons
tmpfs 1024 0 1024 0% /mnt/rootshare
/dev/sda1 976284620 78088652 898195968 8% /mnt/main
/dev/loop2 52428800 594812 51320740 2% /var/lib/docker
/dev/loop3 1048576 6240 926112 1% /etc/libvirt
192.168.0.20:/vol/media 117181523968 77685022720 39496501248 67% /mnt/remotes/192.168.0.20_media
tmpfs 3276512 0 3276512 0% /run/user/0
root@Gerbil:/mnt/main/appdata/Plex-Media-Server/Library/Application Support/Plex Media Server# ls /mnt
addons/ disks/ main/ remotes/ rootshare/ user/
root@Gerbil:/mnt/main/appdata/Plex-Media-Server/Library/Application Support/Plex Media Server# ls
Cache/ Crash\ Reports/ Drivers/ Media/ PlexLogs.tar.gz Plug-ins/ Setup\ Plex.html plexmediaserver.pid
Codecs/ Diagnostics/ Logs/ Metadata/ Plug-in\ Support/ Preferences.xml Updates/
root@Gerbil:/mnt/main/appdata/Plex-Media-Server/Library/Application Support/Plex Media Server#
Grab a tar.gz of the Logs and then post here.
Here’s an update for me this morning. I was able to downgrade my linux PMS install to the previous version. Then I was able to successfully follow the steps from other posts to get my server & libraries to re-appear, as before my Preferences.xml got nuked by a power failure.
Things seem ok now, and I am staying on the previous version of PMS until they find the issue.
And, now that I know about Preferences.xml being so important yet so ephemeral, I will back it up from now on.
7othala, I think you will be able to succeed also, if you are able to downgrade your server version first. The version I am running now is 1.41.9.9961-46083195d
As additional info / working versions:
You can also edit the docker spec on Unraid and use
VERSION (key 4) = 1.41.5.9522-a96edc606
This version will avoid the 1.41.7 DB issues as well.
unsure whether to post a different log then the one posted above after replacing the appdata plex folder with an older backed up version or the current one.
but here’s a log from the backed up version, all in the meanwhile, webui is stuck at Got it! screen.
Logs.tar.gz (1.4 MB)
will give this a go later and post another log. i’ve had no access to my plex server since posting here and really hope that i don’t have to resort to starting it all over again.
