I just got an INTERNAL ERROR: Signal 11 in smbd (4.12.10) in something that sids_to_unixids() in source3/winbindd/idmap_hash/idmap_has.c calls and 3 levels down - unfortunately the stack trace doesn?t say what it is - probably optimised into inline code or something. Recently upgraded from Samba 4.12.5 to 4.12.10 (self-compiled). FreeBSD 12.2 It happened right after 10 hours since that smbd processes started so the 10 hours Kerberos ticket lifetime is probably involved somehow? Nov 10 21:39:11 runur01 smbd_audit[23768]: #3 sig_fault + 0x6c [ip=0x80129a7a9] [sp=0x7fffffffcbb0] Nov 10 21:39:11 runur01 smbd_audit[23768]: #4 <unknown symbol> [ip=0x801517b70] [sp=0x7fffffffcbc0] Nov 10 21:39:12 runur01 smbd_audit[23768]: #5 <unknown symbol> [ip=0x80151713f] [sp=0x7fffffffcf80] Nov 10 21:39:12 runur01 smbd_audit[23768]: #6 <unknown symbol> [ip=0x7ffffffff003] [sp=0x7fffffffcff0] Nov 10 21:39:12 runur01 smbd_audit[23768]: #7 sids_to_unixids + 0x25d Unfortunately no core dump :-( I created a bug in bugzilla for it (14571). The calls that sids_to_unixids() calls are: idmap_hash_initialize wcache_tdc_fetch_list make_tdc_key tdb_fetch unpack_tdc_domains talloc_zero_array domain_has_idmap_config hash_domain_sid dom_sid_str_buf talloc sid_copy sid_copy sid_split_rid hash_domain_sid hash_rid combine_hashes But I don?t see any obvious candidate? - Peter
On 10/11/2020 21:42, Peter Eriksson via samba wrote:> I just got an INTERNAL ERROR: Signal 11 in smbd (4.12.10) in something that sids_to_unixids() in source3/winbindd/idmap_hash/idmap_has.c calls and 3 levels down - unfortunately the stack trace doesn?t say what it is - probably optimised into inline code or something. > > Recently upgraded from Samba 4.12.5 to 4.12.10 (self-compiled). FreeBSD 12.2 > > It happened right after 10 hours since that smbd processes started so the 10 hours Kerberos ticket lifetime is probably involved somehow? > > Nov 10 21:39:11 runur01 smbd_audit[23768]: #3 sig_fault + 0x6c [ip=0x80129a7a9] [sp=0x7fffffffcbb0] > Nov 10 21:39:11 runur01 smbd_audit[23768]: #4 <unknown symbol> [ip=0x801517b70] [sp=0x7fffffffcbc0] > Nov 10 21:39:12 runur01 smbd_audit[23768]: #5 <unknown symbol> [ip=0x80151713f] [sp=0x7fffffffcf80] > Nov 10 21:39:12 runur01 smbd_audit[23768]: #6 <unknown symbol> [ip=0x7ffffffff003] [sp=0x7fffffffcff0] > Nov 10 21:39:12 runur01 smbd_audit[23768]: #7 sids_to_unixids + 0x25d > > Unfortunately no core dump :-( > > I created a bug in bugzilla for it (14571). > > The calls that sids_to_unixids() calls are: > > idmap_hash_initialize > wcache_tdc_fetch_list > make_tdc_key > tdb_fetch > unpack_tdc_domains > talloc_zero_array > domain_has_idmap_config > hash_domain_sid > dom_sid_str_buf > talloc > sid_copy > sid_copy > sid_split_rid > hash_domain_sid > hash_rid > combine_hashes > > But I don?t see any obvious candidate? > > - Peter > > >Have you read 'man idmap_hash' ? If you did, did you miss this at the top: idmap_hash - DO NOT USE THIS BACKEND Please do not use idmap_hash Rowland
Well, we don?t use it. At least not intentionally? Ie, nothing references it in the configuration files. Hmm.. Aha! There are multiple instances of a function with that name and I just found the first match when grepping? My bad. Then it?s probably the variant found in source3/passdb/lookup_sid.c or perhaps something in source3/winbbind/idmap_ad or source3/winbindd/idmap_tdb that is causing the signal 11.. (We use idmap backends tdb & ad) - Peter> Have you read 'man idmap_hash' ? > > If you did, did you miss this at the top: > > idmap_hash - DO NOT USE THIS BACKEND > > > Please do not use idmap_hash > > Rowland > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba <https://lists.samba.org/mailman/options/samba>
On Tue, Nov 10, 2020 at 5:01 PM Peter Eriksson via samba < samba at lists.samba.org> wrote:> I just got an INTERNAL ERROR: Signal 11 in smbd (4.12.10) in something > that sids_to_unixids() in source3/winbindd/idmap_hash/idmap_has.c calls and > 3 levels down - unfortunately the stack trace doesn?t say what it is - > probably optimised into inline code or something. > > Recently upgraded from Samba 4.12.5 to 4.12.10 (self-compiled). FreeBSD > 12.2 > > It happened right after 10 hours since that smbd processes started so the > 10 hours Kerberos ticket lifetime is probably involved somehow? > > Nov 10 21:39:11 runur01 smbd_audit[23768]: #3 sig_fault + 0x6c > [ip=0x80129a7a9] [sp=0x7fffffffcbb0] > Nov 10 21:39:11 runur01 smbd_audit[23768]: #4 <unknown symbol> > [ip=0x801517b70] [sp=0x7fffffffcbc0] > Nov 10 21:39:12 runur01 smbd_audit[23768]: #5 <unknown symbol> > [ip=0x80151713f] [sp=0x7fffffffcf80] > Nov 10 21:39:12 runur01 smbd_audit[23768]: #6 <unknown symbol> > [ip=0x7ffffffff003] [sp=0x7fffffffcff0] > Nov 10 21:39:12 runur01 smbd_audit[23768]: #7 sids_to_unixids + 0x25d > > Unfortunately no core dump :-( >You may need to run the command "sysctl kern.sugid_coredump=1" and also set kern.corefile to an appropriate path (for example /tmp/%N_%P.core -- this ensures program name and pid are in corefile name). If possible compile without optimizations and with debugging symbols (this will improve visibility of error).