Server Version#:1.40.3.8555
Player Version#:
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>
I updated my server, but now my server can’t be found. Service is running, but I can’t connect to the server locally and I can’t find the server using app.plex.tv.
Last time this happened, I had to start another instance of the server to get it back. Do I have to do this everytime I update the server? Is there something I’m doing wrong?
Look in Preferences.xml,
Make certain it is still owned by you and has a valid PlexOnlineToken.
Sometimes it gets caught rebooting/etc and forgets itself.
I checked and it’s still owned by plex. I can’t even hit the localhost:32400 address. It times out.
Can I remove the server then re-claim it and still keep all my metadata intact?
The file is still owned by Plex. I tried renaming it to start over and my server just exit codes whenever I start the service.
Did change my password which I think causes a new Token to be created, could that be the problem? But wouldn’t I bypass that by creating a new Preferences file?
Do I really have to start from scratch and re-load everything after each update?
It’s completely broken now and I don’t know what happened.
I’ve tried removing the Preferences file, nothing.
I’ve tried uninstalling Plex and starting over, still won’t run properly.
I’ve reset my password to get a new token, still won’t run.
What am I doing wrong? Why did I get a crash after only updating the app?
Any chance you have server logs?
About updating/crashing, that can be due to the updates doing more with the database than normally usage. With logs we might be able to narrow down what is happening.
I’m at a loss. I can’t get the service to run, y’all are my last hope.
Plex Media Server.1.log (4.9 KB)
Plex Media Server.2.log (332.0 KB)
Plex Media Server.log (5.2 KB)
Thats a fairly limited export of the server logs, but we got lucky:
Jul 03, 2024 14:55:33.939 [139984669219472] ERROR - SQLITE3:0x80000001, 13, statement aborts at 5: [CREATE TABLE "media_parts" ("id" INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, "media_item_id" integer, "directory_id" integer, "hash" varchar(255), "open_subtitle_hash" varchar(255), "file" varchar(255), "index" integer, "size" integer(8), "duration" integer, "created_at" dt_integer(8), "updated_at" dt_integer(8), "deleted_at" dt_integer(8), "extra_data" varchar(255))] database or disk is full
Jul 03, 2024 14:55:33.940 [139984669219472] ERROR - SQLITE3:0x80000001, 13, statement aborts at 1: [VACUUM] database or disk is full
Jul 03, 2024 14:55:33.944 [139984669219472] ERROR - Exception thrown during migrations, aborting: sqlite3_statement_backend::loadOne: database or disk is full
Jul 03, 2024 14:55:33.944 [139984669219472] ERROR - Database corruption: sqlite3_statement_backend::loadOne: database or disk is full
Jul 03, 2024 14:55:33.944 [139984669219472] ERROR - Error: Unable to set up server: sqlite3_statement_backend::loadOne: database or disk is full (N4soci10soci_errorE)
Looks like you have a full disk
which has also led to database corruption:
https://support.plex.tv/articles/repair-a-corrupted-database/
It’s possible on the main file system, but on the disk I have it on, I have space. I moved it there for this reason.
Here’s a screen of the free space on that disk.
Could it possibly be the databases? Could I still be pointing to the main file system if my override failed?
And I’m sorry for the limited logs. I’ve been trying to remove the folder and start anew. It fixed the issue last time, but the service still crashes when I try.
I didn’t think to save the logs until afterward.
lets start with looking at all of your drives, are there any that are full?
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
