joghurt

Dec 14 21:27:10 unnas kernel: WARNING: CPU: 2 PID: 214 at net/netfilter/nf_conntrack_core.c:1210 __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Dec 14 21:27:10 unnas kernel: Modules linked in: xt_connmark xt_comment iptable_raw xt_mark veth xt_nat xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap macvlan xt_conntrack nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter xfs md_mod nvidia_uvm(PO) nfsd auth_rpcgss oid_registry lockd grace sunrpc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs bridge stp llc r8169 realtek nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) edac_mce_amd edac_core intel_rapl_msr intel_rapl_common iosf_mbi kvm_amd video drm_kms_helper wmi_bmof kvm drm i2c_piix4 backlight crct10dif_pclmul Dec 14 21:27:10 unnas kernel: crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel mpt3sas crypto_simd cryptd rapl i2c_core nvme ccp k10temp syscopyarea sysfillrect joydev sysimgblt nvme_core raid_class fb_sys_fops ahci scsi_transport_sas libahci wmi acpi_cpufreq button unix [last unloaded: md_mod] Dec 14 21:27:10 unnas kernel: CPU: 2 PID: 214 Comm: kworker/u64:2 Tainted: P S O 6.1.64-Unraid #1 Dec 14 21:27:10 unnas kernel: Hardware name: Micro-Star International Co., Ltd. MS-7C91/MAG B550 TOMAHAWK (MS-7C91), BIOS A.30 09/03/2020 Dec 14 21:27:10 unnas kernel: Workqueue: events_unbound macvlan_process_broadcast [macvlan] Dec 14 21:27:10 unnas kernel: RIP: 0010:__nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Dec 14 21:27:10 unnas kernel: Code: 44 24 10 e8 e2 e1 ff ff 8b 7c 24 04 89 ea 89 c6 89 04 24 e8 7e e6 ff ff 84 c0 75 a2 48 89 df e8 9b e2 ff ff 85 c0 89 c5 74 18 <0f> 0b 8b 34 24 8b 7c 24 04 e8 18 dd ff ff e8 93 e3 ff ff e9 72 01 Dec 14 21:27:10 unnas kernel: RSP: 0018:ffffc900002d0d98 EFLAGS: 00010202 Dec 14 21:27:10 unnas kernel: RAX: 0000000000000001 RBX: ffff888f171ddb00 RCX: d14fec8bffaba235 Dec 14 21:27:10 unnas kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff888f171ddb00 Dec 14 21:27:10 unnas kernel: RBP: 0000000000000001 R08: 66001eb332a4e646 R09: 8b6df33dc3efa0ed Dec 14 21:27:10 unnas kernel: R10: 8129f0f28ff1f46a R11: ffffc900002d0d60 R12: ffffffff82a14d00 Dec 14 21:27:10 unnas kernel: R13: 00000000000153a7 R14: ffff888cfb4b4b00 R15: 0000000000000000 Dec 14 21:27:10 unnas kernel: FS: 0000000000000000(0000) GS:ffff888fee880000(0000) knlGS:0000000000000000 Dec 14 21:27:10 unnas kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 14 21:27:10 unnas kernel: CR2: 0000000000556000 CR3: 00000002f40b8000 CR4: 0000000000750ee0 Dec 14 21:27:10 unnas kernel: PKRU: 55555554 Dec 14 21:27:10 unnas kernel: Call Trace: Dec 14 21:27:10 unnas kernel: Dec 14 21:27:10 unnas kernel: ? __warn+0xab/0x122 Dec 14 21:27:10 unnas kernel: ? report_bug+0x109/0x17e Dec 14 21:27:10 unnas kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Dec 14 21:27:10 unnas kernel: ? handle_bug+0x41/0x6f Dec 14 21:27:10 unnas kernel: ? exc_invalid_op+0x13/0x60 Dec 14 21:27:10 unnas kernel: ? asm_exc_invalid_op+0x16/0x20 Dec 14 21:27:10 unnas kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Dec 14 21:27:10 unnas kernel: ? __nf_conntrack_confirm+0x9e/0x2b0 [nf_conntrack] Dec 14 21:27:10 unnas kernel: ? nf_nat_inet_fn+0x126/0x1a8 [nf_nat] Dec 14 21:27:10 unnas kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack] Dec 14 21:27:10 unnas kernel: nf_hook_slow+0x3d/0x96 Dec 14 21:27:10 unnas kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Dec 14 21:27:10 unnas kernel: NF_HOOK.constprop.0+0x79/0xd9 Dec 14 21:27:10 unnas kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Dec 14 21:27:10 unnas kernel: __netif_receive_skb_one_core+0x77/0x9c Dec 14 21:27:10 unnas kernel: process_backlog+0x8c/0x116 Dec 14 21:27:10 unnas kernel: __napi_poll.constprop.0+0x2b/0x124 Dec 14 21:27:10 unnas kernel: net_rx_action+0x159/0x24f Dec 14 21:27:10 unnas kernel: __do_softirq+0x129/0x288 Dec 14 21:27:10 unnas kernel: do_softirq+0x7f/0xab Dec 14 21:27:10 unnas kernel: Dec 14 21:27:10 unnas kernel: Dec 14 21:27:10 unnas kernel: __local_bh_enable_ip+0x4c/0x6b Dec 14 21:27:10 unnas kernel: netif_rx+0x52/0x5a Dec 14 21:27:10 unnas kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Dec 14 21:27:10 unnas kernel: ? _raw_spin_unlock+0x14/0x29 Dec 14 21:27:10 unnas kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Dec 14 21:27:10 unnas kernel: process_one_work+0x1ab/0x295 Dec 14 21:27:10 unnas kernel: worker_thread+0x18b/0x244 Dec 14 21:27:10 unnas kernel: ? rescuer_thread+0x281/0x281 Dec 14 21:27:10 unnas kernel: kthread+0xe7/0xef Dec 14 21:27:10 unnas kernel: ? kthread_complete_and_exit+0x1b/0x1b Dec 14 21:27:10 unnas kernel: ret_from_fork+0x22/0x30 Dec 14 21:27:10 unnas kernel: Dec 14 21:27:10 unnas kernel: ---[ end trace 0000000000000000 ]--- Hi. Since update to Unraid 6.12.6 i see this error message in the log file. By searching this through the unraid forum i found a couple of same topics, but with an older version of unraid. Before update i didn't had this log file entries. Is there any suggest what i could do in order to fix it ? Thank you very much.

