Whenever I use samba-tool with 'vfs objects = full_audit' on smb.conf I get a segmentation fault. I have seen it runnig 'samba-tool domain classicupgrade' or '/usr/local/samba/bin/samba-tool ntacl get' With log level = 10 I get: Initialising default vfs hooks vfs_find_backend_entry called for posixacl Successfully added vfs backend 'posixacl' vfs_find_backend_entry called for /[Default VFS]/ Successfully added vfs backend '/[Default VFS]/' vfs_find_backend_entry called for dfs_samba4 Successfully added vfs backend 'dfs_samba4' vfs_dfs_samba4: Debug class number of 'fileid': 23 Initialising custom vfs hooks from [/[Default VFS]/] vfs_find_backend_entry called for /[Default VFS]/ Successfully loaded vfs module [/[Default VFS]/] with the new modules system Initialising custom vfs hooks from [full_audit] vfs_find_backend_entry called for full_audit vfs module [full_audit] not loaded - trying to load... Loading module 'full_audit' Loading module 'full_audit': Trying to load from /usr/local/samba/lib/vfs/full_audit.so Module 'full_audit' loaded vfs_find_backend_entry called for full_audit Successfully added vfs backend 'full_audit' vfs_full_audit: Debug class number of 'full_audit': 24 vfs_find_backend_entry called for full_audit Successfully loaded vfs module [full_audit] with the new modules system Segmentation fault Best regards.
Have same situation here. Samba 4.1.17
FreeBSD 11 p8 Samba 4.5.7 from ports Issue still exists. Workaround is to comment out full_audit lines in samba3 smb.conf
The issue here is that the full audit modules don't like to run without a connect() being called, but because samba-tool operates on a path, not a share, it does not call the VFS connect() method.
I think this got fixed in the latest 4.8.x and 4.9.x releases. My $work ran into this and it is now fixed for us.
Marking as fixed per comment #4.