I commented out the [printers] and [print$] statements and smb starts, but when I run smbtree, the following error is displayed: Receiving SMB: Server stopped responding
And the logfile: [2009/02/20 19:29:03, 0] lib/fault.c:fault_report(40) =============================================================== [2009/02/20 19:29:03, 0] lib/fault.c:fault_report(41) INTERNAL ERROR: Signal 11 in pid 25511 (3.3.0) Please read the Trouble-Shooting section of the Samba3-HOWTO [2009/02/20 19:29:03, 0] lib/fault.c:fault_report(43) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2009/02/20 19:29:03, 0] lib/fault.c:fault_report(44) =============================================================== [2009/02/20 19:29:03, 0] lib/util.c:smb_panic(1673) PANIC (pid 25511): internal error [2009/02/20 19:29:03, 0] lib/util.c:log_stack_trace(1777) BACKTRACE: 16 stack frames: #0 /usr/sbin/smbd(log_stack_trace+0x1c) [0x7fc574e185cd] #1 /usr/sbin/smbd(smb_panic+0x5b) [0x7fc574e186db] #2 /usr/sbin/smbd [0x7fc574e05dad] #3 /lib/libpthread.so.0 [0x7fc5733e8080] #4 /usr/sbin/smbd(file_load+0x1e) [0x7fc574e151d5] #5 /usr/sbin/smbd(file_lines_load+0x1b) [0x7fc574e15241] #6 /usr/sbin/smbd [0x7fc574ff71eb] #7 /usr/sbin/smbd [0x7fc574ff7c4c] #8 /usr/sbin/smbd(api_reply+0x3e6) [0x7fc574ff7018] #9 /usr/sbin/smbd [0x7fc574ff2364] #10 /usr/sbin/smbd(reply_trans+0x727) [0x7fc574ff312f] #11 /usr/sbin/smbd [0x7fc574d2dadf] #12 /usr/sbin/smbd(smbd_process+0xdc6) [0x7fc574d2f91d] #13 /usr/sbin/smbd(main+0x20f4) [0x7fc574cfd9a0] #14 /lib/libc.so.6(__libc_start_main+0xe6) [0x7fc57195a5a6] #15 /usr/sbin/smbd [0x7fc574cfad89] [2009/02/20 19:29:03, 0] lib/util.c:smb_panic(1678) smb_panic(): calling panic action [/usr/share/samba/panic-action 25511] [2009/02/20 19:29:03, 0] lib/util.c:smb_panic(1686) smb_panic(): action returned status 0 [2009/02/20 19:29:03, 0] lib/fault.c:dump_core(218) Can not dump core: corepath not set up -- 9.04 Jaunty Samba 2:3.3.0-3ubuntu2 fails to start on update https://bugs.launchpad.net/bugs/330626 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
