-
-
7.0.1 Unraid unresponsive
Hi @DanW. Did you ever resolve the issue? I am seeing similar winbindd logs, and think it could be related. Thanks
-
System freeze every 10 days on Unraid 7.1.4 (winbindd running even with AD disabled)
Ok, I killed it. I will update if I see the issue again. Thanks for all your help!
-
System freeze every 10 days on Unraid 7.1.4 (winbindd running even with AD disabled)
Thank you for the reply. The timeout event I was referring to happened at Aug 17 ~16:00–16:01 Aug 17 01:43:45 Sparrow winbindd[1930]: [2025/08/17 01:43:41.888272, 0, traceid=41381] ../../source3/winbindd/winbindd_samr.c:71(open_internal_samr_conn) Aug 17 01:43:45 Sparrow winbindd[1930]: open_internal_samr_conn: Could not connect to samr pipe: NT_STATUS_IO_TIMEOUTAnd there is another one at Aug 17 16:01:44 Aug 17 16:01:44 Sparrow winbindd[1928]: [2025/08/17 16:01:44.335300, 0, traceid=42533] ../../source3/winbindd/winbindd.c:819(winbind_client_processed) Aug 17 16:01:44 Sparrow winbindd[1928]: winbind_client_processed: request took 103.132831 seconds Aug 17 16:01:44 Sparrow winbindd[1928]: [struct process_request_state] ../../source3/winbindd/winbindd.c:438 [2025/08/17 16:00:01.151017] ../../source3/winbindd/winbindd.c:619 [2025/08/17 16:01:44.283848] [103.132831] -> TEVENT_REQ_DONE (2 0)) Aug 17 16:01:44 Sparrow winbindd[1928]: [struct winbindd_getgroups_state] ../../source3/winbindd/winbindd_getgroups.c:53 [2025/08/17 16:00:01.151020] ../../source3/winbindd/winbindd_getgroups.c:115 [2025/08/17 16:01:44.192080] [103.041060] -> TEVENT_REQ_USER_ERROR (3 10483072397370982581)) Aug 17 16:01:44 Sparrow winbindd[1928]: [struct wb_lookupname_state] ../../source3/winbindd/wb_lookupname.c:47 [2025/08/17 16:00:01.180855] ../../source3/winbindd/wb_lookupname.c:99 [2025/08/17 16:01:44.192069] [103.011214] -> TEVENT_REQ_USER_ERROR (3 10483072397370982581)) Aug 17 16:01:44 Sparrow winbindd[1928]: [struct dcerpc_wbint_LookupName_state] librpc/gen_ndr/ndr_winbind_c.c:795 [2025/08/17 16:00:01.246545] librpc/gen_ndr/ndr_winbind_c.c:862 [2025/08/17 16:01:44.069891] [102.823346] -> TEVENT_REQ_DONE (2 0)) Aug 17 16:01:44 Sparrow winbindd[1928]: [struct dcerpc_wbint_LookupName_r_state] librpc/gen_ndr/ndr_winbind_c.c:707 [2025/08/17 16:00:01.272231] librpc/gen_ndr/ndr_winbind_c.c:742 [2025/08/17 16:01:44.065269] [102.793038] -> TEVENT_REQ_DONE (2 0)) Aug 17 16:01:44 Sparrow winbindd[1928]: [struct dcerpc_binding_handle_call_state] ../../librpc/rpc/binding_handle.c:370 [2025/08/17 16:00:01.295907] ../../librpc/rpc/binding_handle.c:520 [2025/08/17 16:01:43.895303] [102.599396] -> TEVENT_REQ_DONE (2 0)) Aug 17 16:01:44 Sparrow winbindd[1928]: [struct dcerpc_binding_handle_raw_call_state] ../../librpc/rpc/binding_handle.c:148 [2025/08/17 16:00:01.324714] ../../librpc/rpc/binding_handle.c:203 [2025/08/17 16:01:42.834369] [101.509655] -> TEVENT_REQ_DONE (2 0)) Aug 17 16:01:44 Sparrow winbindd[1928]: [struct wbint_bh_raw_call_state] ../../source3/winbindd/winbindd_dual_ndr.c:93 [2025/08/17 16:00:01.324718] ../../source3/winbindd/winbindd_dual_ndr.c:209 [2025/08/17 16:01:35.744982] [94.420264] -> TEVENT_REQ_DONE (2 0)) Aug 17 16:01:44 Sparrow winbindd[1928]: [struct wb_domain_request_state] ../../source3/winbindd/winbindd_dual.c:507 [2025/08/17 16:00:01.360959] ../../source3/winbindd/winbindd_dual.c:745 [2025/08/17 16:01:22.514507] [81.153548] -> TEVENT_REQ_DONE (2 0)) Aug 17 16:01:44 Sparrow winbindd[1928]: [struct wb_child_request_state] ../../source3/winbindd/winbindd_dual.c:203 [2025/08/17 16:00:01.360974] ../../source3/winbindd/winbindd_dual.c:306 [2025/08/17 16:01:19.115725] [77.754751] -> TEVENT_REQ_DONE (2 0)) Aug 17 16:01:44 Sparrow winbindd[1928]: [struct tevent_queue_wait_state] ../../tevent_queue.c:408 [2025/08/17 16:00:01.360976] ../../tevent_queue.c:429 [2025/08/17 16:00:01.360977] [0.000001] -> TEVENT_REQ_DONE (2 0)) Aug 17 16:01:44 Sparrow winbindd[1928]: [struct wb_simple_trans_state] ../../nsswitch/wb_reqtrans.c:375 [2025/08/17 16:00:01.360985] ../../nsswitch/wb_reqtrans.c:432 [2025/08/17 16:01:17.375294] [76.014309] -> TEVENT_REQ_DONE (2 0)) Aug 17 16:01:44 Sparrow winbindd[1928]: [struct req_write_state] ../../nsswitch/wb_reqtrans.c:158 [2025/08/17 16:00:01.360985] ../../nsswitch/wb_reqtrans.c:194 [2025/08/17 16:00:01.361008] [0.000023] -> TEVENT_REQ_DONE (2 0)) Aug 17 16:01:44 Sparrow winbindd[1928]: [struct writev_state] ../../lib/async_req/async_sock.c:261 [2025/08/17 16:00:01.360986] ../../lib/async_req/async_sock.c:369 [2025/08/17 16:00:01.361006] [0.000020] -> TEVENT_REQ_DONE (2 0)) Aug 17 16:01:44 Sparrow winbindd[1928]: [struct resp_read_state] ../../nsswitch/wb_reqtrans.c:222 [2025/08/17 16:00:01.361008] ../../nsswitch/wb_reqtrans.c:275 [2025/08/17 16:01:16.255509] [74.894501] -> TEVENT_REQ_DONE (2 0)) Aug 17 16:01:44 Sparrow winbindd[1928]: [struct read_packet_state] ../../lib/async_req/async_sock.c:461 [2025/08/17 16:00:01.361009] ../../lib/async_req/async_sock.c:549 [2025/08/17 16:01:07.225952] [65.864943] -> TEVENT_REQ_DONE (2 0)) Aug 17 16:01:44 Sparrow winbindd[1928]: [struct resp_write_state] ../../nsswitch/wb_reqtrans.c:307 [2025/08/17 16:01:44.283802] ../../nsswitch/wb_reqtrans.c:344 [2025/08/17 16:01:44.283847] [0.000045] -> TEVENT_REQ_DONE (2 0)) Aug 17 16:01:44 Sparrow winbindd[1928]: [struct writev_state] ../../lib/async_req/async_sock.c:261 [2025/08/17 16:01:44.283804] ../../lib/async_req/async_sock.c:369 [2025/08/17 16:01:44.283818] [0.000014] -> TEVENT_REQ_DONE (2 0)) Ok. Good to know! I have attached the diagnostics. Thank you! I really appreciate you taking a look into this sparrow-diagnostics-20250818-0141.zip
-
System freeze every 10 days on Unraid 7.1.4 (winbindd running even with AD disabled)
Hello! I’m running into an issue with a fresh install of Unraid 7.1.4, where my system seems to freeze/lock-up about every 10 days. It has happened 3 times now. During a freeze, the fans spin up to max, the system goes extremely slow/unresponsive (SSH and WebGUI unavailable), and I have to plug in a keyboard and reboot locally to recover. After enabling syslog to disk, the last freeze (Aug 17) shows a timeout event just before everything locks up. Soon after, a Docker container begins failing and looping repeatedly (in the last case, it was autobrr - br-bbfbd846e5fe). In my investigation, I noticed something strange: even though I never enabled Active Directory, I can see winbindd running. From what I’ve read, winbindd should only be there if AD is enabled. I’ve seen old posts suggesting killing it on boot as a workaround, but I thought that was fixed in newer versions. I’m wondering if this is a deeper issue that’s still present. Has anyone else seen this behavior on 7.x? Do you think I am overthinking it and should just kill winbindd? Thank you. syslog-10.0.10.10.log
jamesmoran
Members
-
Joined
-
Last visited