Server Randomly Shutting Down

Server Version#:1.42.2.10156
Player Version#:4.147.1

My server, while watching, will randomly stop playing. I’m running Ubuntu 24.04.3 LTS.

I can ssh into the server, services are up, memory is good. But when this happens I can’t access Plex via web browser. It happens often, but I can’t for the life of me figure out why. Not sure what logs are needed. Attaching the log that was during the time of it freezing most recently.

Plex Media Server.1.log (4.6 MB)

Plex Media Server Logs_2025-12-21_20-24-48.zip (2.1 MB)

<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>

Something tole PMS to stop.

Dec 21, 2025 20:21:30.754 [139434028792632] DEBUG - Shutting down with signal 15 (Terminated)
Dec 21, 2025 20:21:30.754 [139434028792632] DEBUG - Ordered to stop server.
Dec 21, 2025 20:21:30.754 [139434028792632] DEBUG - [JobRunner] Job running: /usr/lib/plexmediaserver/CrashUploader --sessionStatus=exited --sessionStart=1766364666 --sessionDuration=5424 --version=1.42.2.10156-f737b826c --userId=team.boips@gmail.com --sentryUrl=https://o17675.ingest.sentry.io/api/1233455/ --sentryKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Dec 21, 2025 20:21:30.754 [139434028792632] DEBUG - [JobRunner] Jobs: Starting child process with pid 4943
Dec 21, 2025 20:21:30.754 [139434033535632] DEBUG - Stopping server...

I do see it completing an earlier crash report upload.

That was me, I restarted it to get it back working.

I think I’ll run your db repair utility because in looking at the logs I see it trying to hit my old xSteve server which I haven’t had in at least a year. In looking at the PMS settings I don’t even have the tuner setup in there.

This stopping of playing is very frustrating as I cannot pin down the cause. It’s so random

Anything in the crash report uploaded?

I ran your DB repair, I’ll see if that fixes anything:

Automatic Check,Repair,Index started.

Checking the PMS databases
Check complete. PMS main database is OK.
Check complete. PMS blobs database is OK.

Exporting current databases using timestamp: 2025-12-21_22.02.30
Exporting Main DB
Exporting Blobs DB
Successfully exported the main and blobs databases.
Start importing into new databases.
Importing Main DB.
Importing Blobs DB.
Successfully imported databases.
Verifying databases integrity after importing.
Verification complete. PMS main database is OK.
Verification complete. PMS blobs database is OK.
Saving current databases with ‘-BACKUP-2025-12-21_22.02.30’
Making repaired databases active
Repair complete. Please check your library settings and contents for completeness.
Recommend: Scan Files and Refresh all metadata for each library section.

Backing up of databases
Backup current databases with ‘-BACKUP-2025-12-21_22.04.32’ timestamp.
Reindexing main database
Reindexing main database successful.
Reindexing blobs database
Reindexing blobs database successful.
Reindex complete.
Automatic Check, Repair/optimize, & Index successful.

I cannot see what’s in a crash report.
That info is stored in the cloud and only accessible by Engineering.

It did it again, at 3:26. I did not restart it and pulled the logs. Are you able to see what it might be?

Plex Media Server Logs_2025-12-24_15-27-48.zip (3.5 MB)

Hope you have an amazing Christmas!!!

So, I can access the PMS via ssh, but not via web…it’s the oddest thing! It pings, it’s almost like the webserver is shutdown

Memory looks good:

Services are up:

Odd thing is…I can’t see my storage,when running a df it freezes:

image

Minutes later it works

And then the server comes back up:

Here’s new logs after the server comes back up (via web):

Plex Media Server Logs_2025-12-24_15-43-54.zip (3.6 MB)

@lance_mayfield

Looking at your logs shows no errors.

I see the server communicating with Plex.tv and being reachable (remote access)

I’ve had trouble with Plex/web when those long URLs are used.

If you strip everything after /web, does it populate ?

No, still not reachable. I discovered that my PiHole was not allowing local access so I resolved that.

It just shut down again and I’m think it has something to do with the mount to my NAS. I ran a dmesg and it looks like there’s issues with the NAS but I can access it from every other platform.

This isn’t new…I’ve had this setup for about 2 years.

If NFS isn’t responding, are you not allowing the NFS UDP/TCP traffic ?

Definitely something with my NFS mount, but I just don’t know what.

I mount at startup with: sudo mount -t nfs 192.168.1.247:/volume1/data /mnt\r

Why not set the mounts in /etc/fstab and let them mount by systemd at startup?

Here is my main NFS mount for backups

192.168.0.20:/vol/backup /glock/backup nfs defaults,sec=sys,rw,auto,async,rsize=4194304,wsize=4194304,x-systemd.after=network-online.target,nofail,bg 0 0

Well…I’m not blocking it that I know of. It wors, sometime for hours with no issue. Then, it just stops.

If I do nothing, it resolves itself in 10ish minutes

I can research that and try…think it would be better?

10 minutes is the retry interval.

Are you using standard MTU=1500 packets?

Yes, Ubiquiti DM pro, standard MTU

I would definitely look at getting things into /etc/fstab

/etc/fstab is processed BEFORE Plex and other system services start.