NOLA_DireWolff Posted February 14, 2020 Share Posted February 14, 2020 (edited) I have had 2 Hard Crashes and 1 Soft crash in the last two weeks. I have had 100% reliability over the last year with no crashes. There have been no hardware changes in months. The most recent change was added Deluge docker. It doesn't run 24/7. ShinobiCCTV docker was the addition prior to that. There were no crashes before Deluge, but I'd prefer to actually learn something than just guess. I experienced a hard crash while connected via Wireguard yesterday. When I got home, the fans were blowing hard, there was no web access, no SSH, no WinSCP. I had to hard reset. I restarted everything, Shinobi and Deluge (for testing) and watched plex. I started the syslog to Cache before bed, no issues. I woke up this morning - WebGUI is semi-responsive. The UNraid animation is present over some sections and won't finish it's job. Unassigned devices doesn't show me anything. WinSCP doesn't work. SSH doesn't work. Docker section shows Unraid animation. I only left Plex, Shinobi and Deluge running over night. VM section won't populate, but nothing was running. Terminal from inside the GUI does appear to work! I want to reboot it, but I'll wait to see if there are any other terminal commands you want me to run. The syslog is attached. I'm new to this - your help is appreciated I may not know much, but the sections below are repeated almost every minute and doesn't seem necessary - is this a hint? If you are curious about my pinning: I currently have 12 CPU threads. Six are isolated and reserved for my Win10Gaming VM. The other six are available to Unraid. Shinobi is pinned to 2 and 7. Feb 13 23:52:08 GLADOS kernel: ? cpuidle_enter_state+0xbf/0x141 Feb 13 23:52:08 GLADOS kernel: do_idle+0x17e/0x1fc Feb 13 23:52:08 GLADOS kernel: cpu_startup_entry+0x6a/0x6c Feb 13 23:52:08 GLADOS kernel: start_secondary+0x197/0x1b2 Feb 13 23:52:08 GLADOS kernel: secondary_startup_64+0xa4/0xb0 Feb 13 23:55:05 GLADOS kernel: rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 0-... 11-... } 1322496 jiffies s: 721 root: 0x801/. Feb 13 23:55:05 GLADOS kernel: rcu: blocking rcu_node structures: Feb 13 23:55:05 GLADOS kernel: Task dump for CPU 0: Feb 13 23:55:05 GLADOS kernel: kworker/u24:3 R running task 0 20413 2 0x80000008 Feb 13 23:55:05 GLADOS kernel: Workqueue: events_power_efficient gc_worker Feb 13 23:55:05 GLADOS kernel: Call Trace: Feb 13 23:55:05 GLADOS kernel: ? process_one_work+0x16e/0x24f Feb 13 23:55:05 GLADOS kernel: ? worker_thread+0x1e2/0x2b8 Feb 13 23:55:05 GLADOS kernel: ? rescuer_thread+0x2a7/0x2a7 Feb 13 23:55:05 GLADOS kernel: ? kthread+0x10c/0x114 Feb 13 23:55:05 GLADOS kernel: ? kthread_park+0x89/0x89 Feb 13 23:55:05 GLADOS kernel: ? ret_from_fork+0x35/0x40 Feb 13 23:55:05 GLADOS kernel: Task dump for CPU 11:\ What is this? Feb 14 04:20:09 GLADOS kernel: RIP: 0010:nf_conntrack_tuple_taken+0x7f/0x221 Feb 14 04:20:09 GLADOS kernel: Code: fb 49 c1 ef 20 4b 8d 04 fe 49 c7 c6 f0 ff ff ff 48 8b 18 f6 c3 01 0f 85 8a 01 00 00 0f b6 43 37 4c 89 f7 48 89 c1 48 6b c0 38 <48> 29 c7 48 01 df 48 39 ef 0f 84 65 01 00 00 48 8b 05 12 f2 88 00 Feb 14 04:20:09 GLADOS kernel: RSP: 0000:ffff88903bac3a08 EFLAGS: 00000202 Feb 14 04:20:09 GLADOS kernel: RAX: 0000000000000038 RBX: ffff888dbb62c7c8 RCX: 0000000000000001 Feb 14 04:20:09 GLADOS kernel: RDX: 00000000000f020a RSI: 0000000000000000 RDI: fffffffffffffff0 Feb 14 04:20:09 GLADOS kernel: RBP: ffff888dbb62d2c0 R08: 0000000000000003 R09: ffffffff81c8a9c0 Feb 14 04:20:09 GLADOS kernel: R10: 0000000000000001 R11: ffff888ffdec4400 R12: ffff88903bac3a48 Feb 14 04:20:09 GLADOS kernel: R13: ffffffff81e91140 R14: fffffffffffffff0 R15: 000000000000cddc Feb 14 04:20:09 GLADOS kernel: FS: 0000000000000000(0000) GS:ffff88903bac0000(0000) knlGS:0000000000000000 Feb 14 04:20:09 GLADOS kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 14 04:20:09 GLADOS kernel: CR2: 0000000000000000 CR3: 0000000001e0a001 CR4: 00000000003606e0 Feb 14 04:20:09 GLADOS kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Feb 14 04:20:09 GLADOS kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Feb 14 04:20:09 GLADOS kernel: Call Trace: Whats next? 🔎 syslog.log Edited February 14, 2020 by NOLA_DireWolff Corrected Sentence :) Quote Link to comment
NOLA_DireWolff Posted February 14, 2020 Author Share Posted February 14, 2020 htop output: and top output Quote Link to comment
NOLA_DireWolff Posted February 14, 2020 Author Share Posted February 14, 2020 Digging around in other terminal stuff for high CPU items: From PS -f -aux root 20413 96.3 0.0 0 0 ? R Feb13 505:32 \_ [kworker/u24:3+events_power_efficient] and root 2184 0.0 0.0 2532 1636 ? Ss Feb13 0:00 /usr/sbin/crond root 20187 0.0 0.0 3748 2860 ? S Feb13 0:00 \_ /bin/sh -c /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/null root 20190 0.0 0.0 104628 26088 ? SL Feb13 0:00 | \_ /usr/bin/php -q /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster root 20196 0.0 0.0 3748 2904 ? S Feb13 0:00 | \_ sh -c nmblookup -M -- - 2>/dev/null|grep -Pom1 '^\S+' root 20197 0.0 0.0 34044 11728 ? D Feb13 0:00 | \_ nmblookup -M -- - root 20198 0.0 0.0 3332 1700 ? S Feb13 0:00 | \_ grep -Pom1 ^\S+ root 20188 0.0 0.0 3748 2756 ? S Feb13 0:00 \_ /bin/sh -c /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null root 20191 99.8 0.0 4016 2080 ? R Feb13 501:07 | \_ /usr/lib64/sa/sadc -F -L 1 1 /var/sa and root 14044 31.8 0.0 1269016 19428 ? Rl Feb13 259:21 /usr/sbin/libvirtd -d -l -f /etc/libvirt/libvirtd.conf -p /var/run/libvirt/libvirtd.pid nobody 14158 0.0 0.0 7028 1956 ? S Feb13 0:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper root 14159 0.0 0.0 6896 240 ? S Feb13 0:00 \_ /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper root 14861 0.0 0.0 101920 11684 ? Ss Feb13 0:00 php-fpm: master process (/etc/php-fpm/php-fpm.conf) root 2901 0.0 0.0 105016 13160 ? S 05:29 0:00 \_ php-fpm: pool www root 2939 0.0 0.0 3840 2816 ? S 05:29 0:00 | \_ sh -c /usr/bin/timeout 5 /usr/bin/lsof '/mnt/disks/downloads' 2>/dev/null | /bin/sort -k8 | /bin/uniq -f7 | /bin/grep -c -e REG root 2940 0.0 0.0 2644 816 ? S 05:29 0:00 | \_ /usr/bin/timeout 5 /usr/bin/lsof /mnt/disks/downloads root 2944 0.0 0.0 2748 1864 ? D 05:29 0:00 | | \_ /usr/bin/lsof /mnt/disks/downloads root 2951 0.0 0.0 0 0 ? Z 05:29 0:00 | | \_ [lsof] <defunct> root 2941 0.0 0.0 19188 800 ? S 05:29 0:00 | \_ /bin/sort -k8 root 2942 0.0 0.0 2456 760 ? S 05:29 0:00 | \_ /bin/uniq -f7 root 2943 0.0 0.0 3268 1716 ? S 05:29 0:00 | \_ /bin/grep -c -e REG root 3261 0.0 0.0 105276 13804 ? S 05:30 0:00 \_ php-fpm: pool www root 4459 0.0 0.0 3840 2920 ? S 05:33 0:00 | \_ sh -c sar 1 1 -u -b -r -n DEV|grep -a '^A'|tr -d '\0'|awk '$2=="all" {u=$3;n=$4;s=$5;}; $2=="tps" {getline;r=$5;w=$6;}; $2=="kbmemfree" {getline;f=$2;c=$6+$7;d=$4;}; $2=="eth0" {x=$5;y=$6;} END{pri root 4460 0.0 0.0 2564 768 ? S 05:33 0:00 | \_ sar 1 1 -u -b -r -n DEV root 4464 99.5 0.0 4016 2196 ? R 05:33 141:57 | | \_ sadc 1 2 -Z -S A_NULL A_CPU A_IO A_MEMORY A_NET_DEV root 4461 0.0 0.0 3268 1696 ? S 05:33 0:00 | \_ grep -a ^A root 4462 0.0 0.0 2472 696 ? S 05:33 0:00 | \_ tr -d \0 root 4463 0.0 0.0 10032 2736 ? S 05:33 0:00 | \_ awk $2=="all" {u=$3;n=$4;s=$5;}; $2=="tps" {getline;r=$5;w=$6;}; $2=="kbmemfree" {getline;f=$2;c=$6+$7;d=$4;}; $2=="eth0" {x=$5;y=$6;} END{print u,n,s"\n"r,w"\n"f,c,d"\n"x,y} root 3509 0.0 0.0 105016 13556 ? S 05:31 0:00 \_ php-fpm: pool www root 3857 0.0 0.0 3840 2920 ? S 05:32 0:00 | \_ sh -c /usr/bin/timeout 5 /usr/bin/lsof '/mnt/disks/downloads' 2>/dev/null | /bin/sort -k8 | /bin/uniq -f7 | /bin/grep -c -e REG root 3860 0.0 0.0 2644 748 ? S 05:32 0:00 | \_ /usr/bin/timeout 5 /usr/bin/lsof /mnt/disks/downloads root 3864 0.0 0.0 2748 1740 ? D 05:32 0:00 | | \_ /usr/bin/lsof /mnt/disks/downloads root 3865 0.0 0.0 0 0 ? Z 05:32 0:00 | | \_ [lsof] <defunct> root 3861 0.0 0.0 19188 800 ? S 05:32 0:00 | \_ /bin/sort -k8 root 3862 0.0 0.0 2456 760 ? S 05:32 0:00 | \_ /bin/uniq -f7 root 3863 0.0 0.0 3268 1684 ? S 05:32 0:00 | \_ /bin/grep -c -e REG root 4419 0.0 0.0 105276 13748 ? S 05:33 0:00 \_ php-fpm: pool www root 4523 0.0 0.0 3840 2968 ? S 05:33 0:00 | \_ sh -c sar 1 1 -u -b -r -n DEV|grep -a '^A'|tr -d '\0'|awk '$2=="all" {u=$3;n=$4;s=$5;}; $2=="tps" {getline;r=$5;w=$6;}; $2=="kbmemfree" {getline;f=$2;c=$6+$7;d=$4;}; $2=="eth0" {x=$5;y=$6;} END{pri root 4525 0.0 0.0 2564 764 ? S 05:33 0:00 | \_ sar 1 1 -u -b -r -n DEV root 4566 99.9 0.0 4016 2272 ? R 05:33 142:34 | | \_ sadc 1 2 -Z -S A_NULL A_CPU A_IO A_MEMORY A_NET_DEV Quote Link to comment
NOLA_DireWolff Posted February 14, 2020 Author Share Posted February 14, 2020 And the top HTOP user PPIDs and other info: ps -ef output: root 14044 1 33 Feb13 ? 04:40:13 /usr/sbin/libvirtd -d -l -f /etc/libvirt/libvirtd.conf -p /var/run/libvirt/libvirtd.pid root 20191 20188 99 Feb13 ? 08:31:31 /usr/lib64/sa/sadc -F -L 1 1 /var/sa root 4464 4460 99 05:33 ? 02:32:21 sadc 1 2 -Z -S A_NULL A_CPU A_IO A_MEMORY A_NET_DEV root 4566 4525 99 05:33 ? 02:33:02 sadc 1 2 -Z -S A_NULL A_CPU A_IO A_MEMORY A_NET_DEV Other strange thing PID 14176 shows as active in htop but it doesn't show in the ps output? I'm learning, but maybe I'm not understanding something. Quote Link to comment
NOLA_DireWolff Posted March 4, 2020 Author Share Posted March 4, 2020 This is continuing. 2 hard crashes this week. No new dockers/vms or hardware. Can anyone help with troubleshooting? Prior to 6.8.2 with this hardware and docker setup I had no crashes ever I got rid of deluge and there was no file sharing between the last post and this one. I'll post syslog data in the next post. Quote Link to comment
JorgeB Posted March 4, 2020 Share Posted March 4, 2020 You could try safe mode without dockers/VMs, if it still crashes it's likely a hardware problem, you can also downgrade back to the last known working release, again if it keeps crashing likely a recent hardware issue. Most call traces on the first syslog are network/NIC related (or at least they mention them), so it might be worth simplifying the lan and/or using another NIC to see if it helps. Quote Link to comment
NOLA_DireWolff Posted March 4, 2020 Author Share Posted March 4, 2020 Quote Mar 3 15:47:17 GLADOS kernel: mdcmd (52): spindown 2 Mar 3 19:38:45 GLADOS dhcpcd[2077]: br1: failed to renew DHCP, rebinding Mar 4 00:11:23 GLADOS kernel: mdcmd (53): spindown 2 Mar 4 00:11:53 GLADOS kernel: mdcmd (54): spindown 29 These are from last night... it was found unresponsive this morning. This is the crash prior: Quote Feb 28 04:46:55 GLADOS kernel: mdcmd (70): spindown 1 Feb 28 04:46:56 GLADOS kernel: mdcmd (71): spindown 2 Feb 28 04:46:57 GLADOS kernel: mdcmd (72): spindown 29 Feb 28 04:47:31 GLADOS kernel: mdcmd (73): set md_write_method 0 Feb 28 04:47:31 GLADOS kernel: Feb 28 05:32:31 GLADOS kernel: mdcmd (74): set md_write_method 1 Feb 28 05:32:31 GLADOS kernel: Feb 28 06:00:12 GLADOS root: /etc/libvirt: 925.8 MiB (970715136 bytes) trimmed on /dev/loop3 Feb 28 06:00:12 GLADOS root: /var/lib/docker: 10.7 GiB (11437334528 bytes) trimmed on /dev/loop2 Feb 28 06:00:12 GLADOS root: /mnt/disks/nongamingvm: 409.1 GiB (439217426432 bytes) trimmed on /dev/nvme1n1p1 Feb 28 06:00:12 GLADOS root: /mnt/disks/guild_process_vm: 836.1 GiB (897730297856 bytes) trimmed on /dev/nvme0n1p1 Feb 28 06:00:12 GLADOS root: /mnt/cache: 1.8 TiB (1953963548672 bytes) trimmed on /dev/sdb1 Mar 2 11:46:33 GLADOS kernel: mdcmd (39): set md_write_method 1 Mar 2 11:46:33 GLADOS kernel: Mar 2 11:46:33 GLADOS cache_dirs: Arguments=-i Media -i downloads -l off Mar 2 11:46:33 GLADOS cache_dirs: Max Scan Secs=10, Min Scan Secs=1 Mar 2 11:46:33 GLADOS cache_dirs: Scan Type=adaptive Mar 2 11:46:33 GLADOS cache_dirs: Min Scan Depth=4 Mar 2 11:46:33 GLADOS cache_dirs: Max Scan Depth=none Mar 2 11:46:33 GLADOS cache_dirs: Use Command='find -noleaf' An entry I'm curious about - but nothing bad happened. Quote Mar 3 07:07:20 GLADOS kernel: mdcmd (45): spindown 2 Mar 3 07:07:50 GLADOS kernel: mdcmd (46): spindown 29 Mar 3 07:19:09 GLADOS kernel: mdcmd (47): spindown 1 Mar 3 07:19:09 GLADOS kernel: mdcmd (48): set md_write_method 0 Mar 3 07:19:09 GLADOS kernel: Mar 3 07:40:07 GLADOS kernel: ------------[ cut here ]------------ Mar 3 07:40:07 GLADOS kernel: WARNING: CPU: 9 PID: 147 at net/netfilter/nf_nat_core.c:420 nf_nat_setup_info+0x94/0x666 [nf_nat] Mar 3 07:40:07 GLADOS kernel: Modules linked in: xt_nat xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat nf_nat_ipv6 iptable_mangle ip6table_filter ip6_tables vhost_net tun vhost tap macvlan iptable_filter xfs md_mod iptable_nat ipt_MASQUERADE nf_nat_ipv4 nf_nat ip_tables wireguard ip6_udp_tunnel udp_tunnel e1000e igb(O) hid_logitech_hidpp wmi_bmof x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate intel_uncore intel_rapl_perf mpt3sas i2c_i801 i2c_core ahci nvme raid_class libahci scsi_transport_sas pcc_cpufreq hid_logitech_dj nvme_core video wmi backlight thermal acpi_pad button fan [last unloaded: e1000e] Mar 3 07:40:07 GLADOS kernel: CPU: 9 PID: 147 Comm: kworker/9:1 Tainted: G W O 4.19.98-Unraid #1 Mar 3 07:40:07 GLADOS kernel: Hardware name: ASUSTeK COMPUTER INC. System Product Name/WS C246 PRO, BIOS 1102 11/08/2019 Mar 3 07:40:07 GLADOS kernel: Workqueue: events macvlan_process_broadcast [macvlan] Mar 3 07:40:07 GLADOS kernel: RIP: 0010:nf_nat_setup_info+0x94/0x666 [nf_nat] Mar 3 07:40:07 GLADOS kernel: Code: 0d 8b 87 80 00 00 00 25 80 00 00 00 eb 0c 41 8b 86 80 00 00 00 25 00 01 00 00 85 c0 74 13 48 c7 c7 cc c1 09 a0 e8 bc 36 ff e0 <0f> 0b e9 49 01 00 00 4c 8d 6c 24 30 49 8d 76 58 4c 89 ef e8 73 9c Mar 3 07:40:07 GLADOS kernel: RSP: 0018:ffff88903ba43c50 EFLAGS: 00010246 Mar 3 07:40:07 GLADOS kernel: RAX: 0000000000000024 RBX: ffff88903ba43df0 RCX: 0000000000000000 Mar 3 07:40:07 GLADOS kernel: RDX: 0000000000000000 RSI: ffff88903ba564f8 RDI: ffff88903ba564f8 Mar 3 07:40:07 GLADOS kernel: RBP: ffff88903ba43d28 R08: 0000000000000003 R09: 0000000000018100 Mar 3 07:40:07 GLADOS kernel: R10: 0000000000000000 R11: 0000000000000044 R12: 0000000000000000 Mar 3 07:40:07 GLADOS kernel: R13: 0000000000000000 R14: ffff888fe3fe72c0 R15: ffff88903ba43d3c Mar 3 07:40:07 GLADOS kernel: FS: 0000000000000000(0000) GS:ffff88903ba40000(0000) knlGS:0000000000000000 Mar 3 07:40:07 GLADOS kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 3 07:40:07 GLADOS kernel: CR2: 0000560084b14248 CR3: 0000000001e0a001 CR4: 00000000003606e0 Mar 3 07:40:07 GLADOS kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Mar 3 07:40:07 GLADOS kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Mar 3 07:40:07 GLADOS kernel: Call Trace: Mar 3 07:40:07 GLADOS kernel: <IRQ> Mar 3 07:40:07 GLADOS kernel: nf_nat_alloc_null_binding+0x71/0x88 [nf_nat] Mar 3 07:40:07 GLADOS kernel: nf_nat_inet_fn+0x9f/0x1b9 [nf_nat] Mar 3 07:40:07 GLADOS kernel: nf_hook_slow+0x3a/0x90 Mar 3 07:40:07 GLADOS kernel: ip_local_deliver+0xad/0xdc Mar 3 07:40:07 GLADOS kernel: ? ip_sublist_rcv_finish+0x54/0x54 Mar 3 07:40:07 GLADOS kernel: ip_sabotage_in+0x38/0x3e Mar 3 07:40:07 GLADOS kernel: nf_hook_slow+0x3a/0x90 Mar 3 07:40:07 GLADOS kernel: ip_rcv+0x8e/0xbe Mar 3 07:40:07 GLADOS kernel: ? ip_rcv_finish_core.isra.0+0x2e1/0x2e1 Mar 3 07:40:07 GLADOS kernel: __netif_receive_skb_one_core+0x53/0x6f Mar 3 07:40:07 GLADOS kernel: process_backlog+0x77/0x10e Mar 3 07:40:07 GLADOS kernel: net_rx_action+0x107/0x26c Mar 3 07:40:07 GLADOS kernel: __do_softirq+0xc9/0x1d7 Mar 3 07:40:07 GLADOS kernel: do_softirq_own_stack+0x2a/0x40 Mar 3 07:40:07 GLADOS kernel: </IRQ> Mar 3 07:40:07 GLADOS kernel: do_softirq+0x4d/0x5a Mar 3 07:40:07 GLADOS kernel: netif_rx_ni+0x1c/0x22 Mar 3 07:40:07 GLADOS kernel: macvlan_broadcast+0x111/0x156 [macvlan] Mar 3 07:40:07 GLADOS kernel: ? __switch_to_asm+0x41/0x70 Mar 3 07:40:07 GLADOS kernel: macvlan_process_broadcast+0xea/0x128 [macvlan] Mar 3 07:40:07 GLADOS kernel: process_one_work+0x16e/0x24f Mar 3 07:40:07 GLADOS kernel: worker_thread+0x1e2/0x2b8 Mar 3 07:40:07 GLADOS kernel: ? rescuer_thread+0x2a7/0x2a7 Mar 3 07:40:07 GLADOS kernel: kthread+0x10c/0x114 Mar 3 07:40:07 GLADOS kernel: ? kthread_park+0x89/0x89 Mar 3 07:40:07 GLADOS kernel: ret_from_fork+0x1f/0x40 Mar 3 07:40:07 GLADOS kernel: ---[ end trace f75a383c9e5ca688 ]--- Quote Link to comment
JorgeB Posted March 4, 2020 Share Posted March 4, 2020 2 minutes ago, NOLA_DireWolff said: [macvlan] Macvlan call traces are usually related to dockers with a custom IP address. But the crashes without anything logged suggest more a hardware issue. Quote Link to comment
NOLA_DireWolff Posted March 4, 2020 Author Share Posted March 4, 2020 There have been no hardware changes prior to the first three crashes. Between those and this recent one, I've change MOBO and CPU... same crashes. I'll run a memtest tonight and report back. Quote Link to comment
NOLA_DireWolff Posted March 5, 2020 Author Share Posted March 5, 2020 16 hours of Memtest on 64GB of ECC - 1.32x passes and 0 errors. Memtest is satisfied. CPU was at 46-47 degrees the whole time. I don't know 😭what to test next. During the prior crashes the only things running were Plex Official docker and ShinobiCCTV docker. Plex I have had for a year. Shinobi has been 3-4 months - there is slight correlation in timing. Shinobi shows very low resource utilization. Question on Network simplification. I have eth0 and eht1 - separated, each is allowed to bridge. eth0 is my primary server interface and all of my usual dockers use that. eth1 is dedicated to my cctv cameras, plugs into a different switch which has the majority of my hardwired traffic (same whole network, different VLAN). The Shinobi docker is given an IP address on that VLAN (eth1) which I can reach when I wireguard in remotely via eth0 Am I being too cautious about bandwidth with the motivating being to isolate the majority of my camera traffic on eth1 like this? Would it be better to bond them, plug them both into my network? My network is only 1000. I honestly don't know the best way. Quote Link to comment
NOLA_DireWolff Posted March 5, 2020 Author Share Posted March 5, 2020 As an aside note - on the Unraid Dashboard my eth1 shows only 60Mbps down and 1.5Mbps up. That is all CCTV traffic. I'll happily take guidance on the best network setup for my use case Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.