Hi, I have a problem with Samba from last week. Our SMB server( Debian Linux 2.2.12, samba 2.0.5a) was working very well since october 99. We didn't do any changes with our SMB server sw or hw configuration. There is my problem: content of samba log file: [2000/01/25 05:52:52, 1] smbd/service.c:make_connection(521) PC1 (10.0.0.42) connect to service database$ as user USER1 (uid=10391, gid=113) (pid 4884) [2000/01/25 05:54:21, 0] lib/fault.c:fault_report(40) ========================================= [2000/01/25 05:54:21, 0] lib/fault.c:fault_report(41) INTERNAL ERROR: Signal 11 in pid 4884 (2.0.5a) Please read the file BUGS.txt in the distribution [2000/01/25 05:54:21, 0] lib/fault.c:fault_report(43) ========================================= [2000/01/25 05:54:21, 0] lib/util.c:smb_panic(2427) PANIC: internal error -- [2000/01/25 06:18:43, 0] locking/locking_shm.c:shm_get_share_modes(241) get_share_modes: file with dev 3001 inode 3466648 empty [2000/01/25 06:18:56, 0] lib/fault.c:fault_report(40) ========================================= security is domain, all lock/oplock is default. Can you help me? Is the problem in hardware or in samba ? With regards Tomas Fulajtar -- Tomas Fulajtar, sprava site MORAVIAPRESS, a.s. Breclav ->Please use pure ASCII or ISO-8859-2 code
John E. Malmberg
2000-Feb-04 14:20 UTC
Plain Text to Mailing List Please - Re: No. 1519 Seeing Around the Corner.htm
"Bob Hillegas" <bhille@gammabio.com> wrote:> This is a multi-part message in MIME format.Please, a MIME is a terrible thing to waste on a Mailing List. It gives the SAMBA DIGEST mode terrible indigestion, and it mails out unreadable HEX dumps to everyone receiving the Digest mode. Please just post a URL for this type of information to be read. The DIGEST mode can not handle VCF, PGP, or RICH-TEXT, or any binary attachments. Please set your mail sending to PLAIN-TEXT only when sending to unknown recipients. Please turn VCF and PGP off unless your recipient explicitly requires them, when not required, they simply waste space in the mail server.> > ------=_NextPart_000_000C_01BF6E25.EB2FFFE0 > Content-Type: text/html; > name="No. 1519 Seeing Around the Corner.htm" > Content-Transfer-Encoding: base64 > Content-Disposition: attachment; > filename="No. 1519 Seeing Around the Corner.htm" > >PEJBU0UgSFJFRj0iaHR0cDovL3d3dy51aC5lZHUvZW5naW5lcy9lcGkxNTE5Lmh0bSI+CjxIVE1M>Pgo8SEVBRD4KPFRJVExFPk5vLiAxNTE5OiBTZWVpbmcgQXJvdW5kIHRoZSBDb3JuZXI8L1RJVExF <Very large Hex Dump snipped>> Date: Thu, 3 Feb 2000 11:00:57 -0600 > From: "Dan Malcolm" <dmalcolm@hiwaay.net> > To: <Rob.Exley@equifax.com> > Cc: <samba@samba.org> > Subject: Re: Problems authenticating against NT PDC > Message-ID: <00d301bf6e68$3e0a9bc0$6f498cd0@gets1000.com> > MIME-Version: 1.0 > Content-Type: multipart/alternative; > boundary="----=_NextPart_000_00D0_01BF6E35.F2FAADA0" > > This is a multi-part message in MIME format. > > ------=_NextPart_000_00D0_01BF6E35.F2FAADA0 > Content-Type: text/html; > charset="Windows-1252" > Content-Transfer-Encoding: quoted-printable > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><Almost Unreadable texified HTML copy of message snipped> Thank you, John wb8tyw@qsl.net
> Samba however is consistently slower than both, and its "write" time is much > slower, and quite inconsistent. I was hoping Samba/FreeBSD would be at least > as fast as the NetWare box (which I'm considering replacing w/ the Samba > Box), given that it's running on faster processor w/ more ram.I have the same experience on my P3/500 server with RH6.1 on a 100Mbit network. Samba was very slow at writing from a Win98 client, no matter what I tuned. Reading was 7MB/s, that is fine, writing was varying from 5 to 2 MB/s and that is too slow for me (and my boss). But I got this writing speed for every of simultaneous connections on one client, up to the 100Mbit bandwith. So it is definitely not a Linux's problem. FTP was both writing and reading 8MB/s, and what is interesting: so was Samba to Samba ! So I think there could be a problem how Samba handles the Win98 Microsoft's implementation of SMB. Well, it's really hard to persuade your boss to install Linux&Samba, when it's 60% slower than NT. I had to install (hopefully) temporarily W2K on that server and I'll wait for faster Samba ;-), coz W2K and NT is a PAIN (slow software RAID5, no good free backuping software, no low bandwith remote control, huge memory requirements etc etc.) Yours sincerely Petr Sulla
Hello, we got the following error in the samba logs: Oct 30 06:29:01 hornbill smbd[12783]: [2002/10/30 06:29:01, 0] lib/fault.c:fault_report(38) Oct 30 06:29:01 hornbill smbd[12783]: =============================================================== Oct 30 06:29:01 hornbill smbd[12783]: [2002/10/30 06:29:01, 0] lib/fault.c:fault_report(39) Oct 30 06:29:01 hornbill smbd[12783]: INTERNAL ERROR: Signal 11 in pid 12783 (2.2.6-SuSE) Oct 30 06:29:01 hornbill smbd[12783]: Please read the file BUGS.txt in the distribution Oct 30 06:29:01 hornbill smbd[12783]: [2002/10/30 06:29:01, 0] lib/fault.c:fault_report(41) Oct 30 06:29:01 hornbill smbd[12783]: =============================================================== Oct 30 06:29:01 hornbill smbd[12783]: [2002/10/30 06:29:01, 0] lib/util.c:smb_panic(1094) Oct 30 06:29:01 hornbill smbd[12783]: PANIC: internal error Oct 30 06:29:01 hornbill smbd[12783]: The error is continuously repeated with increased pids until the machine will be rebooted. Restart of smbd, nmbd and winbind has no effect. Clients can connect to samba but they cannot access files. File access on NT clients is aborted with different messages. Samba version is 2.2.6 (Suse RPM) and linux kernel is 2.4.19, but it already happened with 2.2.4 and kernel 2.4.16. I cannot reproduce the error, but it happens once in a week. I found similar errors discussed in the list archives but no explanation or solution. Can anybody help. Thanks Gerhard
On Wed, Oct 30, 2002 at 11:35:42AM +0000, Gerhard V?gel wrote:> Hello, > > we got the following error in the samba logs: > > Oct 30 06:29:01 hornbill smbd[12783]: [2002/10/30 06:29:01, 0] > lib/fault.c:fault_report(38) > Oct 30 06:29:01 hornbill smbd[12783]: > =============================================================== > Oct 30 06:29:01 hornbill smbd[12783]: [2002/10/30 06:29:01, 0] > lib/fault.c:fault_report(39) > Oct 30 06:29:01 hornbill smbd[12783]: INTERNAL ERROR: Signal 11 in pid > 12783 (2.2.6-SuSE) > Oct 30 06:29:01 hornbill smbd[12783]: Please read the file BUGS.txt in > the distribution > Oct 30 06:29:01 hornbill smbd[12783]: [2002/10/30 06:29:01, 0] > lib/fault.c:fault_report(41) > Oct 30 06:29:01 hornbill smbd[12783]: > =============================================================== > Oct 30 06:29:01 hornbill smbd[12783]: [2002/10/30 06:29:01, 0] > lib/util.c:smb_panic(1094) > Oct 30 06:29:01 hornbill smbd[12783]: PANIC: internal error > Oct 30 06:29:01 hornbill smbd[12783]: > > The error is continuously repeated with increased pids until the machine > will be rebooted. Restart of smbd, nmbd and winbind has no effect. > > Clients can connect to samba but they cannot access files. File access on > NT clients is aborted with different messages. > > Samba version is 2.2.6 (Suse RPM) and linux kernel is 2.4.19, but it > already happened with 2.2.4 and kernel 2.4.16. I cannot reproduce the > error, but it happens once in a week.Can you add the following to the smb.conf file : In the [global] section add : panic action = /bin/sleep 99999 and then when this occurs attach to the frozen smbd process with gdb. Once attached, type "bt" (backtrace) at the gdb prompt and then mail in the backtrace. Please ensure smbd is built with symbols. This will help us track down and fix the bug. Thanks, Jeremy.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 30 Oct 2002 jra@dp.samba.org wrote:> On Wed, Oct 30, 2002 at 11:35:42AM +0000, Gerhard V?gel wrote: > > Hello, > > > > we got the following error in the samba logs: > > > > Oct 30 06:29:01 hornbill smbd[12783]: [2002/10/30 06:29:01, 0] > > lib/fault.c:fault_report(38) > > Oct 30 06:29:01 hornbill smbd[12783]: > > =============================================================== > > Oct 30 06:29:01 hornbill smbd[12783]: [2002/10/30 06:29:01, 0] > > lib/fault.c:fault_report(39) > > Oct 30 06:29:01 hornbill smbd[12783]: INTERNAL ERROR: Signal 11 in pid > > 12783 (2.2.6-SuSE)Suggest you contact SuSE first to see if there is a bug in their RPM. They patched 2.2.6 IIRC with some new acl code. cheers, jerry> panic action = /bin/sleep 99999cheers, jerry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE9wV8RIR7qMdg1EfYRAo61AJ9bnfnnxOAhMbdXTIRROsdli75q9ACfQuhM cBgN3vSqsWN9HJ7wsH4Bgag=cB1e -----END PGP SIGNATURE-----
Am 30.10.02, 17:56:54, schrieb jra@dp.samba.org zum Thema Re: [Samba] internal error: signal 11:> On Wed, Oct 30, 2002 at 11:35:42AM +0000, Gerhard V?gel wrote: > > Hello, > > > > we got the following error in the samba logs: > > > > Oct 30 06:29:01 hornbill smbd[12783]: [2002/10/30 06:29:01, 0] > > lib/fault.c:fault_report(38) > > Oct 30 06:29:01 hornbill smbd[12783]: > > ==============================================================> > Oct 30 06:29:01 hornbill smbd[12783]: [2002/10/30 06:29:01, 0] > > lib/fault.c:fault_report(39) > > Oct 30 06:29:01 hornbill smbd[12783]: INTERNAL ERROR: Signal 11 in pid > > 12783 (2.2.6-SuSE) > > Oct 30 06:29:01 hornbill smbd[12783]: Please read the file BUGS.txt in > > the distribution > > Oct 30 06:29:01 hornbill smbd[12783]: [2002/10/30 06:29:01, 0] > > lib/fault.c:fault_report(41) > > Oct 30 06:29:01 hornbill smbd[12783]: > > ==============================================================> > Oct 30 06:29:01 hornbill smbd[12783]: [2002/10/30 06:29:01, 0] > > lib/util.c:smb_panic(1094) > > Oct 30 06:29:01 hornbill smbd[12783]: PANIC: internal error > > Oct 30 06:29:01 hornbill smbd[12783]: > > > > The error is continuously repeated with increased pids until the machine > > will be rebooted. Restart of smbd, nmbd and winbind has no effect. > > > > Clients can connect to samba but they cannot access files. File access on > > NT clients is aborted with different messages. > > > > Samba version is 2.2.6 (Suse RPM) and linux kernel is 2.4.19, but it > > already happened with 2.2.4 and kernel 2.4.16. I cannot reproduce the > > error, but it happens once in a week.> Can you add the following to the smb.conf file : > In the [global] section add :> panic action = /bin/sleep 99999> and then when this occurs attach to the frozen smbd process > with gdb. Once attached, type "bt" (backtrace) at the gdb > prompt and then mail in the backtrace. Please ensure smbd is > built with symbols.> This will help us track down and fix the bug.Today the signal 11 error occured again an I could take a backtrace. The log showed following lines: Nov 24 10:20:05 hornbill smbd[29296]: [2002/11/24 10:20:05, 0] lib/fault.c:fault_report(38) Nov 24 10:20:05 hornbill smbd[29296]: =============================================================== Nov 24 10:20:05 hornbill smbd[29296]: [2002/11/24 10:20:05, 0] lib/fault.c:fault_report(39) Nov 24 10:20:05 hornbill smbd[29296]: INTERNAL ERROR: Signal 11 in pid 29296 (2.2.6-SuSE) Nov 24 10:20:05 hornbill smbd[29296]: Please read the file BUGS.txt in the distribution Nov 24 10:20:05 hornbill smbd[29296]: [2002/11/24 10:20:05, 0] lib/fault.c:fault_report(41) Nov 24 10:20:05 hornbill smbd[29296]: =============================================================== Nov 24 10:21:15 hornbill smbd[29299]: [2002/11/24 10:21:15, 0] lib/fault.c:fault_report(38) Nov 24 10:21:15 hornbill smbd[29299]: =============================================================== Nov 24 10:21:15 hornbill smbd[29299]: [2002/11/24 10:21:15, 0] lib/fault.c:fault_report(39) Nov 24 10:21:15 hornbill smbd[29299]: INTERNAL ERROR: Signal 11 in pid 29299 (2.2.6-SuSE) Nov 24 10:21:15 hornbill smbd[29299]: Please read the file BUGS.txt in the distribution Nov 24 10:21:15 hornbill smbd[29299]: [2002/11/24 10:21:15, 0] lib/fault.c:fault_report(41) Nov 24 10:21:15 hornbill smbd[29299]: =============================================================== Nov 24 10:22:25 hornbill smbd[29301]: [2002/11/24 10:22:25, 0] lib/fault.c:fault_report(38) Nov 24 10:22:25 hornbill smbd[29301]: =============================================================== Nov 24 10:22:25 hornbill smbd[29301]: [2002/11/24 10:22:25, 0] lib/fault.c:fault_report(39) Nov 24 10:22:25 hornbill smbd[29301]: INTERNAL ERROR: Signal 11 in pid 29301 (2.2.6-SuSE) Nov 24 10:22:25 hornbill smbd[29301]: Please read the file BUGS.txt in the distribution Nov 24 10:22:25 hornbill smbd[29301]: [2002/11/24 10:22:25, 0] lib/fault.c:fault_report(41) Nov 24 10:22:25 hornbill smbd[29301]: =============================================================== Backtraces of all 3 pids were identical. hornbill:~ # gdb /usr/lib/samba/classic/smbd 29296 GNU gdb 5.0 Copyright 2000 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-suse-linux"...(no debugging symbols found)... /root/29296: No such file or directory. Attaching to program: /usr/lib/samba/classic/smbd, Pid 29296 Reading symbols from /lib/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /lib/libnsl.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libnsl.so.1 Reading symbols from /lib/libpam.so.0...(no debugging symbols found)...done. Loaded symbols for /lib/libpam.so.0 Reading symbols from /usr/lib/libpopt.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libpopt.so.0 Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /lib/ld-linux.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /lib/libnss_files.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libnss_files.so.2 Reading symbols from /lib/libnss_dns.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libnss_dns.so.2 Reading symbols from /lib/libresolv.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libresolv.so.2 0x400f1299 in wait4 () from /lib/libc.so.6 (gdb) bt full #0 0x400f1299 in wait4 () from /lib/libc.so.6 No symbol table info available. #1 0x4015f2e8 in __DTOR_END__ () from /lib/libc.so.6 No symbol table info available. #2 0x40092016 in system () from /lib/libc.so.6 No symbol table info available. #3 0x8146cad in smb_panic () No symbol table info available. #4 0x8134a63 in fault_report () No symbol table info available. #5 0x8134ac2 in sig_fault () No symbol table info available. #6 <signal handler called> No symbol table info available. #7 0x400b6b19 in fgets_unlocked () from /lib/libc.so.6 No symbol table info available. #8 0x40115e11 in getmntent_r () from /lib/libc.so.6 No symbol table info available. #9 0x40115d55 in getmntent () from /lib/libc.so.6 No symbol table info available. #10 0x815d85f in disk_quotas () No symbol table info available. #11 0x806ea2f in disk_free () No symbol table info available. #12 0x806ec52 in sys_disk_free () No symbol table info available. #13 0x809f334 in vfswrap_disk_free () No symbol table info available. #14 0x8092561 in call_trans2qfsinfo () No symbol table info available. #15 0x8096f99 in reply_trans2 () No symbol table info available. #16 0x80a5f9f in switch_message () No symbol table info available. #17 0x80a6040 in construct_reply () No symbol table info available. #18 0x80a629e in process_smb () No symbol table info available. #19 0x80a6c8c in smbd_process () No symbol table info available. #20 0x806ad58 in main () No symbol table info available. #21 0x40064c5f in __libc_start_main () from /lib/libc.so.6 No symbol table info available. (gdb) quit Thank you Gerhard
Hello everybody, I just installed a samba-3.0.1 from sources, and I have an INTERNAL ERROR when I launch smbd, nmbd or even swat (from inetd) to try to configure something. I use a slackware 9.1 with glibc-2.3.2 The glibc seems to be the problem, because when I jump back on a 2.3.1, I can launch swat without this "bug". Can someone help me to fix that ? Thanks. Here is a "screeshot" of /var/samba/log.swat, I know, 4:14 am is not a good time to make samba works correctly ;) ==============================================================[2003/12/17 04:14:51, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 11 in pid 4626 (3.0.1) Please read the appendix Bugs of the Samba HOWTO collection [2003/12/17 04:14:51, 0] lib/fault.c:fault_report(39) ==============================================================[2003/12/17 04:14:51, 0] lib/util.c:smb_panic(1400) PANIC: internal error [2003/12/17 04:14:51, 0] lib/util.c:smb_panic(1408) BACKTRACE: 25 stack frames: #0 swat(smb_panic+0x181) [0x80b962d] #1 swat [0x80a9f4e] #2 swat [0x80a9f97] #3 /lib/libc.so.6 [0x400a4988] #4 /lib/libc.so.6 [0x40091f24] #5 /lib/libc.so.6(iconv+0x132) [0x40091602] #6 swat [0x80c3b8a] #7 swat(smb_iconv+0x36) [0x80c3bcc] #8 swat [0x80a7d01] #9 swat(convert_string+0x14b) [0x80a8011] #10 swat [0x80b5605] #11 swat(init_doschar_table+0x29) [0x80b5653] #12 swat(init_iconv+0x1a2) [0x80a7c07] #13 swat(lazy_initialize_conv+0x23) [0x80a7a61] #14 swat(convert_string_allocate+0x5e) [0x80a809d] #15 swat(push_ucs2_allocate+0x30) [0x80a8ab5] #16 swat(unix_strupper+0x19) [0x80a8533] #17 swat(strupper_m+0x60) [0x80b3738] #18 swat(set_global_myname+0x56) [0x80b7646] #19 swat [0x806405c] #20 swat(lp_load+0xa5) [0x806a00e] #21 swat [0x8061818] #22 swat(main+0xf1) [0x8063887] #23 /lib/libc.so.6(__libc_start_main+0xc6) [0x40090d06] #24 swat(chroot+0x31) [0x805ee11]
On Wed, Dec 17, 2003 at 04:29:26AM +0100, togusa at free.fr wrote:> Hello everybody, > [...] > Here is a "screeshot" of /var/samba/log.swat, I know, 4:14 am is not a good time > to make samba works correctly ;) > > ==============================================================> [2003/12/17 04:14:51, 0] lib/fault.c:fault_report(37) > INTERNAL ERROR: Signal 11 in pid 4626 (3.0.1) > Please read the appendix Bugs of the Samba HOWTO collection > [2003/12/17 04:14:51, 0] lib/fault.c:fault_report(39) > ==============================================================> ... (stuff deleted)Hi! Did you already get any response to your posting? If so, please let me know, as your problem description fits exactly to mine... (if not - I'm in the mailing list now, so don't bother, I should get it anyway) Thanks -- Regards amrito ------------------------------- DI Johann Divisch Sysadmin ADV TU Wien A-1040 Wien, Karlsplatz 13 ------------------------------- Tel: (01) 58801-41079 Fax: (01) 58801-41098 ------------------------------- email: jdivisch@zv.tuwien.ac.at -------------------------------