Execution of analog web log tool causes Samba to crash - likely due to heavy load on name servers leading to timeout. Nov 2 10:55:51 fs2 smbd[27271]: [2006/11/02 10:55:51, 0] lib/fault.c:fault_report(36) Nov 2 10:55:51 fs2 smbd[27271]: =============================================================== Nov 2 10:55:51 fs2 smbd[27271]: [2006/11/02 10:55:51, 0] lib/fault.c:fault_report(37) Nov 2 10:55:51 fs2 smbd[27271]: INTERNAL ERROR: Signal 11 in pid 27271 (3.0.22-13.18-SUSE-CODE10) Nov 2 10:55:51 fs2 smbd[27271]: Please read the Trouble-Shooting section of the Samba3-HOWTO Nov 2 10:55:51 fs2 smbd[27271]: [2006/11/02 10:55:51, 0] lib/fault.c:fault_report(39) Nov 2 10:55:51 fs2 smbd[27271]: Nov 2 10:55:51 fs2 smbd[27271]: From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf Nov 2 10:55:51 fs2 smbd[27271]: [2006/11/02 10:55:51, 0] lib/fault.c:fault_report(40) Nov 2 10:55:51 fs2 smbd[27271]: =============================================================== Nov 2 10:55:51 fs2 smbd[27271]: [2006/11/02 10:55:51, 0] lib/util.c:smb_panic2(1554) Nov 2 10:55:51 fs2 smbd[27271]: PANIC: internal error Nov 2 10:55:51 fs2 smbd[27271]: [2006/11/02 10:55:51, 0] lib/util.c:smb_panic2(1562) Nov 2 10:55:51 fs2 smbd[27271]: BACKTRACE: 20 stack frames: Nov 2 10:55:51 fs2 smbd[27271]: #0 /usr/sbin/smbd(smb_panic2+0x8a) [0x801fa17a] Nov 2 10:55:51 fs2 smbd[27271]: #1 /usr/sbin/smbd(smb_panic+0x19) [0x801fa3d9] Nov 2 10:55:51 fs2 smbd[27271]: #2 /usr/sbin/smbd [0x801e4732] Nov 2 10:55:51 fs2 smbd[27271]: #3 [0xffffe420] Nov 2 10:55:51 fs2 smbd[27271]: #4 /lib/libc.so.6 [0xb7bc25bd] Nov 2 10:55:51 fs2 smbd[27271]: #5 /lib/libc.so.6 [0xb7bc2ca3] Nov 2 10:55:51 fs2 smbd[27271]: #6 /lib/libc.so.6(gethostbyname_r+0x18d) [0xb7ba966d] Nov 2 10:55:51 fs2 smbd[27271]: #7 /lib/libc.so.6(gethostbyname+0xe0) [0xb7ba8f30] Nov 2 10:55:51 fs2 smbd[27271]: #8 /usr/lib/libcups.so.2(httpGetHostByName+0x45) [0xb7dd1545] Nov 2 10:55:51 fs2 smbd[27271]: #9 /usr/lib/libcups.so.2(httpConnectEncrypt+0x31) [0xb7dd1351] Nov 2 10:55:51 fs2 smbd[27271]: #10 /usr/lib/libcups.so.2(httpConnect+0x36) [0xb7dd14f6] Nov 2 10:55:51 fs2 smbd[27271]: #11 /usr/sbin/smbd(cups_cache_reload+0x4b) [0x801d9ffb] Nov 2 10:55:51 fs2 smbd[27271]: #12 /usr/sbin/smbd(pcap_cache_reload+0xff) [0x801d809f] Nov 2 10:55:51 fs2 smbd[27271]: #13 /usr/sbin/smbd(reload_printers+0x31) [0x802994f1] Nov 2 10:55:51 fs2 smbd[27271]: #14 /usr/sbin/smbd(check_reload+0xc3) [0x800acd53] Nov 2 10:55:52 fs2 smbd[27271]: #15 /usr/sbin/smbd [0x800ace7a] Nov 2 10:55:52 fs2 smbd[27271]: #16 /usr/sbin/smbd(smbd_process+0xd9) [0x800ae1f9] Nov 2 10:55:52 fs2 smbd[27271]: #17 /usr/sbin/smbd(main+0x7e5) [0x8029ac85] Nov 2 10:55:52 fs2 smbd[27271]: #18 /lib/libc.so.6(__libc_start_main+0xdc) [0xb7aec87c] Nov 2 10:55:52 fs2 smbd[27271]: #19 /usr/sbin/smbd [0x8003ed51]
nmbd was not the right component as the crash was in smbd. This is almost 20 years old I haven't seen this crash. I assume it's not an issue anymore, otherwise, open a new bug report with a reproducer please.
It looks like CUPS's cupsServer() was returning NULL, which probably changed to a panic in smb_xstrdup() with commit 17ed5d07f4fbae8c4a9e1f171a36b7978f653769 Author: Jelmer Vernooij <jelmer@samba.org> Date: Thu Aug 24 22:10:59 2006 +0000 r17816: Merge my cupsprot branch. It is now possible to (optionally) specify :port in the "cups server" smb.conf parameter. (This used to be commit 3f665f4ec4cda80cc20e050458e150c086dc1412) and into a proper failure with commit 3bfb53caa86ece1d7ff1bf3c7759f003203d4247 Author: Jeremy Allison <jra@samba.org> Date: Wed Oct 1 16:40:41 2008 -0700 Fix bug #5080. Access to cups-printers via samba broken with cups 1.3.4, Unsupported character set. Cups 1.3.4 expects utf8 to be used in all messages to/from the server. We may be using a different character set so we need to use talloc utf8 push/pull functions in all communication. Needs more testing. Don't release until I've done a thorough test. I also have a version for 3.2.x. Jeremy. (not that I should even be looking at this).