Проверил на KVM (Proxmox):
[root@ad ~]# /usr/bin/samba-tool domain provision --realm "samba.test" --domain "samba" --dns-backend=SAMBA_INTERNAL --server-role=dc --use-rfc2307
INFO 2022-05-17 11:40:57,138 pid:338297 /usr/lib64/samba-dc/python3.9/samba/netcmd/domain.py #430: Administrator password will be set randomly!
INFO 2022-05-17 11:40:57,145 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #2105: Looking up IPv4 addresses
INFO 2022-05-17 11:40:57,145 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #2122: Looking up IPv6 addresses
INFO 2022-05-17 11:40:57,837 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #2273: Setting up share.ldb
INFO 2022-05-17 11:40:57,981 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #2277: Setting up secrets.ldb
INFO 2022-05-17 11:40:58,061 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #2282: Setting up the registry
INFO 2022-05-17 11:40:58,399 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #2285: Setting up the privileges database
INFO 2022-05-17 11:40:58,565 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #2288: Setting up idmap db
INFO 2022-05-17 11:40:58,685 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #2295: Setting up SAM db
INFO 2022-05-17 11:40:58,718 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #880: Setting up sam.ldb partitions and settings
INFO 2022-05-17 11:40:58,721 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #892: Setting up sam.ldb rootDSE
INFO 2022-05-17 11:40:58,745 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #1305: Pre-loading the Samba 4 and AD schema
Unable to determine the DomainSID, can not enforce uniqueness constraint on local domainSIDs
INFO 2022-05-17 11:40:58,874 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #1383: Adding DomainDN: DC=samba,DC=test
INFO 2022-05-17 11:40:58,923 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #1415: Adding configuration container
INFO 2022-05-17 11:40:58,971 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #1430: Setting up sam.ldb schema
INFO 2022-05-17 11:41:02,009 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #1448: Setting up sam.ldb configuration data
INFO 2022-05-17 11:41:02,164 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #1489: Setting up display specifiers
INFO 2022-05-17 11:41:04,119 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #1497: Modifying display specifiers and extended rights
INFO 2022-05-17 11:41:04,157 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #1504: Adding users container
INFO 2022-05-17 11:41:04,159 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #1510: Modifying users container
INFO 2022-05-17 11:41:04,160 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #1513: Adding computers container
INFO 2022-05-17 11:41:04,162 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #1519: Modifying computers container
INFO 2022-05-17 11:41:04,163 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #1523: Setting up sam.ldb data
INFO 2022-05-17 11:41:04,304 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #1553: Setting up well known security principals
INFO 2022-05-17 11:41:04,348 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #1567: Setting up sam.ldb users and groups
INFO 2022-05-17 11:41:04,579 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #1575: Setting up self join
Repacking database from v1 to v2 format (first record CN=FRS-Replica-Set-GUID,CN=Schema,CN=Configuration,DC=samba,DC=test)
Repack: re-packed 10000 records so far
Repacking database from v1 to v2 format (first record CN=foreignSecurityPrincipal-Display,CN=410,CN=DisplaySpecifiers,CN=Configuration,DC=samba,DC=test)
Repacking database from v1 to v2 format (first record CN=WMIGPO,CN=WMIPolicy,CN=System,DC=samba,DC=test)
INFO 2022-05-17 11:41:06,644 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/sambadns.py #1143: Adding DNS accounts
INFO 2022-05-17 11:41:06,752 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/sambadns.py #1177: Creating CN=MicrosoftDNS,CN=System,DC=samba,DC=test
INFO 2022-05-17 11:41:06,807 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/sambadns.py #1190: Creating DomainDnsZones and ForestDnsZones partitions
INFO 2022-05-17 11:41:06,958 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/sambadns.py #1195: Populating DomainDnsZones and ForestDnsZones partitions
Repacking database from v1 to v2 format (first record DC=a.root-servers.net,DC=RootDNSServers,CN=MicrosoftDNS,DC=DomainDnsZones,DC=samba,DC=test)
Repacking database from v1 to v2 format (first record DC=_msdcs.samba.test,CN=MicrosoftDNS,DC=ForestDnsZones,DC=samba,DC=test)
INFO 2022-05-17 11:41:07,425 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #2009: Setting up sam.ldb rootDSE marking as synchronized
INFO 2022-05-17 11:41:07,440 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #2014: Fixing provision GUIDs
INFO 2022-05-17 11:41:08,897 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #2347: A Kerberos configuration suitable for Samba AD has been generated at /var/lib/samba/private/krb5.conf
INFO 2022-05-17 11:41:08,898 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #2349: Merge the contents of this file with your system krb5.conf or replace it with this one. Do not create a symlink!
INFO 2022-05-17 11:41:09,038 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #2079: Setting up fake yp server settings
INFO 2022-05-17 11:41:09,189 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #487: Once the above files are installed, your Samba AD server will be ready to use
INFO 2022-05-17 11:41:09,189 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #491: Admin password: X,<(GFQNYRo.
INFO 2022-05-17 11:41:09,190 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #492: Server Role: active directory domain controller
INFO 2022-05-17 11:41:09,190 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #493: Hostname: ad
INFO 2022-05-17 11:41:09,190 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #494: NetBIOS Domain: SAMBA
INFO 2022-05-17 11:41:09,191 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #495: DNS Domain: samba.test
INFO 2022-05-17 11:41:09,191 pid:338297 /usr/lib64/samba-dc/python3.9/samba/provision/__init__.py #496: DOMAIN SID: S-1-5-21-578881226-703906863-2679424616
[root@ad ~]# systemctl disable --now bind
Synchronizing state of bind.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable bind
Removed /etc/systemd/system/multi-user.target.wants/bind.service.
[root@ad ~]# systemctl enable --now samba
Synchronizing state of samba.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable samba
[root@ad ~]# samba-tool domain info 127.0.0.1
Forest : samba.test
Domain : samba.test
Netbios domain : SAMBA
DC name : ad.samba.test
DC netbios name : AD
Server site : Default-First-Site-Name
Client site : Default-First-Site-Name
samba-dc-4.14.12-alt2.x86_64. И даже без swap.
Our Ubuntu clients are in an AD domain using realm. Accessing a samba share (SSO) with dolphin/nautilus (smb://HOST/share) is working on ubuntu clients where the host with the shared directory is ubuntu 16.04 or 17.10.
Accessing the shared folder on ubuntu 18.04 with same configuration as 16.04 or 17.10 clients throws a panic on the system with 18.04:
/var/log/samba/log.LOCALHOST on HOST with 18.04
===============================================
[2018/04/06 13:43:50.360655, 5] ../source3/smbd/reply.c:780(reply_special)
init msg_type=0x81 msg_flags=0x0
[2018/04/06 13:43:50.361179, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 0 of length 194 (0 toread)
[2018/04/06 13:43:50.361241, 5] ../source3/lib/util.c:184(show_msg)
[2018/04/06 13:43:50.361264, 5] ../source3/lib/util.c:194(show_msg)
size=190
smb_com=0x72
smb_rcls=0
smb_reh=0
smb_err=0
smb_flg=24
smb_flg2=51267
smb_tid=0
smb_pid=65534
smb_uid=0
smb_mid=0
smt_wct=0
smb_bcc=155
[2018/04/06 13:43:50.361467, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBnegprot (pid 2538) conn 0x0
[2018/04/06 13:43:50.361554, 4] ../source3/smbd/sec_ctx.c:320(set_sec_ctx_internal)
setting sec ctx (0, 0) — sec_ctx_stack_ndx = 0
[2018/04/06 13:43:50.361617, 5] ../libcli/security/security_token.c:53(security_token_debug)
Security token: (NULL)
[2018/04/06 13:43:50.361667, 5] ../source3/auth/token_util.c:651(debug_unix_user_token)
UNIX token of user 0
Primary group is 0 and contains 0 supplementary groups
[2018/04/06 13:43:50.361766, 5] ../source3/smbd/uid.c:425(smbd_change_to_root_user)
change_to_root_user: now uid=(0,0) gid=(0,0)
[2018/04/06 13:43:50.363559, 3] ../source3/smbd/negprot.c:612(reply_negprot)
Requested protocol [PC NETWORK PROGRAM 1.0]
[2018/04/06 13:43:50.363638, 3] ../source3/smbd/negprot.c:612(reply_negprot)
Requested protocol [MICROSOFT NETWORKS 1.03]
[2018/04/06 13:43:50.363677, 3] ../source3/smbd/negprot.c:612(reply_negprot)
Requested protocol [MICROSOFT NETWORKS 3.0]
[2018/04/06 13:43:50.363712, 3] ../source3/smbd/negprot.c:612(reply_negprot)
Requested protocol [LANMAN1.0]
[2018/04/06 13:43:50.363747, 3] ../source3/smbd/negprot.c:612(reply_negprot)
Requested protocol [LM1.2X002]
[2018/04/06 13:43:50.363782, 3] ../source3/smbd/negprot.c:612(reply_negprot)
Requested protocol [DOS LANMAN2.1]
[2018/04/06 13:43:50.363817, 3] ../source3/smbd/negprot.c:612(reply_negprot)
Requested protocol [LANMAN2.1]
[2018/04/06 13:43:50.363852, 3] ../source3/smbd/negprot.c:612(reply_negprot)
Requested protocol [Samba]
[2018/04/06 13:43:50.363888, 3] ../source3/smbd/negprot.c:612(reply_negprot)
Requested protocol [NT LANMAN 1.0]
[2018/04/06 13:43:50.363924, 3] ../source3/smbd/negprot.c:612(reply_negprot)
Requested protocol [NT LM 0.12]
[2018/04/06 13:43:50.364019, 5] ../lib/dbwrap/dbwrap.c:160(dbwrap_check_lock_order)
check lock order 2 for /var/run/samba/serverid.tdb
[2018/04/06 13:43:50.364077, 5] ../lib/dbwrap/dbwrap.c:128(dbwrap_lock_order_state_destructor)
release lock order 2 for /var/run/samba/serverid.tdb
[2018/04/06 13:43:50.364259, 5] ../source3/auth/auth.c:537(make_auth3_context_for_ntlm)
Making default auth method list for server role = ‘standalone server’, encrypt passwords = yes
[2018/04/06 13:43:50.364282, 5] ../source3/auth/auth.c:48(smb_register_auth)
Attempting to register auth backend trustdomain
[2018/04/06 13:43:50.364300, 5] ../source3/auth/auth.c:60(smb_register_auth)
Successfully added auth method ‘trustdomain’
[2018/04/06 13:43:50.364316, 5] ../source3/auth/auth.c:48(smb_register_auth)
Attempting to register auth backend ntdomain
[2018/04/06 13:43:50.364334, 5] ../source3/auth/auth.c:60(smb_register_auth)
Successfully added auth method ‘ntdomain’
[2018/04/06 13:43:50.364352, 5] ../source3/auth/auth.c:48(smb_register_auth)
Attempting to register auth backend guest
[2018/04/06 13:43:50.364364, 5] ../source3/auth/auth.c:60(smb_register_auth)
Successfully added auth method ‘guest’
[2018/04/06 13:43:50.364392, 5] ../source3/auth/auth.c:48(smb_register_auth)
Attempting to register auth backend sam
[2018/04/06 13:43:50.364404, 5] ../source3/auth/auth.c:60(smb_register_auth)
Successfully added auth method ‘sam’
[2018/04/06 13:43:50.364415, 5] ../source3/auth/auth.c:48(smb_register_auth)
Attempting to register auth backend sam_ignoredomain
[2018/04/06 13:43:50.364427, 5] ../source3/auth/auth.c:60(smb_register_auth)
Successfully added auth method ‘sam_ignoredomain’
[2018/04/06 13:43:50.364438, 5] ../source3/auth/auth.c:48(smb_register_auth)
Attempting to register auth backend sam_netlogon3
[2018/04/06 13:43:50.364450, 5] ../source3/auth/auth.c:60(smb_register_auth)
Successfully added auth method ‘sam_netlogon3’
[2018/04/06 13:43:50.364461, 5] ../source3/auth/auth.c:48(smb_register_auth)
Attempting to register auth backend winbind
[2018/04/06 13:43:50.364473, 5] ../source3/auth/auth.c:60(smb_register_auth)
Successfully added auth method ‘winbind’
[2018/04/06 13:43:50.364484, 5] ../source3/auth/auth.c:48(smb_register_auth)
Attempting to register auth backend unix
[2018/04/06 13:43:50.364502, 5] ../source3/auth/auth.c:60(smb_register_auth)
Successfully added auth method ‘unix’
[2018/04/06 13:43:50.364514, 5] ../source3/auth/auth.c:400(load_auth_module)
load_auth_module: Attempting to find an auth method to match guest
[2018/04/06 13:43:50.364527, 5] ../source3/auth/auth.c:425(load_auth_module)
load_auth_module: auth method guest has a valid init
[2018/04/06 13:43:50.364539, 5] ../source3/auth/auth.c:400(load_auth_module)
load_auth_module: Attempting to find an auth method to match sam_ignoredomain
[2018/04/06 13:43:50.364551, 5] ../source3/auth/auth.c:425(load_auth_module)
load_auth_module: auth method sam_ignoredomain has a valid init
[2018/04/06 13:43:50.365880, 3] ../auth/gensec/gensec_start.c:977(gensec_register)
GENSEC backend ‘gssapi_spnego’ registered
[2018/04/06 13:43:50.365916, 3] ../auth/gensec/gensec_start.c:977(gensec_register)
GENSEC backend ‘gssapi_krb5’ registered
[2018/04/06 13:43:50.365930, 3] ../auth/gensec/gensec_start.c:977(gensec_register)
GENSEC backend ‘gssapi_krb5_sasl’ registered
[2018/04/06 13:43:50.365942, 3] ../auth/gensec/gensec_start.c:977(gensec_register)
GENSEC backend ‘spnego’ registered
[2018/04/06 13:43:50.365954, 3] ../auth/gensec/gensec_start.c:977(gensec_register)
GENSEC backend ‘schannel’ registered
[2018/04/06 13:43:50.365967, 3] ../auth/gensec/gensec_start.c:977(gensec_register)
GENSEC backend ‘naclrpc_as_system’ registered
[2018/04/06 13:43:50.365979, 3] ../auth/gensec/gensec_start.c:977(gensec_register)
GENSEC backend ‘sasl-EXTERNAL’ registered
[2018/04/06 13:43:50.365992, 3] ../auth/gensec/gensec_start.c:977(gensec_register)
GENSEC backend ‘ntlmssp’ registered
[2018/04/06 13:43:50.366004, 3] ../auth/gensec/gensec_start.c:977(gensec_register)
GENSEC backend ‘ntlmssp_resume_ccache’ registered
[2018/04/06 13:43:50.366017, 3] ../auth/gensec/gensec_start.c:977(gensec_register)
GENSEC backend ‘http_basic’ registered
[2018/04/06 13:43:50.366029, 3] ../auth/gensec/gensec_start.c:977(gensec_register)
GENSEC backend ‘http_ntlm’ registered
[2018/04/06 13:43:50.366042, 3] ../auth/gensec/gensec_start.c:977(gensec_register)
GENSEC backend ‘krb5’ registered
[2018/04/06 13:43:50.366055, 3] ../auth/gensec/gensec_start.c:977(gensec_register)
GENSEC backend ‘fake_gssapi_krb5’ registered
[2018/04/06 13:43:50.366109, 5] ../auth/gensec/gensec_start.c:739(gensec_start_mech)
Starting GENSEC mechanism spnego
[2018/04/06 13:43:50.366144, 5] ../auth/gensec/gensec_start.c:739(gensec_start_mech)
Starting GENSEC submechanism gse_krb5
[2018/04/06 13:43:50.366323, 0] ../lib/util/fault.c:78(fault_report)
===============================================================
[2018/04/06 13:43:50.366346, 0] ../lib/util/fault.c:79(fault_report)
INTERNAL ERROR: Signal 11 in pid 2538 (4.7.6-Ubuntu)
Please read the Trouble-Shooting section of the Samba HOWTO
[2018/04/06 13:43:50.366368, 0] ../lib/util/fault.c:81(fault_report)
===============================================================
[2018/04/06 13:43:50.366387, 0] ../source3/lib/util.c:815(smb_panic_s3)
PANIC (pid 2538): internal error
[2018/04/06 13:43:50.366896, 0] ../source3/lib/util.c:926(log_stack_trace)
BACKTRACE: 33 stack frames:
#0 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(log_stack_trace+0x1f) [0x7f738c2bd9cf]
#1 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(smb_panic_s3+0x20) [0x7f738c2bdaa0]
#2 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f) [0x7f738e3a65af]
#3 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(+0x197c6) [0x7f738e3a67c6]
#4 /lib/x86_64-linux-gnu/libpthread.so.0(+0x12890) [0x7f738e817890]
#5 /usr/lib/x86_64-linux-gnu/samba/libgse.so.0(+0x8070) [0x7f73866c5070]
#6 /usr/lib/x86_64-linux-gnu/samba/libgse.so.0(gse_krb5_get_server_keytab+0x95) [0x7f73866c5ac5]
#7 /usr/lib/x86_64-linux-gnu/samba/libgse.so.0(+0xac89) [0x7f73866c7c89]
#8 /usr/lib/x86_64-linux-gnu/samba/libgensec.so.0(+0x187a5) [0x7f73864ab7a5]
#9 /usr/lib/x86_64-linux-gnu/samba/libgensec.so.0(+0xa2a7) [0x7f738649d2a7]
#10 /usr/lib/x86_64-linux-gnu/samba/libgensec.so.0(+0xb7fe) [0x7f738649e7fe]
#11 /usr/lib/x86_64-linux-gnu/samba/libgensec.so.0(gensec_update_ev+0x64) [0x7f73864aafa4]
#12 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(negprot_spnego+0xa8) [0x7f738df764f8]
#13 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0x12ba3b) [0x7f738df76a3b]
#14 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(reply_negprot+0x4e3) [0x7f738df771f3]
#15 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0x1814ca) [0x7f738dfcc4ca]
#16 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0x183aee) [0x7f738dfceaee]
#17 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0x1849fc) [0x7f738dfcf9fc]
#18 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x9ed0) [0x7f738aeefed0]
#19 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x8357) [0x7f738aeee357]
#20 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x9d) [0x7f738aeea7cd]
#21 /usr/lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x7f738aeea9eb]
#22 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x82f7) [0x7f738aeee2f7]
#23 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(smbd_process+0x718) [0x7f738dfd0d78]
#24 /usr/sbin/smbd(+0xcfcc) [0x55a15e207fcc]
#25 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x9ed0) [0x7f738aeefed0]
#26 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x8357) [0x7f738aeee357]
#27 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x9d) [0x7f738aeea7cd]
#28 /usr/lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x7f738aeea9eb]
#29 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x82f7) [0x7f738aeee2f7]
#30 /usr/sbin/smbd(main+0x1d0a) [0x55a15e20334a]
#31 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f738ab16b97]
#32 /usr/sbin/smbd(_start+0x2a) [0x55a15e20345a]
[2018/04/06 13:43:50.367078, 0] ../source3/lib/util.c:827(smb_panic_s3)
smb_panic(): calling panic action [/usr/share/samba/panic-action 2538]
30 ../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory.
mail: cannot send message: Process exited with a non-zero status
[2018/04/06 13:43:51.587520, 0] ../source3/lib/util.c:835(smb_panic_s3)
smb_panic(): action returned status 36
[2018/04/06 13:43:51.587618, 0] ../source3/lib/dumpcore.c:318(dump_core)
coredump is handled by helper binary specified at /proc/sys/kernel/core_pattern[2018/04/06 13:43:52.153171, 5]
client
======
HOST: Ubuntu 18.04RC (2018-04-06), amd64
samba: 4.7.6+dfsg~ubuntu-0ubuntu1
krb5: 1.16-2build1
sssd: 1.16.0-5ubuntu2
This is a blocker for us to upgrade from 16.04 to 18.04 after release. 
Internal error signal 11 in pid
Помогите СРОЧНО. НЕ могу найти в чем глюк.
Linux 2.4.22 (debian unstable)
libc6 2.3.2
Samba 3.0.0 as PDC (from debian package)
Файловая система : XFS
Клиенты — win2k(rus, with SP3rus), win98SE(rus)
ПОСТОЯННО у клиентов отваливается сетевой диск, и к серверу невозможно подключиться. При попытке зайти на сервер аутентификация не проходит. В это время другие клиенты нормально работают с сервером. Только после убивания smbd клиента возможно переподключение.
Единственное подозрение что использую старый метод аутентификации smbpasswd.
********************************
My smb.conf:
[global]
workgroup = MDOM
netbios name = SERVER2
server string = Mega Server
log file = /var/log/samba/log.%m
max log size = 100000
time server = Yes
load printers = No
add user script = /usr/sbin/useradd -g 100 -d /home/%u -s /bin/false -m
%u
delete user script = /usr/sbin/userdel %u
add group script = /usr/sbin/groupadd %g
delete group script = /usr/sbin/groupdel %g
add user to group script = /usr/sbin/adduser %u %g
delete user from group script = /usr/sbin/deluser %u %g
set primary group script = /usr/sbin/usermod -g %g %u
add machine script = /usr/sbin/useradd -g 110 -d /dev/null -s /bin/false
-M %u
logon script = all.bat
logon path =
logon home =
domain logons = Yes
os level = 255
preferred master = Yes
domain master = Yes
admin users = vadim, ozol
map acl inherit = Yes
[projects]
comment = Project disk
path = /mnt/disk1
read only = No
create mask = 0666
directory mask = 0777
[netlogon]
path = /etc/samba/netlogon
browseable = No
******************************************
Logs:
[2003/11/19 10:36:06, 1] smbd/service.c:make_connection_snum(698)
design2 (192.168.1.220) connect to service projects initially as user kd
(uid=1009, gid=100) (pid 21975)
[2003/11/19 10:39:25, 0] lib/fault.c:fault_report(36)
===============================================================
[2003/11/19 10:39:25, 0] lib/fault.c:fault_report(37)
INTERNAL ERROR: Signal 11 in pid 21975 (3.0.0-Debian)
Please read the appendix Bugs of the Samba HOWTO collection
[2003/11/19 10:39:25, 0] lib/fault.c:fault_report(39)
===============================================================
[2003/11/19 10:39:25, 0] lib/util.c:smb_panic(1400)
PANIC: internal error
[2003/11/19 10:39:25, 0] lib/util.c:smb_panic(1407)
BACKTRACE: 20 stack frames:
#0 /usr/sbin/smbd(smb_panic+0x101) [0x81bcf41]
#1 /usr/sbin/smbd [0x81ab587]
#2 /lib/libc.so.6 [0x401d8498]
#3 /lib/libc.so.6 [0x402214df]
#4 /lib/libc.so.6(__libc_realloc+0x100) [0x40220020]
#5 /usr/sbin/smbd(Realloc+0x26) [0x81bc096]
#6 /usr/sbin/smbd(convert_string_allocate+0x402) [0x81a9342]
#7 /usr/sbin/smbd(push_ucs2_allocate+0x48) [0x81a9bf8]
#8 /usr/sbin/smbd(StrCaseCmp+0xa0) [0x81b4380]
#9 /usr/sbin/smbd [0x80a9d83]
#10 /usr/sbin/smbd [0x80aa1b6]
#11 /usr/sbin/smbd [0x80abbbb]
#12 /usr/sbin/smbd(reply_trans2+0x619) [0x80b32c9]
#13 /usr/sbin/smbd [0x80c6b1a]
#14 /usr/sbin/smbd [0x80c6d80]
#15 /usr/sbin/smbd(process_smb+0x8c) [0x80c6f8c]
#16 /usr/sbin/smbd(smbd_process+0x168) [0x80c7bf8]
#17 /usr/sbin/smbd(main+0x4bc) [0x8224d7c]
#18 /lib/libc.so.6(__libc_start_main+0xc6) [0x401c4da6]
#19 /usr/sbin/smbd(chroot+0x35) [0x8076ba1]
[2003/11/19 10:39:25, 1] smbd/service.c:make_connection_snum(698)
design2 (192.168.1.220) connect to service projects initially as user kd
(uid=1009, gid=100) (pid 22021)
[2003/11/19 10:39:27, 1] smbd/service.c:make_connection_snum(698)
design2 (192.168.1.220) connect to service projects initially as user kd
(uid=1009, gid=100) (pid 22021)
**********************************************
Если в это время клиенты обращаются к серверу соединение теряется
Рекомендовать в FAQ | Cообщить модератору | Наверх
- СРОЧНО. Достала SAMBA3. INTERNAL ERROR: Signal 11, Vadim, 12:44 , 01-Дек-03, (1)
- СРОЧНО. Достала SAMBA3. INTERNAL ERROR: Signal 11, VictorK, 15:23 , 01-Дек-03, (2)
- СРОЧНО. Достала SAMBA3. INTERNAL ERROR: Signal 11, vadim, 05:53 , 02-Дек-03, (3)
- СРОЧНО. Достала SAMBA3. INTERNAL ERROR: Signal 11, screepah, 10:02 , 02-Дек-03, (4)
- СРОЧНО. Достала SAMBA3. INTERNAL ERROR: Signal 11, Vadim, 10:33 , 03-Дек-03, (5)
- СРОЧНО. Достала SAMBA3. INTERNAL ERROR: Signal 11, screepah, 10:02 , 02-Дек-03, (4)
- СРОЧНО. Достала SAMBA3. INTERNAL ERROR: Signal 11, vadim, 05:53 , 02-Дек-03, (3)
- СРОЧНО. Достала SAMBA3. INTERNAL ERROR: Signal 11, Vadim, 10:48 , 03-Дек-03, (6)
- СРОЧНО. Достала SAMBA3. INTERNAL ERROR: Signal 11, q, 20:14 , 06-Дек-03, ( 7 )
Индекс форумов | Темы | Пред. тема | След. тема
Неужели только у меня SAMBA3 работает с ошибками.
| 2. «СРОЧНО. Достала SAMBA3. INTERNAL ERROR: Signal 11» |
Сообщение от VictorK   on 01-Дек-03, 15:23 (MSK) |
|
| Рекомендовать в FAQ | Cообщить модератору | Наверх |
 |
| 3. «СРОЧНО. Достала SAMBA3. INTERNAL ERROR: Signal 11» |
| Сообщение от vadim on 02-Дек-03, 05:53 (MSK) |
|
| Рекомендовать в FAQ | Cообщить модератору | Наверх |
|
| 4. «СРОЧНО. Достала SAMBA3. INTERNAL ERROR: Signal 11» |
| Сообщение от screepah on 02-Дек-03, 10:02 (MSK) |
sig11 — это ошибка работы с памятью |
| Рекомендовать в FAQ | Cообщить модератору | Наверх |
|
| 5. «СРОЧНО. Достала SAMBA3. INTERNAL ERROR: Signal 11» |
| Сообщение от Vadim on 03-Дек-03, 10:33 (MSK) |
Поставил Samba 3.0.1 pre3 ситуация НЕ изменилась. Насчет памяти, может быть(но сомневаюсь). Для достоверности поменял и память, та же хрень. |
| Рекомендовать в FAQ | Cообщить модератору | Наверх |
| 6. «СРОЧНО. Достала SAMBA3. INTERNAL ERROR: Signal 11» |
| Сообщение от Vadim on 03-Дек-03, 10:48 (MSK) |
Источник Падает nmbdПадает nmbd, по непонятным причинам. Это только у меня? Fedora 17
А что с ним не так?
Ну так засабминить коредамп в багзиллу
Толк от него будет? То есть, может мне еще что дополнительное включить?
Сначала отключи selinux и проверь, что дело не в нем 😉
pam-auth-чего-то там Была похожая проблема, не стоял чек бокс на против одно из пунктов, сильно вникать что-почем не стал, поставил и забыл.
Еще он ругается на « Cannot find my workgroup WORKGROUP on subnet UNICAST_SUBNET.» На файрволе широкоопевещательные в сеть разрешены ?
Не в нем, раньше без него тоже падал, просто я в крон поставил перезапуск nmbd раз в 5 минут. Замел крошки под ковер, так сказать.
Проблема на конкретной версии, или на всех ?
ещё обрати внимание на последовательность загрузки самбы и сетевой карты в системд
Самба была остановлена, потом запущена. То есть последняя в любом случае.
Я вот этого не понимаю:
pam-auth-update [X] Winbind NT/Active Directory authentication
у меня тоже такое было, я забил и работаю по Scp
scp не очень удобно пользоваться на телевизоре 🙂
конфиг global smb и список интерфейсов покажи plz. Конфиг fw тоже было бы неплохо (iptables?)
не должно быть связано с pam’ом, поскольку Nmbd отвечает только за сеть.
Тогда как вариант перейти на версию 4.0 =)
1) Вот это бы я бы временно убрал: use mmap = yes (вряд ли связано, но чтобы не мешались пока, пострадает скорее всего только скорость) 2) Добавил бы в global: interfaces = 192.168.2.0/24 3) И, если не поможет, убрал бы (только для проверки ессно) ipv6 с интерфейса p4p1, было дело, сталкивался в 3.4.какой_то с похожим багом, -skipped-
А у тебя в самбовском спуле какой-нибудь файлик случаем не битый? Судя по следам libtdb в трейсе как-то так Источник Adblock |
Переехав на своём основном сервере на CentOS я столкнулся с такой неприятной проблемой, что на одной из шар я никак не мог сохранить файлы. В частности это была директория веб-сервера, где у меня лежит в том числе и мой проект TorrentMonitor, правки в который я вношу постоянно. Ну и естественно этот факт не мог меня не напрягать. Но выход из ситуации был найден.
Лог пестрил вот такими вот красивыми записями:
Окт 23 13:00:54.950789 afpd[8851] {ea.c:722} (E:AFPDaemon): ea_open('.AppleDouble/config.php::EA'): bogus EA header file
Окт 23 13:00:54.950822 afpd[8851] {ea.c:1152} (E:AFPDaemon): list_eas: error calling ea_open for file: config.php
Окт 23 13:00:54.951571 afpd[8851] {ea.c:722} (E:AFPDaemon): ea_open('.AppleDouble/config.php::EA'): bogus EA header file
Окт 23 13:00:54.951593 afpd[8851] {ea.c:1152} (E:AFPDaemon): list_eas: error calling ea_open for file: config.php
Окт 23 13:00:55.391208 afpd[8851] {ea.c:722} (E:AFPDaemon): ea_open('.AppleDouble/config.php::EA'): bogus EA header file
Окт 23 13:00:55.391228 afpd[8851] {ea.c:1002} (E:AFPDaemon): get_easize: error calling ea_open for file: config.php
Окт 23 13:00:56.515909 afpd[8851] {ea.c:722} (E:AFPDaemon): ea_open('.AppleDouble/config.php::EA'): bogus EA header file
Окт 23 13:00:56.515932 afpd[8851] {ea.c:1152} (E:AFPDaemon): list_eas: error calling ea_open for file: config.php
Окт 23 13:00:56.516855 afpd[8851] {ea.c:722} (E:AFPDaemon): ea_open('.AppleDouble/config.php::EA'): bogus EA header file
Окт 23 13:00:56.516880 afpd[8851] {ea.c:1152} (E:AFPDaemon): list_eas: error calling ea_open for file: config.php
Окт 23 13:01:03.435142 afpd[8851] {ea.c:722} (E:AFPDaemon): ea_open('.AppleDouble/config.php::EA'): bogus EA header file
Окт 23 13:01:03.435185 afpd[8851] {ea.c:1002} (E:AFPDaemon): get_easize: error calling ea_open for file: config.php
Окт 23 13:01:33.434724 afpd[8851] {ea.c:722} (E:AFPDaemon): ea_open('.AppleDouble/config.php::EA'): bogus EA header file
Окт 23 13:01:33.434772 afpd[8851] {ea.c:1002} (E:AFPDaemon): get_easize: error calling ea_open for file: config.php
Окт 23 13:02:03.462347 afpd[8851] {ea.c:722} (E:AFPDaemon): ea_open('.AppleDouble/config.php::EA'): bogus EA header file
Окт 23 13:02:03.462415 afpd[8851] {ea.c:1002} (E:AFPDaemon): get_easize: error calling ea_open for file: config.php
Окт 23 13:02:04.004253 afpd[8851] {ea.c:722} (E:AFPDaemon): ea_open('.AppleDouble/config.php::EA'): bogus EA header file
Окт 23 13:02:04.004278 afpd[8851] {ea.c:1002} (E:AFPDaemon): get_easize: error calling ea_open for file: config.php
Окт 23 13:02:33.947712 afpd[8851] {ea.c:722} (E:AFPDaemon): ea_open('.AppleDouble/config.php::EA'): bogus EA header file
Окт 23 13:02:33.947754 afpd[8851] {ea.c:1002} (E:AFPDaemon): get_easize: error calling ea_open for file: config.php
А порой afp просто крэшился:
Окт 23 13:00:48.892432 afpd[8837] {fault.c:122} (S:Default): ===============================================================
Окт 23 13:00:48.892451 afpd[8837] {fault.c:123} (S:Default): INTERNAL ERROR: Signal 11 in pid 8837 (2.2.0)
Окт 23 13:00:48.892456 afpd[8837] {fault.c:124} (S:Default): ===============================================================
Окт 23 13:00:48.893793 afpd[8837] {fault.c:96} (S:Default): BACKTRACE: 15 stack frames:
Окт 23 13:00:48.893806 afpd[8837] {fault.c:102} (S:Default): #0 /usr/sbin/afpd(netatalk_panic+0x1f) [0x4512cf]
Окт 23 13:00:48.893811 afpd[8837] {fault.c:102} (S:Default): #1 /usr/sbin/afpd() [0x4513cc]
Окт 23 13:00:48.893815 afpd[8837] {fault.c:102} (S:Default): #2 /lib64/libc.so.6(+0x326b0) [0x7f36c11626b0]
Окт 23 13:00:48.893819 afpd[8837] {fault.c:102} (S:Default): #3 /lib64/libc.so.6(+0x1282aa) [0x7f36c12582aa]
Окт 23 13:00:48.893823 afpd[8837] {fault.c:102} (S:Default): #4 /usr/sbin/afpd() [0x461f5b]
Окт 23 13:00:48.893827 afpd[8837] {fault.c:102} (S:Default): #5 /usr/sbin/afpd(ea_renamefile+0x146) [0x464f86]
Окт 23 13:00:48.893830 afpd[8837] {fault.c:102} (S:Default): #6 /usr/sbin/afpd() [0x45c566]
Окт 23 13:00:48.893834 afpd[8837] {fault.c:102} (S:Default): #7 /usr/sbin/afpd(renamefile+0x72) [0x422ea2]
Окт 23 13:00:48.893838 afpd[8837] {fault.c:102} (S:Default): #8 /usr/sbin/afpd() [0x426857]
Окт 23 13:00:48.893842 afpd[8837] {fault.c:102} (S:Default): #9 /usr/sbin/afpd(afp_moveandrename+0x252) [0x426ce2]
Окт 23 13:00:48.893846 afpd[8837] {fault.c:102} (S:Default): #10 /usr/sbin/afpd(afp_over_dsi+0x4f9) [0x410699]
Окт 23 13:00:48.893850 afpd[8837] {fault.c:102} (S:Default): #11 /usr/sbin/afpd() [0x40f277]
Окт 23 13:00:48.893855 afpd[8837] {fault.c:102} (S:Default): #12 /usr/sbin/afpd(main+0x55b) [0x42a92b]
Окт 23 13:00:48.893860 afpd[8837] {fault.c:102} (S:Default): #13 /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f36c114ed5d]
Окт 23 13:00:48.893865 afpd[8837] {fault.c:102} (S:Default): #14 /usr/sbin/afpd() [0x40e539]
Конечно кто то может сказать что версия 2.2.0 давным-давно не актуальна, но что поделать, если в репах свежих версий нет, а ставить 3-ю версию в ручную лично мне как то не очень хочется. Вообще я не сторонник собирать что то руками, когда есть пакетный менеджер. Уж в крайнем случае подключить альтернативный репозиторий, в котором можно найти актуальную версию. Но для netatalk таких реп я найти не смог.
Проблема решилась после эксперимента с методами аутентификации в netatalk. В частности в своём мануале по настройке AFP под Gentoo, я использовал для авторизации 2 метода:
uams_dhx.so — Allow Diffie-Hellman eXchange (DHX) for authentication.
и
uams_dhx2.so — Allow Diffie-Hellman eXchange 2 (DHX2) for authentication.
И проблема крылась как раз-таки во втором из них. Уж не знаю что там накосячили разработчики, но методом научного тыка было установлено, если заменить uams_dhx2.so на uams_dhx2_passwd.so, а в документации указаны на выбор один из этих модулей для DHX2, то проблема с сохранением данных пропадает. Конечно в логе остаётся какой то мусор:
Окт 23 13:04:02.857207 afpd[8913] {ea_sys.c:388} (E:AFPDaemon): sys_remove_ea(config.php/com.apple.document.draft#PS): error: Нет доступных данных
Окт 23 13:04:08.076925 afpd[8913] {ea_sys.c:388} (E:AFPDaemon): sys_remove_ea(config.php/com.apple.document.draft#PS): error: Нет доступных данных
Окт 23 13:04:21.988429 afpd[8913] {ea_sys.c:388} (E:AFPDaemon): sys_remove_ea(System.class.php/com.apple.document.draft#PS): error: Нет доступных данных
но я не заметил что бы это как то отразилось на работе системы в целом или netatalk в частности.
|
Created attachment 1210937 [details]
smb.conf
Description of problem:
Samba crashes with "internal error: Signal 11" at startup.
Version-Release number of selected component (if applicable):
samba-4.5.0-2.fc25.x86_64
How reproducible:
Always.
Steps to Reproduce:
1. Install Samba
2. Start Samba (systemctl start smb)
Actual results:
[2016/10/16 11:53:26.406049, 1] ../source3/profile/profile.c:51(set_profile_level)
INFO: Profiling turned OFF from pid 5248
[2016/10/16 11:53:26.411048, 0] ../lib/util/fault.c:78(fault_report)
===============================================================
[2016/10/16 11:53:26.411122, 0] ../lib/util/fault.c:79(fault_report)
INTERNAL ERROR: Signal 11 in pid 5251 (4.5.0)
Please read the Trouble-Shooting section of the Samba HOWTO
[2016/10/16 11:53:26.411150, 0] ../lib/util/fault.c:81(fault_report)
===============================================================
[2016/10/16 11:53:26.411169, 0] ../source3/lib/util.c:791(smb_panic_s3)
PANIC (pid 5251): internal error
[2016/10/16 11:53:26.411262, 0] ../lib/util/fault.c:78(fault_report)
===============================================================
[2016/10/16 11:53:26.411335, 0] ../lib/util/fault.c:79(fault_report)
INTERNAL ERROR: Signal 11 in pid 5252 (4.5.0)
Please read the Trouble-Shooting section of the Samba HOWTO
[2016/10/16 11:53:26.411361, 0] ../lib/util/fault.c:81(fault_report)
===============================================================
[2016/10/16 11:53:26.411379, 0] ../source3/lib/util.c:791(smb_panic_s3)
PANIC (pid 5252): internal error
[2016/10/16 11:53:26.411682, 0] ../source3/lib/util.c:902(log_stack_trace)
BACKTRACE: 14 stack frames:
#0 /lib64/libsmbconf.so.0(log_stack_trace+0x1c) [0x7f70b11cb80c]
#1 /lib64/libsmbconf.so.0(smb_panic_s3+0x20) [0x7f70b11cb8e0]
#2 /lib64/libsamba-util.so.0(smb_panic+0x2f) [0x7f70b36bf82f]
#3 /lib64/libsamba-util.so.0(+0x22a46) [0x7f70b36bfa46]
#4 /lib64/libpthread.so.0(+0x115c0) [0x7f70b39235c0]
#5 /lib64/libtevent.so.0(tevent_debug+0x56) [0x7f70afc04f06]
#6 /lib64/libtevent.so.0(tevent_common_loop_timer_delay+0xba) [0x7f70afc094ea]
#7 /lib64/libsmbconf.so.0(run_events_poll+0x1a9) [0x7f70b11e32b9]
#8 /lib64/libsmbconf.so.0(+0x36457) [0x7f70b11e3457]
#9 /lib64/libtevent.so.0(_tevent_loop_once+0x9d) [0x7f70afc04abd]
#10 /lib64/libtevent.so.0(tevent_req_poll+0x23) [0x7f70afc05e23]
#11 /usr/sbin/smbd(main+0x860) [0x55889a3176b0]
#12 /lib64/libc.so.6(__libc_start_main+0xf1) [0x7f70af85a401]
#13 /usr/sbin/smbd(_start+0x2a) [0x55889a3186ba]
[2016/10/16 11:53:26.411797, 0] ../source3/lib/util.c:902(log_stack_trace)
BACKTRACE: 5 stack frames:
[2016/10/16 11:53:26.411818, 0] ../source3/lib/dumpcore.c:303(dump_core)
#0 /lib64/libsmbconf.so.0(log_stack_trace+0x1c) [0x7f70b11cb80c]
dumping core in /var/log/samba/cores/smbd
#1 /lib64/libsmbconf.so.0(smb_panic_s3+0x20) [0x7f70b11cb8e0]
#2 /lib64/libsamba-util.so.0(smb_panic+0x2f) [0x7f70b36bf82f]
#3 /lib64/libsamba-util.so.0(+0x22a46) [0x7f70b36bfa46]
#4 /lib64/libpthread.so.0(+0x115c0) [0x7f70b39235c0]
[2016/10/16 11:53:26.411874, 0] ../source3/lib/dumpcore.c:303(dump_core)
dumping core in /var/log/samba/cores/smbd
[2016/10/16 11:53:26.416653, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2016/10/16 11:53:26.417636, 1] ../source3/printing/printer_list.c:234(printer_list_get_last_refresh)
Failed to fetch record!
[2016/10/16 11:53:26.421938, 0] ../lib/util/fault.c:78(fault_report)
===============================================================
[2016/10/16 11:53:26.422014, 0] ../lib/util/fault.c:79(fault_report)
INTERNAL ERROR: Signal 11 in pid 5255 (4.5.0)
Please read the Trouble-Shooting section of the Samba HOWTO
[2016/10/16 11:53:26.422046, 0] ../lib/util/fault.c:81(fault_report)
===============================================================
[2016/10/16 11:53:26.422064, 0] ../source3/lib/util.c:791(smb_panic_s3)
PANIC (pid 5255): internal error
[2016/10/16 11:53:26.422610, 0] ../source3/lib/util.c:902(log_stack_trace)
BACKTRACE: 15 stack frames:
#0 /lib64/libsmbconf.so.0(log_stack_trace+0x1c) [0x7f70b11cb80c]
#1 /lib64/libsmbconf.so.0(smb_panic_s3+0x20) [0x7f70b11cb8e0]
#2 /lib64/libsamba-util.so.0(smb_panic+0x2f) [0x7f70b36bf82f]
#3 /lib64/libsamba-util.so.0(+0x22a46) [0x7f70b36bfa46]
#4 /lib64/libpthread.so.0(+0x115c0) [0x7f70b39235c0]
#5 /lib64/libtalloc.so.2(talloc_get_size+0x5) [0x7f70afe15125]
#6 /lib64/libsmbconf.so.0(event_add_to_poll_args+0x76) [0x7f70b11e2eb6]
#7 /lib64/libsmbconf.so.0(+0x36491) [0x7f70b11e3491]
#8 /lib64/libtevent.so.0(_tevent_loop_once+0x9d) [0x7f70afc04abd]
#9 /lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x7f70afc04ceb]
#10 /usr/lib64/samba/libsmbd-base-samba4.so(start_background_queue+0x2b1) [0x7f70b31d5a31]
#11 /usr/lib64/samba/libsmbd-base-samba4.so(printing_subsystem_init+0xb7) [0x7f70b31d5d57]
#12 /usr/sbin/smbd(main+0x17e1) [0x55889a318631]
#13 /lib64/libc.so.6(__libc_start_main+0xf1) [0x7f70af85a401]
#14 /usr/sbin/smbd(_start+0x2a) [0x55889a3186ba]
[2016/10/16 11:53:26.422774, 0] ../source3/lib/dumpcore.c:303(dump_core)
dumping core in /var/log/samba/cores/smbd
[2016/10/16 11:53:26.453473, 1] ../source3/smbd/server.c:803(remove_child_pid)
remove_child_pid: Restarting cleanupd
[2016/10/16 11:53:26.453523, 0] ../lib/util/fault.c:78(fault_report)
===============================================================
[2016/10/16 11:53:26.453571, 0] ../lib/util/fault.c:79(fault_report)
INTERNAL ERROR: Signal 11 in pid 5250 (4.5.0)
Please read the Trouble-Shooting section of the Samba HOWTO
[2016/10/16 11:53:26.453595, 0] ../lib/util/fault.c:81(fault_report)
===============================================================
[2016/10/16 11:53:26.453612, 0] ../source3/lib/util.c:791(smb_panic_s3)
PANIC (pid 5250): internal error
[2016/10/16 11:53:26.453870, 0] ../source3/lib/util.c:902(log_stack_trace)
BACKTRACE: 19 stack frames:
#0 /lib64/libsmbconf.so.0(log_stack_trace+0x1c) [0x7f70b11cb80c]
#1 /lib64/libsmbconf.so.0(smb_panic_s3+0x20) [0x7f70b11cb8e0]
#2 /lib64/libsamba-util.so.0(smb_panic+0x2f) [0x7f70b36bf82f]
#3 /lib64/libsamba-util.so.0(+0x22a46) [0x7f70b36bfa46]
#4 /lib64/libpthread.so.0(+0x115c0) [0x7f70b39235c0]
#5 /lib64/libtevent.so.0(tevent_timeval_compare+0) [0x7f70afc090a0]
#6 /lib64/libtevent.so.0(+0x9251) [0x7f70afc09251]
#7 /lib64/libtevent.so.0(tevent_common_add_timer+0x13) [0x7f70afc09403]
#8 /lib64/libtevent.so.0(tevent_req_set_endtime+0x60) [0x7f70afc05ef0]
#9 /lib64/libtevent.so.0(tevent_wakeup_send+0x55) [0x7f70afc097a5]
#10 /usr/sbin/smbd(+0xaebe) [0x55889a31bebe]
#11 /lib64/libtevent.so.0(tevent_common_check_signal+0x278) [0x7f70afc08a58]
#12 /lib64/libsmbconf.so.0(run_events_poll+0x24) [0x7f70b11e3134]
#13 /lib64/libsmbconf.so.0(+0x364f7) [0x7f70b11e34f7]
#14 /lib64/libtevent.so.0(_tevent_loop_once+0x9d) [0x7f70afc04abd]
#15 /lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x7f70afc04ceb]
#16 /usr/sbin/smbd(main+0x1642) [0x55889a318492]
#17 /lib64/libc.so.6(__libc_start_main+0xf1) [0x7f70af85a401]
#18 /usr/sbin/smbd(_start+0x2a) [0x55889a3186ba]
[2016/10/16 11:53:26.454026, 0] ../source3/lib/dumpcore.c:303(dump_core)
dumping core in /var/log/samba/cores/smbd
Expected results:
smbd should start correctly.
Additional info:
- SELinux is disabled.
- Even if the log says, there is no core dump file in the mentioned directory.
- smb.conf for a standalone server with guest share attached.
I figured out, what causes the problem: The libtevent package is incompatible. F25 ships libtevent-0.9.30-1.fc25.x86_64. I downloaded the libtevent-0.9.28-1.fc24.x86_64 from the F24 repo and downgraded it using "dnf". Now Samba starts correctly. Can you please ship an older version of libtevent in F25 or fix whatever causes this incompatibility? Thanks.
Same here, downgrading libtevent helped.
*** This bug has been marked as a duplicate of bug 1375973 *** |
|
net/samba410 built from ports with most features turned off (just AESNI, SYSLOG, UTMP, GSSAPI_BUILTIN, and ZEROCONF_NONE) will periodically crash with a SIGSEGV. The trigger seems to be if I store a couple of icon (*.ico) files on the exported samba share and then try to use those icons in a shortcut object (*.lnk), and then try to trigger Windows to refresh its icon cache (by executing "C:WindowsSystem32ie4uinit.exe -show"). Furthermore, these shortcut objects have to be stored in a "quick launch" toolbar folder that I have added to my Windows taskbar (right-click -> Toolbars -> New Toolbar -> ...). Under that setup, by re-running the icon cache refresh command, one or more of the shortcut objects will lose their icons and default to the blank document icon stred in "C:WindowsSystem32shell32.dll". When that happens, if I then try to manually reset the icon by reselecting it, I may, or may not, get an error stating that Windows can no longer find the icon on the remote samba share path. Sometimes, when re-selecting the icon file in the file dialog, Windows will then claim that it cannot read the icon file. When one of these two events happens, it MAY indicate that the smbd process on the FreeBSD server has SIGSEGV'ed. But not always. You kinda have to play around with it to trigger it. It seems running the icon cache refresh command several times, with a small pause between each run, has the best chance of triggering it. When it does happen, this is the output I get (hostname scrubbed): Apr 17 21:59:12 foo smbd[97026]: [2020/04/17 21:59:12.993900, 0] ../../lib/util/become_daemon.c:136(daemon_ready) Apr 17 21:59:12 foo smbd[97026]: daemon_ready: daemon 'smbd' finished starting up and ready to serve connections Apr 17 22:00:37 foo smbd[164]: [2020/04/17 22:00:37.766807, 0] ../../lib/util/fault.c:79(fault_report) Apr 17 22:00:37 foo smbd[164]: =============================================================== Apr 17 22:00:37 foo smbd[164]: [2020/04/17 22:00:37.767238, 0] ../../lib/util/fault.c:80(fault_report) Apr 17 22:00:37 foo smbd[164]: INTERNAL ERROR: Signal 11 in pid 164 (4.10.14) Apr 17 22:00:37 foo smbd[164]: If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting Apr 17 22:00:37 foo smbd[164]: [2020/04/17 22:00:37.767282, 0] ../../lib/util/fault.c:86(fault_report) Apr 17 22:00:37 foo smbd[164]: =============================================================== Apr 17 22:00:37 foo smbd[164]: [2020/04/17 22:00:37.767304, 0] ../../source3/lib/util.c:824(smb_panic_s3) Apr 17 22:00:37 foo smbd[164]: PANIC (pid 164): internal error Apr 17 22:00:37 foo smbd[164]: [2020/04/17 22:00:37.767983, 0] ../../lib/util/fault.c:265(log_stack_trace) Apr 17 22:00:37 foo smbd[164]: BACKTRACE: 6 stack frames: Apr 17 22:00:37 foo smbd[164]: #0 0x36b07d6eaa77 <log_stack_trace+0x37> at /usr/local/lib/samba4/libsamba-util.so.0 Apr 17 22:00:37 foo smbd[164]: #1 0x36b085ee512d <smb_panic_s3+0x4d> at /usr/local/lib/samba4/libsmbconf.so.0 Apr 17 22:00:37 foo smbd[164]: #2 0x36b07d6ea867 <smb_panic+0x17> at /usr/local/lib/samba4/libsamba-util.so.0 Apr 17 22:00:37 foo smbd[164]: #3 0x36b07d6eac4e <log_stack_trace+0x20e> at /usr/local/lib/samba4/libsamba-util.so.0 Apr 17 22:00:37 foo smbd[164]: #4 0x36b07d6ea849 <fault_setup+0x59> at /usr/local/lib/samba4/libsamba-util.so.0 Apr 17 22:00:37 foo smbd[164]: #5 0x36b0b6a593c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3 Apr 17 22:00:37 foo smbd[164]: [2020/04/17 22:00:37.768103, 0] ../../source3/lib/dumpcore.c:310(dump_core) Apr 17 22:00:37 foo smbd[164]: unable to change to %N.core Apr 17 22:00:37 foo smbd[164]: refusing to dump core It also seems that I can trigger this crash more often under the newly-minted net/samba411 port, but I did not extensively test that before falling back to net/samba410. I understand if that is somewhat convoluted, and it WILL require a Windows system to actually try and test for this, but I don't have much else to offer. Browsing the share normally from Windows Explorer works fine and icons cache and load fine from virtually any other place in Windows EXCEPT from a shortcut object (*.lnk) in a toolbar added to the taskbar. I don't know if there is something different about how shortcuts in a toolbar folder added to the taskbar behave differently when fetching their icon resources or what. I've tried turning the Samba logging level up to 7, but that did not add any additional context to the above crash log. I also tried attach gdb to the parent process, but the crashing process is some child process that is spawned only when doing file operations, and I am not sure how to trace that.
Adding an update here and changing the bug title, because I can reproduce a similar error (or the same one, not sure) in net/samba413 (4.13.0) as well as Samba-4.12.8. And I believe I have reproduction steps that are easier to simulate than what I originally described. I have further isolated the problem to what I believe is an issue in Samba's vfs_dirsort module. First, does anyone know how I can rebuild the Samba port with full debugging symbols turned on? Current backtrace dumps from the crashing processes are missing debug information. Getting that turned on and reproducing the crash would probably help a lot here. Steps to reproduce: Requirements: - Windows 10-based machine - 7-Zip 20.00 alpha x64 - Snort.org subscriber ruleset tar.gz archive (snortrules-snapshot-xxxxx.tar.gz) - Samba share on ZFS - 'dirsort' loaded in "vfs objects" Steps: - On the Windows machine, map a drive letter to the Samba share - Using 7-zip, open the snortrules-snapshot-xxxxx.tar.gz archive - Drag and drop the "rules" subfolder directly into the share - Attempt to double-click on the folder - Crash should be triggered (may have to repeat or F5 a bunch of times) As far as I can tell, some content in one of the Snort rule files may be a trigger, but I cannot work out if it's a specific file, combination of files, file sizes, number of files, etc. I tried stripping off any and all acls via 'setfacl -b *', and removed execute permissions via 'chmod -x *', but that has had no effect. I tried moving files elsewhere and refreshing the folder, but still couldn't isolate it to a specific file or files. After I gave up on that, I started removing vfs modules, starting with the zfsacl and freebsd ones, but that didn't work. After removing dirsort, however, I have been unable to reproduce the crash via the new method described here. I can reproduce the icon issue, but apparently without the crash described in my original comment. So likely, the crash issue is tied to something in the dirsort module on FreeBSD platforms, while the icon issue is something else. Fixing the crash is more important, so changing the bug to match that is best. I also suspect that the use of 7-zip to unpack the Snort rules archive is important. I tried unpacking that archive directly on the NAS machine's shell using tar zfx, and was unable to get it to crash via Samba afterward. When you drag and drop files from an archive to their destination, 7-zip will first extract to %TMPDIR% on the Windows host, then move the files to the final destination. Something in this process apparently sets up conditions that enable the crash to happen, but I cannot determine what these conditions are.
Created attachment 219294 [details]
Samba config file for net/samba413
"hosts allow" and "workgroup" have been redacted. Everything else is as-is.
Created attachment 219295 [details]
Crash log snippet from net/samba413
One specific set of crash dump output when the problem is triggered. Multiple such dumps get generated when the error is reproduced, eventually flooding 'dmesg' out. And "foo" is the redacted name for the machine. Unlike the net/samba410 crash, the backtrace info is missing the symbol names, so it's impossible to work out exactly what happened.
|