XtremeOwnage

Nearly 10 years late to the party- but, since I came looking for this, I landed here- and I am going to provide the solution. `root@Tower:~# /usr/local/etc/rc.d/rc.nfsd restart`

Sure- and to note- it has been rock solid since re-configuring the networking.

Changed Status to Solved

Since, doing those changes this morning, its been rock solid. Appears my issue was related to networking, bridges, docker, etc....

Ran a full hardware diagnostics / memory scan. Came back clean. So, re-updated to 6.12.4. Moved docker to a dedicated NIC, following the instructions linked from release notes. Changed docker from ipvlan to macvlan. Disabled bridging on NICs. Has been running stable so far. Will post again this evening.

So far, appears that may have resolved the issue. If the issue doesn't crop up again tomm, will close this one.

Rebooted the underlying host. going to keep troubleshooting things on my side...

Nope. went and ate dinner after stopping suspect containers. Tried to turn plex on TV, and its dead. Get back to observe, Unraid is completely unresponsive, using around 16 threads worth of CPU. No services responding. No NFS, SMB, No docker containers responding. No SSH. Nothing.

Issue still exists. Would appear, this issue appears to potentially be related to one of my docker containers. Happened to have a top running, and noticed a certain "java" process using a ton of CPU. stopped the container which uses java on the backend. Will post updates, if this turns out it was the problem.

Changed Status to Solved

Marking this one as closed- as one of the recent RCs disabled exclusive shares when NFS is enabled, technically fixing the issue.

Reproduced the issue. root@Tower:~# tail -n 40 /var/log/samba/log.winbindd-idmap [2023/06/11 21:30:34.502927, 0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler) Got sig[15] terminate (is_parent=0) [2023/06/13 11:17:36.643885, 0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler) Got sig[15] terminate (is_parent=0) [2023/06/13 11:17:49.141681, 0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler) Got sig[15] terminate (is_parent=0) [2023/06/14 13:24:32.275543, 0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler) Got sig[15] terminate (is_parent=0) [2023/06/14 13:26:44.716683, 0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler) Got sig[15] terminate (is_parent=0) [2023/06/14 13:27:03.166807, 0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler) Got sig[15] terminate (is_parent=0) [2023/06/14 13:27:26.754073, 0] ../../source3/passdb/pdb_smbpasswd.c:1251(build_sam_account) build_sam_account: smbpasswd database is corrupt! username media with uid 1003 is not in unix passwd database! Just- created a new user account, and added it to a share.

Yea, I don't know how to explain this, but, it only randomly spins up disks for a day or two after booting. (Disk in the array, empty, unused) Another disk in the array, also empty, unused. Random, unmounted, unused disk. Not in any pool or array. This matches what I noticed before. To note, these images were taken on 6/14 @ 11:47am. Disks have not spun up in two days. Any ideas on that one?

I... think I have solved the cause here- Appears restarting samba "fixed" being able to su/ssh/sftp/etc.... root@Tower:/etc/samba# /etc/rc.d/rc.samba restart Starting Samba: /usr/sbin/smbd -D /usr/sbin/nmbd -D /usr/sbin/wsdd2 -d -4 /usr/sbin/winbindd -D root@Tower:/etc/samba# cd .. root@Tower:/etc# nano nsswitch.conf root@Tower:/etc# su root root@Tower:~# exit exit root@Tower:/etc# time id root uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),17(audio),281(docker) real 0m0.011s user 0m0.006s sys 0m0.003s root@Tower:/etc# Guess the remaining question- is what happened? Is it a bug? And- should it be fixed? Edit... Appears some of the logs got cutoff from earlier.