When will this BUG finally be fixed? - I tried this workaround from @ryddan. But this does not solve the problem completely. Once in a while it happens again and again and again.... IF you now ask for diagnostic file, I would ask you why this happens since the version where you established the cache pools ? You tell me to use SMB, but I don't want to use SMB, I want to use NFS, as it is provided by the system. So please when will it finally be fixed? - On other tasks you received already a lot of diags regarding this problem. Thank for qualified answer.

i faced problems with smb shares and honestly spoken i am not familiar with the options to put in my fstab file. my Client is MX Linux. Could you maybe please let me know the entry in my fstab ? i mean the options. I would very appreciate it. Thx

thx for your reply. switch to smb is the solution ? - i use NFS. and i love NFS. 😭 Is there another solution for this issue maybe ? i never had problems before and i use NFS for years already in unraid.

Hi. I've read a lot about the mnt/user problem here in the forum and that you should upload your diagnostics. I found out the following. my shares disappear when i try to delete directories that still contain files. I try to delete them from my PC, but then I get the message: "Delete not possible, directory not empty." The files have been deleted anyway, but the empty directories are still there. If I try again now, the directory is either deleted and everything continues to run normally, or I get the same error again. If that happens, then I can see in the unraid gui that all shares have disappeared. only a restart will help. what i also noticed is that it doesn't matter whether the directories are on the array or on a single cache_pool hard disk. it seems to happen more often on the cache pool hard drive. I hope I was able to contribute a bit to finding a solution and you can help me. I installed tdarr but never had any problems with it, because of a thread here I uninstalled it, but that didn't solve my problem. I thank you in advance for any support. diagnostics-20221206-1142.zip

