Organizr: Kernel Crash - Unraid and Organizr Docker Container

Created on 10 Dec 2020  Â·  9Comments  Â·  Source: causefx/Organizr

Organizr Version: Latest version as of date of issue submission
Branch: Master
WebServer: Nginx
Operating System: Unraid (organizr/organizr:latest in docker container)

Problem Description:

Using this Docker Container is causing system instability and Kernel crash in Unraid OS frequently (about every 18-24 hours). I know this might be difficult to diagnose but myself and others have experienced this behavior and it has been tracked down to The Organizr docker container causing the instability. I do not know if this is something Unraid devs or Organizr devs can fix...but I am posting it here for tracking purposes for you guys.

Not all Unraid users are affected by this. Some have been able to achieve stability by changing appdata directory from /mnt/user/appdata/.....to /mnt/cache/appdata/.....

Further information found in these Unraid Forum Crash reports:
https://forums.unraid.net/topic/98455-strange-unraid-crashes-possibly-linked-to-a-docker/
https://forums.unraid.net/topic/99741-unraid-crashing-frequently/


Reproduction Steps:

Install Organizr docker container.....open the web UI. Leave it open. Monitor Unraid syslog for Kernel error/crash. I receive the crash anywhere from 18-24 hours after Organizr Docker container is active.


Errors on screen? If so paste here:


This is an example syslog showing the Unraid Kernel Crash. Something to do with php-fpm7. Let me know if you'd like additional information.

