Steviewunda Posted November 2, 2018 Share Posted November 2, 2018 Hi - after a few days Fix Common Problems states that the system log has grown too large, and the system becomes less responsive - until I restart the unRaid server. Any help appreciated - diagnostics log attached tower-diagnostics-20181103-1216.zip unRaid 6.6.3 Model: Custom M/B: Gigabyte Technology Co., Ltd. - AX370-Gaming K7 CPU: AMD Ryzen 3 2200G with Radeon Vega Graphics @ 3500 HVM: Enabled IOMMU: Enabled Cache: 384 kB, 2048 kB, 4096 kB Memory: 32 GB (max. installable capacity 256 GB) Network: eth0: 1000 Mb/s, full duplex, mtu 1500 eth1: not connected eth2: 10000 Mb/s, full duplex, mtu 9000 Kernel: Linux 4.18.15-unRAID x86_64 OpenSSL: 1.1.0i Link to comment
Steviewunda Posted November 3, 2018 Author Share Posted November 3, 2018 Can anyone help with this? Link to comment
JorgeB Posted November 3, 2018 Share Posted November 3, 2018 You log is filled with these: Nov 2 09:13:01 Tower winbindd[1795]: [2018/11/02 09:13:01.828109, 3] ../source3/winbindd/winbindd_samr.c:741(sam_rids_to_names) Nov 2 09:13:01 Tower winbindd[1795]: sam_rids_to_names for TOWER Nov 2 09:13:01 Tower winbindd[1795]: [2018/11/02 09:13:01.828559, 3] ../source3/winbindd/winbindd_samr.c:741(sam_rids_to_names) Nov 2 09:13:01 Tower winbindd[1795]: sam_rids_to_names for TOWER Nov 2 09:13:01 Tower winbindd[1795]: [2018/11/02 09:13:01.828938, 3] ../source3/winbindd/winbindd_samr.c:741(sam_rids_to_names) Nov 2 09:13:01 Tower winbindd[1795]: sam_rids_to_names for TOWER Nov 2 09:13:01 Tower nmbd[1784]: [2018/11/02 09:13:01.855754, 3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request) Nov 2 09:13:01 Tower nmbd[1784]: process_name_query_request: Name query from 10.10.10.2 on subnet 10.10.10.2 for name #001#002__MSBROWSE__#002<01> Nov 2 09:13:01 Tower nmbd[1784]: [2018/11/02 09:13:01.855816, 3] ../source3/nmbd/nmbd_incomingrequests.c:574(process_name_query_request) Nov 2 09:13:01 Tower nmbd[1784]: OK Nov 2 09:13:01 Tower nmbd[1784]: [2018/11/02 09:13:01.855924, 3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request) Nov 2 09:13:01 Tower nmbd[1784]: process_name_query_request: Name query from 192.168.1.50 on subnet 192.168.1.50 for name #001#002__MSBROWSE__#002<01> Nov 2 09:13:01 Tower nmbd[1784]: [2018/11/02 09:13:01.855954, 3] ../source3/nmbd/nmbd_incomingrequests.c:574(process_name_query_request) Nov 2 09:13:01 Tower nmbd[1784]: OK Do winbindd and nmbd mean anything to you? Likely something you installed, or it's used by plugin or something. Link to comment
Steviewunda Posted November 4, 2018 Author Share Posted November 4, 2018 Thanks Johnnie - no I don't know what they relate to. The only dockers running are duckdns and openvpn-as. I have just shut them down to see if those log entries are are related to either of them. I have also just removed Dynamix Local Master for troubleshooting purposes Here are my SMB extras, if they could be relevant: [rootshare] path = /mnt/user comment = browseable = yes # Public public = yes writeable = yes vfs objects = [global] domain master = yes preferred master = yes os level = 255 log level = 3 logging = syslog Link to comment
BRiT Posted November 4, 2018 Share Posted November 4, 2018 Typically NMBD is for resolving NETBIOS system names. It runs as part of SAMBA. Typically WINBINDD is used for resolving users and groups for Windows NT servers. It runs as part of SAMBA. https://www.samba.org/samba/docs/current/man-html/nmbd.8.html https://www.samba.org/samba/docs/current/man-html/winbindd.8.html Link to comment
Steviewunda Posted November 4, 2018 Author Share Posted November 4, 2018 Thanks Brit - I'm wondering if I should remove the lines in the SMB extras (see above) pertaining to logging? Or remove the whole [global] section? Link to comment
Steviewunda Posted November 4, 2018 Author Share Posted November 4, 2018 I seem to have resolved this by removing the [global] section of the SMB extras (see above). Thanks very much to those who responded Link to comment
JorgeB Posted November 4, 2018 Share Posted November 4, 2018 8 hours ago, Steviewunda said: log level = 3 logging = syslog These were the culprits, they increase Samba's log level and output everything to the syslog. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.