Bug 4991 - Winbind fails, cannot stacktrace
Winbind fails, cannot stacktrace
Status: NEW
Product: Samba 3.0
Classification: Unclassified
Component: winbind
3.0.25a
x86 FreeBSD
: P3 major
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-09-24 14:23 UTC by Christopher Neill
Modified: 2007-09-28 03:32 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Neill 2007-09-24 14:23:08 UTC
Sep 24 11:53:55 juicy winbindd[90763]: [2007/09/24 11:53:55, 0] nsswitch/winbindd_cache.c:initialize_winbindd_cache(2221)
Sep 24 11:53:55 juicy winbindd[90763]:   initialize_winbindd_cache: clearing cache and re-creating with version number 1
Sep 24 11:53:55 juicy winbindd[90765]: [2007/09/24 11:53:55, 0] nsswitch/idmap.c:idmap_init(438)
Sep 24 11:53:55 juicy winbindd[90765]:   ERROR: Initialization failed for backend rid (domain default domain), deferred!
Sep 24 11:53:55 juicy winbindd[90765]: [2007/09/24 11:53:55, 0] nsswitch/idmap.c:smb_register_idmap(129)
Sep 24 11:53:55 juicy winbindd[90765]:   Idmap module rid already registered!
Sep 24 11:53:55 juicy winbindd[90765]: [2007/09/24 11:53:55, 0] lib/module.c:do_smb_load_module(69)
Sep 24 11:53:55 juicy winbindd[90765]:   Module '/usr/local/lib/samba/idmap/rid.so' initialization failed: NT_STATUS_OBJECT_NAME_COLLISION
Sep 24 11:53:55 juicy winbindd[90765]: [2007/09/24 11:53:55, 0] lib/fault.c:fault_report(41)
Sep 24 11:53:55 juicy winbindd[90765]:   ===============================================================
Sep 24 11:53:55 juicy winbindd[90765]: [2007/09/24 11:53:55, 0] lib/fault.c:fault_report(42)
Sep 24 11:53:55 juicy winbindd[90765]:   INTERNAL ERROR: Signal 11 in pid 90765 (3.0.25a)
Sep 24 11:53:55 juicy winbindd[90765]:   Please read the Trouble-Shooting section of the Samba3-HOWTO
Sep 24 11:53:55 juicy winbindd[90765]: [2007/09/24 11:53:55, 0] lib/fault.c:fault_report(44)
Sep 24 11:53:55 juicy winbindd[90765]:
Sep 24 11:53:55 juicy winbindd[90765]:   From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
Sep 24 11:53:55 juicy winbindd[90765]: [2007/09/24 11:53:55, 0] lib/fault.c:fault_report(45)
Sep 24 11:53:55 juicy winbindd[90765]:   ===============================================================
Sep 24 11:53:55 juicy winbindd[90765]: [2007/09/24 11:53:55, 0] lib/util.c:smb_panic(1626)
Sep 24 11:53:55 juicy winbindd[90765]:   smb_panic: clobber_region() last called from [smb_probe_module(117)]
Sep 24 11:53:55 juicy winbindd[90765]: [2007/09/24 11:53:55, 0] lib/util.c:smb_panic(1632)
Sep 24 11:53:55 juicy winbindd[90765]:   PANIC (pid 90765): internal error
Sep 24 11:53:55 juicy winbindd[90765]: [2007/09/24 11:53:55, 0] lib/util.c:log_stack_trace(1786)
Sep 24 11:53:55 juicy winbindd[90765]:   unable to produce a stack trace on this platform
Sep 24 11:53:55 juicy winbindd[90765]: [2007/09/24 11:53:55, 0] lib/util.c:smb_panic(1637)
Sep 24 11:53:55 juicy winbindd[90765]:   smb_panic(): calling panic action [/bin/sleep 999999999]
Sep 24 11:55:01 juicy winbindd[90763]: [2007/09/24 11:55:01, 0] nsswitch/idmap.c:idmap_init(438)
Sep 24 11:55:01 juicy winbindd[90763]:   ERROR: Initialization failed for backend rid (domain default domain), deferred!
Sep 24 11:55:01 juicy winbindd[90763]: [2007/09/24 11:55:01, 0] nsswitch/idmap.c:smb_register_idmap(129)
Sep 24 11:55:01 juicy winbindd[90763]:   Idmap module rid already registered!
Sep 24 11:55:01 juicy winbindd[90763]: [2007/09/24 11:55:01, 0] lib/module.c:do_smb_load_module(69)
Sep 24 11:55:01 juicy winbindd[90763]:   Module '/usr/local/lib/samba/idmap/rid.so' initialization failed: NT_STATUS_OBJECT_NAME_COLLISION
Sep 24 11:55:01 juicy winbindd[90763]: [2007/09/24 11:55:01, 0] lib/fault.c:fault_report(41)
Sep 24 11:55:01 juicy winbindd[90763]:   ===============================================================
Sep 24 11:55:01 juicy winbindd[90763]: [2007/09/24 11:55:01, 0] lib/fault.c:fault_report(42)
Sep 24 11:55:01 juicy winbindd[90763]:   INTERNAL ERROR: Signal 11 in pid 90763 (3.0.25a)
Sep 24 11:55:01 juicy winbindd[90763]:   Please read the Trouble-Shooting section of the Samba3-HOWTO
Sep 24 11:55:01 juicy winbindd[90763]: [2007/09/24 11:55:01, 0] lib/fault.c:fault_report(44)
Sep 24 11:55:01 juicy winbindd[90763]:
Sep 24 11:55:01 juicy winbindd[90763]:   From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
Sep 24 11:55:01 juicy winbindd[90763]: [2007/09/24 11:55:01, 0] lib/fault.c:fault_report(45)
Sep 24 11:55:01 juicy winbindd[90763]:   ===============================================================
Sep 24 11:55:01 juicy winbindd[90763]: [2007/09/24 11:55:01, 0] lib/util.c:smb_panic(1626)
Sep 24 11:55:01 juicy winbindd[90763]:   smb_panic: clobber_region() last called from [sid_to_string(194)]
Sep 24 11:55:01 juicy winbindd[90763]: [2007/09/24 11:55:01, 0] lib/util.c:smb_panic(1632)
Sep 24 11:55:01 juicy winbindd[90763]:   PANIC (pid 90763): internal error
Sep 24 11:55:01 juicy winbindd[90763]: [2007/09/24 11:55:01, 0] lib/util.c:log_stack_trace(1786)
Sep 24 11:55:01 juicy winbindd[90763]:   unable to produce a stack trace on this platform
Sep 24 11:55:01 juicy winbindd[90763]: [2007/09/24 11:55:01, 0] lib/util.c:smb_panic(1637)
Sep 24 11:55:01 juicy winbindd[90763]:   smb_panic(): calling panic action [/bin/sleep 999999999]

