Plex may be non-responsive, but it is still running. The two shutdowns in the log files are orderly (meaning you or something else gracefully stopped Plex Media Server).
Verbose Logging
Disable verbose logging in Settings → server_name → General + Show Advanced (reference). Debug logging is sufficient. Verbose adds many additional lines to the log files. It can cause them to wrap too quickly, losing desired information.
Plex Media Server must be restarted for the change to take effect.
Fan art plugin errors
Plex is logging errors for the legacy Fanart.tv agent.
-
In Settings → Agents (Legacy), uncheck Fanart.tv anywhere it is checked.
-
Delete the plug-in caches directories.
See Clearing Plugin/Channel/Agent HTTP Caches.
- Stop Plex Media Server.
- Go to
/Plug-in Support/Caches in the Plex Data Folder.
- Delete everything in Caches. Plex will re-create them.
- Start Plex Media Server.
VPN on server?
If so, configure it to not run/connect when the system starts, you login, etc.
Restart the PC
This restarts everything, not just Plex. Makes sure Windows networking is restarted, etc.
Start with those steps. If you still have issues, pull and post another set of log files.
Reading Log Files
The log files are cryptic and there is no magic decoder ring. They’re written by the devs for the devs. End users are not the intended audience. There are many false positives. You learn which ones are real or not by experience and reading/posting in the forum.
The primary log file is Plex Media Server.log and its rollovers .1.log to .5.log.
When you start Plex it bumps the log files. They also rollover when they reach a pre-set size limit.
You recently restarted Plex, so Plex Media Server.log contains the entries since startup.
This is Plex Media Server starting. It will be in the top 10 lines whenever PMS starts.
Jan 28, 2026 11:51:00.008 [8596] DEBUG - BPQ: [Idle] -> [Starting]
The bottom of Plex Media Server.1.log has the last entries before Plex was stopped.
This is a graceful shutdown. If Plex had crashed, then these lines would not be present.
Jan 28, 2026 11:50:52.929 [4768] DEBUG - Ordered to stop server.
...
Jan 28, 2026 11:50:52.974 [2692] DEBUG - Stopping server...
...
Jan 28, 2026 11:50:53.240 [2692] DEBUG - Database: Shutting down.
Fanart error messages. These repeat many times. Not sure fanart.tv is the cause of your problems, but they’re in the log files several times, including before you shutdown Plex.
Jan 28, 2026 11:50:35.133 [7688] ERROR - [Req#a936] Timeout or error reading status line from plug-in pipe [com.plexapp.agents.fanarttv], we're killing it.
Jan 28, 2026 11:50:35.133 [7688] DEBUG - [Req#a936] Stopping [com.plexapp.agents.fanarttv].
Jan 28, 2026 11:50:35.133 [7688] DEBUG - [Req#a936] [com.plexapp.agents.fanarttv] Killing.
Jan 28, 2026 11:50:35.134 [7688] ERROR - [Req#a936] Error received reading configuration for com.plexapp.agents.fanarttv
Jan 28, 2026 11:50:35.134 [7688] DEBUG - [Req#a936] Stopping [com.plexapp.agents.fanarttv].
False Positive Examples
The developers changed something, but have not updated the log messages.
Jan 27, 2026 22:21:02.802 [16188] ERROR - [Req#ecd] Unknown metadata type: folder
Plex no longer uses client profile files, but still logs when one does not exist.
Jan 27, 2026 21:59:05.659 [14036] ERROR - [Req#ce6] Unable to find client profile for device; platform=Tizen, platformVersion=5, device=19_MUSEL_UHD_BASIC, model=UN58RU710DFXZA
Bad Problems
This is NOT from your server. Just an example.
Any ERROR message that says the database is corrupt or malformed.
Jul 05, 2020 19:36:56.959 [0x7f59f1b85740] ERROR - SQLITE3:(nil), 11, database corruption at line 64817 of [bf8c1b2b7a]
Jul 05, 2020 19:36:56.959 [0x7f59f1b85740] ERROR - SQLITE3:(nil), 11, statement aborts at 10: [select max(max(metadata_items.changed_at),max(metadata_items.resources_changed_at)) from metadata_items] database disk image is malformed
Jul 05, 2020 19:36:56.978 [0x7f59f1b85740] ERROR - Database corruption: sqlite3_statement_backend::loadOne: database disk image is malformed