Dec 4 20:05:06 BEAST-UNRAID kernel: BUG: kernel NULL pointer dereference, address: 0000000000000402
Dec 4 20:05:06 BEAST-UNRAID kernel: #PF: supervisor read access in kernel mode
Dec 4 20:05:06 BEAST-UNRAID kernel: #PF: error_code(0x0000) - not-present page
Dec 4 20:05:06 BEAST-UNRAID kernel: PGD 0 P4D 0
Dec 4 20:05:06 BEAST-UNRAID kernel: Oops: 0000 [#1] SMP NOPTI
Dec 4 20:05:06 BEAST-UNRAID kernel: CPU: 1 PID: 19008 Comm: php-fpm7 Not tainted 5.8.18-Unraid #1
Dec 4 20:05:06 BEAST-UNRAID kernel: Hardware name: System manufacturer System Product Name/TUF GAMING X570-PLUS, BIOS 2816 11/24/2020
Dec 4 20:05:06 BEAST-UNRAID kernel: RIP: 0010:fuse_readahead+0x124/0x352
Dec 4 20:05:06 BEAST-UNRAID kernel: Code: 41 bd 01 00 00 00 41 8b 44 24 18 48 8d 74 02 ff e8 eb b3 16 00 41 8d 55 ff 48 85 c0 44 89 eb 0f 84 03 01 00 00 4b 89 44 ef f8 <48> 8b 10 41 8b 4c 24 1c 81 e2 00 00 01 00 48 83 fa 01 19 d2 81 e2
Dec 4 20:05:06 BEAST-UNRAID kernel: RSP: 0000:ffffc9000088bc50 EFLAGS: 00010202
Dec 4 20:05:06 BEAST-UNRAID kernel: RAX: 0000000000000402 RBX: 0000000000000001 RCX: 0000000000000000
Dec 4 20:05:06 BEAST-UNRAID kernel: RDX: 0000000000000000 RSI: ffff888ea29ad6d0 RDI: 0000000000000402
Dec 4 20:05:06 BEAST-UNRAID kernel: RBP: 0000000000000001 R08: 0000000000000402 R09: ffffc9000088bc60
Dec 4 20:05:06 BEAST-UNRAID kernel: R10: ffffc9000088bc60 R11: ffffc9000088bc60 R12: ffffc9000088bd68
Dec 4 20:05:06 BEAST-UNRAID kernel: R13: 0000000000000001 R14: ffff8885f74ecf00 R15: ffff888104343db0
Dec 4 20:05:06 BEAST-UNRAID kernel: FS: 00001549b406cd48(0000) GS:ffff888fee840000(0000) knlGS:0000000000000000
Dec 4 20:05:06 BEAST-UNRAID kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec 4 20:05:06 BEAST-UNRAID kernel: CR2: 0000000000000402 CR3: 000000064187e000 CR4: 0000000000340ee0
Dec 4 20:05:06 BEAST-UNRAID kernel: Call Trace:
Dec 4 20:05:06 BEAST-UNRAID kernel: read_pages+0x59/0x11f
Dec 4 20:05:06 BEAST-UNRAID kernel: ? 0xffffffff81000000
Dec 4 20:05:06 BEAST-UNRAID kernel: page_cache_readahead_unbounded+0x16e/0x19e
Dec 4 20:05:06 BEAST-UNRAID kernel: filemap_fault+0x264/0x441
Dec 4 20:05:06 BEAST-UNRAID kernel: __do_fault+0x49/0x64
Dec 4 20:05:06 BEAST-UNRAID kernel: handle_mm_fault+0xae0/0xe1a
Dec 4 20:05:06 BEAST-UNRAID kernel: exc_page_fault+0x298/0x40c
Dec 4 20:05:06 BEAST-UNRAID kernel: ? asm_exc_page_fault+0x8/0x30
Dec 4 20:05:06 BEAST-UNRAID kernel: asm_exc_page_fault+0x1e/0x30
Dec 4 20:05:06 BEAST-UNRAID kernel: RIP: 0033:0x5607eea40cc9
Dec 4 20:05:06 BEAST-UNRAID kernel: Code: 01 00 00 00 48 39 ca 0f 86 8f 04 00 00 e9 0b 6f 00 00 48 89 55 28 41 80 7f 01 3d 0f 85 f4 04 00 00 e9 ba 04 00 00 48 89 55 28 <41> 8a 47 01 3c 5f 0f 86 d7 04 00 00 e9 94 06 00 00 48 89 55 28 41
Dec 4 20:05:06 BEAST-UNRAID kernel: RSP: 002b:00007ffc2975d460 EFLAGS: 00010207
Dec 4 20:05:06 BEAST-UNRAID kernel: RAX: 00005607eebdb740 RBX: 00005607eecc9820 RCX: 00001549b2cce0db
Dec 4 20:05:06 BEAST-UNRAID kernel: RDX: 00001549b2ccd7fa RSI: 00001549b2cce0fb RDI: ffffffffffe65c55
Dec 4 20:05:06 BEAST-UNRAID kernel: RBP: 00005607eecc96c0 R08: 0000000000000000 R09: 00001549b26770a8
Dec 4 20:05:06 BEAST-UNRAID kernel: R10: 00005607eebdb740 R11: 00005607eea40cc5 R12: 00007ffc2975d5f8
Dec 4 20:05:06 BEAST-UNRAID kernel: R13: 00005607eebdb540 R14: 00000000000000e4 R15: 00001549b2ccd7f9
Dec 4 20:05:06 BEAST-UNRAID kernel: Modules linked in: macvlan xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat iptable_mangle ip6table_filter ip6_tables vhost_net tun vhost vhost_iotlb tap veth xt_nat iptable_filter xfs nfsd lockd grace sunrpc md_mod nct6775 hwmon_vid iptable_nat xt_MASQUERADE nf_nat ip_tables wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libblake2s blake2s_x86_64 libblake2s_generic libchacha bonding wmi_bmof edac_mce_amd kvm_amd kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper rapl k10temp i2c_piix4 i2c_core ccp r8169 ahci libahci realtek mpt3sas nvme raid_class scsi_transport_sas nvme_core button wmi acpi_cpufreq
Dec 4 20:05:06 BEAST-UNRAID kernel: CR2: 0000000000000402
Dec 4 20:05:06 BEAST-UNRAID kernel: ---[ end trace 416906022743205d ]---
Dec 4 20:05:06 BEAST-UNRAID kernel: RIP: 0010:fuse_readahead+0x124/0x352
Dec 4 20:05:06 BEAST-UNRAID kernel: Code: 41 bd 01 00 00 00 41 8b 44 24 18 48 8d 74 02 ff e8 eb b3 16 00 41 8d 55 ff 48 85 c0 44 89 eb 0f 84 03 01 00 00 4b 89 44 ef f8 <48> 8b 10 41 8b 4c 24 1c 81 e2 00 00 01 00 48 83 fa 01 19 d2 81 e2
Dec 4 20:05:06 BEAST-UNRAID kernel: RSP: 0000:ffffc9000088bc50 EFLAGS: 00010202
Dec 4 20:05:06 BEAST-UNRAID kernel: RAX: 0000000000000402 RBX: 0000000000000001 RCX: 0000000000000000
Dec 4 20:05:06 BEAST-UNRAID kernel: RDX: 0000000000000000 RSI: ffff888ea29ad6d0 RDI: 0000000000000402
Dec 4 20:05:06 BEAST-UNRAID kernel: RBP: 0000000000000001 R08: 0000000000000402 R09: ffffc9000088bc60
Dec 4 20:05:06 BEAST-UNRAID kernel: R10: ffffc9000088bc60 R11: ffffc9000088bc60 R12: ffffc9000088bd68
Dec 4 20:05:06 BEAST-UNRAID kernel: R13: 0000000000000001 R14: ffff8885f74ecf00 R15: ffff888104343db0
Dec 4 20:05:06 BEAST-UNRAID kernel: FS: 00001549b406cd48(0000) GS:ffff888fee840000(0000) knlGS:0000000000000000
Dec 4 20:05:06 BEAST-UNRAID kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec 4 20:05:06 BEAST-UNRAID kernel: CR2: 0000000000000402 CR3: 000000064187e000 CR4: 0000000000340ee0

Most helpful comment

Thank you for notifying us about a thread we already commented on.

All 9 comments

Thank you for notifying us about a thread we already commented on.

Please do not misunderstand....I did not post this here to throw any "shade" or anything of that sort. I apologize if it appears that way

I tried to say in my post.
"but I am posting it here for tracking purposes for you guys."

I really thought I was doing you guys a service. We can delete this if feel the need to.

There is nothing really for us to track, it's not something we deliberately do. I have found kernel commits that looks promising, gonna need to test the new RC to see what comes from it.

I was just commenting on the fact that we are aware of this, and have, and continue to look into it.

i'm thinking it is an issue with the kernel and maybe php. rod we should try upgrading the pho version on the container to see if it still happens.

We are using the same php as linuxserver, I doubt that's the problem

could be one of php’s dependencies

Sent from my iPhone

On Dec 10, 2020, at 5:19 PM, Roxedus notifications@github.com wrote:


We are using the same php as linuxserver, I doubt that's the problem

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Kernel in the RC seems to be working out.

Yay.....been on Unraid 6.9.0 RC2 for a few days now with Organizr Docker running. No crash.

is it safe to say that this has been resolved? If not please open again.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

jaydee99 picture jaydee99  Â·  6Comments

Ryonez picture Ryonez  Â·  6Comments

bbviking picture bbviking  Â·  3Comments

Cookie-Monster-Coder picture Cookie-Monster-Coder  Â·  5Comments

silentArtifact picture silentArtifact  Â·  3Comments