Please let me know what additional configs, logs, details you need.

cneill@juicy [12:07pm](1):317:~> smbd -V
Version 3.0.25a
cneill@juicy [12:15pm](1):318:~> uname -a
FreeBSD juicy.dev.biz360.com 6.2-STABLE FreeBSD 6.2-STABLE #2: Thu Aug 30 16:01:27 PDT 2007     root@juicy.dev.biz360.com:/usr/obj/usr/src/sys/JUICYSMP  i386
Comment 1 Timur Bakeyev 2007-09-28 03:32:27 UTC
Hi, Chris!

(In reply to comment #0)
> ===============================================================
> Sep 24 11:53:55 juicy winbindd[90765]: [2007/09/24 11:53:55, 0]
> lib/fault.c:fault_report(42)
> Sep 24 11:53:55 juicy winbindd[90765]:   INTERNAL ERROR: Signal 11 in pid 90765
> (3.0.25a)
> Sep 24 11:53:55 juicy winbindd[90765]:   Please read the Trouble-Shooting
> section of the Samba3-HOWTO
> Sep 24 11:53:55 juicy winbindd[90765]: [2007/09/24 11:53:55, 0]
> lib/fault.c:fault_report(44)
> Sep 24 11:53:55 juicy winbindd[90765]:
> Sep 24 11:53:55 juicy winbindd[90765]:   From:
> http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
> Sep 24 11:53:55 juicy winbindd[90765]: [2007/09/24 11:53:55, 0]
> lib/fault.c:fault_report(45)
> Sep 24 11:53:55 juicy winbindd[90765]:  
> ===============================================================
> Sep 24 11:53:55 juicy winbindd[90765]: [2007/09/24 11:53:55, 0]
> lib/util.c:smb_panic(1626)
> Sep 24 11:53:55 juicy winbindd[90765]:   smb_panic: clobber_region() last
> called from [smb_probe_module(117)]
> Sep 24 11:53:55 juicy winbindd[90765]: [2007/09/24 11:53:55, 0]
> lib/util.c:smb_panic(1632)
> Sep 24 11:53:55 juicy winbindd[90765]:   PANIC (pid 90765): internal error
> Sep 24 11:53:55 juicy winbindd[90765]: [2007/09/24 11:53:55, 0]
> lib/util.c:log_stack_trace(1786)
> Sep 24 11:53:55 juicy winbindd[90765]:   unable to produce a stack trace on
> this platform
> Sep 24 11:53:55 juicy winbindd[90765]: [2007/09/24 11:53:55, 0]
> lib/util.c:smb_panic(1637)
> Sep 24 11:53:55 juicy winbindd[90765]:   smb_panic(): calling panic action
> [/bin/sleep 999999999]
> Sep 24 11:55:01 juicy winbindd[90763]: [2007/09/24 11:55:01, 0]
> nsswitch/idmap.c:idmap_init(438)
> Sep 24 11:55:01 juicy winbindd[90763]:   ERROR: Initialization failed for
> backend rid (domain default domain), deferred!
> Sep 24 11:55:01 juicy winbindd[90763]: [2007/09/24 11:55:01, 0]
> nsswitch/idmap.c:smb_register_idmap(129)
> Sep 24 11:55:01 juicy winbindd[90763]:   Idmap module rid already registered!
> Sep 24 11:55:01 juicy winbindd[90763]: [2007/09/24 11:55:01, 0]
> lib/module.c:do_smb_load_module(69)
> Sep 24 11:55:01 juicy winbindd[90763]:   Module

What is your bug report exactly about?

As from 3.0.26a port Samba links with the library that allow it to print stacktrace in the log file, which of itself doesn't have much use but pretty.

As for the winbindd bug - you can try to compile Samba with -g flag(or, in 3.0.26a choose MAXIMUM_DEBUG option) and next time it crash you should be able to attach to the dead process and get a more detailed stacktrace there.

To do so you have to identify PID of the sleeping process, run:

gdb /usr/loca/sbin/smbd PID_of_the_process

You'll be attached to it an be able to issue 'bt' command, for example to get stacktrace.