On Sun, 9 Nov 2025 13:12:57 -0800
Cathryn Mataga via samba <samba at lists.samba.org> wrote:
> I'm getting a crash, pretty frequent, but not really sure what it's
> doing when this happens. Looking for help.
> Thanks.
>
> [root at ecuador cathryn]# samba --version
> Version 4.22.6
>
>
> Stack trace of
> thread 12687:
> #0
> 0x00007fd3643f9735 abort (libc.so.6 + 0x1735)
> #1
> 0x00007fd36464810a smb_panic_default.isra.0
> (libgenrand-private-samba.so + 0x310a) #2 0x00007fd3646486a5
> smb_panic (libgenrand-private-samba.so + 0x36a5)
> #3
> 0x00007fd364648744 sig_fault (libgenrand-private-samba.so + 0x3744)
> #4
> 0x00007fd364412070 __restore_rt (libc.so.6 + 0x1a070)
> #5
> 0x00007fd36446677c __internal_syscall_cancel (libc.so.6 + 0x6e77c)
> #6
> 0x00007fd3644667a4 __syscall_cancel (libc.so.6 + 0x6e7a4)
> #7
> 0x00007fd3644e07fe read (libc.so.6 + 0xe87fe)
> #8
> 0x00007fd36419231e sys_read (libsys-rw-private-samba.so + 0x231e)
> #9
> 0x00007fd364927a8e tfork_create (libsamba-util.so.0 + 0x65a8e)
> #10
> 0x00007fd3622c03dc prefork_fork_master (prefork.so + 0x53dc)
> #11
> 0x00007fd3622c0e43 prefork_new_task (prefork.so + 0x5e43)
> #12
> 0x00007fd364aaa1f5 task_server_startup (libservice-private-samba.so +
> 0x61f5) #13 0x00007fd364aaa2c6
> server_service_startup (libservice-private-samba.so + 0x62c6)
> #14
> 0x000056280a1fcc61 binary_smbd_main.constprop.0 (/usr/bin/samba +
> 0x7c61) #15 0x000056280a1fd440
> main (/usr/bin/samba + 0x8440)
> #16
> 0x00007fd3643fb575 __libc_start_call_main (libc.so.6 + 0x3575)
> #17
> 0x00007fd3643fb628 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x3628)
> #18
> 0x000056280a1fb4b5 _start (/usr/bin/samba + 0x64b5)
> ELF object binary
> architecture: AMD x86-64
>
> # Global parameters
> [global]
> netbios name = ECUADOR
> realm = JUNGLEVISION.JUNGLEVISION.COM
> server role = active directory domain controller
> server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc,
> drepl, winbindd, ntp_signd, kcc, dnsupdate
> workgroup = JUNGLEVISION
> idmap_ldb:use rfc2307 = yes
> hosts allow = 127.0.0.0/8 192.168.1.0/24 192.168.2.0/24
> 192.168.3.0/24 192.168.4.0/24 192.168.5.0/24 192.168.6.0/24
> 192.168.8.0/24 hosts deny = 0.0.0.0/0
> interfaces = 192.168.1.146 127.0.0.1
> bind interfaces only = yes
> log level 1
> min protocol = SMB2
> time server = yes
> vfs objects = fruit streams_xattr, dfs_samba4, acl_xattr
> username map = /home/etc/samba/user.map
> fruit:metadata = stream
> fruit:model = MacSamba
> fruit:posix_rename = yes
> fruit:veto_appledouble = no
> fruit:wipe_intentionally_left_blank_rfork = yes
> fruit:delete_empty_adfiles = yes
>
> [netlogon]
> path >
/var/lib/samba/sysvol/junglevision.junglevision.com/scripts read only
> = No vfs objects = dfs_samba4, acl_xattr, full_audit
> [sysvol]
> path = /var/lib/samba/sysvol
> read only = No
> vfs objects = dfs_samba4, acl_xattr, full_audit
> ~
>
>
First, Samba shouldn't crash, but you have may have found yet another
reason not to use a Samba AD DC as a fileserver.
I 'think' your problems may be being caused by the way you are using
'vfs objects'. Normally if you read the various 'vfs' manpages,
they
will tell you if they are stackable, the manpage for vfs_fruit tells
you that it must be used before vfs_streams_xattr, but the manpage for
vfs_streams_xattr does not say it is stackable, in my opinion, this
means it should be last on the list.
However, you do not seem to have any shares that are actually using any
of the extra 'vfs objects' you have added to your smb.conf file, unless
that '~' is a placeholder for any missing shares, if so, then please
post them.
In my opinion, your best plan would be to set up another computer or
VM and install Samba on that and configure it as a Unix domain member
and use that as the fileserver and move any shares to that.
You also have 'username map = /home/etc/samba/user.map' in your
smb.conf file, why ?
Finally, posting the same thing twice doesn't help.
Rowland