Plex 1.43.0.10389 crashes

Server Version#:Version 1.43.0.10389
Player Version#:
cant tell why, but server periodically crashes. not daily but at least a few times a week.

Plex Media Server Logs_2026-01-03_21-18-31.zip (5.9 MB)

@jrandallnyc

From the logs attached,

  1. The server didn’t crash. It was ordered to shutdown
Jan 03, 2026 21:17:36.832 [132374484151096] DEBUG - Shutting down with signal 15 (Terminated)
Jan 03, 2026 21:17:36.832 [132374484151096] DEBUG - Ordered to stop server.
Jan 03, 2026 21:17:36.832 [132374484151096] DEBUG - [JobRunner] Job running: /usr/lib/plexmediaserver/CrashUploader --sessionStatus=exited --sessionStart=1767321074 --sessionDuration=171982 --version=1.43.0.10389-8be686aa6 --userId=jrandall@contentfusion.net --sentryUrl=https://o17675.ingest.sentry.io/api/1233455/ --sentryKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Jan 03, 2026 21:17:36.833 [132374484151096] DEBUG - [JobRunner] Jobs: Starting child process with pid 317900
Jan 03, 2026 21:17:36.833 [132374488930960] DEBUG - Stopping server...
Jan 03, 2026 21:17:36.833 [132374488930960] DEBUG - HttpServer: Stopping server.
Jan 03, 2026 21:17:36.906 [132374484151096] VERBOSE - JobManager: child process with handle 317900 exited
Jan 03, 2026 21:17:36.906 [132374484151096] DEBUG - Jobs: '/usr/lib/plexmediaserver/CrashUploader' exit code for process 317900 is 0 (success)
Jan 03, 2026 21:17:37.833 [132374488930960] WARN - Timed out waiting for server to finish.
Jan 03, 2026 21:17:37.833 [132374488930960] DEBUG - Server stopped.
Jan 03, 2026 21:17:37.833 [132374488930960] DEBUG - Killing plug-ins.
Jan 03, 2026 21:17:37.851 [132374488930960] DEBUG - [com.plexapp.system] Killing.
Jan 03, 2026 21:17:37.855 [132374484151096] WARN - JobManager: Could not find job for handle 468
Jan 03, 2026 21:17:37.857 [132374488930960] DEBUG - ChildProcessMonitor: Waiting for Plex Tuner Service to exit.
Jan 03, 2026 21:17:37.858 [132374488930960] DEBUG - [JobRunner] Signalling job ID 505 with 2
Jan 03, 2026 21:17:37.889 [132374484151096] VERBOSE - JobManager: child process with handle 505 exited
Jan 03, 2026 21:17:37.889 [132374484151096] DEBUG - Jobs: '/usr/lib/plexmediaserver/Plex Tuner Service' exit code for process 505 is 0 (success)
Jan 03, 2026 21:17:37.889 [132374274411320] DEBUG - [ChildProcessMonitor] Plex Tuner Service exited.
Jan 03, 2026 21:17:37.889 [132374488930960] DEBUG - Job was already killed, not killing again.
Jan 03, 2026 21:17:37.889 [132374488930960] DEBUG - Database: Shutting down.
Jan 03, 2026 21:17:37.902 [132374488930960] DEBUG - Database: Shutting down.
  1. Would you please turn off VERBOSE logging until/unless requests.
    Debug logging is usually all we ever need.

the only way to get it back is to shut it down and start it back up. also verbose should be off, i turned it off a few days ago on the last restart, so depending on how far back the logs are tracking it shouldnt be on anymore. the last time it stopped responding was about an hour ago

going to try:

Your Plex server is healthy, but Docker is being too aggressive. The healthcheck is killing Plex during normal NAS stalls.

Disable the healthcheck and this problem almost always disappears.
healthcheck:

healthcheck:
    disable: true

Whose server image are you using ?

Which NAS?

Please define / share what you mean by a NAS stall ?

that was a chat GPT comment.

its using a Synology

# Plex - Media Server

plex:

image: plexinc/pms-docker:plexpass

I also just updated to use nfs4.1 to see if that helps too, per some chat GPT comments in /etc/fstab

192.168.3.130:/volume1/video/plex-library/movies /volume1/video/plex-library/movies nfs rw,vers=4.1,hard,timeo=600,retrans=2,_netdev,nofail,noatime 0 0

