loheiman

Recently been having an issue where after a few days of uptime, the server seems to hang and the web UI becomes inaccessible. I've heard that using macvlan could be the culprit but haven't been able to verify that. I do use custom networks for docker containers. I just noticed my server not responding and rebooted. I exported diagnostics zip from the webUI but have also been mirroring the syslos to the flash drive and have attached that directly. The attached syslog shows this right before it hung: Jun 5 02:30:47 Tower kernel: BUG: kernel NULL pointer dereference, address: 0000000000000008 Jun 5 02:30:47 Tower kernel: #PF: supervisor read access in kernel mode Jun 5 02:30:47 Tower kernel: #PF: error_code(0x0000) - not-present page Jun 5 02:30:47 Tower kernel: PGD 0 P4D 0 Jun 5 02:30:47 Tower kernel: Oops: 0000 [#2] PREEMPT SMP PTI Jun 5 02:30:47 Tower kernel: CPU: 2 PID: 6743 Comm: btrfs-transacti Tainted: G B D 5.19.17-Unraid #2 Jun 5 02:30:47 Tower kernel: Hardware name: HP HP Slim Desktop 290-p0xxx/843F, BIOS F.40 11/21/2019 Jun 5 02:30:47 Tower kernel: RIP: 0010:rb_erase+0x17c/0x294 Jun 5 02:30:47 Tower kernel: Code: 48 89 7e 10 49 89 01 e8 2d f8 ff ff 4c 89 ce 48 8b 4e 08 48 85 c9 74 05 f6 01 01 74 3f 48 8b 46 10 48 85 c0 0f 84 8b 00 00 00 <f6> 00 01 0f 85 82 00 00 00 48 8b 50 08 48 85 d2 48 89 56 10 48 89 Jun 5 02:30:47 Tower kernel: RSP: 0018:ffffc90000697d18 EFLAGS: 00010202 Jun 5 02:30:47 Tower kernel: RAX: 0000000000000008 RBX: ffff8881ef355960 RCX: 0000000000000000 Jun 5 02:30:47 Tower kernel: RDX: ffff8881ef355960 RSI: ffff888029afd690 RDI: ffff888029afd840 Jun 5 02:30:47 Tower kernel: RBP: ffff888103a9e240 R08: ffff8881ef355960 R09: ffff888029afd690 Jun 5 02:30:47 Tower kernel: R10: ffff8882e563e3f0 R11: ffff88801820ed60 R12: ffff888103a9e2a0 Jun 5 02:30:47 Tower kernel: R13: ffff888153964000 R14: 0000000000000000 R15: ffff888155678f70 Jun 5 02:30:47 Tower kernel: FS: 0000000000000000(0000) GS:ffff88845f480000(0000) knlGS:0000000000000000 Jun 5 02:30:47 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 5 02:30:47 Tower kernel: CR2: 0000000000000008 CR3: 000000000220a006 CR4: 00000000003706e0 Jun 5 02:30:47 Tower kernel: Call Trace: Jun 5 02:30:47 Tower kernel: <TASK> Jun 5 02:30:47 Tower kernel: btrfs_delete_ref_head+0x30/0x52 Jun 5 02:30:47 Tower kernel: __btrfs_run_delayed_refs+0x9e6/0xb5e Jun 5 02:30:47 Tower kernel: btrfs_run_delayed_refs+0x5b/0x12c Jun 5 02:30:47 Tower kernel: ? preempt_latency_start+0x2b/0x46 Jun 5 02:30:47 Tower kernel: btrfs_commit_transaction+0x60/0xa66 Jun 5 02:30:47 Tower kernel: ? start_transaction+0x3d2/0x442 Jun 5 02:30:47 Tower kernel: transaction_kthread+0x105/0x17b Jun 5 02:30:47 Tower kernel: ? btrfs_cleanup_transaction.isra.0+0x3b1/0x3b1 Jun 5 02:30:47 Tower kernel: kthread+0xe4/0xef Jun 5 02:30:47 Tower kernel: ? kthread_complete_and_exit+0x1b/0x1b Jun 5 02:30:47 Tower kernel: ret_from_fork+0x1f/0x30 Jun 5 02:30:47 Tower kernel: </TASK> Jun 5 02:30:47 Tower kernel: Modules linked in: veth macvlan xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod tcp_diag inet_diag ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge 8021q garp mrp stp llc bonding tls i915 x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel iosf_mbi drm_buddy i2c_algo_bit ttm kvm drm_display_helper drm_kms_helper drm crct10dif_pclmul btusb crc32_pclmul btrtl r8169 crc32c_intel i2c_i801 btbcm input_leds ghash_clmulni_intel wmi_bmof aesni_intel crypto_simd cryptd rapl intel_cstate intel_uncore led_class i2c_smbus btintel realtek bluetooth ahci intel_gtt nvme libahci agpgart nvme_core i2c_core ecdh_generic ecc syscopyarea sysfillrect sysimgblt intel_pch_thermal fb_sys_fops fan thermal wmi tpm_crb tpm_tis video tpm_tis_core backlight tpm acpi_pad button acpi_tad unix Jun 5 02:30:47 Tower kernel: CR2: 0000000000000008 Jun 5 02:30:47 Tower kernel: ---[ end trace 0000000000000000 ]--- Jun 5 02:30:47 Tower kernel: RIP: 0010:vfs_getattr_nosec+0x68/0x97 Jun 5 02:30:47 Tower kernel: Code: 20 05 df 07 00 00 89 06 41 f6 42 0d 08 74 08 48 c7 46 10 00 10 00 00 48 c7 46 18 00 10 20 00 49 8b 01 48 8b 78 18 49 8b 42 20 <48> 8b 40 70 48 85 c0 74 14 89 d1 41 81 e0 00 60 00 00 48 89 f2 4c Jun 5 02:30:47 Tower kernel: RSP: 0018:ffffc900031bfe08 EFLAGS: 00010246 Jun 5 02:30:47 Tower kernel: RAX: 0000000000000000 RBX: ffffc900031bfe98 RCX: 0000000000000000 Jun 5 02:30:47 Tower kernel: RDX: 00000000000007ff RSI: ffffc900031bfe98 RDI: ffffffff8223dbc0 Jun 5 02:30:47 Tower kernel: RBP: 0000000000000000 R08: 0000000000000900 R09: ffffc900031bfe18 Jun 5 02:30:47 Tower kernel: R10: ffff888029c59010 R11: ffffc900031bfe9c R12: 0000000000000900 Jun 5 02:30:47 Tower kernel: R13: 00000000ffffff9c R14: ffff888100e5c000 R15: 00000000000007ff Jun 5 02:30:47 Tower kernel: FS: 0000000000000000(0000) GS:ffff88845f480000(0000) knlGS:0000000000000000 Jun 5 02:30:47 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 5 02:30:47 Tower kernel: CR2: 0000000000000008 CR3: 000000000220a006 CR4: 00000000003706e0 Jun 5 02:30:47 Tower kernel: note: btrfs-transacti[6743] exited with preempt_count 2 Jun 5 10:50:15 Tower kernel: microcode: microcode updated early to revision 0xf0, date = 2021-11-15 Jun 5 10:50:15 Tower kernel: Linux version 5.19.17-Unraid (root@Develop) (gcc (GCC) 12.2.0, GNU ld version 2.39-slack151) #2 SMP PREEMPT_DYNAMIC Wed Nov 2 11:54:15 PDT 2022 tower-diagnostics-20230605-1051.zip syslog

