# Plex crashed on Synology **URL:** \ **Category:** Plex Media Server\ **Tags:** server-synology\ **Created:** [February 25, 2023, 9:26pm UTC](https://forums.plex.tv/t/plex-crashed-on-synology/832414 "2023-02-25T21:26:55Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![wiifm](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/wiifm/32/153708_2.png) [@wiifm](https://forums.plex.tv/u/wiifm)\ **Post date:** [February 25, 2023, 9:26pm UTC](https://forums.plex.tv/t/plex-crashed-on-synology/832414/1 "2023-02-25T21:26:55Z")
NAS Model: DSM918+ DSM Version installed: DSM 7.1.1-42962 Update 4 Server Version#: 1.31.0.6654 Woke up this morning to Plex not working unsure exactly what caused it, downloaded the logs, and found some issues where the db might have been locked, unsure if this is the root cause or not. ```auto Feb 26, 2023 02:12:53.998 [0x7fd6f3fc1b38] WARN - Waited one whole second for a busy database. Feb 26, 2023 02:12:56.221 [0x7fd6f3fc1b38] WARN - Waited one whole second for a busy database. Feb 26, 2023 02:12:56.675 [0x7fd6f2541b38] DEBUG - Request: [192.168.1.188:60295 (Subnet)] GET /:/websockets/notifications (10 live) #42386f TLS GZIP Signed-in Token (wiifm) (Seans-MBP-2022.localdomain) Feb 26, 2023 02:12:56.675 [0x7fd6f2541b38] DEBUG - WebSocket: Performing handshake from origin file:// Feb 26, 2023 02:12:56.675 [0x7fd6f2541b38] DEBUG - Beginning read from WebSocket Feb 26, 2023 02:12:56.713 [0x7fd6f2541b38] DEBUG - Request: [192.168.1.188:60303 (Subnet)] GET /:/websockets/notifications?Accept-Language=en (11 live) #423870 TLS GZIP Signed-in Token (wiifm) (Seans-MBP-2022.localdomain) Feb 26, 2023 02:12:56.713 [0x7fd6f2541b38] DEBUG - WebSocket: Performing handshake from origin file:// Feb 26, 2023 02:12:56.714 [0x7fd6f2541b38] DEBUG - Beginning read from WebSocket Feb 26, 2023 02:12:56.732 [0x7fd6f2541b38] DEBUG - Request: [192.168.1.188:60305 (Subnet)] GET /activities (12 live) #423871 TLS GZIP Signed-in Token (wiifm) (Seans-MBP-2022.localdomain) Feb 26, 2023 02:12:56.733 [0x7fd71652bb38] DEBUG - Completed: [192.168.1.188:60305] 200 GET /activities (12 live) TLS GZIP 0ms 559 bytes (pipelined: 1) Feb 26, 2023 02:12:58.445 [0x7fd6f3fc1b38] WARN - Waited one whole second for a busy database. Feb 26, 2023 02:12:59.743 [0x7fd70f70cb38] DEBUG - NetworkServiceBrowser: Parsing SSDP schema for http://192.168.1.8:8080/upnp Feb 26, 2023 02:12:59.743 [0x7fd70f70cb38] DEBUG - [HCl#ea4b] HTTP requesting GET http://192.168.1.8:8080/upnp Feb 26, 2023 02:12:59.756 [0x7fd713d6fb38] DEBUG - [HttpClient/HCl#ea4b] HTTP/1.1 (0.0s) 404 response from GET http://192.168.1.8:8080/upnp Feb 26, 2023 02:12:59.756 [0x7fd70f70cb38] ERROR - SSDP: Error parsing device schema for http://192.168.1.8:8080/upnp Feb 26, 2023 02:13:00.669 [0x7fd6f3fc1b38] WARN - Waited one whole second for a busy database. Feb 26, 2023 02:13:02.893 [0x7fd6f3fc1b38] WARN - Waited one whole second for a busy database. Feb 26, 2023 02:13:05.117 [0x7fd6f3fc1b38] WARN - Waited one whole second for a busy database. Feb 26, 2023 02:13:07.340 [0x7fd6f3fc1b38] WARN - Waited one whole second for a busy database. Feb 26, 2023 02:13:09.562 [0x7fd6f3fc1b38] WARN - Waited one whole second for a busy database. Feb 26, 2023 02:13:10.769 [0x7fd6f3fc1b38] ERROR - Saving activity history aborted with soci exception: sqlite3_statement_backend::loadOne: database is locked Feb 26, 2023 02:13:10.769 [0x7fd6f3fc1b38] DEBUG - Activity: registered new activity ee011ed8-ae9c-48c3-a39b-2e223635d77b - "Updating Metadata" Feb 26, 2023 02:13:10.886 [0x7fd6f3fc1b38] DEBUG - [JobRunner] Job running: FFMPEG_EXTERNAL_LIBS='/var/packages/PlexMediaServer/shares/PlexMediaServer/AppData/Plex\ Media\ Server/Codecs/7e8dc7a-4467-linux-x86_64/' X_PLEX_TOKEN=xxxxxxxxxxxxxxxxxxxx "/volume1/@appstore/PlexMediaServer/Plex Media Scanner" --match --type 2 --log-file-suffix " Matcher" --item 29258 --match-tag-mode=all Feb 26, 2023 02:13:10.887 [0x7fd6f3fc1b38] DEBUG - [JobRunner] Jobs: Starting child process with pid 25996 Feb 26, 2023 02:13:11.121 [0x7fd6f3fc1b38] DEBUG - Killing job. Feb 26, 2023 02:13:11.121 [0x7fd6f3fc1b38] DEBUG - Signalling job ID 25996 with 9 Feb 26, 2023 02:13:11.121 [0x7fd716769b38] DEBUG - Jobs: '/volume1/@appstore/PlexMediaServer/Plex Media Scanner' exit code for process 25996 is 0 (success) ``` Full logs [Plex Media Server Logs\_2023-02-26\_09-26-21.zip](https://forums.plex.tv/uploads/short-url/nccnrnXmNrtuLTxXtIJNTF2XekQ.zip) (5.4 MB) ---
**Author:** ![trumpy81](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/trumpy81/32/189687_2.png) [@trumpy81](https://forums.plex.tv/u/trumpy81)\ **Post date:** [February 26, 2023, 7:14pm UTC](https://forums.plex.tv/t/plex-crashed-on-synology/832414/2 "2023-02-26T19:14:38Z")
I am also seeing this issue. Plex is crashing during maintenance. I have observed this on all of my servers. I have also observed: 1. Performing Refresh Metadata on my Movies library (6446 Movies) will cause the server to crash and stop running. 2. Opening and/or attempting to scroll through my Movies library may cause the server to crash and stop running. This applies to my DS1813+ (DSM7) mostly, but I have observed this behaviour on my DS1815+ (DSM6) NAS and my Windows 11 Pro PC as well. I have tried reverting to `PMS - 1.30.0.6406-f3f2fcc0a` and other versions on my DS1813+ (DSM7) NAS, but that resulted in being unable to run the server for more than a few minutes without a crash and the server stopping. I eventually restored `PMS - 1.31.1.6733-bc0674160` and now the server will run for more than a few minutes at least, but I still have the issues outlined above at points 1 & 2. I did `Optimise Database` and `Clean Bundles` on all servers before attempting to re-run Refresh Metadata on my Movies library, with little to no change in the outcome, although the PC succeeds now and no further crashes have been observed on the PC. All servers are running `PMS - 1.31.1.6733-bc0674160`. The logs below were captured after various crashes: DS1813+ (DSM7) Logs: 1. [Plex Media Server Logs\_2023-02-25\_05-22-02.zip](https://forums.plex.tv/uploads/short-url/32wzAoPVJKTPLFqfscDxVQ1Xi5y.zip) (1.8 MB) 2. [Plex Media Server Logs\_2023-02-27\_02-49-18.zip](https://forums.plex.tv/uploads/short-url/6FS3XYAqODxBWPgQGhR3SpVwi6a.zip) (3.6 MB) 3. [Plex Media Server Logs\_2023-02-27\_04-38-55.zip](https://forums.plex.tv/uploads/short-url/rJ4qj38iGEggdo1hsRFjlG41b3e.zip) (963.0 KB) 4. [Logs.zip](https://forums.plex.tv/uploads/short-url/yCBMW6vD5qoJqXJgCwvhYYciHZT.zip) (978.5 KB) DS1815+ (DSM6) Logs: 1. [Plex Media Server Logs\_2023-02-26\_09-47-22.zip](https://forums.plex.tv/uploads/short-url/3sLf75IOQMlsVmGe6f2qGEDJqEc.zip) (4.1 MB) 2. [Plex Media Server Logs\_2023-02-27\_04-27-12.zip](https://forums.plex.tv/uploads/short-url/hBMs19PmzO2lNCVrbBWiZtE5Jv4.zip) (1.1 MB) 3. [Plex Media Server Logs\_2023-02-27\_04-30-45.zip](https://forums.plex.tv/uploads/short-url/4sYLLrFTFa7cIlSAcchzm3pqY2B.zip) (3.3 MB) ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [February 26, 2023, 7:41pm UTC](https://forums.plex.tv/t/plex-crashed-on-synology/832414/3 "2023-02-26T19:41:04Z")
@wiifm You have (first) a network issue. It think it’s a Yo-Yo. ```auto %2Flibrary%2Fsections%2F1%2Fall%3Ftype%3D1%26sort%3Dyear%253Adesc%26label%3D89640' Feb 26, 2023 07:10:07.475 [0x7f43fc554aa0] DEBUG - [DatabaseFixups] Setting container serialization range to [0, 0] (total=-1) Feb 26, 2023 07:10:07.479 [0x7f43fc554aa0] DEBUG - [DatabaseFixups] Collections: Refreshed attributes for 0 collections in section 8 in 12ms. Feb 26, 2023 07:10:08.124 [0x7f43f5798b38] DEBUG - NetworkInterface: received Netlink message len=1224, type=RTM_NEWLINK, flags=0x0 Feb 26, 2023 07:10:08.124 [0x7f43f5798b38] DEBUG - NetworkInterface: Netlink information message family=0, type=1, index=8, flags=0x1002, change=0xffffffff Feb 26, 2023 07:10:08.124 [0x7f43f5798b38] DEBUG - Network change. Feb 26, 2023 07:10:08.124 [0x7f43f5798b38] DEBUG - NetworkInterface: Notified of network changed (force=0) Feb 26, 2023 07:10:08.124 [0x7f43f5798b38] DEBUG - Network change notification but nothing changed. Feb 26, 2023 07:10:08.124 [0x7f43f5798b38] DEBUG - NetworkInterface: received Netlink message len=1224, type=RTM_NEWLINK, flags=0x0 Feb 26, 2023 07:10:08.124 [0x7f43f5798b38] DEBUG - NetworkInterface: Netlink information message family=0, type=1, index=9, flags=0x1002, change=0xffffffff Feb 26, 2023 07:10:08.124 [0x7f43f5798b38] DEBUG - Network change. Feb 26, 2023 07:10:08.124 [0x7f43f5798b38] DEBUG - NetworkInterface: Notified of network changed (force=0) Feb 26, 2023 07:10:08.152 [0x7f43f5798b38] DEBUG - Network change notification but nothing changed. Feb 26, 2023 07:10:08.153 [0x7f43f5798b38] DEBUG - NetworkInterface: received Netlink message len=1224, type=RTM_NEWLINK, flags=0x0 Feb 26, 2023 07:10:08.153 [0x7f43f5798b38] DEBUG - NetworkInterface: Netlink information message family=0, type=1, index=9, flags=0x1002, change=0x0 Feb 26, 2023 07:10:08.153 [0x7f43f5798b38] DEBUG - Network change. Feb 26, 2023 07:10:08.153 [0x7f43f5798b38] DEBUG - NetworkInterface: Notified of network changed (force=0) Feb 26, 2023 07:10:08.153 [0x7f43f5798b38] DEBUG - Network change notification but nothing changed. Feb 26, 2023 07:10:08.153 [0x7f43f5798b38] DEBUG - NetworkInterface: received Netlink message len=1444, type=RTM_NEWLINK, flags=0x0 Feb 26, 2023 07:10:08.153 [0x7f43f5798b38] DEBUG - NetworkInterface: Netlink information message family=0, type=1, index=9, flags=0x1002, change=0x0 Feb 26, 2023 07:10:08.153 [0x7f43f5798b38] DEBUG - Network change. Feb 26, 2023 07:10:08.153 [0x7f43f5798b38] DEBUG - NetworkInterface: Notified of network changed (force=0) Feb 26, 2023 07:10:08.153 [0x7f43f5798b38] DEBUG - Network change notification but nothing changed. Feb 26, 2023 07:10:08.153 [0x7f43f5798b38] DEBUG - NetworkInterface: received Netlink message len=1444, type=RTM_NEWLINK, flags=0x0 Feb 26, 2023 07:10:08.153 [0x7f43f5798b38] DEBUG - NetworkInterface: Netlink information message family=0, type=1, index=9, flags=0x1002, change=0x100 Feb 26, 2023 07:10:08.153 [0x7f43f5798b38] DEBUG - Network change. Feb 26, 2023 07:10:08.153 [0x7f43f5798b38] DEBUG - NetworkInterface: Notified of network changed (force=0) Feb 26, 2023 07:10:08.154 [0x7f43f5798b38] DEBUG - Network change notification but nothing changed. Feb 26, 2023 07:10:08.154 [0x7f43f5798b38] DEBUG - NetworkInterface: received Netlink message len=296, type=RTM_NEWLINK, flags=0x0 Feb 26, 2023 07:10:08.154 [0x7f43f5798b38] DEBUG - NetworkInterface: Netlink information message family=7, type=1, index=9, flags=0x1002, change=0x0 Feb 26, 2023 07:10:08.154 [0x7f43f5798b38] DEBUG - Network change. Feb 26, 2023 07:10:08.154 [0x7f43f5798b38] DEBUG - NetworkInterface: Notified of network changed (force=0) Feb 26, 2023 07:10:08.154 [0x7f43f5798b38] DEBUG - Network change notification but nothing changed. Feb 26, 2023 07:10:08.154 [0x7f43f5798b38] DEBUG - NetworkInterface: received Netlink message len=1444, type=RTM_NEWLINK, flags=0x0 Feb 26, 2023 07:10:08.154 [0x7f43f5798b38] DEBUG - NetworkInterface: Netlink information message family=0, type=1, index=9, flags=0x1003, change=0x1 Feb 26, 2023 07:10:08.154 [0x7f43f5798b38] DEBUG - Network change. Feb 26, 2023 07:10:08.154 [0x7f43f5798b38] DEBUG - NetworkInterface: Notified of network changed (force=0) Feb 26, 2023 07:10:08.155 [0x7f43f5798b38] DEBUG - Network change notification but nothing changed. Feb 26, 2023 07:10:08.155 [0x7f43f5798b38] DEBUG - NetworkInterface: received Netlink message len=296, type=RTM_NEWLINK, flags=0x0 Feb 26, 2023 07:10:08.155 [0x7f43f5798b38] DEBUG - NetworkInterface: Netlink information message family=7, type=1, index=9, flags=0x1003, change=0x0 Feb 26, 2023 07:10:08.155 [0x7f43f5798b38] DEBUG - Network change. Feb 26, 2023 07:10:08.155 [0x7f43f5798b38] DEBUG - NetworkInterface: Notified of network changed (force=0) Feb 26, 2023 07:10:08.155 [0x7f43f5798b38] DEBUG - Network change notification but nothing changed. ``` and again ```auto Feb 26, 2023 07:10:17.394 [0x7f43facf8b38] DEBUG - Request: [192.168.1.1:61272 (Subnet)] GET /status/sessions (4 live) #56 TLS GZIP Signed-in Token (wiifm) (Seans-MBP-2022.localdomain) Feb 26, 2023 07:10:17.394 [0x7f43facf8b38] DEBUG - [Req#56] [Now] Adding 0 sessions. Feb 26, 2023 07:10:17.395 [0x7f43fbe69b38] DEBUG - Completed: [192.168.1.1:61272] 200 GET /status/sessions (4 live) TLS GZIP 1ms 350 bytes (pipelined: 2) Feb 26, 2023 07:10:17.396 [0x7f43f5798b38] DEBUG - Network change notification but nothing changed. Feb 26, 2023 07:10:17.396 [0x7f43f5798b38] DEBUG - NetworkInterface: received Netlink message len=1444, type=RTM_NEWLINK, flags=0x0 Feb 26, 2023 07:10:17.396 [0x7f43f5798b38] DEBUG - NetworkInterface: Netlink information message family=0, type=1, index=11, flags=0x1002, change=0x0 Feb 26, 2023 07:10:17.396 [0x7f43f5798b38] DEBUG - Network change. Feb 26, 2023 07:10:17.396 [0x7f43f5798b38] DEBUG - NetworkInterface: Notified of network changed (force=0) Feb 26, 2023 07:10:17.397 [0x7f43f5798b38] DEBUG - Network change notification but nothing changed. Feb 26, 2023 07:10:17.397 [0x7f43f5798b38] DEBUG - NetworkInterface: received Netlink message len=1444, type=RTM_NEWLINK, flags=0x0 Feb 26, 2023 07:10:17.397 [0x7f43f5798b38] DEBUG - NetworkInterface: Netlink information message family=0, type=1, index=11, flags=0x1002, change=0x100 Feb 26, 2023 07:10:17.397 [0x7f43f5798b38] DEBUG - Network change. Feb 26, 2023 07:10:17.397 [0x7f43f5798b38] DEBUG - NetworkInterface: Notified of network changed (force=0) Feb 26, 2023 07:10:17.397 [0x7f43f5798b38] DEBUG - Network change notification but nothing changed. Feb 26, 2023 07:10:17.397 [0x7f43f5798b38] DEBUG - NetworkInterface: received Netlink message len=296, type=RTM_NEWLINK, flags=0x0 Feb 26, 2023 07:10:17.397 [0x7f43f5798b38] DEBUG - NetworkInterface: Netlink information message family=7, type=1, index=11, flags=0x1002, change=0x0 Feb 26, 2023 07:10:17.397 [0x7f43f5798b38] DEBUG - Network change. Feb 26, 2023 07:10:17.397 [0x7f43f5798b38] DEBUG - NetworkInterface: Notified of network changed (force=0) Feb 26, 2023 07:10:17.400 [0x7f43f83c1b38] DEBUG - Request: [192.168.1.1:61272 (Subnet)] GET /updater/status (4 live) #5a TLS GZIP Signed-in Token (wiifm) (Seans-MBP-2022.localdomain) Feb 26, 2023 07:10:17.401 [0x7f43fbe69b38] DEBUG - Completed: [192.168.1.1:61272] 200 GET /updater/status (4 live) TLS GZIP 0ms 433 bytes (pipelined: 3) Feb 26, 2023 07:10:17.408 [0x7f43facf8b38] DEBUG - Request: [192.168.1.1:61273 (Subnet)] GET /:/websockets/notifications (5 live) #53 TLS GZIP Signed-in Token (wiifm) (Seans-MBP-2022.localdomain) Feb 26, 2023 07:10:17.408 [0x7f43facf8b38] DEBUG - WebSocket: Performing handshake from origin file:// Feb 26, 2023 07:10:17.409 [0x7f43facf8b38] DEBUG - Beginning read from WebSocket Feb 26, 2023 07:10:17.409 [0x7f43f5798b38] DEBUG - Network change notification but nothing changed. Feb 26, 2023 07:10:17.409 [0x7f43f5798b38] DEBUG - NetworkInterface: received Netlink message len=1444, type=RTM_NEWLINK, flags=0x0 Feb 26, 2023 07:10:17.409 [0x7f43f5798b38] DEBUG - NetworkInterface: Netlink information message family=0, type=1, index=11, flags=0x1003, change=0x1 Feb 26, 2023 07:10:17.409 [0x7f43f5798b38] DEBUG - Network change. Feb 26, 2023 07:10:17.409 [0x7f43f5798b38] DEBUG - NetworkInterface: Notified of network changed (force=0) Feb 26, 2023 07:10:17.409 [0x7f43f5798b38] DEBUG - Network change notification but nothing changed. Feb 26, 2023 07:10:17.409 [0x7f43f5798b38] DEBUG - NetworkInterface: received Netlink message len=296, type=RTM_NEWLINK, flags=0x0 Feb 26, 2023 07:10:17.409 [0x7f43f5798b38] DEBUG - NetworkInterface: Netlink information message family=7, type=1, index=11, flags=0x1003, change=0x0 Feb 26, 2023 07:10:17.409 [0x7f43f5798b38] DEBUG - Network change. Feb 26, 2023 07:10:17.409 [0x7f43f5798b38] DEBUG - NetworkInterface: Notified of network changed (force=0) Feb 26, 2023 07:10:17.410 [0x7f43f5798b38] DEBUG - Network change notification but nothing changed. Feb 26, 2023 07:10:17.453 [0x7f43f923bb38] DEBUG - [HttpClient/HCl#38] HTTP/1.1 (0.3s) 200 response from GET ht ``` Bad / loose cable ? DHCP server settings (Lease time value too short) ? ---
**Author:** ![wiifm](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/wiifm/32/153708_2.png) [@wiifm](https://forums.plex.tv/u/wiifm)\ **Post date:** [February 26, 2023, 10:15pm UTC](https://forums.plex.tv/t/plex-crashed-on-synology/832414/4 "2023-02-26T22:15:08Z")
The only application not working on the Synology was Plex (other apps and docker containers were fine). Checking Unifi client connections for the NAS (which would list event such as reconnections etc) only shows the last time I unplugged the NAS. ![synology](https://global.discourse-cdn.com/plex/original/4X/1/d/3/1d3df954885eed29e9b1aa908bbcc7d62781022e.png) Checking DSM logs, I see the upgrade DSM on the 17th, and then my reboot to “fix” Plex at 7:05. ![dsm](https://global.discourse-cdn.com/plex/original/4X/5/2/4/5248717914665b8a921c5db58087e3b2d1fa1112.png) I suspect the logs you saw in Plex, are due to the DSM reboot 5 minutes prior. Plex was dead prior to the reboot. ---
**Author:** ![trumpy81](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/trumpy81/32/189687_2.png) [@trumpy81](https://forums.plex.tv/u/trumpy81)\ **Post date:** [February 26, 2023, 10:27pm UTC](https://forums.plex.tv/t/plex-crashed-on-synology/832414/5 "2023-02-26T22:27:54Z")
After some back and forth with Chuck in PM and using his DB repair tool, it appears that I have my library scrolling/crashing issues sorted. I will wait to see if the server crashes during maintenance again, fingers crossed it does not. Spoke too soon, Plex still crashes when trying to Refresh Metadata on my Movies library. ---
**Author:** ![wiifm](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/wiifm/32/153708_2.png) [@wiifm](https://forums.plex.tv/u/wiifm)\ **Post date:** [February 26, 2023, 10:44pm UTC](https://forums.plex.tv/t/plex-crashed-on-synology/832414/6 "2023-02-26T22:44:53Z")
FWIW, I use [PlexMetaManager](https://github.com/meisnate12/Plex-Meta-Manager) and it does use the Plex API heavily. ---
**Author:** ![trumpy81](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/trumpy81/32/189687_2.png) [@trumpy81](https://forums.plex.tv/u/trumpy81)\ **Post date:** [February 26, 2023, 11:57pm UTC](https://forums.plex.tv/t/plex-crashed-on-synology/832414/7 "2023-02-26T23:57:05Z")
Thanks for that, but I have little need for such a tool. The only metadata manipulation I use is to add my own posters to all of my Movies, hence the need to Refresh Metadata after updating all of my posters. I did notice in your log snippet above that an invalid IP address was assigned (169.254.211.59). That may be due to your use of NoIP though. That may relate to the network errors that Chuck pointed out, but probably not related to the server crash. From your logs: ```auto Feb 26, 2023 07:13:45.945 [0x7f43f965ab38] ERROR - [Req#1d6] Couldn't check for the existence of file "/volume1/Downloads/Preroll/Plex1080.mp4": boost::filesystem::status: Permission denied: "/volume1/Downloads/Preroll/Plex1080.mp4" ``` That would not help and Plex should not crash because of it, but worth checking out and correcting just the same. ```auto Feb 26, 2023 01:29:37.777 [0x7fd6f3fc1b38] ERROR - [CreditsDetectionManager] Mis-matching media items detected, skipping Feb 26, 2023 01:29:38.758 [0x7fd6f3fc1b38] ERROR - [CreditsDetectionManager] BufferingLineReader: failed to read line (error: -1) Feb 26, 2023 01:29:38.759 [0x7fd6f3fc1b38] ERROR - [CreditsDetectionManager] Job failed: Decryption failed ``` These errors seem more like the actual cause of the crash, although that is not definitive. Unless you use Credit Detection, I would recommend you disable it in `Plex Settings > Library > Generate credits video markers` and see if the server crashes during maintenance again. ---
**Author:** ![wiifm](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/wiifm/32/153708_2.png) [@wiifm](https://forums.plex.tv/u/wiifm)\ **Post date:** [February 27, 2023, 12:31am UTC](https://forums.plex.tv/t/plex-crashed-on-synology/832414/8 "2023-02-27T00:31:25Z")
Removed the preroll setting. As for the credit detection, this is quite new, and seems to be of some use in TV shows, I would prefer it to leave enabled if possible. I checked on the maintenance time ![maintenance](https://global.discourse-cdn.com/plex/original/4X/2/7/3/2731dc3c50d62274ff6a720a7a35d53da9fc8d11.png) And it does fit within when I expect Plex actually crashed. ---
**Author:** ![trumpy81](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/trumpy81/32/189687_2.png) [@trumpy81](https://forums.plex.tv/u/trumpy81)\ **Post date:** [February 27, 2023, 12:41am UTC](https://forums.plex.tv/t/plex-crashed-on-synology/832414/9 "2023-02-27T00:41:12Z")
Yes, I also saw server crashes within the maintenance times, which is why I suspect you have a similar issue. If you can disable Credit Detection for a day or two just to confirm it is the cause of the server crash or not, that would suffice. Needless to say, I do not have Credit Detection enabled on any of my servers at all, but I have still seen crashing during maintenance, so it may not be the cause at all. ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [February 27, 2023, 2:28am UTC](https://forums.plex.tv/t/plex-crashed-on-synology/832414/10 "2023-02-27T02:28:57Z")
As usual, Trumpy has more problems than the rest of us 🤣😛 (Welcome back OLD friend… LOLOL) I’m working with him in PM to figure out the root cause. I’ll post here when we resolve it. ---
**Author:** ![trumpy81](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/trumpy81/32/189687_2.png) [@trumpy81](https://forums.plex.tv/u/trumpy81)\ **Post date:** [February 27, 2023, 3:45am UTC](https://forums.plex.tv/t/plex-crashed-on-synology/832414/11 "2023-02-27T03:45:23Z")
Maybe I should rename my user to ProblemChild … lol 😛 Still having a ton of issues here and no resolutions so far ☹ ---
**Author:** ![trumpy81](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/trumpy81/32/189687_2.png) [@trumpy81](https://forums.plex.tv/u/trumpy81)\ **Post date:** [March 24, 2023, 8:02pm UTC](https://forums.plex.tv/t/plex-crashed-on-synology/832414/12 "2023-03-24T20:02:03Z")
Still having an issue with Plex running on my DS1813+ (DSM 7.1.1-42962 Update 4) NAS, it sometimes crashes soon after maintenance starts at 2am and will crash if I scroll through my Movies library too quickly (6446 Movies). My DS1815+ (DSM 6.2.4-25556 Update 6) NAS still crashes when quickly scrolling through the Movies library (6446 Movies). It has not crashed during maintenance for some time though. My Windows 11 Pro 22H2 build 22621.1413 machine does not seem to be having any issues ATM. Plex version 1.31.3.6819 running on all machines. Latest logs DSM 7 - [Plex Media Server Logs\_2023-03-25\_05-43-05.zip](https://forums.plex.tv/uploads/short-url/vZOjTAsWwGOGeUIjkFSGMcnyqGo.zip) (3.4 MB) DSM 6 - [Plex Media Server Logs\_2023-03-25\_05-56-23.zip](https://forums.plex.tv/uploads/short-url/bgfnXdKVzWqukAupEIn9hOCxoEl.zip) (2.8 MB) . ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [March 24, 2023, 9:28pm UTC](https://forums.plex.tv/t/plex-crashed-on-synology/832414/13 "2023-03-24T21:28:02Z")
I’m trying to figure out what the problem is. I have PMS running on the DS1815+ (DSM 6) and DS418play (DSM 7) without crashing. I haven’t found the trigger. ---
**Author:** ![trumpy81](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/trumpy81/32/189687_2.png) [@trumpy81](https://forums.plex.tv/u/trumpy81)\ **Post date:** [March 27, 2023, 9:31pm UTC](https://forums.plex.tv/t/plex-crashed-on-synology/832414/14 "2023-03-27T21:31:52Z")
I just installed PlexMediaServer-1.31.3.6868-28fc46b27-x86\_64\_DSM7 on the DS1813+ & DS1815+. So far I do not seem to have any issues on the DS1815+ (DSM 6), but the DS1813+ (DSM 7) is constantly crashing when trying to navigate any of my Movies type libraries. I cannot scroll through the libraries slowly or quickly, without the server crashing and stopping. I tried rolling back to PlexMediaServer-1.31.3.6819-2ef591a4c-x86\_64\_DSM7, but that also caused a crash. I reinstalled PlexMediaServer-1.31.3.6868-28fc46b27-x86\_64\_DSM7 and then optimised the DB and cleaned bundles, but that does not seem to have had any effect. The DB should be clean and in working condition after running it through Chuck’s DB Tool, so I do NOT think the issue is DB related. The server appears to crash when attempting to display the posters in my library. The logs do NOT show any clues to the issue, they simply stop at the time of the crash. I did spot this though: ```auto Mar 28, 2023 07:05:37.807 [0x7ff8cf5e8aa8] ERROR - Error creating directory "/transcode": Permission denied ``` That might explain the issue when attempting to transcode the images for display in Plex/Web? Anyhow, here are the logs: [Plex Media Server Logs\_2023-03-28\_07-17-52.zip](https://forums.plex.tv/uploads/short-url/9jfDR4QkP8549etCwXvAG2i9vbr.zip) (985.5 KB) I found some .dmp files in the /tmp directory on the DS1813+ and opened one of them in WinDbg and got the following: ```auto Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [\\PlexStation\PlexMediaServer\AppData\tmp\f702997a-3c62-4c6b-345c5583-faea4d50.dmp] User Mini Dump File: Only registers, stack and portions of memory are available Symbol search path is: srv* Executable search path is: Generic Unix Version 0 (Linux 3.10.108 #42962 SMP Tue Oct 18 15:04:45 CST 2022 x86_64) MP (4 procs) Free x64 Machine Name: Debug session time: Tue Mar 7 02:35:25.000 2023 (UTC + 10:00) System Uptime: not available Process Uptime: not available ................................................................ .... This dump file has an exception of interest stored in it. The stored exception information can be accessed via .ecxr. (f0f0f0f0.1a4): Unknown exception - code 0000000b (first/second chance not available) For analysis of this file, run !analyze -v *** WARNING: Unable to verify timestamp for libfreeimage.so libfreeimage+0x31c388: 00007f84`6b313388 0fb606 movzx eax,byte ptr [rsi] ds:00007f84`669b1688=?? ``` I get the same error from all .dmp files I have opened so far, so that seems to point to the issue being in the libfreeimage library. ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [March 27, 2023, 9:52pm UTC](https://forums.plex.tv/t/plex-crashed-on-synology/832414/15 "2023-03-27T21:52:39Z")
> [@trumpy81](#): > > ```auto > Mar 28, 2023 07:05:37.807 [0x7ff8cf5e8aa8] ERROR - Error creating directory "/transcode": Permission denied > > ``` The transcoder directory is in / ? on the syno? Shouldn’t it be in `/volumeX//transcode` ? In a container, `/transcode` is legitimate because `/transcode` maps to /volumeX/something/transcode – right? Looking at the rest now ---
**Author:** ![trumpy81](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/trumpy81/32/189687_2.png) [@trumpy81](https://forums.plex.tv/u/trumpy81)\ **Post date:** [March 27, 2023, 9:54pm UTC](https://forums.plex.tv/t/plex-crashed-on-synology/832414/16 "2023-03-27T21:54:45Z")
The only place I have a Transcode folder is in: \\PlexStation\PlexMediaServer\AppData\tmp\Transcode So that may be a red herring, as I have not created that folder at all. ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [March 27, 2023, 9:55pm UTC](https://forums.plex.tv/t/plex-crashed-on-synology/832414/17 "2023-03-27T21:55:27Z")
Right. That’s the default location. Remove `/transcode` from Settings - Server - Transcoder - Show Advanced. 🙂 ---
**Author:** ![trumpy81](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/trumpy81/32/189687_2.png) [@trumpy81](https://forums.plex.tv/u/trumpy81)\ **Post date:** [March 27, 2023, 9:56pm UTC](https://forums.plex.tv/t/plex-crashed-on-synology/832414/18 "2023-03-27T21:56:02Z")
done! If it is any consolation, the Transcode folder has a folder named Sessions in it and nothing else. ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [March 27, 2023, 9:56pm UTC](https://forums.plex.tv/t/plex-crashed-on-synology/832414/19 "2023-03-27T21:56:47Z")
Restart … Wait for next puff of blue smoke. ---
**Author:** ![trumpy81](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/trumpy81/32/189687_2.png) [@trumpy81](https://forums.plex.tv/u/trumpy81)\ **Post date:** [March 27, 2023, 9:59pm UTC](https://forums.plex.tv/t/plex-crashed-on-synology/832414/20 "2023-03-27T21:59:46Z")
Restarted Plex, entered Movies library, scrolled down once and then crash, so that did not help ☹ [Next page](https://forums.plex.tv/t/plex-crashed-on-synology/832414.md?page=2)