Server Version#: 4.148.0
Player Version#: not sure
I’m running a Plex server on a 2020 MacBook Air 13-inch retina running on Intel and with the Sequoia 15.5 OS. It’s been running fine for months but today I added a new hard drive and for unknown reasons the computer rebooted. It came back on line immediately but it will no longer open the Plex Media server and won’t recognize the server, giving me the “currently unavailable” screen even through the server runs on the same computer as the libraries are on.
Under no circumstances will the Media server run. It doesn’t open in the browser when I hit the icon in the toolbar; it doesn’t open when I select it from applications; it doesn’t open when I drag it into the browser or enter the server info directly into the browser address bar. It also won’t connect to the server at all so I can’t access any libraries.
It’s the latest version of the server software and (I believe) the latest version of the Mac OS. Any idea what the problem might be? I’d really like to get it running again as I just added new stuff to the library (it’s all on there, too - the hard drives show up on the desktop just like always.)
If the Plex Media Server won’t start and doesn’t even get to the stage where it’ll be writing to the server logs, you can attempt the following procedure to see if there’s any error messages on the OS level:
Open Finder and navigate to /Applications
Select Show Content from the context menu of the Plex Media Server.app item
Navigate to Contents/MacOS
Open the Terminal app
Drag the Plex Media Server executable from the Finder window (#3) into the Terminal Window and press Return to execute it
This is no different from running the app, so it won’t succeed – but you should get a more specific error message about what’s causing it to fail starting.
This is the response. No idea what it means. (If you can’t read the screenshot, it says “Error: Unable to set up server: sqlite_statement_backend::loadOne: database disk image is malformed (N4soci10soci_errorE)”.)
It means your server’s database has been corrupted. This can happen if the server is stopped while writing to the database, not being able to finish the write.
You could try running this script to attempt fixing the issue.
Chuck has done a terrific job with providing that Utility. I would become very familiar with it’s features and run the utility as regular maintenance. to keep your Database running smooth.