What does "Create separate archives (one per folder)?" option do exactly? Does it create separate archiver per folder in the appdata folder and thus allow the user to restore a single app's appdata folder? Also why does the Verify Backups option say it can lead to broken backups? Where can I learn more about the pros/cons of enabling this? Thanks

Weird. Decided to simply create a new config again and now all my shares are back.

Yesterday I started getting issues that a disk was missing and I thought it was a bad SATA cable so i decided to create a new config without the missing disk. I didn't think it would be a big deal because I don't run parity so I didn't think I'd lose anything. However, now the issue is that all of the default shares (isos, domains, appdatasystem) as well as previously created ones that were once set to use cache only eg. Downloads are no longer shown in the User Shares page thus many containers are having issues. Additionally, if i try to create a new share, after entering the share details and clicking "add share" the share is not created and the list of User Shares remains the same. I've attached diagnostics. Thanks tower-diagnostics-20221219-2207.zip

Any plans to add the ability to automatically invoke mover when disk usage reaches a certain usage percentage? Thanks

When I entered https://ipaddress without internet access, chrome gave me a DNS resolution error. Yes, I am trying to make sure I have access to my server during a temporary internet outage. A previous poster suggested a solution that to add an entry to your local hosts file which I don't feel comfortable doing on a company-managed device.

Thanks for the suggestions but entering https://ipaddress did not work for me. I cannot change the DNS settings on the device i'm using as it's corporate-managed. I guess the only solution is to disable SSL and remote access?

After enabling remote management, I seem to be unable to access the Unraid login/dashboard page when my internet is down. Previously, I could always just go the IP address eg. 10.0.0.5 and the login page would load. Now, when I enter that IP address, it always forwards to xxxx.unraid.net therefore appearing to try to load the page over the internet. Am I imagining this? What's the solution here?

Ahh, yes i see that now in the syslogs. Thanks for the clarification!

Everytime the plugin does its scan, i get the error: "Fix Common Problems: Warning: CPU Overheating" but i'm certain it's a false positive. For example, i just ran it now (by clicking "rescan" on the plugin page) when the CPU temp is 50 deg C and I got the warning. Any ideas on how to fix this?

+1

I'm having trouble getting this to work but I'm probably missing something very obvious. I have no experience with syslog servers. I'm trying to use this as a remote syslog server for my Unifi controller (running on same Unraid machine but different IP). I verified that my Unifi controller is sending logs by creating a temporary server on my mac in terminal (using UDP 514). I then pointed the Unifi controller to this container's and set port to 9997 (I also tried 514). When I search in Splunk, it says 0 events have been recorded. EDIT: Once i created a Data Input in the Splunk Container for UDP 514 and added the 514 port to the container during the install it worked. Am I correct in that both of those steps were required? What's the benefit of using 9997 and how would i do that? Thanks!

Is it possible to leave the Unraid GUI and Unifi docker container on VLAN 1 untagged and have all the other docker containers on another VLAN and have those other docker containers share the same IP address? I want to avoid having to update the IP address of each docker to docker connection with a unique IP address and would like to reduce the noise when viewing my Router's DHCP lease table (and not see a client for each docker container).