Server Version#: 1.18.0.1913 in Docker
Player Version#: web 4.10.1, Android 7.22.1.12828
Home screen is not loading on players, and neither is recommended for certain libraries. Home screen shows all libraries as unreachable. But I can browse media in the library tab, and search for it in those libraries. Playback is working fine. This is happening over local network. I’ve tried removing and recreating the docker image twice now, to no effect. Plex Media Server.log (1.4 MB)
You can try going into Settings - Show Advanced - Debug - Restore Defaults
That would have zero affect on your metadata or media. It’s cosmetic.
No effect with that, Home screen still shows server as unreachable and some libraries have an unexpected error when loading. I’m probably going to try deleting my Docker file next to rule out the possibility it got corrupted.
Not a corrupt Docker file, error persists. Also tried downgrading server to 1.17.0.1841-d42cfa161, error still persists.
OK, I’ve looked through the log file, and the error lines that are coming up when I try to refresh the Home screen are:
Oct 13, 2019 17:30:05.334 [0x145ddc5c2700] ERROR - SQLITE3:(nil), 11, database corruption at line 64757 of [bf8c1b2b7a]
Oct 13, 2019 17:30:05.334 [0x145ddc5c2700] ERROR - SQLITE3:(nil), 11, database corruption at line 64798 of [bf8c1b2b7a]
Oct 13, 2019 17:30:05.334 [0x145ddc5c2700] ERROR - SQLITE3:(nil), 11, statement aborts at 4: [insert into media_stream_settings (account_id,media_stream_id,extra_data,created_at,updated_at) values (:media_stream_settings_account_id,:media_stream_settings_media_stream_id,:media_s
Oct 13, 2019 17:30:05.334 [0x145ddc5c2700] ERROR - Exception inside transaction (inside=1) (../Library/MediaStreamSetting.cpp:36): sqlite3_statement_backend::loadOne: database disk image is malformed
Oct 13, 2019 17:30:05.334 [0x145ddc5c2700] ERROR - Soci Exception handled: sqlite3_statement_backend::loadOne: database disk image is malformed
So it seems like the database file got corrupted, not anything in the Docker image. Anyway around this without creating a new Plex database and app data?
You can try to repair your database.
https://support.plex.tv/articles/201100678-repair-a-corrupt-database/
Import from the SQL dump wouldn’t complete; I guess I can try removing the libraries and then restoring watch states.
Removing libraries that had issues loading didn’t fix the problem, so I’ve had to rebuild the database from scratch. And the steps given in the support article for moving viewstates give a UNIQUE constraint failed error for metadata_item_settings.id, so I I’ve lost all my viewstates. Oh well.
EDIT: importing the viewstates semi-worked, but it also recreated the original error.
plex automatically creates database backups, if it hasn’t been disabled.
assuming they have been backed up, you could try restoring them from the newest to oldest.
There were 3 backups, but they were all over a year old, and I don’t ever remember turning the backups off, so that’s another mystery.
unfortunately probably a permissions issue.
if plex can’t write to the configured folder, no backups.
fwiw, with the plex mobile apps and server notifications, you can enable notification for database backup, so in the future you can watch for the notification and investigate if you do not see it every few days.
I’d be surprised if it was permissions issue, since the backups were writing to the database folder in AppData. I’m chalking this one up to gremlins.
I’m not too familiar with docker, but from my understanding the docker permissions are (or can be) different from inside the docker and outside the docker.
in any case, it sucks to lose your db, been there done that, lesson learned check backups often.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
