On Mon, Feb 02, 2004 at 12:22:31PM +0100, Collen wrote: > Well got a problem i gues... > > i got even more error's in my log files.. > some about schannel processing error, or no route to host or get peer > name... > still everything looks to be working fine.. (got no complaints from > the users) > but these internal error's i get a fewtimes aday.. > dunno, do i need to make a bugreport for it ? > or do you need some extra debug info.. > > l8r > Collen > #--------------------------------------------------------------------- > [2004/01/30 11:10:34, 0] lib/fault.c:fault_report(37) > INTERNAL ERROR: Signal 11 in pid 15118 (3.0.2rc1) > Please read the appendix Bugs of the Samba HOWTO collection > [2004/01/30 11:10:34, 0] lib/fault.c:fault_report(39) > =============================================================== > [2004/01/30 11:10:34, 0] lib/util.c:smb_panic(1400) > PANIC: internal error > [2004/01/30 11:10:34, 0] lib/util.c:smb_panic(1408) > BACKTRACE: 17 stack frames: > #0 smbd(smb_panic+0x181) [0x818a994] > #1 smbd [0x817b5ce] > #2 smbd [0x817b617] > #3 /lib/libc.so.6 [0x401734f8] > #4 /lib/libc.so.6(__libc_free+0x7c) [0x401bdfbc] > #5 smbd(talloc_destroy_pool+0x26) [0x818eebd] > #6 smbd(talloc_destroy+0x17) [0x818ef0c] > #7 smbd(conn_free+0x1a2) [0x808646f] > #8 smbd(close_cnum+0x22c) [0x80c04fc] > #9 smbd(reply_tdis+0xa4) [0x809cbdb] > #10 smbd [0x80bce0c] > #11 smbd [0x80bce96] > #12 smbd(process_smb+0x1b9) [0x80bd191] > #13 smbd(smbd_process+0x153) [0x80bdbec] > #14 smbd(main+0x6ec) [0x81e3e5b] > #15 /lib/libc.so.6(__libc_start_main+0xc7) [0x40160917] > #16 smbd(chroot+0x31) [0x8076d21]
This is a corrupted malloc pool. If you have a malloc with checking ability (such as the GNU one) you could try running for a while with the environment variable MALLOC_CHECK_=2. This will make Samba a little slower but will help track down the memory problem. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
