Red Hat Bugzilla – Bug 984870
[abrt] samba-winbind-4.0.7-1.fc19: dump_core: Process /usr/sbin/winbindd was killed by signal 6 (SIGABRT)
Last modified: 2015-02-18 09:00:41 EST
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#2 dump_core at ../source3/lib/dumpcore.c:336
#3 smb_panic_s3 at ../source3/lib/util.c:833
#4 smb_panic at ../lib/util/fault.c:159
#5 pdb_get_methods at ../source3/passdb/pdb_interface.c:225
#6 pdb_get_seq_num at ../source3/passdb/pdb_interface.c:1201
#7 query_dom_info_8 at ../source3/rpc_server/samr/srv_samr_nt.c:3452
#8 _samr_QueryDomainInfo at ../source3/rpc_server/samr/srv_samr_nt.c:3660
#9 api_samr_QueryDomainInfo at default/librpc/gen_ndr/srv_samr.c:680
#10 rpcint_dispatch at ../source3/rpc_server/rpc_ncacn_np.c:133
#11 rpcint_bh_raw_call_send at ../source3/rpc_server/rpc_ncacn_np.c:220
Potential duplicate: bug 893121
Created attachment 774098 [details]
Created attachment 774099 [details]
Created attachment 774100 [details]
Created attachment 774103 [details]
Created attachment 774105 [details]
Created attachment 774107 [details]
Created attachment 774110 [details]
Created attachment 774114 [details]
Created attachment 774116 [details]
Created attachment 774117 [details]
Christian, could you please add your smb.conf to the bug report?
Created attachment 774184 [details]
Sorry but the file has been modified afterwards, "winbind use default domain" and "security" might have been different.
Reassign to myself for investigation.
Do you have /usr/lib64/samba/pdb/tdbsam.so available? What does 'rpm -qf /usr/lib64/samba/pdb/tdbsam.so' return? Also, what does 'stat /usr/lib64/samba/pdb/tdbsam.so' show?
Here you go:
$ rpm -qf /usr/lib64/samba/pdb/tdbsam.so
$ stat /usr/lib64/samba/pdb/tdbsam.so
Fichier : « /usr/lib64/samba/pdb/tdbsam.so »
Taille : 36416 Blocs : 72 Blocs d'E/S : 4096 fichier
Périphérique : fd01h/64769d Inœud : 1581916 Liens : 1
Accès : (0755/-rwxr-xr-x) UID : ( 0/ root) GID : ( 0/ root)
Contexte : system_u:object_r:lib_t:s0
Accès : 2013-07-19 11:32:17.217965726 +0200
Modif. : 2013-07-03 18:41:01.000000000 +0200
Changt : 2013-07-06 10:00:40.327352744 +0200
Créé : -
Attempt login using domain account. Unable to login. Additional sssd information in "messages": Aug 6 07:24:48 w7pxe1 [sssd[ldap_child]]: Failed to initialize credentials using keytab [default]: Preauthentication failed. Unable to create GSSAPI-encrypted LDAP connection.
Aug 6 07:24:48 w7pxe1 [sssd[ldap_child]]: Preauthentication failed
reason: Process /usr/sbin/winbindd was killed by signal 6 (SIGABRT)
runlevel: N 5
(In reply to Aniello Di Meglio from comment #16)
> Attempt login using domain account. Unable to login. Additional sssd
> information in "messages": Aug 6 07:24:48 w7pxe1 [sssd[ldap_child]]:
> Failed to initialize credentials using keytab [default]: Preauthentication
> failed. Unable to create GSSAPI-encrypted LDAP connection.
> Aug 6 07:24:48 w7pxe1 [sssd[ldap_child]]: Preauthentication failed
Do you see any SELinux AVCs in /var/log/audit/audit.log?
Can you please describe your configuration a bit since sssd and winbindd are not really directly related.
This crash occurs every time my wife tries to access a samba share after it's been
sitting for a while. It does not impede her ability to use the samba share and the
files and/or directories within. Very reproducible.
reason: Process /usr/sbin/smbd was killed by signal 6 (SIGABRT)
runlevel: N 3
Ignore comment #18: It was auto-appended by abortd. My problem
seems completely unrelated, and I opened bug #1007433 for it.
Happened to me while updating the samba-winbind package while the service was running. I don't know wether it's reproducible or not.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.