Question regarding NUT Docker. How can i make it accessible with Nginx reverse proxy from WAN? inside LAN it is working fine with nutfs protocol. Accessing from WAN i am lost. please help. Thx. I tried already https protocol with SSL. With browser i get 404 which is ok i think. but with the nintendo i get nothing. no listing and in log i see: HEAD /api/scan HTTP/1.1" 401

I have problems with the actual version 2.7.8 How can I roll back to an older version. Is there a chance by changing the repository path? the actual entry says: jlesage/avidemux thx in advance.

Thx, I followed the instructions and deleted the conf files. The most of the log entry disappeared. 👍 Last message left is the system warning: nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html) Is there anything I could do on this? Many thx in advance,

Hi, this is my first post, I am still new in unraid, sorry for mybe non-professionel question. I tried to migrate my running let'sencrypt docker to swag like described, so far so good. all is running. but in the logs i can see the following and I hope you can advice me what has to be done. nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html) nginx: [error] lua_load_resty_core failed to load the resty.core module from https://github.com/openresty/lua-resty-core; ensure you are using an OpenResty release from https://openresty.org/en/download.html (rc: 2, reason: module 'resty.core' not found: no field package.preload['resty.core'] no file './resty/core.lua' no file '/usr/share/luajit-2.1.0-beta3/resty/core.lua' no file '/usr/local/share/lua/5.1/resty/core.lua' no file '/usr/local/share/lua/5.1/resty/core/init.lua' no file '/usr/share/lua/5.1/resty/core.lua' no file '/usr/share/lua/5.1/resty/core/init.lua' no file '/usr/share/lua/common/resty/core.lua' no file '/usr/share/lua/common/resty/core/init.lua' no file './resty/core.so' no file '/usr/local/lib/lua/5.1/resty/core.so' no file '/usr/lib/lua/5.1/resty/core.so' no file '/usr/local/lib/lua/5.1/loadall.so' no file './resty.so' no file '/usr/local/lib/lua/5.1/resty.so' no file '/usr/lib/lua/5.1/resty.so' no file '/usr/local/lib/lua/5.1/loadall.so') Server ready Thx in advance.

Thx for reply. Indeed, this seems to be my problem, too. I downgraded to 6.6.7 and the freezing problem disappeared.

Hi. I am new in the Unraid area. I built my 1 st server and I need help please. My hardware is: M/B: ASRock Z390 Phantom Gaming 4S Version BIOS: American Megatrends Inc. Version P1.20. Dated: 05/06/2019 CPU: Intel® Core™ i7-9700 CPU @ 3.00GHz HVM: Enabled IOMMU: Enabled Cache: 512 KiB, 2048 KiB, 12288 KiB Memory: 32 GiB DDR4 SATA controller: DELL perc h310 (flashed) for AHCI mode Harddisks: Parity (1x12TB HDD), Array (2x12 TB, 1x 8TB), Cache: 1x M2 Samsung SSD 500 GB my problem is: I can only do 1 task simultaneously. i.e. if I copy in the background 1 file, 8 CPU threads run up to red 100% and the stream, which is running at the same time, is freezing, until copying is finished. It doesn't matter what I do. unpacking, copy, moving or downloading files, always the same. As soon, as I try to start 2 things parallel, 2nd task starts to freeze or even go very slow until the other task finished. I followed the instruction to setup the BIOS from here: BIOS Settings The only thing I didn't find was: Hyper-Threading, the rest I changed as it is described in the video. I tried the HDD's on both SATA controller (Dell perc and onboard). Same result, unfortunately. My hardware should be powerful enough ti handle this, right ? What else can I check? - Does someone know this problem? Thanks in advance for help. Installed plugin: Fix common problems: 0 errors found.