192.168.3.130:/volume1/video/plex-library/TV\040Shows /volume1/video/plex-library/TV\040Shows nfs rw,vers=4.1,hard,timeo=600,retrans=2,_netdev,nofail,noatime 0 0

192.168.3.130:/volume1/PlexMediaServer /mnt/synology/PlexServerSource nfs rw,vers=4.1,hard,timeo=600,retrans=2,_netdev,nofail,noatime 0 0

here is what chatGPT was saying about my config. so made the updates:

Your Plex crashes were not Docker, not Plex, and not disk failure.

They were NFS stalls caused by DSM load on a DS218+, which you have now largely mitigated by:

  • Fixing Docker mounts

  • Moving transcode to RAM

  • Enabling NFSv4.1

Jan 03 21:10:33 PlexServer kernel: nfs: server 192.168.3.130 not responding, still trying

Jan 03 21:10:33 PlexServer kernel: nfs: server 192.168.3.130 not responding, still trying

Jan 03 21:10:33 PlexServer kernel: nfs: server 192.168.3.130 not responding, still trying

Jan 03 21:10:33 PlexServer kernel: nfs: server 192.168.3.130 not responding, still trying

Jan 03 21:18:20 PlexServer kernel: nfs: server 192.168.3.130 OK

Jan 03 21:18:20 PlexServer kernel: nfs: server 192.168.3.130 OK

Jan 03 21:18:20 PlexServer kernel: nfs: server 192.168.3.130 OK

Jan 03 21:18:20 PlexServer kernel: nfs: server 192.168.3.130 OK

Couple of questions then a few recommendations to improve your NFS.

  1. Why are you mounting the PlexMediaServer shared folder ?

  2. Are you using PlexMediaServer in the container over the LAN ?

Recommendations:

  1. Confirm NFS block size set to 32KB (Default is 8KB). 32KB significantly reduces the overhead thereby improving performance (it will saturate gigabit)

  1. Change your NFS mount. I would change:

192.168.3.130:/volume1/video/plex-library/movies /volume1/video/plex-library/movies nfs rw,vers=4.1,hard,timeo=600,retrans=2,_netdev,nofail,noatime 0 0

to

192.168.3.130:/volume1/video/plex-library/movies /volume1/video/plex-library/movies nfs defaults,rw,rsize=131072,wsize=131072,nofail,noatime,bg 0 0

– NFS 4.1 (highest offered by the syno) will be negotiated by default.
– 131072 tells the syno you want max read/write buffer size (auto-negotiation is 4meg on other hosts but Syno needs ‘coaching’)

– You can replicate this to your other NFS mounts from the Syno.

  1. ChatGPT isn’t the best source. Grok is far better.

no idea why PlexMediaServer was shared.. i think that was something i must have done before (I unmounted it now and removed it from fstab). I was originally running Plex on the Synology before i put it on an extra linux box I had laying around with an Nvidia GPU, bunch of memory and migrated the library and settings over from SYN to Linux

and PlexMediaServer is running on a docker container, and the SYN is on the LAN next to it. I using it internally and remote as well.

I do also have issues with LiveTV struggling at times when both locations have 1GB up and 1GB down… i had to set the player on AppleTV to like 10MB otherwise it seems to start and stop, go back to the guide, pixelate, or say not enough bandwidth (which makes no sense as they are all hardwired)

as for recco’s, thanks:

1- done, it was 8KB. (also it was set to max NFSv3 earlier, so changed that to v4.1 as well
2 - updated the NFS mount(s) to your settings.

ChatGPT did “pretty good”.. it pointed out that i was using NFSv3, had the transcode directory set wrong, needed to turn of some indexing on the Synology that was useless overhead.

i guess we can see now if it stops “crashing”

let me know if you have any thoughts on the LiveTV stuff. it seems to work “ok” but not great and has 2 HDHomeRuns with cabelcards, so 6 tuners available.

Depending on how you have your drives/storage setup,

  1. JBOD (single drive per volume) should give you 100 MB/drive – which functionally maxes the gigabit (Observed max on a strong CPU is 117 MB/sec)

  2. Given you have a dual-core CPU, do your best to minimize what Syno does in the background to rob you of CPU resources. ( I have a 418J dev system. It’s not bad but can get overwhelmed if I use it for more than NFS or light PMS serving )

I have no LiveTV recommendations. I have not used LiveTV in several years (I sold my HDHomeRun) because there’s was no way for me to record – and OTA television was far from watchable.

that looks good. Mirror perf will allow you to fully saturate gigabit

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.