January 8, 20179 yr Greeting, I've been having issues for the last 2 weeks with Unraid where it will freeze randomly and starting to refuse all connections. I've ran MemTest 1 pass without errors. I've tested using a brand new USB drive but it froze too. Unraid version: 6.2.4 Hardware: Asus P5Q Pro Intel q9550 8GB Kingstom Ram Intel Pro1000/PT dual port Intel Desktop CT HDDs: 4 x Seagate ST3000VN000 1 x WD WD30EFRX 1 x Samsung SSD 850 Evo 120G Here is the last error I got: Jan 8 13:54:34 RServer kernel: general protection fault: 0000 [#1] PREEMPT SMP Jan 8 13:54:34 RServer kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables vhost_net tun vhost macvtap macvlan xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod bonding coretemp kvm_intel kvm i2c_i801 i2c_core intel_agp e1000e atl1e ptp ata_piix intel_gtt pps_core agpgart asus_atk0110 acpi_cpufreq [last unloaded: md_mod] Jan 8 13:54:34 RServer kernel: CPU: 0 PID: 22904 Comm: qemu-system-x86 Tainted: G W 4.4.30-unRAID #2 Jan 8 13:54:34 RServer kernel: Hardware name: System manufacturer System Product Name/P5Q-PRO, BIOS 2002 02/23/2009 Jan 8 13:54:34 RServer kernel: task: ffff880164bdb700 ti: ffff8801decd0000 task.ti: ffff8801decd0000 Jan 8 13:54:34 RServer kernel: RIP: 0010:[<ffffffff81044ff3>] [<ffffffff81044ff3>] gup_huge_pmd+0xa7/0xe3 Jan 8 13:54:34 RServer kernel: RSP: 0018:ffff8801decd39b0 EFLAGS: 00010002 Jan 8 13:54:34 RServer kernel: RAX: ffffea0004548000 RBX: 00003fffffe00000 RCX: ffffea000454f640 Jan 8 13:54:34 RServer kernel: RDX: 00002b3bd93da000 RSI: 00002b3bd93d9000 RDI: ff5eea0004548000 Jan 8 13:54:34 RServer kernel: RBP: ffff8801decd39c0 R08: ffff8801decd3aa0 R09: ffff8801decd3a4c Jan 8 13:54:34 RServer kernel: R10: 0000000000000000 R11: ff5eea0004548001 R12: 0000000000000080 Jan 8 13:54:34 RServer kernel: R13: 00002b3bd93da000 R14: ffff8801decd3aa0 R15: ffff8801decd3a4c Jan 8 13:54:34 RServer kernel: FS: 00002b3b39213700(0000) GS:ffff88022fc00000(0000) knlGS:fffff80359f5d000 Jan 8 13:54:34 RServer kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jan 8 13:54:34 RServer kernel: CR2: 0000022c3b04aff0 CR3: 00000000a88df000 CR4: 00000000000426f0 Jan 8 13:54:34 RServer kernel: Stack: Jan 8 13:54:34 RServer kernel: 00002b3bd93da000 00002b3bd93da000 ffff8801decd3a20 ffffffff810453a7 Jan 8 13:54:34 RServer kernel: 00002b3bd93d9fff 00002b3bd93d9fff ffff8800a97d6648 ffff8800b1105778 Jan 8 13:54:34 RServer kernel: 0000000100000000 00002b3bd93da000 00002b3bd93da000 ffff8800a88df2b0 Jan 8 13:54:34 RServer kernel: Call Trace: Jan 8 13:54:34 RServer kernel: [<ffffffff810453a7>] gup_pud_range+0x18c/0x1d6 Jan 8 13:54:34 RServer kernel: [<ffffffff810454c3>] __get_user_pages_fast+0xd2/0x101 Jan 8 13:54:34 RServer kernel: [<ffffffffa0119f93>] __gfn_to_pfn_memslot+0xce/0x30f [kvm] Jan 8 13:54:34 RServer kernel: [<ffffffffa012e250>] ? mmu_set_spte+0x21e/0x22d [kvm] Jan 8 13:54:34 RServer kernel: [<ffffffffa011a241>] gfn_to_pfn_memslot_atomic+0x19/0x1b [kvm] Jan 8 13:54:34 RServer kernel: [<ffffffffa0129f37>] pte_prefetch_gfn_to_pfn+0x2a/0x2d [kvm] Jan 8 13:54:34 RServer kernel: [<ffffffffa012e95a>] paging64_prefetch_gpte.part.52+0x57/0x9c [kvm] Jan 8 13:54:34 RServer kernel: [<ffffffffa0130118>] paging64_page_fault+0x689/0x6da [kvm] Jan 8 13:54:34 RServer kernel: [<ffffffffa0130d6c>] ? kvm_mmu_new_cr3+0x9/0xb [kvm] Jan 8 13:54:34 RServer kernel: [<ffffffffa012bd9d>] kvm_mmu_page_fault+0x20/0xe2 [kvm] Jan 8 13:54:34 RServer kernel: [<ffffffffa0277aee>] handle_exception+0x15b/0x324 [kvm_intel] Jan 8 13:54:34 RServer kernel: [<ffffffffa027d63f>] vmx_handle_exit+0xfbb/0x1053 [kvm_intel] Jan 8 13:54:34 RServer kernel: [<ffffffffa027f105>] ? vmx_vcpu_run+0x30e/0x31d [kvm_intel] Jan 8 13:54:34 RServer kernel: [<ffffffffa0127f92>] kvm_arch_vcpu_ioctl_run+0x38a/0x1080 [kvm] Jan 8 13:54:34 RServer kernel: [<ffffffffa0122a00>] ? kvm_arch_vcpu_load+0x133/0x16c [kvm] Jan 8 13:54:34 RServer kernel: [<ffffffffa0118cff>] kvm_vcpu_ioctl+0x178/0x499 [kvm] Jan 8 13:54:34 RServer kernel: [<ffffffffa011b152>] ? kvm_vm_ioctl+0x3e8/0x5d8 [kvm] Jan 8 13:54:34 RServer kernel: [<ffffffffa0118b88>] ? kvm_vcpu_ioctl+0x1/0x499 [kvm] Jan 8 13:54:34 RServer kernel: [<ffffffff8111869e>] do_vfs_ioctl+0x3a3/0x416 Jan 8 13:54:34 RServer kernel: [<ffffffff8112070e>] ? __fget+0x72/0x7e Jan 8 13:54:34 RServer kernel: [<ffffffff8111874f>] SyS_ioctl+0x3e/0x5c Jan 8 13:54:34 RServer kernel: [<ffffffff81629c2e>] entry_SYSCALL_64_fastpath+0x12/0x6d Jan 8 13:54:34 RServer kernel: Code: 48 c1 e8 06 48 01 f8 48 01 c1 49 63 39 49 89 0c f8 48 8b 79 20 40 80 e7 01 74 23 4c 8b 59 20 49 8d 7b ff 41 80 e3 01 48 0f 44 f9 <f6> 47 08 01 74 0d 48 8b 3f 40 80 e7 80 75 04 f0 ff 41 18 48 81 Jan 8 13:54:34 RServer kernel: RIP [<ffffffff81044ff3>] gup_huge_pmd+0xa7/0xe3 Jan 8 13:54:34 RServer kernel: RSP <ffff8801decd39b0> Jan 8 13:54:34 RServer kernel: ---[ end trace 5d6e418e0e1a03e3 ]--- Jan 8 13:54:34 RServer kernel: note: qemu-system-x86[22904] exited with preempt_count 1 Any idea what might be causing this or how I can troubleshoot it? Thanks, Best Regards, Ricardo M.
January 8, 20179 yr The first thing I'd do is disable VMs (Settings -> VM Manager -> Enable VMs: No) and see if the system behaves properly. If it does then that's where the problem lies so re-enable VMs and post diagnostics.
January 8, 20179 yr Author The first thing I'd do is disable VMs (Settings -> VM Manager -> Enable VMs: No) and see if the system behaves properly. If it does then that's where the problem lies so re-enable VMs and post diagnostics. I rebooted the server and disabled the VMs in settings. 20mins after I started the array, the server froze again with a kernel panic. One I know that normally follows the ram being used at 100% for an unknown reason.
January 8, 20179 yr 20mins after I started the array, the server froze again with a kernel panic. One I know that normally follows the ram being used at 100% for an unknown reason. Install Fix Common Problems plugin. Toss it into troubleshooting mode. After the next crash, upload the syslog.txt file and the latest diagnostics file that will be stored on the flash drive in the logs folder. It'll show the trend with RAM usage trend (amongst other things)
January 8, 20179 yr Author 20mins after I started the array, the server froze again with a kernel panic. One I know that normally follows the ram being used at 100% for an unknown reason. Install Fix Common Problems plugin. Toss it into troubleshooting mode. After the next crash, upload the syslog.txt file and the latest diagnostics file that will be stored on the flash drive in the logs folder. It'll show the trend with RAM usage trend (amongst other things) yeah, due to lazyniess I didnt track/log the "top" command like I did the other times. Im doing both now, tracking syslog, "top" and using troubleshooting mode like you requested. I also removed the extra Nic cards just to try remove variables from the equation.
January 8, 20179 yr Author Update: So I noticed earlier in the day when I was watching an episode of a series and I told Plex to rescan the library that my available ram was low to the point where Unraid killed the process. So I went and told Plex to scan both my libraries and yes, Plex Media Scanner is using all ram available. Waiting to see if it will crash or the process killed.
January 8, 20179 yr Author Crash after a while of Plex Media Scanner using all Ram available: Jan 8 19:39:22 RServer root: Fix Common Problems Version 2016.12.16 Jan 8 19:39:22 RServer root: Fix Common Problems: Troubleshooting scan running Jan 8 19:39:22 RServer root: Fix Common Problems: Uptime: 19:39:22 up 1:27, 2 users, load average: 27.10, 26.79, 24.88 Jan 8 19:39:22 RServer root: Fix Common Problems: total used free shared buff/cache available Jan 8 19:39:22 RServer root: Fix Common Problems: Mem: 8178848 7564892 197104 340724 416852 51864 Jan 8 19:39:22 RServer root: Fix Common Problems: Swap: 0 0 0 Jan 8 19:39:22 RServer root: Fix Common Problems: ps aux output (only CPU % > 0) Jan 8 19:39:22 RServer root: Fix Common Problems: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND Jan 8 19:39:22 RServer root: Fix Common Problems: root 1 0.1 0.0 4372 1700 ? Ss 18:11 0:08 init Jan 8 19:39:22 RServer root: Fix Common Problems: root 545 24.7 0.0 0 0 ? R 18:11 21:42 [kswapd0] Jan 8 19:39:22 RServer root: Fix Common Problems: root 2415 1.3 0.0 89872 3648 ? Sl 18:11 1:08 /usr/local/sbin/emhttp Jan 8 19:39:22 RServer root: Fix Common Problems: root 2998 0.4 0.0 16612 2836 pts/1 S+ 18:13 0:22 top Jan 8 19:39:22 RServer root: Fix Common Problems: root 3605 1.1 0.0 695436 6524 ? Ssl 18:15 0:58 /usr/local/sbin/shfs /mnt/user -disks 31 2048000000 -o noatime,big_writes,allow_other,use_ino -o remember=0 Jan 8 19:39:22 RServer root: Fix Common Problems: root 3777 5.2 0.0 0 0 ? D< 18:15 4:25 [loop0] Jan 8 19:39:22 RServer root: Fix Common Problems: nobody 4370 0.5 1.5 1432688 128904 ? Dsl 18:15 0:25 mono --debug NzbDrone.exe -nobrowser -data=/config Jan 8 19:39:22 RServer root: Fix Common Problems: nobody 4613 0.6 0.5 149000 42376 ? Ssl 18:15 0:32 /usr/bin/python /usr/bin/deluged -c /config -d --loglevel=info -l /config/deluged.log Jan 8 19:39:22 RServer root: Fix Common Problems: nobody 4711 0.8 0.9 611052 76460 ? Sl 18:15 0:41 ./Plex Media Server Jan 8 19:39:22 RServer root: Fix Common Problems: nobody 4729 0.1 0.6 1962860 49852 ? SNl 18:15 0:09 Plex Plug-in [com.plexapp.system] /usr/lib/plexmediaserver/Resources/Plug-ins-b38628e/Framework.bundle/Contents/Resources/Versions/2/Python/bootstrap.py --server-version 1.3.3.3148-b38628e /usr/lib/plexmediaserver/Resources/Plug-ins-b38628e/System.bundle Jan 8 19:39:22 RServer root: Fix Common Problems: root 20323 0.9 0.0 0 0 ? S 18:45 0:30 [kworker/u8:3] Jan 8 19:39:22 RServer root: Fix Common Problems: root 23580 0.9 0.0 0 0 ? S 18:52 0:26 [kworker/u8:0] Jan 8 19:39:22 RServer root: Fix Common Problems: nobody 23666 3.9 86.2 7299992 7052200 ? Sl 18:52 1:50 /usr/lib/plexmediaserver/Plex Media Scanner --analyze --section 1 --log-file-suffix Analysis Jan 8 19:39:22 RServer root: Fix Common Problems: root 23728 0.8 0.0 0 0 ? S 18:52 0:24 [kworker/u8:7] Jan 8 19:39:22 RServer root: Fix Common Problems: root 26404 0.9 0.0 0 0 ? S 18:59 0:23 [kworker/u8:8] Jan 8 19:39:22 RServer root: Fix Common Problems: root 27889 0.9 0.0 0 0 ? S 19:10 0:16 [kworker/u8:1] Jan 8 19:39:22 RServer root: Fix Common Problems: root 28823 0.7 0.0 0 0 ? S 19:17 0:10 [kworker/u8:6] Jan 8 19:39:22 RServer root: Fix Common Problems: root 31182 0.9 0.0 0 0 ? S 19:34 0:02 [kworker/u8:2] Jan 8 19:39:22 RServer root: Fix Common Problems: Sensors output: Jan 8 19:39:22 RServer root: Fix Common Problems: 'atk0110-acpi-0' Jan 8 19:39:22 RServer root: Fix Common Problems: 'Vcore Voltage: +1.11 V (min = +0.80 V, max = +1.60 V)' Jan 8 19:39:22 RServer root: Fix Common Problems: ' +3.3 Voltage: +3.26 V (min = +2.97 V, max = +3.63 V)' Jan 8 19:39:22 RServer root: Fix Common Problems: ' +5 Voltage: +5.02 V (min = +4.50 V, max = +5.50 V)' Jan 8 19:39:22 RServer root: Fix Common Problems: ' +12 Voltage: +12.15 V (min = +10.20 V, max = +13.80 V)' Jan 8 19:39:22 RServer root: Fix Common Problems: 'CPU FAN Speed: 1140 RPM (min = 600 RPM, max = 7200 RPM)' Jan 8 19:39:22 RServer root: Fix Common Problems: 'CHASSIS1 FAN Speed: 0 RPM (min = 600 RPM, max = 7200 RPM)' Jan 8 19:39:22 RServer root: Fix Common Problems: 'CHASSIS2 FAN Speed: 0 RPM (min = 600 RPM, max = 7200 RPM)' Jan 8 19:39:22 RServer root: Fix Common Problems: 'POWER FAN Speed: 0 RPM (min = 600 RPM, max = 7200 RPM)' Jan 8 19:39:22 RServer root: Fix Common Problems: 'CPU Temperature: +26.0 C (high = +60.0 C, crit = +95.0 C)' Jan 8 19:39:22 RServer root: Fix Common Problems: 'MB Temperature: +29.0 C (high = +45.0 C, crit = +95.0 C)' Jan 8 19:39:22 RServer root: Fix Common Problems: '' Jan 8 19:39:22 RServer root: Fix Common Problems: 'coretemp-isa-0000' Jan 8 19:39:22 RServer root: Fix Common Problems: 'Core 0: +34.0 C (high = +76.0 C, crit = +100.0 C)' Jan 8 19:39:22 RServer root: Fix Common Problems: 'Core 1: +33.0 C (high = +76.0 C, crit = +100.0 C)' Jan 8 19:39:22 RServer root: Fix Common Problems: 'Core 2: +33.0 C (high = +76.0 C, crit = +100.0 C)' Jan 8 19:39:22 RServer root: Fix Common Problems: 'Core 3: +33.0 C (high = +76.0 C, crit = +100.0 C)' Jan 8 19:39:22 RServer root: Fix Common Problems: '' Jan 8 19:39:23 RServer emhttp: err: sendOutput: fork failed Jan 8 19:41:52 RServer emhttp: err: sendOutput: fork failed Jan 8 19:41:52 RServer kernel: kworker/u8:3 invoked oom-killer: gfp_mask=0x2420848, order=0, oom_score_adj=0 Jan 8 19:41:52 RServer kernel: kworker/u8:3 cpuset=/ mems_allowed=0 Jan 8 19:41:52 RServer kernel: CPU: 3 PID: 20323 Comm: kworker/u8:3 Not tainted 4.4.30-unRAID #2 Jan 8 19:41:52 RServer kernel: Hardware name: System manufacturer System Product Name/P5Q-PRO, BIOS 2002 02/23/2009 Jan 8 19:41:52 RServer kernel: Workqueue: writeback wb_workfn (flush-8:96) Jan 8 19:41:52 RServer kernel: 0000000000000000 ffff880063cbf788 ffffffff8136f79f ffff880063cbf960 Jan 8 19:41:52 RServer kernel: ffffffff8177d510 ffff880063cbf7f8 ffffffff8110857d 0000000000000206 Jan 8 19:41:52 RServer kernel: 0000000000000206 ffff880063cbf7d8 ffffffff810a936b ffff88022fff6b30 Jan 8 19:41:52 RServer kernel: Call Trace: Jan 8 19:41:52 RServer kernel: [<ffffffff8136f79f>] dump_stack+0x61/0x7e Jan 8 19:41:52 RServer kernel: [<ffffffff8110857d>] dJan 8 19:42:58 RServer kernel: general protection fault: 0000 [#1] PREEMPT SMP Jan 8 19:42:58 RServer kernel: Modules linked in: xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod bonding coretemp kvm_intel i2c_i801 i2c_core ata_piix kvm atl1e intel_agp intel_gtt agpgart asus_atk0110 acpi_cpufreq [last unloaded: md_mod] Jan 8 19:42:58 RServer kernel: CPU: 0 PID: 4642 Comm: deluged Not tainted 4.4.30-unRAID #2 Jan 8 19:42:58 RServer kernel: Hardware name: System manufacturer System Product Name/P5Q-PRO, BIOS 2002 02/23/2009 Jan 8 19:42:58 RServer kernel: task: ffff8802117f2c00 ti: ffff88007dd40000 task.ti: ffff88007dd40000 Jan 8 19:42:58 RServer kernel: RIP: 0010:[<ffffffff810be5e7>] [<ffffffff810be5e7>] __free_page_frag+0x40/0x5f Jan 8 19:42:58 RServer kernel: RSP: 0018:ffff88007dd43c18 EFLAGS: 00010202 Jan 8 19:42:58 RServer kernel: RAX: ff00ea000845e401 RBX: ffff880211796040 RCX: ffffffff818cbde0 Jan 8 19:42:58 RServer kernel: RDX: ff00ea000845e400 RSI: 0000000000000201 RDI: ff00ea000845e400 Jan 8 19:42:58 RServer kernel: RBP: ffff88007dd43c38 R08: ffff88007dd43cc4 R09: ffff88007dd43d04 Jan 8 19:42:58 RServer kernel: R10: ffff88007dd44000 R11: 000000007ffff000 R12: ffff880063d0c400 Jan 8 19:42:58 RServer kernel: R13: 0000000000000000 R14: ffff880063d0c400 R15: 0000000000000000 Jan 8 19:42:58 RServer kernel: FS: 00002b29e3ee6ab0(0000) GS:ffff88022fc00000(0000) knlGS:0000000000000000 Jan 8 19:42:58 RServer kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jan 8 19:42:58 RServer kernel: CR2: 0000000000419107 CR3: 000000020f282000 CR4: 00000000000406f0 Jan 8 19:42:58 RServer kernel: Stack: Jan 8 19:42:58 RServer kernel: ffffffff8152fffc ffff880063d0c400 ffff880223ae1180 ffff88007dd43d00 Jan 8 19:42:58 RServer kernel: ffff88007dd43c50 ffffffff81530029 ffff880063d0c400 ffff88007dd43c78 Jan 8 19:42:58 RServer kernel: ffffffff815334b5 ffff880223ae1180 ffff88007dd43ec8 ffff88007dd43df0 Jan 8 19:42:58 RServer kernel: Call Trace: Jan 8 19:42:58 RServer kernel: [<ffffffff8152fffc>] ? skb_release_data+0xa7/0xb5 Jan 8 19:42:58 RServer kernel: [<ffffffff81530029>] __kfree_skb+0x1f/0x6e Jan 8 19:42:58 RServer kernel: [<ffffffff815334b5>] skb_free_datagram_locked+0xa4/0xab Jan 8 19:42:58 RServer kernel: [<ffffffff815ac771>] udp_recvmsg+0x2ae/0x357 Jan 8 19:42:58 RServer kernel: [<ffffffff815b5ccf>] inet_recvmsg+0x86/0x9e Jan 8 19:42:58 RServer kernel: [<ffffffff8152696f>] sock_recvmsg+0xb/0xd Jan 8 19:42:58 RServer kernel: [<ffffffff81527f9b>] ___sys_recvmsg+0xc7/0x15d Jan 8 19:42:58 RServer kernel: [<ffffffff8113ca46>] ? ep_scan_ready_list+0x165/0x185 Jan 8 19:42:58 RServer kernel: [<ffffffff8113cbd7>] ? ep_poll+0x152/0x281 Jan 8 19:42:58 RServer kernel: [<ffffffff8112070e>] ? __fget+0x72/0x7e Jan 8 19:42:58 RServer kernel: [<ffffffff81528c75>] __sys_recvmsg+0x3d/0x5e Jan 8 19:42:58 RServer kernel: [<ffffffff81528c75>] ? __sys_recvmsg+0x3d/0x5e Jan 8 19:42:58 RServer kernel: [<ffffffff81528c9f>] SyS_recvmsg+0x9/0xb Jan 8 19:42:58 RServer kernel: [<ffffffff81629c2e>] entry_SYSCALL_64_fastpath+0x12/0x6d Jan 8 19:42:58 RServer kernel: Code: 05 4f 1a 79 00 48 01 c7 48 b8 00 00 00 00 00 ea ff ff 48 c1 ef 0c 48 c1 e7 06 48 01 c7 48 8b 47 20 48 8d 50 ff a8 01 48 0f 45 fa <f0> ff 4f 1c 74 01 c3 55 48 8b 07 31 f6 48 89 e5 f6 c4 40 74 03 Jan 8 19:42:58 RServer kernel: RIP [<ffffffff810be5e7>] __free_page_frag+0x40/0x5f Jan 8 19:42:58 RServer kernel: RSP <ffff88007dd43c18> Jan 8 19:42:58 RServer kernel: ---[ end trace dafcae36aa23439c ]--- Update: Running now with plex Docker stopped.
January 8, 20179 yr Limit the memory to the plex container (look in the docker FAQ) Don't know how much memory you've got in the system.
January 8, 20179 yr Author Limit the memory to the plex container (look in the docker FAQ) Don't know how much memory you've got in the system. Oh, I didnt know you could do that since there are no options. I have my specs on the first post and you can see the memory on the "Top" prints. I have 8GB. Im considering mounting just VMs, since I think its very unreliable docker crashing the host. I rather setup a VM with docker and have it crash the VM. Lets see if without plex its stable, if its the case, I have my 2 week mystery solved.
January 8, 20179 yr Limit the memory to the plex container (look in the docker FAQ) Don't know how much memory you've got in the system. Oh, I didnt know you could do that since there are no options. I have my specs on the first post and you can see the memory on the "Top" prints. I have 8GB. Im considering mounting just VMs, since I think its very unreliable docker crashing the host. I rather setup a VM with docker and have it crash the VM. Lets see if without plex its stable, if its the case, I have my 2 week mystery solved. Docker is stable. However if you are running the entire system right at the edge of memory, then stuff like this is going to happen. You haven't posted any diagnostics, so hard to tell what is running on the system. If you are currently running a VM and trying to run a bunch of docker containers all in 8GB then its basically a disaster waiting to hapen
January 8, 20179 yr Author Docker is stable. However if you are running the entire system right at the edge of memory, then stuff like this is going to happen. You haven't posted any diagnostics, so hard to tell what is running on the system. If you are currently running a VM and trying to run a bunch of docker containers all in 8GB then its basically a disaster waiting to hapen I did post it, you look at the last log in "quote", you can see the "Fix Common Problems: Troubleshooting scan" result that tells you everything that is running. Here: Jan 8 19:39:22 RServer root: Fix Common Problems: root 3777 5.2 0.0 0 0 ? D< 18:15 4:25 [loop0] Jan 8 19:39:22 RServer root: Fix Common Problems: nobody 4370 0.5 1.5 1432688 128904 ? Dsl 18:15 0:25 mono --debug NzbDrone.exe -nobrowser -data=/config Jan 8 19:39:22 RServer root: Fix Common Problems: nobody 4613 0.6 0.5 149000 42376 ? Ssl 18:15 0:32 /usr/bin/python /usr/bin/deluged -c /config -d --loglevel=info -l /config/deluged.log Jan 8 19:39:22 RServer root: Fix Common Problems: nobody 4711 0.8 0.9 611052 76460 ? Sl 18:15 0:41 ./Plex Media Server Jan 8 19:39:22 RServer root: Fix Common Problems: nobody 4729 0.1 0.6 1962860 49852 ? SNl 18:15 0:09 Plex Plug-in [com.plexapp.system] /usr/lib/plexmediaserver/Resources/Plug-ins-b38628e/Framework.bundle/Contents/Resources/Versions/2/Python/bootstrap.py --server-version 1.3.3.3148-b38628e /usr/lib/plexmediaserver/Resources/Plug-ins-b38628e/System.bundle Jan 8 19:39:22 RServer root: Fix Common Problems: root 20323 0.9 0.0 0 0 ? S 18:45 0:30 [kworker/u8:3] Jan 8 19:39:22 RServer root: Fix Common Problems: root 23580 0.9 0.0 0 0 ? S 18:52 0:26 [kworker/u8:0] Jan 8 19:39:22 RServer root: Fix Common Problems: nobody 23666 3.9 86.2 7299992 7052200 ? Sl 18:52 1:50 /usr/lib/plexmediaserver/Plex Media Scanner --analyze --section 1 --log-file-suffix Analysis Like you can see, I was running Plex, Sonarr (as NzbDrone) and Deluge Apps using Docker. I even posted current memory usage on the first post and everything where you could see a VM using 37% Memory (I have allocated 2560MB) and even with all the apps I still had 3.5GB available ram. So I wasnt running my server on the edge of memory, far from that. Im sorry if it wasn't clear, I though it was enough. I will post an update if it crashes again or if it stays stable from now. Current Status in attachment. Thanks, Ralms.
January 8, 20179 yr Log snippets are seldom very useful. (And I'm not alone in that opinion here) As an example, your system load in that snippet is 27. And yet the top isn't showing any processes using more than 24%. And based upon the averages its been increasing steadily. While I'm not saying that the answers are definitely contained within the syslog, when push comes to shove, plex should NOT crash the system under any circumstances, regardless of the amount of memory in there. Snippets just give the results when the system crashed. Doesn't give the info of what might have led up to it.
January 8, 20179 yr Author Log snippets are seldom very useful. (And I'm not alone in that opinion here) As an example, your system load in that snippet is 27. And yet the top isn't showing any processes using more than 24%. And based upon the averages its been increasing steadily. While I'm not saying that the answers are definitely contained within the syslog, when push comes to shove, plex should NOT crash the system under any circumstances, regardless of the amount of memory in there. Snippets just give the results when the system crashed. Doesn't give the info of what might have led up to it. The system load is not showing because Im sorting Top by Memory usage. I will post full logs next time.
January 8, 20179 yr Jan 8 19:39:22 RServer root: Fix Common Problems Version 2016.12.16 Jan 8 19:39:22 RServer root: Fix Common Problems: Troubleshooting scan running Jan 8 19:39:22 RServer root: Fix Common Problems: Uptime: 19:39:22 up 1:27, 2 users, load average: 27.10, 26.79, 24.88
Archived
This topic is now archived and is closed to further replies.