Plex server continually locking up

Server Version#: 1.41.8.9834
Player Version#:
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>

I have plex server running as a ProxMox VM. I have had this running OK for over a year no issues. recently my plex server locks up the entire Proxmox host hardware and only a hard reset will fix it. I have tried different hardware etc.

When you get into the VM and down into where PMS stores the Databases (/var/lib/plexmediaserver),

How big are they?

1.41.7 had a major bloat problem.

File: /var/lib/plexmediaserver/Library/Application Support/Plex Media Server
Type: directory
Size: 6.68 GiB (4096 bytes)

171M /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.db

com.plexapp.plugins.library.blobs.db
124.82 MiB
com.plexapp.plugins.library.blobs.db-2025-06-29
78.09 MiB
com.plexapp.plugins.library.blobs.db-2025-07-02
98.73 MiB
com.plexapp.plugins.library.blobs.db-shm
32 KiB
com.plexapp.plugins.library.blobs.db-wal
113.35 MiB
com.plexapp.plugins.library.db
170.49 MiB
com.plexapp.plugins.library.db-2025-06-29
183.5 MiB
com.plexapp.plugins.library.db-2025-07-02
187.34 MiB
com.plexapp.plugins.library.db-shm
1.34 MiB
com.plexapp.plugins.library.db-wal
174.38 MiB

I have increased the server memory from 4gb - 8gb and it still locked up however improved. I have increased to 12GB and may have soled it. I will see how it goes over the next few days.

Did not fix issue server is still locking up during playback

Server debug logs ZIP file please (captured 3 minutes after restarting PMS)?

Plex Media Server Logs_2025-07-08_03-56-14.zip (2.6 MB)

So after increasing the memory of the server it last longer however as you can see the attached screen shots of the host memory it seems to consume 100% of the memory. I think this might be the underlying issue


116K /tmp
1.2G /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Plug-in Support/Databases/

This is not an accurate representation of the memory used by applications inside the vm, only the memory allocated to it.

My Proxmox also shows 20GB+ memory allocation but my PMS instance is only using 245MB.

hmm Ok I wondered about that as the VM itself is also using low memory. But the PMS only seems to crash once all the memory has been allocated… still working on why seems a mystery. With more memory allocated it is crashing less often.

Hi have you had any opportunity to look at the logs? server is locking up continually.

@benruss

I’ve had some time , but nothing definitive, into finding this.

