Plex server docker going offline (crash) multiple times a day.

Plex Media Server NAS & Devices
1

Started several days ago. UnRaid log snippet below saying plex docker is tainted. At present, I have deleted the docker container and recreated it fresh. Latest Plex Pass version. Today it lasted about 20 hours until I noticed it was down (i was not using it myself). There is a thread on UnRaid forum that is basically not getting any feedback due to this being a 3rd party app but it’s notable that the OS version updated to the current stable release roughly the same day as these problems appeared.

thread on limetech

(unraid server log snippet from most recent tonight)

Mar 17 20:50:36 Tower kernel: PGD 121027067 P4D 121027067 PUD 177b21067 PMD 0
Mar 17 20:50:36 Tower kernel: Oops: 0002 [#3] PREEMPT SMP NOPTI
Mar 17 20:50:36 Tower kernel: Modules linked in: xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat reiserfs md_mod edac_mce_amd kvm_amd kvm r8169 i2c_piix4 i2c_core crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper mii fam15h_power k10temp ahci cryptd libahci pata_atiixp arcmsr wmi_bmof wmi button acpi_cpufreq
Mar 17 20:50:36 Tower kernel: CPU: 2 PID: 2543 Comm: Plex Media Serv Tainted: G D 4.14.26-unRAID #1
Mar 17 20:50:36 Tower kernel: Hardware name: MSI MS-7641/760GMA-P34(FX) (MS-7641) , BIOS V25.0 05/28/2013
Mar 17 20:50:36 Tower kernel: task: ffff88010cacaa00 task.stack: ffffc90002828000
Mar 17 20:50:36 Tower kernel: RIP: 0010:tcp_push+0x4e/0xee
Mar 17 20:50:36 Tower kernel: RSP: 0018:ffffc9000282bc70 EFLAGS: 00010246
Mar 17 20:50:36 Tower kernel: RAX: 0000000000000000 RBX: 00000000000005a8 RCX: 0000000000000000
Mar 17 20:50:36 Tower kernel: RDX: 0000000000000000 RSI: 0000000000004040 RDI: ffff880408092800
Mar 17 20:50:36 Tower kernel: RBP: 0000000000000000 R08: 00000000000005a8 R09: ffffffff8151be00
Mar 17 20:50:36 Tower kernel: R10: ffff880408092958 R11: 0000000000000000 R12: ffff880408092800
Mar 17 20:50:36 Tower kernel: R13: 0000000000000000 R14: ffff880117e2a800 R15: 00000000ffffffe0
Mar 17 20:50:36 Tower kernel: FS: 000014f4f8fff700(0000) GS:ffff88040d080000(0000) knlGS:0000000000000000
Mar 17 20:50:36 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 17 20:50:36 Tower kernel: CR2: 0000000000000038 CR3: 00000001220be000 CR4: 00000000000406e0
Mar 17 20:50:36 Tower kernel: Call Trace:
Mar 17 20:50:36 Tower kernel: tcp_sendmsg_locked+0xa53/0xbac
Mar 17 20:50:36 Tower kernel: tcp_sendmsg+0x23/0x35
Mar 17 20:50:36 Tower kernel: sock_sendmsg+0x14/0x1e
Mar 17 20:50:36 Tower kernel: ___sys_sendmsg+0x1ab/0x229
Mar 17 20:50:36 Tower kernel: ? seccomp_run_filters+0xdc/0x106
Mar 17 20:50:36 Tower kernel: ? generic_file_read_iter+0x595/0x6e4
Mar 17 20:50:36 Tower kernel: ? __seccomp_filter+0x26/0x1c5
Mar 17 20:50:36 Tower kernel: ? __vfs_read+0xde/0x101
Mar 17 20:50:36 Tower kernel: ? __sys_sendmsg+0x3c/0x5d
Mar 17 20:50:36 Tower kernel: __sys_sendmsg+0x3c/0x5d
Mar 17 20:50:36 Tower kernel: do_syscall_64+0xfe/0x107
Mar 17 20:50:36 Tower kernel: entry_SYSCALL_64_after_hwframe+0x3d/0xa2
Mar 17 20:50:36 Tower kernel: RIP: 0033:0x14f505988a6d
Mar 17 20:50:36 Tower kernel: RSP: 002b:000014f4f8ffde10 EFLAGS: 00000293 ORIG_RAX: 000000000000002e
Mar 17 20:50:36 Tower kernel: RAX: ffffffffffffffda RBX: 000014f4f8ffde40 RCX: 000014f505988a6d
Mar 17 20:50:36 Tower kernel: RDX: 0000000000004000 RSI: 000014f4f8ffde40 RDI: 000000000000005b
Mar 17 20:50:36 Tower kernel: RBP: 000014f4f8ffde40 R08: 000014f4e10663d8 R09: 000014f4e10663e8
Mar 17 20:50:36 Tower kernel: R10: 0000000000000001 R11: 0000000000000293 R12: 000014f4f8fff5b8
Mar 17 20:50:36 Tower kernel: R13: 0000000000000001 R14: 0000000000000001 R15: 000014f4e10663d8
Mar 17 20:50:36 Tower kernel: Code: d0 75 02 31 c0 41 89 f3 41 81 e3 00 80 00 00 74 1a 44 8b 8f 68 05 00 00 41 d1 e9 44 2b 8f 6c 06 00 00 44 03 8f 74 06 00 00 79 10 <80> 48 38 08 8b 8f 6c 06 00 00 89 8f 74 06 00 00 40 80 e6 01 74
Mar 17 20:50:36 Tower kernel: RIP: tcp_push+0x4e/0xee RSP: ffffc9000282bc70
Mar 17 20:50:36 Tower kernel: CR2: 0000000000000038
Mar 17 20:50:36 Tower kernel: —[ end trace 00af71e0515f0d45 ]—
Mar 17 21:24:11 Tower nginx: 2018/03/17 21:24:11 [error] 8286#8286: *536216 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.26, server: , request: “POST /plugins/dynamix.docker.manager/include/Events.php HTTP/2.0”, upstream: “fastcgi://unix:/var/run/php5-fpm.sock”, host: “c660dbb7f4f305799046a5e90477700ce58c8c08.unraid.net”, referrer: “https://c660dbb7f4f305799046a5e90477700ce58c8c08.unraid.net/Docker”

2

I have the same exact problem lately.

3

Seems unRaid staff believe its a Linux issue and have a patch coming soon. Likely to be in the next 6.5.1 RC release (my guess). In the meantime, rolling back to 6.4.1 appears to get rid of the problem.

https://lime-technology.com/prerelease-support/same-call-trace-as-in-650-diagnostics-attached-r16/

4

I have this exact same issue with the PMS docker container on my Ubuntu 17.10 Server.

5

6.5.1-rc2 released today. Claims to solve this issue.

6

Upgrading to 6.5.1-rc2 seems to have fixed for me.

7

I will sign off on the fix once I pass the 72-hour mark. I have had it fail at 40 hours.