Created attachment 13028 [details] /var/log/messages Hi, We have a set of fileservers running CTDB on a distributed FS in a Samba 4 AD Domain. These were running OK with 4.4.2, but we decided to upgrade to 4.5.5. Things looked OK at first, but as more users connected we started to have windows clients throwing up error dialogs saying "file is in use by another user", even for directories and top-level shares. smbd processes were also crashing all over the place. I've attached log files from /var/log/messages, /var/log/log.ctdb, smbd and a samba log for a windows client. I'm reticent to perform any upgrade of our fileserver to 4.5 or above because of this issue.
Created attachment 13029 [details] /var/log/samba/smbd
Created attachment 13030 [details] /var/log/log.ctdb
Created attachment 13031 [details] /var/log/samba/<client machine name>
Did you upgrade Samba and CTDB both? You must run the same version of Samba and CTDB. It appears from the logs that you are running CTDB 4.4.9. 2017/02/13 08:58:36.211182 [ 5298]: Starting CTDBD (Version 4.4.9-SerNet-RedHat-37.el7) as PID: 5298
Also, since you are running on Linux, you should enable TDB mutex support for better performance. In CTDB configuration file, add following: CTDB_SET_TDBMutexEnabled=1 In Samba configuration, add following: dbwrap_tdb_mutexes:*=true To do this change, - Shutdown CTDB on all the nodes - Make the config changes on all the nodes - Start CTDB on all the nodes
Looks like you Samba configuration is wrong. Feb 13 00:00:06 zearing smbd[26944]: [2017/02/13 00:00:06.390823, 0] ../lib/util/debug.c:951(reopen_logs_internal) Feb 13 00:00:06 zearing smbd[26944]: Unable to open new log file '/var/log/samba/': Is a directory Check "log file" parameter in your samba configuration (smb.conf). It should point to a file and NOT to a directory.
(In reply to Amitay Isaacs from comment #6) My logging is set thusly: log file = /var/log/samba/%m So I'm wondering why %m would be empty in some cases? This is an unrelated issue, and we still see this in the logs (only since we went Samba 4 AD).
(In reply to Amitay Isaacs from comment #4) That's really interesting. I had run a: yum -y update "sernet-samba*" which should have upgraded both of them, but obviously did not. Maybe sernet missed the ctdb package - I'll look at the repo. Cheers Alex
(In reply to Amitay Isaacs from comment #4) Looks like the sernet repos are OK right now. Something must have gone wrong with the update then. Cheers Alex
Closing as "invalid" due to Samba/CTDB version mismatch.