Server Version#: v.1.41.2.9200-c6bbc1b53
Player Version#:
Hi all,
So, to start, I’m running a 10tb JBOD Asustor server for use with Plex. It’s always run fine (with the occasional blip that needs a restart).
In June, I ran the latest update as I always like to make sure everything is kept up to date, and as soon as I did everything fell apart. Plex could no longer find the server, whole mess. I forget exactly what I did to fix it, but I think I managed to find an older version of the server software and roll it back. I should have made a note, as now I’m entirely lost as to how to fix it.
I can still access the server by hitting command + K (I’m on a Mac) and connecting to it directly, and I can still access the Asustor portal just fine, however Plex isn’t playing ball.
Whenever I try to connect to Plex through the Asustor portal I get ‘Firefox can’t establish a connection to the server at ipaddress:32400.’
Previously I was getting the 503 PMS maintenance error so I just let it do it’s thing, but now I just get the error above.
I’ll admit I’m just barely managing to make all this work at the best of times, so please forgive my ignorance, I’m doing my best to learn but wow this is complicated. Any help would be hugely appreciated, thanks in advance!
I have found a temporary fix in what I feel is an incredibly stupid way. I can add Plex libraries from my server, through the Plex Media Server app for Mac, which I assume will only work when the server is linked. If there is a less stupid and fiddly way around this I would love to know about it.
Still getting a ‘can’t establish connection to the server’ error whenever I try and open Plex from within the Asustor portal.
You installed Plex on your MacBook, not your NAS. Dec 03, 2024 03:12:05.857 [0x16b5af000] INFO - Plex Media Server v1.41.2.9200-c6bbc1b53 - Apple MacBookPro18,3 arm64 - build: darwin-aarch64 macos - GMT 00:00
Yeah I had to after the NAS stopped being able to open Plex, otherwise there would be no way to keep using it. Any other options besides a full reset of the NAS, as that’s my current plan.
Dec 03, 2024 11:22:20.671 [548374728736] ERROR - SQLITE3:0x7fadae9908, 13, statement aborts at 23: [update blobs set created_at = iif(typeof(created_at) in ('integer', 'real'), created_at, strftime('%s', created_at, 'utc'))] database or disk is full
Dec 03, 2024 11:25:05.618 [548374728736] ERROR - Exception inside transaction (inside=1) (/home/runner/actions-runner/_work/plex-media-server/plex-media-server/Library/DatabaseMigrations.cpp:342): sqlite3_statement_backend::loadOne: database or disk is full
Dec 03, 2024 11:26:49.268 [548374728736] ERROR - Exception thrown during migrations, aborting: sqlite3_statement_backend::loadOne: database or disk is full
Dec 03, 2024 11:26:49.270 [548374728736] ERROR - Database corruption: sqlite3_statement_backend::loadOne: database or disk is full
Yeah unfortunately this is where my knowledge falls apart entirely.
To run through the list in the screenshot, I can get as far as step 5, opening Terminal, before I have no idea what any of it means. I understand extracting a file in as much as running Archive Utility to extract something, past that my knowledge base is zero I’m afraid.
You can delete those files, its just not my first choice. What you can do as a test, is stop plex, rename the blobs.db and library.db files by adding .old to the file names (keeps the files as a fail safe, but moves them out of the way) Then take the 2 files ending in 24-11-16 and rename them to end with .db instead of the date. Then restart plex. That will revert your database back to the oldest backup you have which is hopefully prior to the crash.
If you’ve not already done so, clear out some working room before running the DBRepair utility. It needs room to make backup copies and working copies of the database files.
If the Asustor has wget (standard Linux command), then this should work.
When you run the utility, stop Plex Media Server and use AUTO.
If AUTO fails to repair the database, try REPLACE. That will check the backup databases and restore the most recent undamaged backup if one is available.
If that fails, post the output of the utility to the thread.
# ssh to the NAS
# On Windows run from the c:\ prompt in a CMD window or in PowerShell.
# or use a terminal emulator such as PuTTY
# On Mac/Linux, run from a terminal sessions.
ssh username@IP
# cd to download location
cd /volume1/Public
# Download latest version.
# This overwrites any existing version. Remove "-O DBRepair.sh" to not overwrite.
wget -O DBRepair.sh https://github.com/ChuckPa/PlexDBRepair/releases/latest/download/DBRepair.sh
# Make it executable
chmod a+x DBRepair.sh
# Run it as root. You will be asked for the NAS admin password
sudo ./DBRepair.sh
I assume I’ve fallen at the first hurdle, whenever I’ve tried to make anything work in Terminal it has never worked, so yeah, apologies, I am not too literate at this side of things.