We need more info. Specifically see if it’s PMS or just Linux using memory (it should be Linux ( Linux will use all physical memory to improve performance over time )

This is my server on 8GB.

Just to rule out memory contention, I would like you to do the following.

  1. Stop Plex
  2. Edit Preferences.xml
  3. On the last line, before the closing />,
  4. Add LogMemoryUse="1" (keep a space between it and the preceding preference)
  5. Start PMS
  6. Confirm DEBUG logging is enabled.
  7. Make it fail or wait for it to fail (whichever is most predictable)

sorry I have been unwell not really had a chance to test properly. Plex does seem to behaving itself but will do more testing. I see there is a new update should I do this? Also there was a Linux update to SQL which may have fixed this. Will do more testing and confirm

@benruss

I know how “health” goes. Been there myself recently.

As for updating, There is no immediate need to update to 1.41.9 unless you’re waiting for a specific bug fix.

A Linux update for SQLite won’t help PMS. Plex uses their own build of Plex SQLite with additional functionality added above standard distribution.

Test as you can, no rush, we’ll be here.

Plex Media Server Logs_2025-07-18_03-37-07.zip (3.3 MB)

latest log files.

Thank you.

This caught the error as it occurred.

  1. Everything was running normally.
  2. It had started a transcode and was running normally.
  3. Suddenly, it lost internet connectivity (the VM’s network stack failed)
    – Routing table was gone
    – DNS was inoperative
    – Adapter not accessible

Segment in your logs which capture it.

Jul 18, 2025 02:11:54.932 [137211707456312] DEBUG - [Req#3049b] Statistics: (i832doi7rfjzqzj2rotynbht) Reporting active playback in state 0 of type 4 (scrobble: 0) for account 1
Jul 18, 2025 02:11:54.937 [137211792255800] DEBUG - Completed: [138.217.115.254:49405] 200 GET /:/timeline?ratingKey=24625&key=%2Flibrary%2Fmetadata%2F24625&playbackTime=242902&playQueueItemID=806&state=playing&hasMDE=1&context=home%3Ahub.continueWatching&row=0&col=5&time=306000&duration=1699000 (7 live) #3049b TLS GZIP 7ms 880 bytes (pipelined: 443) (Memory Usage: 90.0 MB/976.0 MB)
Jul 18, 2025 02:11:55.018 [137211713784632] DEBUG - [Req#304b0/Transcode/psr7y0hdwe90104q9oqt9lkw/e98b48c6-0982-447c-b017-0e6493ac074a] Transcoder segment range: 30 - 436 (436)
Jul 18, 2025 02:11:55.094 [137211705346872] DEBUG - [Req#304af/Transcode/psr7y0hdwe90104q9oqt9lkw/e98b48c6-0982-447c-b017-0e6493ac074a] Session psr7y0hdwe90104q9oqt9lkw (4) is throttling
Jul 18, 2025 02:11:55.097 [137211709565752] DEBUG - [Req#304b9/Transcode/psr7y0hdwe90104q9oqt9lkw/e98b48c6-0982-447c-b017-0e6493ac074a] Throttle - Going into sloth mode.
Jul 18, 2025 02:12:07.284 [137211792255800] DEBUG - [EventSourceClient/pubsub/172.105.203.197:443] Failure: 125 - Operation canceled.
Jul 18, 2025 02:12:07.284 [137211792255800] DEBUG - [EventSourceClient/pubsub/172.105.203.197:443] MyPlex: We appear to have lost Internet connectivity, resetting device URL cache.
Jul 18, 2025 02:12:07.284 [137211792255800] ERROR - [EventSourceClient/pubsub/172.105.203.197:443] Retrying in 15 seconds.
Jul 18, 2025 02:12:07.822 [137211692841784] DEBUG - [Req#2cf20/ViewStateSync] Starting
Jul 18, 2025 02:12:07.822 [137211692841784] DEBUG - [Req#2cf20/ViewStateSync] Fetching user tokens
Jul 18, 2025 02:12:07.822 [137211692841784] DEBUG - [Req#2cf20/ViewStateSync/HCl#73d] HTTP requesting GET https://plex.tv/api/v2/server/users/services?auth_token=xxxxxxxxxxxxxxxxxxxx
Jul 18, 2025 02:12:10.907 [137211661798200] DEBUG - SSDP departed after not being seen for 21.325950 seconds: 10.0.1.244 (HomeLand_HA (Home Assistant))
Jul 18, 2025 02:12:10.907 [137211661798200] DEBUG - SSDP departed after not being seen for 22.001408 seconds: 10.0.1.251 (HomeLandNAS01)
Jul 18, 2025 02:12:12.832 [137211766815544] WARN - [HttpClient/HCl#73d] HTTP error requesting GET https://plex.tv/api/v2/server/users/services?auth_token=xxxxxxxxxxxxxxxxxxxx (6, Couldn't resolve host name) (Could not resolve host: plex.tv)
Jul 18, 2025 02:12:12.832 [137211709565752] DEBUG - [Req#2cf20/ViewStateSync] MyPlex: using cached data for request for https://plex.tv/api/v2/server/users/services?auth_token=xxxxxxxxxxxxxxxxxxxx
Jul 18, 2025 02:12:12.833 [137211709565752] DEBUG - [Req#2cf20/ViewStateSync] Failed to get new tokens; aborting
Jul 18, 2025 02:12:22.286 [137211794365240] DEBUG - [EventSourceClient/pubsub/172.105.203.197:443] Resolving 172.105.203.197 port 443
Jul 18, 2025 02:12:22.286 [137211794365240] DEBUG - [EventSourceClient/pubsub/172.105.203.197:443] Resolved 172.105.203.197 to 172.105.203.197:443
Jul 18, 2025 02:12:36.551 [137211792255800] DEBUG - [EventSourceClient/pubsub/172.105.203.197:443] Failure: 113 - Host is unreachable.
Jul 18, 2025 02:12:36.552 [137211792255800] ERROR - [EventSourceClient/pubsub/172.105.203.197:443] Retrying in 30 seconds.
Jul 18, 2025 02:13:06.552 [137211792255800] DEBUG - [EventSourceClient/pubsub/172.105.203.197:443] Resolving 172.105.203.197 port 443
Jul 18, 2025 02:13:06.552 [137211792255800] DEBUG - [EventSourceClient/pubsub/172.105.203.197:443] Resolved 172.105.203.197 to 172.105.203.197:443
Jul 18, 2025 02:13:06.631 [137211794365240] DEBUG - [EventSourceClient/pubsub/172.105.203.197:443] Failure: 113 - Host is unreachable.
Jul 18, 2025 02:13:06.631 [137211794365240] DEBUG - [EventSourceClient/pubsub/172.105.203.197:443/PubsubServerManager/getNextWorkingHost/hnd] 2 total hosts available in region, starting tests
Jul 18, 2025 02:13:09.703 [137211792255800] DEBUG - [EventSourceClient/connectiontester/139.162.75.196:443] Failure: 113 - Host is unreachable.
Jul 18, 2025 02:13:09.704 [137211794365240] DEBUG - [EventSourceClient/pubsub/172.105.203.197:443/PubsubServerManager/getNextWorkingHost/hnd] Switching to next host in region: 139.162.75.196
Jul 18, 2025 02:13:09.712 [137211794365240] DEBUG - [EventSourceClient/pubsub/172.105.203.197:443] Stopping.
Jul 18, 2025 02:13:09.712 [137211794365240] DEBUG - [EventSourceClient/pubsub/139.162.75.196:443] Resolving 139.162.75.196 port 443

Error 113 = No Route to Host

[chuck@lizum user.2016]$ perror 113
Exit code(113): error "No route to host"
[chuck@lizum user.2017]$ 

At this point, the VM’s network stack is dead. PMS stops

I do see in the logs where Viewstate sync completed.
If you need to create a new VM, it will restore your watch history.