Server Version#: 1.23.6.4810
Player Version#: N/A
I was removing an install of another program from this machine, and deleted the ‘localhost’ folder from /Users/user/Library/Application Support/Plex Media Server/Media. I was doing too many things at the same time, and didn’t realize I was in the wrong window (one that I had opened earlier to see how much space my server was taking up). Is there a way to rebuild the media content without losing my playlists and organization? For those 10sec or so, my whole server is still shown and functions as normal on the web.
Thanks for the help. It was such a stupid mistake.
Edit: I just noticed the issue in other tickets with version 1.23.6.4810 that it shuts down on its own. I did quit Plex to do a firmware update on my RAID array, and deleted the localhost folder while it was shut down, then this issue arose after relaunching. Is that known issue Windows-only, or has it been shown to affect Macs as well?
Turn off verbose logging. Set your system for debug level logging. Verbose adds too much information to the log files, making problem diagnosis more difficult. It also causes the log files to wrap too quickly, losing desirable information. Debug is the default level. See Reporting issues with Plex Media Server for instructions on setting the correct logging level.
Your log files have multiple “database is locked” messages.
Jul 25, 2021 11:50:11.399 [0x70000bdd6000] ERROR - Failed to begin transaction (/data/jenkins/server/1792676798/Plugins/PluginDatabaseState.cpp:110) (tries=5): Cannot begin transaction. database is locked
The thread contains download links to new versions to alleviate the problem. Updated builds will be available via the normal methods (plex.tv/download, etc) at some point (reference).
Read the thread before downloading and installing any of the PMS builds. Some users installed the new builds. Others fell back to older versions. Also backup your database before installing any of the hotfix builds.
Thanks, man, that’s exactly what it was. The new version resolved the issue.
And also thanks for bringing the verbose logging to my attention. It’s been on since a trouble ticket over a year ago, and I forgot to turn it back off.
