Why does plex crash my server doing background maintenance tasks?

Plex Media Server
,
1

Server Version#: 1.31.2.6810-a607d384f

Player Version#: 1.66.1.3632-4d9c7716

Plex Pass User

This forum post explains what was going on.

This picture says it all: (After disabling plex… my rpi server does not have a reboot fit at the time period indicated below)

plexmaitenancesettings
plexmaitenancesettings747×669 43.8 KB

2

Could be this https://support.plex.tv/articles/credits-detection so I’d start by setting this to never and see if it helps.

Plex in their wisdom auto enabled this and it’s a highly intense task.

Also, full server logs might help if it’s not this.

3

Looks like you may be right because before the first reboot it was doing this:

Plex Software Devs / Engineers Please look into this.

Mar 26, 2023 02:15:00.710 [0x7f867430c8] DEBUG - [JobRunner] Jobs: Starting child process with pid 3452
Mar 26, 2023 02:15:15.829 [0x7f88f360c8] DEBUG - Jobs: '/usr/lib/plexmediaserver/Plex Media Scanner' exit code for process 3452 is 0 (success)
Mar 26, 2023 02:15:15.848 [0x7f867430c8] DEBUG - Activity: ended sub-activity 43df5d64-673b-46f1-a8fa-e03eaaab7acf parent: ee6102a8-840e-4dbb-b73a-0383112b821e overall progress: 100.0% (8/8)
Mar 26, 2023 02:15:15.849 [0x7f867430c8] DEBUG - Activity: updated activity ee6102a8-840e-4dbb-b73a-0383112b821e - completed 100.0% - Butler tasks
Mar 26, 2023 02:15:15.849 [0x7f867430c8] DEBUG - The butler performed deep analysis on 1 files
Mar 26, 2023 02:15:15.849 [0x7f867430c8] DEBUG - Activity: registered new sub-activity 29f6b870-a8b8-4c9e-9504-ff5eeb55c053 - "ButlerTaskGenerateCreditsMarkers" parent: ee6102a8-840e-4dbb-b73a-0383112b821e overall progress: 88.9% (8/9)
Mar 26, 2023 02:15:15.849 [0x7f867430c8] DEBUG - Activity: updated activity ee6102a8-840e-4dbb-b73a-0383112b821e - completed 88.9% - Butler tasks
Mar 26, 2023 02:15:15.850 [0x7f867430c8] DEBUG - Butler: Scheduling credits marker creation for: 3109
Mar 26, 2023 02:15:15.876 [0x7f867430c8] DEBUG - [CreditsDetectionManager] Running credits detection for item 3109
Mar 26, 2023 02:15:15.876 [0x7f867430c8] DEBUG - [CreditsDetectionManager] Activity: registered new activity 2d1e0408-74b2-439c-a8b0-417b72c7d35f - "Detecting Credits"
Mar 26, 2023 02:15:15.998 [0x7f867430c8] DEBUG - [CreditsDetectionManager/JobRunner] Job running: FFMPEG_EXTERNAL_LIBS='/var/lib/plexmediaserver/Library/Application\ Support/Plex\ Media\ Server/Codecs/2584b51-4483-linux-aarch64/' X_PLEX_TOKEN=xxxxxxxxxxxxxxxxxxxx "/usr/lib/plexmediaserver/Plex Media Scanner" -C -f "/media/extdrive/data/TvShows/omission " Credits"
Mar 26, 2023 02:15:16.001 [0x7f867430c8] DEBUG - [CreditsDetectionManager/JobRunner] Jobs: Starting child process with pid 3464
Mar 26, 2023 02:15:30.251 [0x7f848cc0c8] DEBUG - [NSB/SSDP] Parsing SSDP schema for http://169.254.34.37:50755/c967563c-4d61-436e-a11c-26e31eba2c57.xml
Mar 26, 2023 02:15:45.265 [0x7f86b510c8] DEBUG - [HttpClient/HCl#52] HTTP simulating 408 after curl timeout
Mar 26, 2023 02:16:15.818 [0x7f848cc0c8] DEBUG - [NSB/SSDP] Parsing SSDP schema for http://169.254.34.37:50755/c967563c-4d61-436e-a11c-26e31eba2c57.xml
Mar 26, 2023 02:16:30.833 [0x7f86b510c8] DEBUG - [HttpClient/HCl#53] HTTP simulating 408 after curl timeout
Mar 26, 2023 02:17:01.807 [0x7f848cc0c8] DEBUG - [NSB/SSDP] Parsing SSDP schema for http://169.254.34.37:50755/c967563c-4d61-436e-a11c-26e31eba2c57.xml
Mar 26, 2023 02:17:16.822 [0x7f86b510c8] DEBUG - [HttpClient/HCl#54] HTTP simulating 408 after curl timeout
Mar 26, 2023 02:17:50.931 [0x7f848cc0c8] DEBUG - [NSB/SSDP] Parsing SSDP schema for http://169.254.34.37:50755/c967563c-4d61-436e-a11c-26e31eba2c57.xm


infinite pts/0        24.141.35.254    Sun Mar 26 09:53   still logged in
infinite pts/0        24.141.35.254    Sun Mar 26 02:29 - 03:42  (01:12)
runlevel (to lvl 3)   6.1.19-v8+       Sun Mar 26 02:28   still running
reboot   system boot  6.1.19-v8+       Wed Dec 31 19:00   still running
infinite pts/0        24.141.35.254    Sun Mar 26 02:26 - crash (-19442+06:26)
runlevel (to lvl 3)   6.1.19-v8+       Sun Mar 26 02:23 - 02:28  (00:05)
reboot   system boot  6.1.19-v8+       Wed Dec 31 19:00   still running
infinite pts/0        24.141.35.254    Sun Mar 26 02:19 - crash (-19442+06:19)
**runlevel (to lvl 3)   6.1.19-v8+       Sun Mar 26 02:18 - 02:23  (00:04)**
reboot   system boot  6.1.19-v8+       Wed Dec 31 19:00   still running
infinite pts/0        24.141.35.254    Sun Mar 26 02:09 - crash (-19442+06:09)
runlevel (to lvl 3)   6.1.19-v8+       Sun Mar 26 02:04 - 02:18  (00:13)
reboot   system boot  6.1.19-v8+       Wed Dec 31 19:00   still running
infinite pts/1        24.141.35.254    Sun Mar 26 00:52 - crash (-19442+04:52)
infinite pts/0        24.141.35.254    Sat Mar 25 20:38 - crash (-19442+00:38)
infinite pts/0        24.141.35.254    Sat Mar 25 10:27 - 12:23  (01:56)

Logs to be PM’d

4

I can confirm the problem.

But the problem is really bad since the issue is escaping my Linux VM and causing the entire Proxmox node to freeze requiring a physical reboot of it.

I have now disabled credit scanning and it passed the other scheduled activities without any freeze.

6

Inherent bump for response.

7

you asked for the thread to be unlisted/hidden – not sure what response you expect if people can no longer see it (except yourself, mods and those who previously replied)

8

Is anyone interested in my logs?

11

I see there is a fix related to credit markers. For stability, I will not turn it back on after the latest update to 1.31.3.6868-28fc46b27. If there are any extensive logs needed let me know. This crash was pretty severe to not be caught by other standard logs implicitly. Including going over debug, syslog on top of what I shared in the first post on the raspberry pi forums.