SOLVED smbd (core dumped)

[Quinniedid]

Trying to figure out why zfsacl is throwing a fit when using a Windows ACL module?

FreeNAS-11.1-U5

This is from the log.smbd:

Code:

[2018/06/04 10:00:00.079666,  1] ../source3/profile/profile_dummy.c:30(set_profile_level)
  INFO: Profiling support unavailable in this build.
[2018/06/04 10:00:00.594510,  1] ../source3/smbd/files.c:218(file_init_global)
  file_init_global: Information only: requested 1885322 open files, 59392 are available.
[2018/06/04 10:00:00.641024,  0] ../lib/util/become_daemon.c:124(daemon_ready)
  STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2018/06/04 10:00:06.945415,  1] ../source3/smbd/service.c:521(make_connection_snum)
  create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
[2018/06/04 10:00:06.950638,  1] ../source3/smbd/service.c:521(make_connection_snum)
  create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
[2018/06/04 10:00:06.952069,  1] ../source3/smbd/service.c:521(make_connection_snum)
  create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
[2018/06/04 10:00:30.458548,  1] ../source3/modules/vfs_posixacl.c:174(smb_ace_to_internal)
  ACL tag type ACL_EVERYONE. FreeBSD with ZFS? Use 'vfs objects = zfsacl'
[2018/06/04 10:00:30.458773,  1] ../source3/modules/vfs_posixacl.c:174(smb_ace_to_internal)
  ACL tag type ACL_EVERYONE. FreeBSD with ZFS? Use 'vfs objects = zfsacl'
[2018/06/04 10:02:23.397859,  1] ../source3/modules/vfs_posixacl.c:174(smb_ace_to_internal)
  ACL tag type ACL_EVERYONE. FreeBSD with ZFS? Use 'vfs objects = zfsacl'
[2018/06/04 10:02:23.398058,  1] ../source3/modules/vfs_posixacl.c:174(smb_ace_to_internal)
  ACL tag type ACL_EVERYONE. FreeBSD with ZFS? Use 'vfs objects = zfsacl'
[2018/06/04 10:02:28.991217,  0] ../lib/dbwrap/dbwrap.c:166(dbwrap_check_lock_order)
  Lock order violation: Trying /var/db/samba4/file_ntacls.tdb at 1 while /var/lock/locking.tdb at 1 is locked
[2018/06/04 10:02:28.991342,  0] ../lib/dbwrap/dbwrap.c:115(debug_lock_order)
  lock order:  1:/var/lock/locking.tdb 2:<none> 3:<none>
[2018/06/04 10:02:28.991365,  0] ../source3/lib/util.c:804(smb_panic_s3)
  PANIC (pid 3545): invalid lock_order

This is what I am seeing in the logs:

Code:

Jun  6 08:52:23 htl-archivebk kernel: pid 67634 (smbd), uid 0: exited on signal 6 (core dumped)
Jun  6 10:02:16 htl-archivebk kernel: pid 70989 (smbd), uid 0: exited on signal 6 (core dumped)
Jun  7 00:00:00 htl-archivebk syslog-ng[1750]: Configuration reload request received, reloading configuration;
Jun  7 06:52:26 htl-archivebk kernel: pid 28214 (smbd), uid 0: exited on signal 6 (core dumped)
Jun  7 10:02:10 htl-archivebk kernel: pid 36958 (smbd), uid 0: exited on signal 6 (core dumped)
Jun  7 16:52:51 htl-archivebk kernel: pid 56921 (smbd), uid 0: exited on signal 6 (core dumped)

smbd4.conf

Code:

[global]
	interfaces = 127.0.0.1 10.86.96.206
	bind interfaces only = yes
	encrypt passwords = yes
	dns proxy = no
	strict locking = no
	oplocks = yes
	deadtime = 15
	max log size = 51200
	max open files = 1885322
	logging = file
	load printers = no
	printing = bsd
	printcap name = /dev/null
	disable spoolss = yes
	getwd cache = yes
	guest account = nobody
	map to guest = Bad User
	obey pam restrictions = yes
	ntlm auth = no
	directory name cache size = 0
	kernel change notify = no
	panic action = /usr/local/libexec/samba/samba-backtrace
	nsupdate command = /usr/local/bin/samba-nsupdate -g
	server string = FreeNAS Server
	ea support = yes
	store dos attributes = yes
	lm announce = yes
	hostname lookups = yes
	unix extensions = no
	time server = yes
	acl allow execute always = true
	dos filemode = yes
	multicast dns register = yes
	domain logons = no
	local master = yes
	idmap config *: backend = tdb
	idmap config *: range = 90000001-100000000
	server role = standalone
	netbios name = HTL-ARCHIVEBK
	workgroup = WORKGROUP
	security = user
	create mask = 0666
	directory mask = 0777
	client ntlmv2 auth = yes
	dos charset = CP437
	unix charset = UTF-8
	log level = 1
	server signing = mandatory


[Backups-S3]
	path = "/mnt/BOI-HTL-ARCHIVE-S3/Backups"
	printable = no
	veto files = /.snapshot/.windows/.mac/.zfs/
	writeable = yes
	browseable = yes
	access based share enum = no
	vfs objects = acl_tdb acl_xattr streams_xattr
	hide dot files = yes
	guest ok = no
	nfs4:mode = special
	nfs4:acedup = merge
	nfs4:chown = true
	zfsacl:acesort = dontcare

EDIT: I have added zfs_space and zfsacl to the VFS objects back to the Backups-S3 share and so far
[2018/06/08 13:45:17.603948, 1] ../source3/modules/vfs_posixacl.c:174(smb_ace_to_internal)
ACL tag type ACL_EVERYONE. FreeBSD with ZFS? Use 'vfs objects = zfsacl' has not been showing in the logs. We will see if smbd will core dump or not. (https://redmine.ixsystems.com/issues/27581)

EDIT2: I am still getting smbd core dumps unfortunately...... Any advice?

 

[anodos]

acl_tdb and acl_xattr are unsupported on FreeNAS. The only supported method of managing acls is through the zfsacl VFS module.

 

[Quinniedid]

@anodos Looks like that has fixed it! Thank you for the help.