linuxserver / docker-plex

GNU General Public License v3.0
1.15k stars 204 forks source link

[BUG] Plex container causing server crashes daily #394

Closed joshsalvi closed 4 days ago

joshsalvi commented 3 months ago

Is there an existing issue for this?

Current Behavior

I am running the Plex docker container, latest version, on an Unraid system. I noticed that each day around 3am or so, the server crashes. When I enable everything OTHER than Plex, the server does not crash. I'm using ipvlan for my network, along with an Intel iGPU for hardware encoding. I also tried disabling a majority of the recurring tasks in Plex and it occurred again.

Any idea why this might be occurring?

image image

Expected Behavior

Server should not crash.

Steps To Reproduce

  1. Start Plex container
  2. Wait overnight
  3. Server crashes

Environment

Unraid
CA

CPU architecture

x86-64

Docker creation

Screenshots of settings are included above.

Container logs

[migrations] started
[migrations] no migrations found
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    99
User GID:    100
───────────────────────────────────────

**** Server already claimed ****
**** creating video group videokzwr with id 18 ****
**** adding /dev/dri/renderD128 to video group videokzwr with id 18 ****
**** permissions for /dev/dri/card0 are good ****
Docker is used for versioning skip update check
[custom-init] No custom files found, skipping...
Starting Plex Media Server. . . (you can ignore the libusb_init error)
[ls.io-init] done.
Critical: libusb_init failed
Connection to 45.56.104.126 closed by remote host.
Dolby, Dolby Digital, Dolby Digital Plus, Dolby TrueHD and the double D symbol are trademarks of Dolby Laboratories.
decoder information: 102
decoder information: 102
decoder information: 102
decoder information: 102
decoder information: 102
decoder information: 102
decoder information: 102
decoder information: 102
decoder information: 102
****** PLEX MEDIA SCANNER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.40.3.8555-fef15d30c/PLEX MEDIA SCANNER/1262db26-3a8f-4d85-82212d9f-9680de28.dmp
[migrations] started
[migrations] no migrations found
usermod: no changes
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    99
User GID:    100
───────────────────────────────────────

**** Server already claimed ****
**** permissions for /dev/dri/renderD128 are good ****
**** permissions for /dev/dri/card0 are good ****
Docker is used for versioning skip update check
[custom-init] No custom files found, skipping...
Starting Plex Media Server. . . (you can ignore the libusb_init error)
[ls.io-init] done.
Critical: libusb_init failed
github-actions[bot] commented 3 months ago

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

bhcompy commented 3 months ago

I've noticed what appears to be a memory leak in the container. Not sure if it's related to your crash, but the more uptime, the more ram it chews up. Restarting the container resets it back (we're talking creeping up to ~8gigs before it maxes out my server's open ram)

LinuxServer-CI commented 2 months ago

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.