raun

Members
  • Posts

    21
  • Joined

  • Last visited

raun's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Anyone upgrade to 6.12.4 to see if this crash as gone away?
  2. Thanks for the help - in the short term I'll roll back to 6.11.5 and keep an eye on the forums.
  3. root@Tower:~# docker network ls NETWORK ID NAME DRIVER SCOPE 3072d7630feb br0 ipvlan local 27dc2f81b4e6 bridge bridge local 1c177321660e host host local 4434f0935c25 none null local 1460fa1acee5 wg0 bridge local b001f8dbb75d wg1 bridge local root@Tower:~#
  4. Now I have a different, but similar crash. Log attached. unraid.log
  5. I switched to ipvlan. All my containers seem to run fine. Now we wait......
  6. Just upgraded from 6.11.5 to 6.12.3 and am experiencing near daily crashes. The machine does not respond to web ui or even pings after this crash occurs. I run about 12 dockers and a VM running hasos/homeassistant. Log from a remote syslog is attached. unraid.crash.log
  7. I'm slightly creeping up after 2 weeks. root@Tower:~# !45 cat /proc/sys/kernel/pty/nr 3714 root@Tower:~# uptime 21:28:59 up 17 days, 10:55, 0 users, load average: 0.35, 0.29, 0.27 root@Tower:~#
  8. After 3 days after a reboot my open ptys are holding steady at 3524 (give-or-take). After hitting this point I dont see ptys not being closed anymore.
  9. Same thing on my box: cat /proc/sys/kernel/pty/max == 4096 cat /proc/sys/kernel/pty/nr == 3518 cat /proc/sys/kernel/pty/reserve == 1024 I'm not creating my own containers.
  10. I'm seeing the same thing when opening the console window to any running docker container. A reboot fixes it a few hours, but at some point this happens again. Same symptoms as you - stopping/restarting doesn't help. My docker.img is not full.
  11. Same boat as me. memtest is clean, run of the mill hardware (skylake i5, no external cards), backed by ubiquiti network equipment with a repeatable panic every few weeks. 6.8.3 is on a LTS kernel, but its ~50 revisions behind (with many kernel panic fixes in those revisions) and with 6.9 looming, I doubt unraid would spin another 6.8.x series to update the kernel. I'm not all that interested in doing a custom 4.19.xxx kernel for the same reason.
  12. You have posts about panics in 6.9.0Beta29, and 6.8.3. These are very different different kernels. You're either very unlucky or have a hardware problem. Run memtest86 for several iterations
  13. I'm been having the same problem, and finally reproduced it after switching to remote syslog. Oct 15 00:11:13 Tower rpc.mountd[8523]: authenticated mount request from 192.168.2.31:918 for /mnt/user/Camera (/mnt/user/Camera) Oct 15 00:11:13 Tower rpcbind[25022]: connect from 192.168.2.31 to getport/addr(nfs) Oct 15 01:32:59 Tower kernel: general protection fault: 0000 [#1] SMP PTI Oct 15 01:32:59 Tower kernel: CPU: 3 PID: 23479 Comm: python3 Tainted: G W 4.19.107-Unraid #1 Oct 15 01:32:59 Tower kernel: Hardware name: Gigabyte Technology Co., Ltd. H170M-D3H-GSM/H170M-D3H-GSM-CF, BIOS F23e 03/09/2018 Oct 15 01:32:59 Tower kernel: RIP: 0010:nf_nat_setup_info+0x365/0x666 [nf_nat] Oct 15 01:32:59 Tower kernel: Code: ed 75 23 45 8b 17 48 8d 7c 24 58 b9 0a 00 00 00 48 8d 74 24 30 f3 a5 41 f6 c2 01 0f 85 c4 00 00 00 e9 25 02 00 00 8a 44 24 56 <41> 38 45 46 74 15 4d 8b ad 98 00 00 00 4d 85 ed 74 c7 49 81 ed 98 Oct 15 01:32:59 Tower kernel: RSP: 0018:ffff88881eb836d8 EFLAGS: 00010202 Oct 15 01:32:59 Tower kernel: RAX: ffff8880106aaa11 RBX: ffffffff81e91080 RCX: 000000002c2404e6 Oct 15 01:32:59 Tower kernel: RDX: ffff8887ade00000 RSI: 00000000b3a23fac RDI: 00000000f115a28e Oct 15 01:32:59 Tower kernel: RBP: ffff88881eb837b0 R08: ffff88881eb83708 R09: ffffffff81c8aa80 Oct 15 01:32:59 Tower kernel: R10: ffff888188d78388 R11: 0000000000000000 R12: 0000000000000000 Oct 15 01:32:59 Tower kernel: R13: 0de29a5fffffff68 R14: ffff88810f1923c0 R15: ffff88881eb837c4 Oct 15 01:32:59 Tower kernel: FS: 00001548557ad700(0000) GS:ffff88881eb80000(0000) knlGS:0000000000000000 Oct 15 01:32:59 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 15 01:32:59 Tower kernel: CR2: 000014944eb6d280 CR3: 000000034629c004 CR4: 00000000003606e0 Oct 15 01:32:59 Tower kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Oct 15 01:32:59 Tower kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Oct 15 01:32:59 Tower kernel: Call Trace: Oct 15 01:32:59 Tower kernel: <IRQ> Oct 15 01:32:59 Tower kernel: ? fib_rules_lookup+0x11f/0x16e Oct 15 01:32:59 Tower kernel: ? __krealloc+0x25/0x5d Oct 15 01:32:59 Tower kernel: ? nf_ct_ext_add+0x97/0xf6 Oct 15 01:32:59 Tower kernel: nf_nat_masquerade_ipv4+0x123/0x14b [nf_nat_ipv4] Oct 15 01:32:59 Tower kernel: masquerade_tg+0x44/0x5e [ipt_MASQUERADE] Oct 15 01:32:59 Tower kernel: ipt_do_table+0x582/0x62a [ip_tables] Oct 15 01:32:59 Tower kernel: ? fib_validate_source+0xc6/0xd5 Oct 15 01:32:59 Tower kernel: ? ipt_do_table+0x5da/0x62a [ip_tables] Oct 15 01:32:59 Tower kernel: nf_nat_inet_fn+0xeb/0x1b9 [nf_nat] Oct 15 01:32:59 Tower kernel: nf_nat_ipv4_out+0xf/0x89 [nf_nat_ipv4] Oct 15 01:32:59 Tower kernel: nf_hook_slow+0x3a/0x90 Oct 15 01:32:59 Tower kernel: ip_output+0xab/0xdd Oct 15 01:32:59 Tower kernel: ? ip_fragment.constprop.0+0x7d/0x7d Oct 15 01:32:59 Tower kernel: ip_forward+0x3c0/0x3ef Oct 15 01:32:59 Tower kernel: ? ipv4_frags_exit_net+0x2b/0x2b Oct 15 01:32:59 Tower kernel: ip_sabotage_in+0x38/0x3e Oct 15 01:32:59 Tower kernel: nf_hook_slow+0x3a/0x90 Oct 15 01:32:59 Tower kernel: ip_rcv+0x8e/0xbe Oct 15 01:32:59 Tower kernel: ? ip_rcv_finish_core.isra.0+0x2e1/0x2e1 Oct 15 01:32:59 Tower kernel: __netif_receive_skb_one_core+0x53/0x6f Oct 15 01:32:59 Tower kernel: netif_receive_skb_internal+0x79/0x94 Oct 15 01:32:59 Tower kernel: br_pass_frame_up+0x128/0x14a Oct 15 01:32:59 Tower kernel: ? br_port_flags_change+0x29/0x29 Oct 15 01:32:59 Tower kernel: br_handle_frame_finish+0x342/0x383 Oct 15 01:32:59 Tower kernel: ? br_pass_frame_up+0x14a/0x14a Oct 15 01:32:59 Tower kernel: br_nf_hook_thresh+0xa3/0xc3 Oct 15 01:32:59 Tower kernel: ? br_pass_frame_up+0x14a/0x14a Oct 15 01:32:59 Tower kernel: br_nf_pre_routing_finish+0x24a/0x271 Oct 15 01:32:59 Tower kernel: ? br_pass_frame_up+0x14a/0x14a Oct 15 01:32:59 Tower kernel: ? br_handle_local_finish+0xe/0xe Oct 15 01:32:59 Tower kernel: ? nf_nat_ipv4_in+0x1e/0x62 [nf_nat_ipv4] Oct 15 01:32:59 Tower kernel: ? br_handle_local_finish+0xe/0xe Oct 15 01:32:59 Tower kernel: br_nf_pre_routing+0x31c/0x343 Oct 15 01:32:59 Tower kernel: ? br_nf_forward_ip+0x362/0x362 Oct 15 01:32:59 Tower kernel: nf_hook_slow+0x3a/0x90 Oct 15 01:32:59 Tower kernel: br_handle_frame+0x27e/0x2bd Oct 15 01:32:59 Tower kernel: ? br_pass_frame_up+0x14a/0x14a Oct 15 01:32:59 Tower kernel: __netif_receive_skb_core+0x4a7/0x7b1 Oct 15 01:32:59 Tower kernel: ? enqueue_task_fair+0xba/0x676 Oct 15 01:32:59 Tower kernel: __netif_receive_skb_one_core+0x35/0x6f Oct 15 01:32:59 Tower kernel: process_backlog+0x77/0x10e Oct 15 01:32:59 Tower kernel: net_rx_action+0x107/0x26c Oct 15 01:32:59 Tower kernel: __do_softirq+0xc9/0x1d7 Oct 15 01:32:59 Tower kernel: do_softirq_own_stack+0x2a/0x40 Oct 15 01:32:59 Tower kernel: </IRQ> Oct 15 01:32:59 Tower kernel: do_softirq+0x4d/0x5a Oct 15 01:32:59 Tower kernel: __local_bh_enable_ip+0x42/0x4a Oct 15 01:32:59 Tower kernel: ip_finish_output2+0x30d/0x353 Oct 15 01:32:59 Tower kernel: ip_output+0xbe/0xdd Oct 15 01:32:59 Tower kernel: ? ip_reply_glue_bits+0x36/0x36 Oct 15 01:32:59 Tower kernel: ip_send_skb+0x10/0x32 Oct 15 01:32:59 Tower kernel: udp_send_skb+0x26a/0x2cb Oct 15 01:32:59 Tower kernel: udp_sendmsg+0x5df/0x809 Oct 15 01:32:59 Tower kernel: ? ip_reply_glue_bits+0x36/0x36 Oct 15 01:32:59 Tower kernel: ? seccomp_run_filters+0x101/0x143 Oct 15 01:32:59 Tower kernel: ? sock_sendmsg+0x14/0x1e Oct 15 01:32:59 Tower kernel: sock_sendmsg+0x14/0x1e Oct 15 01:32:59 Tower kernel: __sys_sendto+0xce/0x10c Oct 15 01:32:59 Tower kernel: ? __sys_connect+0x86/0xad Oct 15 01:32:59 Tower kernel: ? syscall_trace_enter+0x163/0x1aa Oct 15 01:32:59 Tower kernel: __x64_sys_sendto+0x20/0x23 Oct 15 01:32:59 Tower kernel: do_syscall_64+0x57/0xf2 Oct 15 01:32:59 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Oct 15 01:32:59 Tower kernel: RIP: 0033:0x15485eb0ee46 Oct 15 01:32:59 Tower kernel: Code: d5 53 49 89 f4 89 fb 48 83 ec 10 e8 64 da 00 00 45 31 c9 89 c5 45 31 c0 45 89 f2 4c 89 ea 4c 89 e6 89 df b8 2c 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 36 89 ef 48 89 44 24 08 e8 96 da 00 00 48 8b Oct 15 01:32:59 Tower kernel: RSP: 002b:00001548557a9dc0 EFLAGS: 00000246 ORIG_RAX: 000000000000002c Oct 15 01:32:59 Tower kernel: RAX: ffffffffffffffda RBX: 0000000000000036 RCX: 000015485eb0ee46 Oct 15 01:32:59 Tower kernel: R10: 0000000000004000 R11: 0000000000000246 R12: 00001548557aa060 Oct 15 01:32:59 Tower kernel: R13: 000000000000002a R14: 0000000000004000 R15: 0000000000000000 Oct 15 01:32:59 Tower kernel: Modules linked in: veth xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat nf_nat_ipv6 ip6table_filter ip6_tables vhost_net vhost tap macvlan xt_nat ipt_MASQUERADE iptable_filter iptable_nat nf_nat_ipv4 nf_nat iptable_mangle ip_tables ext4 mbcache jbd2 xfs nfsd lockd grace sunrpc md_mod tun bonding 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 e1000e glue_helper cdc_acm intel_cstate intel_wmi_thunderbolt intel_uncore ahci video intel_rapl_perf libahci wmi backlight fan thermal acpi_pad pcc_cpufreq button Oct 15 01:32:59 Tower kernel: ---[ end trace 9b52bba97c992e66 ]---
  14. I'm an idiot. There's nothing wrong. My script adds a prerouting mangle rule. I wasn't displaying the mangle table when looking at iptables rules. My real problem was that my docker container's IP changed - not sure if that was caused the 6.8.3 upgrade, or if it was me messing something up.
  15. Attached. I did check that. Both shares have 0KB minimum free space. tower-diagnostics-20200531-1537.zip