Re: [Samba] INTERNAL ERROR: Signal 11 - winbindd 3.4.2
here the output of gdb --core=/var/log/samba/cores/winbindd/core: GNU gdb 6.6 Copyright (C) 2006 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 x86_64-suse-linux. Core was generated by `/usr/sbin/winbindd -s /var/lib/samba/winbindd/winbindd.conf'. Program terminated with signal 6, Aborted. #0 0x2b03a803dbb5 in ?? () (gdb) backtrace #0 0x2b03a803dbb5 in ?? () #1 0x2b03a803efb0 in ?? () #2 0x7fff03b11750 in ?? () #3 0x2b03a6fb1000 in ?? () #4 0x555a9255 in ?? () #5 0x010055d7dd90 in ?? () #6 0x55d7ddf4 in ?? () #7 0x55d7dd90 in ?? () #8 0x55d7ddf4 in ?? () #9 0x in ?? () (gdb) backtrace full #0 0x2b03a803dbb5 in ?? () No symbol table info available. #1 0x2b03a803efb0 in ?? () No symbol table info available. #2 0x7fff03b11750 in ?? () No symbol table info available. #3 0x2b03a6fb1000 in ?? () No symbol table info available. #4 0x555a9255 in ?? () No symbol table info available. #5 0x010055d7dd90 in ?? () No symbol table info available. #6 0x55d7ddf4 in ?? () No symbol table info available. #7 0x55d7dd90 in ?? () No symbol table info available. #8 0x55d7ddf4 in ?? () No symbol table info available. #9 0x in ?? () No symbol table info available. Does it help somebody? Best Alex Alexander Födisch schrieb: Hi, winbindd (v 3.4.2) crashed last night and in the winbind-log I found following output: [2009/10/14 22:41:13, 0] lib/fault.c:41(fault_report) === [2009/10/14 22:41:13, 0] lib/fault.c:42(fault_report) INTERNAL ERROR: Signal 11 in pid 1472 (3.4.2) Please read the Trouble-Shooting section of the Samba3-HOWTO [2009/10/14 22:41:13, 0] lib/fault.c:44(fault_report) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2009/10/14 22:41:13, 0] lib/fault.c:45(fault_report) === [2009/10/14 22:41:13, 0] lib/util.c:1480(smb_panic) PANIC (pid 1472): internal error [2009/10/14 22:41:13, 0] lib/util.c:1584(log_stack_trace) BACKTRACE: 17 stack frames: #0 /usr/sbin/winbindd(log_stack_trace+0x1a) [0x5569ad4c] #1 /usr/sbin/winbindd(smb_panic+0x55) [0x5569ae50] #2 /usr/sbin/winbindd [0x5568be1d] #3 /lib64/libc.so.6 [0x2b03a803dc30] #4 /usr/sbin/winbindd [0x5560e8d8] #5 /usr/sbin/winbindd [0x55610e15] #6 /usr/sbin/winbindd [0x555f93ff] #7 /usr/sbin/winbindd [0x555ebc41] #8 /usr/sbin/winbindd [0x555ececd] #9 /usr/sbin/winbindd [0x555ed844] #10 /usr/sbin/winbindd [0x55620c5c] #11 /usr/sbin/winbindd [0x5561abc6] #12 /usr/sbin/winbindd [0x55619f7e] #13 /usr/sbin/winbindd [0x555e6a6c] #14 /usr/sbin/winbindd(main+0xf17) [0x555e7d6d] #15 /lib64/libc.so.6(__libc_start_main+0xf4) [0x2b03a802b184] #16 /usr/sbin/winbindd [0x555e51d9] [2009/10/14 22:41:13, 0] lib/fault.c:321(dump_core) dumping core in /var/log/samba/cores/winbindd I'm using the packages from Sernet on a SLES 10 system. Any ideas? Thanks! Alex smime.p7s Description: S/MIME Cryptographic Signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] INTERNAL ERROR: Signal 11 - winbindd 3.4.2
On Thu, Oct 15, 2009 at 09:35:50AM +0200, Alexander Födisch wrote: here the output of gdb --core=/var/log/samba/cores/winbindd/core: Please install debugging symbols (compile with -g). This gives much more info. Volker signature.asc Description: Digital signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Internal Error Signal 11 (Samba 3.2.3)
On Mon, Mar 23, 2009 at 09:17:54PM +0200, Petteri Heinonen wrote: Hello list users. In my journey to world of Linux/Windows interoperability, I have now almost reached my goal to successfully authenticate Linux users using Windows Server 2003 SP2. The (hopefully) last obstacle is that wbinfo -i username causes the following error to be produced in log.wb-DOMAIN file (consequently, logins are failing also of course). Samba version is 3.2.3. Used config and log file below. Any help would be much appreciated. With some help, I guess I should also be able to use gdb to further study the coredump, if that's what is needed. It might be possible that this was fixed after 3.2.3 with http://git.samba.org/?p=samba.git;a=commitdiff;h=2ec8e5ed87c826 Please upgrade to 3.2.8. Thanks, Volker pgpOudcoDN7Bx.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] INTERNAL ERROR: Signal 11 in pid xxxx (3.0.26a)
Marcin Kucharczyk wrote: DV You should be able to delete /var/db/samba (plus maybe the pid file) and DV restart samba. Samba will create any tdb files it needs like the DV initial startup. Tried ... reinstall was required Some mor information: It looks like the same or similar problem: http://lists.samba.org/archive/samba/2007-August/134620.html My system works with ayhlion 64 x2, but I had similar problem on single processor configuration: pentium 4 and duron too. The problem apears not only after power failure, but also after samba upgrade from ports - make deinstall reinstall. /var/db/samba need to be deleted before reinstall becase samba 3.0.26a has the problem with start with tdb files form 3.0.23c. Better file a bug report then. https://bugzilla.samba.org/enter_bug.cgi Regards, Doug -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] INTERNAL ERROR: Signal 11 in pid xxxx (3.0.26a)
On Sun, Nov 25, 2007 at 05:29:52AM -0800, Doug VanLeuven wrote: Marcin Kucharczyk wrote: DV You should be able to delete /var/db/samba (plus maybe the pid file) and DV restart samba. Samba will create any tdb files it needs like the DV initial startup. Tried ... reinstall was required Some mor information: It looks like the same or similar problem: http://lists.samba.org/archive/samba/2007-August/134620.html This particular bug report is highly unlikely to be a Samba problem. Also, I have a hard time to believe that you have to really deinstall Samba after a system crash. It *is* definitely possible to restart Samba from whatever state the system is in, possibly by removing tdb files. Removing and recompiling the daemons is definitely unnecessary. You might want to see what this removing/reinstalling really does. Volker pgpUHOVqv12lL.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] INTERNAL ERROR: Signal 11 in pid xxxx (3.0.26a)
[EMAIL PROTECTED] wrote: Hello, I have a problem with samba 3.0.26a (from ports) on FreeBSD (amd64, SMP, 6.2 RELEASE). My log.smbd looks like below: --- samba starts normally: [2007/11/24 16:55:22, 0] smbd/server.c:main(944) smbd version 3.0.26a started. Copyright Andrew Tridgell and the Samba Team 1992-2007 --- but an error is reported: [2007/11/24 16:55:22, 0] /usr/ports/net/samba3/work/samba-3.0.26a/source/lib/pidfile.c:pidfile_create(112) ERROR: smbd is already running. File /var/run/smbd.pid exists and process id 1961 is running. --- /var/run/smbd.pid exists, becase the error is created after unexpected system shutdown... What os the unexpected system shutdown? Power failure? Reset button after system freeze? --- next I can see in log.smbd: [2007/11/24 16:59:53, 0] lib/util_tdb.c:tdb_log(662) tdb(/var/db/samba/gencache.tdb): tdb_reopen: open failed (No such file or directory) [2007/11/24 16:59:53, 0] smbd/server.c:open_sockets_smbd(572) tdb_reopen_all failed. [2007/11/24 16:59:53, 0] lib/util.c:smb_panic(1632) PANIC (pid 2621): tdb_reopen_all failed. [2007/11/24 16:59:53, 0] lib/fault.c:fault_report(41) The filesystem didn't flush it's buffers on shutdown. Unexpectedly, files are missing and/or corrupted that should be there on startup. === [2007/11/24 16:59:53, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 2621 (3.0.26a) Please read the Trouble-Shooting section of the Samba3-HOWTO [2007/11/24 16:59:53, 0] lib/fault.c:fault_report(44) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2007/11/24 16:59:53, 0] lib/fault.c:fault_report(45) === [2007/11/24 16:59:53, 0] lib/util.c:smb_panic(1632) PANIC (pid 2621): internal error [2007/11/24 16:59:53, 0] lib/util_tdb.c:tdb_log(662) tdb(/var/db/samba/gencache.tdb): tdb_reopen: open failed (No such file or directory) [2007/11/24 16:59:53, 0] smbd/server.c:open_sockets_smbd(572) tdb_reopen_all failed. [2007/11/24 16:59:53, 0] lib/util.c:smb_panic(1632) PANIC (pid 2622): tdb_reopen_all failed. [2007/11/24 16:59:53, 0] lib/fault.c:fault_report(41) === [2007/11/24 16:59:53, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 2622 (3.0.26a) Please read the Trouble-Shooting section of the Samba3-HOWTO [2007/11/24 16:59:53, 0] lib/fault.c:fault_report(44) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2007/11/24 16:59:53, 0] lib/fault.c:fault_report(45) --- the error is repeated about 100 times ... and it is still repeated. Next I can see in the top a lot of run smbd processes. System load grows and smbd makes it unresponsible. Connection with ssh is impossible, I can only use (with problems) console. Command killall -9 smbd helps, system goes back to normal work. I can run samba again but I must use the following procedure: - cd /usr/ports/net/samba3 - make deinstall Samba is now deinstalled. Next I must delete the directory /var/db/samba an I can do: - make reinstall And after start samba works properly until next unexpected system restart :( You need to fix this and ensure you're using a journaled file system with whatever option is available for the safest, most conservative journaling mode. If I do only: - make deinstall reinstall Without deleting /var/db/samba, than the samba will start and procedure described on the start of this message will be repeated :( You should be able to delete /var/db/samba (plus maybe the pid file) and restart samba. Samba will create any tdb files it needs like the initial startup. It is problem with FreeBSD on amd64? Or the problem with samba 3.0.26a? I reverted to samba 3.0.24 to check if the problem back... Regards, Doug -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] INTERNAL ERROR: Signal 11 in pid 8928 (3.0.23c)
Removing mdns did indeed fix the problem. Thanks a lot Jerry Em Segunda 18 Setembro 2006 15:09, Gerald (Jerry) Carter escreveu: Diego Alencar Alves de Lima wrote: smbd version 3.0.22 started. Copyright Andrew Tridgell and the Samba Team 1992-2006 === INTERNAL ERROR: Signal 11 in pid 15675 (3.0.22) Please read the Trouble-Shooting section of the Samba3-HOWTO From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf === PANIC: internal error BACKTRACE: 36 stack frames: #0 smbd(smb_panic2+0x78) [0x81ffea8] #1 smbd(smb_panic+0x19) [0x82000a5] #2 smbd [0x81ee1b5] #3 [0xe420] #4 /usr/lib/libnss_mdns.so.2 [0xb78e3728] #5 /usr/lib/libnss_mdns.so.2 [0xb78e39cd] #6 /usr/lib/libnss_mdns.so.2(mdns_query_ipv4+0x99) [0xb78e3ab0] #7 /usr/lib/libnss_mdns.so.2(_nss_mdns_gethostbyaddr_r+0x18a) [0xb78e5d72] This is a bug in the MDNS library from what I remember. Remove mdns from hosts in /etc/nsswitch.conf cheers, jerry = Samba--- http://www.samba.org Centeris --- http://www.centeris.com What man is a man who does not make the world better? --Balian -- Diego Lima http://sg.homelinux.com:81 pgpEBwFKVxbfg.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] INTERNAL ERROR: Signal 11 in pid 8928 (3.0.23c)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Diego Alencar Alves de Lima wrote: smbd version 3.0.22 started. Copyright Andrew Tridgell and the Samba Team 1992-2006 === INTERNAL ERROR: Signal 11 in pid 15675 (3.0.22) Please read the Trouble-Shooting section of the Samba3-HOWTO From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf === PANIC: internal error BACKTRACE: 36 stack frames: #0 smbd(smb_panic2+0x78) [0x81ffea8] #1 smbd(smb_panic+0x19) [0x82000a5] #2 smbd [0x81ee1b5] #3 [0xe420] #4 /usr/lib/libnss_mdns.so.2 [0xb78e3728] #5 /usr/lib/libnss_mdns.so.2 [0xb78e39cd] #6 /usr/lib/libnss_mdns.so.2(mdns_query_ipv4+0x99) [0xb78e3ab0] #7 /usr/lib/libnss_mdns.so.2(_nss_mdns_gethostbyaddr_r+0x18a) [0xb78e5d72] This is a bug in the MDNS library from what I remember. Remove mdns from hosts in /etc/nsswitch.conf cheers, jerry = Samba--- http://www.samba.org Centeris --- http://www.centeris.com What man is a man who does not make the world better? --Balian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFFDuDgIR7qMdg1EfYRAlNSAKDl+D3iJmedQckkESAzmYUqFbrLbgCeIo// Ya3MJVhafmL/9AmUjEAnb30= =L/p+ -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] INTERNAL ERROR: Signal 11 in pid 8928 (3.0.23c)
On Sat, Sep 16, 2006 at 02:25:47PM -0700, Nolan Garrett wrote: Hello! It seems my struggle with Samba isn't quite over. My latest problem is exactly what you see above, followed by an attempt to core dump. This occurs upon authentication to the system. My system is part of a W2K3 domain. I looked at the Samba HOWTO, but apparently I have a system (FC5), that doesn't allow core dumps when the PID changes, since no core dumps are being created. Also, smbstatus doesn't give me a PID, so I am having a hard time running gdb to further understand this issue. Here is the log output: [2006/09/16 14:19:11, 0] lib/fault.c:fault_report(41) === [2006/09/16 14:19:11, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 8928 (3.0.23c) Please read the Trouble-Shooting section of the Samba3-HOWTO [2006/09/16 14:19:11, 0] lib/fault.c:fault_report(44) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2006/09/16 14:19:11, 0] lib/fault.c:fault_report(45) === [2006/09/16 14:19:11, 0] lib/util.c:smb_panic(1592) PANIC (pid 8928): internal error [2006/09/16 14:19:11, 0] lib/util.c:log_stack_trace(1699) BACKTRACE: 16 stack frames: #0 smbd(log_stack_trace+0x2d) [0x9b39ed] #1 smbd(smb_panic+0x5d) [0x9b3b1d] #2 smbd [0x99f49a] #3 [0x110420] #4 smbd(create_token_from_username+0x7c4) [0x9fbd54] #5 smbd(create_local_token+0x91) [0x9fcd61] #6 smbd [0x9feb55] #7 smbd [0x88a5b8] #8 smbd(ntlmssp_update+0x242) [0x888aa2] #9 smbd(auth_ntlmssp_update+0x4b) [0x9fe7eb] #10 smbd(reply_sesssetup_and_X+0x1a59) [0x8194a9] #11 smbd [0x8470d0] #12 smbd(smbd_process+0x7ab) [0x84820b] #13 smbd(main+0xbd0) [0xa62110] #14 /lib/libc.so.6(__libc_start_main+0xdc) [0xbb5f2c] #15 smbd [0x7d27b1] [2006/09/16 14:19:11, 0] lib/fault.c:dump_core(173) dumping core in /var/log/samba/cores/smbd I'm running: samba-3.0.23c-4 samba-client-3.0.23c-4 samba-common-3.0.23c-4 Any ideas on this? For a core dump, add the lines : panic action = /bin/sleep 99 to the [global] section of your smb.conf, and reproduce the problem. The smbd will hang waiting for the sleep to finish, allowing you to attach to the waiting smbd process with gdb. You can then print out a backtrace with symbols which is a much more helpful review of the problem. Thanks, Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] INTERNAL ERROR: Signal 11
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tim Gibson wrote: | Hi, | | I am getting the following error in my logs: | | lib/fault.c:fault_report(37) INTERNAL ERROR: Signal | 11 in pid 15629 (3.0.2a) Please read the appendix | Bugs of the Samba HOWTO collection : 1 Time(s) | | Everything appears to be working, but I would like to | know what is going on. There also doesn't seem to be a | Bugs appendix in the Samba HOWTO. There have been a couple of seg faults fixes post 3.0.2a. The most common is in bug 1147 (printing crash). cheers, jerry - -- Hewlett-Packard- http://www.hp.com SAMBA Team -- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc ...a hundred billion castaways looking for a home. --- Sting -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFAhP68IR7qMdg1EfYRAm9xAJ942Z7dn2HRvK+eQh9ta3xzOFV5XwCbBDPl HvJtBuwHScOKwuhJ2/hxP74= =H3f1 -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] INTERNAL ERROR: Signal 11 in smbd (samba 3.0.2a)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeremy Allison wrote: | Can you compile with debug symbols included (-g) so we can | get some info as to chat line this is failing on ? | | Thanks, | | Jeremy. Mmm... I'm not very used to gdb... anyway, I've compiled smbd with the - --enable-debug switch on (via ./configure). Firing gdb --pid to attach to a running process, and waiting for it to crash, I've obtained the following data: (gdb) info program ~Using the running image of attached process 6930. Program stopped at 0x81a78ea. It stopped with signal SIGSEGV, Segmentation fault. (gdb) backtrace #0 0x081a78ea in get_stored_queue_info () #1 0x081a7c49 in print_queue_status () #2 0x0810cf00 in _spoolss_enumjobs () #3 0x080fee9a in api_spoolss_enumjobs () #4 0x0812a19c in api_rpcTNP () #5 0x08129f1e in api_pipe_request () #6 0x08124484 in process_request_pdu () #7 0x08124671 in process_complete_pdu () #8 0x081248f6 in process_incoming_data () #9 0x08124ab3 in write_to_internal_pipe () #10 0x08124a33 in write_to_pipe () #11 0x08087feb in api_fd_reply () #12 0x080881d7 in named_pipe () #13 0x08088beb in reply_trans () #14 0x080bd4f5 in switch_message () #15 0x080bd581 in construct_reply () #16 0x080bd891 in process_smb () #17 0x080be2fd in smbd_process () #18 0x081ea34b in main (argc=2, argv=0xbad4) at smbd/server.c:887 #19 0x4026c306 in __libc_start_main (main=0x81e9ac8 main, argc=2, ~ubp_av=0xbad4, init=0x8075420 _init, fini=0x81ea5f0 _fini, ~rtld_fini=0x4000d2fc _dl_fini, stack_end=0xbacc) ~at ../sysdeps/generic/libc-start.c:129 (gdb) info frame Stack level 0, frame at 0xb018: ~ eip = 0x81a78ea in get_stored_queue_info; saved eip 0x81a7c49 ~ called by frame at 0xb168 ~ Arglist at 0xb018, args: ~ Locals at 0xb018, Previous frame's sp is 0x0 ~ Saved registers: ~ ebx at 0xb00c, ebp at 0xb018, esi at 0xb010, edi at 0xb014, ~ eip at 0xb01c (note: info locals seems to have some problem (no symbol table) but as I've said, I'm not used to gdb). Do you need any more data ? There's some more testing I can do ? (And, by the way, thanks in advance). - -- Simone Lazzaris Task84 S.p.A. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFAPw4b/38nB9eqrJYRArxGAKCt730+rfKcjI9JJLvMnAX7Syd4tQCguLZk 4jfuLejqZiacFqYN7Qx1+nM= =CuBq -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] INTERNAL ERROR: Signal 11 in smbd (samba 3.0.2a)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As I've said, I'm not vary proficient with gdb... here are another
inspection (maybe more useful this time).
Program received signal SIGSEGV, Segmentation fault.
0x082071ab in get_stored_queue_info (pdb=0x8397e68, snum=6,
pcount=0xb064,
~ppqueue=0xb1ac) at printing/printing.c:2186
2186jobid = IVAL(cgdata.dptr, i*4);
(gdb) print i
$2 = 1012
(gdb) print extra_count
$3 = 1130
(gdb) print cgdata.dsize
$4 = 4520
(gdb) print cgdata.dsize/4
$5 = 1130
(gdb) print cgdata
$6 = {dptr = 0x83bff20 ~\006, dsize = 4520}
(gdb) l
2181/* Add in the changed jobids. */
2182for( i = 0; i extra_count; i++) {
2183uint32 jobid;
2184struct printjob *pjob;
2185
2186jobid = IVAL(cgdata.dptr, i*4);
2187DEBUG(5,(get_stored_queue_info: changed job =
%u\n,
(unsigned int)jobid));
2188pjob = print_job_find(snum, jobid);
2189if (!pjob) {
2190DEBUG(5,(get_stored_queue_info: failed to
find changed job = %u\n, (unsigned int)jobid));
(gdb)
(gdb) backtrace
#0 0x082071ab in get_stored_queue_info (pdb=0x8397e68, snum=6,
~pcount=0xb064, ppqueue=0xb1ac) at printing/printing.c:2186
#1 0x0820763a in print_queue_status (snum=6, ppqueue=0xb1ac,
~status=0xb1b0) at printing/printing.c:2283
#2 0x0813c149 in _spoolss_enumjobs (p=0x839c530, q_u=0xb320,
~r_u=0xb310) at rpc_server/srv_spoolss_nt.c:6517
#3 0x0812a99c in api_spoolss_enumjobs (p=0x839c530)
~at rpc_server/srv_spoolss.c:693
#4 0x08160654 in api_rpcTNP (p=0x839c530, rpc_name=0x839c53e spoolss,
~api_rpc_cmds=0x82dab84, n_cmds=51) at rpc_server/srv_pipe.c:1530
#5 0x081602d3 in api_pipe_request (p=0x839c530) at
rpc_server/srv_pipe.c:1476
#6 0x08159081 in process_request_pdu (p=0x839c530, rpc_in_p=0xb530)
~at rpc_server/srv_pipe_hnd.c:669
#7 0x0815931f in process_complete_pdu (p=0x839c530)
~at rpc_server/srv_pipe_hnd.c:741
#8 0x08159687 in process_incoming_data (p=0x839c530, data=0x83969b8 (,
n=48)
~at rpc_server/srv_pipe_hnd.c:839
#9 0x081598b3 in write_to_internal_pipe (np_conn=0x839c530,
~data=0x83969b8 (, n=64) at rpc_server/srv_pipe_hnd.c:878
#10 0x0815981a in write_to_pipe (p=0x839c3f0, data=0x83969a8 \005, n=64)
~at rpc_server/srv_pipe_hnd.c:861
#11 0x0808e605 in api_fd_reply (conn=0x8397810, vuid=100,
~outbuf=0x40547008 , setup=0x82f5830, data=0x83969a8 \005,
params=0x0,
~suwcnt=2, tdscnt=64, tpscnt=0, mdrcnt=1024, mprcnt=0) at smbd/ipc.c:306
#12 0x0808e889 in named_pipe (conn=0x8397810, vuid=100,
outbuf=0x40547008 ,
~name=0xb716 , setup=0x82f5830, data=0x83969a8 \005, params=0x0,
~suwcnt=2, tdscnt=64, tpscnt=0, msrcnt=0, mdrcnt=1024, mprcnt=0)
~at smbd/ipc.c:350
#13 0x0808f674 in reply_trans (conn=0x8397810, inbuf=0x40526008 ,
~outbuf=0x40547008 , size=152, bufsize=16644) at smbd/ipc.c:558
#14 0x080d5a4c in switch_message (type=37, inbuf=0x40526008 ,
~outbuf=0x40547008 , size=152, bufsize=16644) at smbd/process.c:767
#15 0x080d5b08 in construct_reply (inbuf=0x40526008 ,
outbuf=0x40547008 ,
~size=152, bufsize=16644) at smbd/process.c:797
#16 0x080d5eb0 in process_smb (inbuf=0x40526008 , outbuf=0x40547008 )
~at smbd/process.c:897
#17 0x080d6c88 in smbd_process () at smbd/process.c:1328
#18 0x08258e07 in main (argc=2, argv=0xbac4) at smbd/server.c:887
#19 0x4026c306 in __libc_start_main (main=0x8258584 main, argc=2,
~ubp_av=0xbac4, init=0x80754a0 _init, fini=0x8259160 _fini,
~rtld_fini=0x4000d2fc _dl_fini, stack_end=0xbabc)
~at ../sysdeps/generic/libc-start.c:129
(gdb) print cgdata
$7 = {dptr = 0x83bff20 ~\006, dsize = 4520}
- --
Simone Lazzaris
Task84 S.p.A.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFAPzgv/38nB9eqrJYRAq8YAKCl8owvKLC+eVx62OfpsMM6BXGaOwCfZwyL
YT2ux6RgMktgLpJbIMNkkEU=
=2QsD
-END PGP SIGNATURE-
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] INTERNAL ERROR: Signal 11 in smbd (samba 3.0.2a)
On Thu, Feb 26, 2004 at 04:02:04PM +0100, Simone Lazzaris wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I've got a serious problem with my samba installation (samba 3.0.2.a, compiled from sources). The problem seems to occour when printing a file on a printer connected ~ to our samba server. Other printers on the same server seems to work just fine. Note that the thing is not sistematic... some days it occours many times, and other days all works like a charm. Can you compile with debug symbols included (-g) so we can get some info as to chat line this is failing on ? Thanks, Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] INTERNAL ERROR: Signal 11 in pid 12262 (3.0.2-Debian)
On Tue, Feb 10, 2004 at 02:19:32PM +0100, Christopher Odenbach wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, just installed and tested 3.0.2 for debian from backports.org. After some time I got an internal error: Can you reproduce this at will ? If so, can you try running this under valgrind as it looks like a memory corruption problem. Thanks, Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] INTERNAL ERROR: Signal 11
Hi, On Wed, Dec 17, 2003 at 04:29:26AM +0100, [EMAIL PROTECTED] 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) === [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] I get similar errors with samba3.0.1 and samba3.0.0, but it effects the other parts of samba. (The machine work correctly no segfault or signal 11 so far with other apps.) I will post some 'INTERNAL ERRORS': [2003/12/16 11:58:50, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 11 in pid 7122 (3.0.1rc2) Please read the appendix Bugs of the Samba HOWTO collection [2003/12/16 11:58:50, 0] lib/fault.c:fault_report(39) === [2003/12/16 11:58:50, 0] lib/util.c:smb_panic(1400) PANIC: internal error [2003/12/16 11:58:50, 0] lib/util.c:smb_panic(1408) BACKTRACE: 17 stack frames: #0 /usr/sbin/smbd(smb_panic+0x1ab) [0x81b047e] #1 /usr/sbin/smbd [0x819f131] #2 /usr/sbin/smbd [0x819f192] #3 /lib/libc.so.6 [0x4018f498] #4 /lib/libc.so.6(__libc_free+0x7f) [0x401d6edf] #5 /usr/sbin/smbd(CloseDir+0x21) [0x8085cbc] #6 /usr/sbin/smbd [0x80845d9] #7 /usr/sbin/smbd(dptr_close+0xb0) [0x80846cc] #8 /usr/sbin/smbd [0x80ab584] #9 /usr/sbin/smbd(reply_trans2+0x804) [0x80b2eee] #10 /usr/sbin/smbd [0x80c638f] #11 /usr/sbin/smbd [0x80c643f] #12 /usr/sbin/smbd(process_smb+0x1eb) [0x80c678b] #13 /usr/sbin/smbd(smbd_process+0x170) [0x80c72ce] #14 /usr/sbin/smbd(main+0x7b4) [0x821a260] #15 /lib/libc.so.6(__libc_start_main+0xc6) [0x4017bda6] #16 /usr/sbin/smbd(ldap_msgfree+0x7d) [0x8076cb1] .. [2003/12/16 12:01:59, 0] lib/util.c:smb_panic(1408) BACKTRACE: 29 stack frames: #0 /usr/sbin/smbd(smb_panic+0x1ab) [0x81b047e] #1 /usr/sbin/smbd [0x819f131] #2 /usr/sbin/smbd [0x819f192] #3 /lib/libc.so.6 [0x4018f498] #4 /lib/libc.so.6 [0x401d84df] #5 /lib/libc.so.6(__libc_realloc+0x100) [0x401d7020] #6 /usr/sbin/smbd(Realloc+0x91) [0x81af58a] #7 /usr/sbin/smbd(convert_string_allocate+0x3bb) [0x819cfd1] #8 /usr/sbin/smbd(push_ucs2_allocate+0x4e) [0x819d8ae] #9 /usr/sbin/smbd(unix_strupper+0x24) [0x819d1c8] #10 /usr/sbin/smbd(strupper_m+0x6b) [0x81a9a71] #11 /usr/sbin/smbd [0x817c35b] #12 /usr/sbin/smbd(secrets_fetch_trusted_domain_password+0x38) [0x817c5f3] #13 /usr/sbin/smbd(is_trusted_domain+0x5e) [0x81ec0ee] #14 /usr/sbin/smbd(make_user_info_map+0xbb) [0x81e95d3] #15 /usr/sbin/smbd [0x81ec723] #16 /usr/sbin/smbd [0x80f298c] #17 /usr/sbin/smbd(ntlmssp_update+0x1ea) [0x80f1d5b] #18 /usr/sbin/smbd(auth_ntlmssp_update+0x3d) [0x81eca8d] #19 /usr/sbin/smbd [0x80a7bb9] #20 /usr/sbin/smbd [0x80a7ee7] #21 /usr/sbin/smbd(reply_sesssetup_and_X+0x193) [0x80a817a] #22 /usr/sbin/smbd [0x80c638f] #23 /usr/sbin/smbd [0x80c643f] #24 /usr/sbin/smbd(process_smb+0x1eb) [0x80c678b] #25 /usr/sbin/smbd(smbd_process+0x170) [0x80c72ce] #26 /usr/sbin/smbd(main+0x7b4) [0x821a260] #27 /lib/libc.so.6(__libc_start_main+0xc6) [0x4017bda6] #28 /usr/sbin/smbd(ldap_msgfree+0x7d) [0x8076cb1] ... [2003/12/16 12:25:37, 0] lib/fault.c:fault_report(39) === [2003/12/16 12:25:37, 0] lib/util.c:smb_panic(1400) PANIC: internal error [2003/12/16 12:25:37, 0] lib/util.c:smb_panic(1408) BACKTRACE: 17 stack frames: #0 /usr/sbin/smbd(smb_panic+0x1ab) [0x81b047e] #1 /usr/sbin/smbd [0x819f131] #2 /usr/sbin/smbd [0x819f192]
Re: [Samba] internal error: signal 11
Am 30.10.02, 17:56:54, schrieb [EMAIL PROTECTED] zum Thema Re: [Samba] internal error: signal 11: On Wed, Oct 30, 2002 at 11:35:42AM +, 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 9 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
Re: [Samba] internal error: signal 11
Ursprüngliche Nachricht Am 30.10.02, 17:56:54, schrieb [EMAIL PROTECTED] zum Thema Re: [Samba] internal error: signal 11: On Wed, Oct 30, 2002 at 11:35:42AM +, 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] Can you add the following to the smb.conf file : In the [global] section add : panic action = /bin/sleep 9 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. I followed Renés suggestion to produce a signal 11 internal error with rpcclient (Thanks). It worked, but I'm not shure it's the same reason causing this error. Backtrace is appended. Panic action is still set to catch the original error. I also rebuild samba from source without suse patches and tried the same action. It produced the same error. Thanks Gerhard Attaching to program: /usr/lib/samba/classic/smbd, Pid 17774 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_winbind.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libnss_winbind.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 0x400f0299 in wait4 () from /lib/libc.so.6 (gdb) bt full #0 0x400f0299 in wait4 () from /lib/libc.so.6 No symbol table info available. #1 0x4015e2e8 in __DTOR_END__ () from /lib/libc.so.6 No symbol table info available. #2 0x40091016 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 0x813eff7 in StrCaseCmp () No symbol table info available. #8 0x81562fb in get_short_archi () No symbol table info available. #9 0x815c728 in delete_printer_driver () No symbol table info available. #10 0x80e5958 in _spoolss_deleteprinterdriver () No symbol table info available. #11 0x80e0e12 in api_spoolss_deleteprinterdriver () No symbol table info available. #12 0x80df26e in api_rpcTNP () No symbol table info available. #13 0x80e361c in api_spoolss_rpc () No symbol table info available. #14 0x80df08a in api_pipe_request () No symbol table info available. #15 0x80cef09 in process_request_pdu () No symbol table info available. #16 0x80cf0d5 in process_complete_pdu () No symbol table info available. #17 0x80cf31b in process_incoming_data () No symbol table info available. #18 0x80cf475 in write_to_pipe () No symbol table info available. #19 0x8075b38 in api_fd_reply () No symbol table info available. #20 0x8075d24 in named_pipe () No symbol table info available. #21 0x8076502 in reply_trans () No symbol table info available. #22 0x80a5f9f in switch_message () No symbol table info available. #23 0x80a6040 in construct_reply () No symbol table info available. #24 0x80a629e in process_smb () No symbol table info available. #25 0x80a6c8c in smbd_process () No symbol table info available. #26 0x806ad58 in main () No symbol table info available.
Re: [Samba] internal error: signal 11
On Fri, Nov 01, 2002 at 01:46:30PM +, Gerhard Vögel wrote:
Ursprüngliche Nachricht
Am 30.10.02, 17:56:54, schrieb [EMAIL PROTECTED] zum Thema Re: [Samba]
internal error: signal 11:
On Wed, Oct 30, 2002 at 11:35:42AM +, 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]
Can you add the following to the smb.conf file :
In the [global] section add :
panic action = /bin/sleep 9
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.
I followed Renés suggestion to produce a signal 11 internal error with
rpcclient (Thanks). It worked, but I'm not shure it's the same reason
causing this error. Backtrace is appended. Panic action is still set to
catch the original error.
I also rebuild samba from source without suse patches and tried the same
action. It produced the same error.
Thanks for this. I already fixed this bug in the Samba CVS. Here is the
patch if you'd like to test it.
Thanks,
Jeremy.
--- printing/nt_printing.c.orig Fri Nov 1 10:12:25 2002
+++ printing/nt_printing.c Fri Nov 1 10:12:35 2002
@@ -664,6 +664,12 @@
int i=-1;
DEBUG(107,(Getting architecture dependant directory\n));
+
+ if (long_archi == NULL) {
+ DEBUGADD(107,(Bad long_archi param.!\n));
+ return False;
+ }
+
do {
i++;
} while ( (archi_table[i].long_archi!=NULL )
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] internal error: signal 11
On Wed, Oct 30, 2002 at 11:35:42AM +, 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. I found similar errors discussed in the list archives but no explanation or solution. Can anybody help. The last timer i got this type of error, it was an hardware problem. Some years ago i compiled e kernel on an 'stable' System, which runs novell netware 3.1 for years. The gcc failes with internal error: signal 11. This was an hardware with PS/2 RAM. One module has another speed (70ns) than the other (60ns), so this was an timing issue of the hardware and not the os or software. Take a look to the memory sub system. More than one module? Same Timing? -- Frank Matthieß[EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] internal error: signal 11
Hi, I can reproduce this internal error. When I use rpcclient to do 'deldriver' this panic is generated and the driver is not removed! Is this of any help? Frank Matthieß heeft geschreven: On Wed, Oct 30, 2002 at 11:35:42AM +, 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. I found similar errors discussed in the list archives but no explanation or solution. Can anybody help. The last timer i got this type of error, it was an hardware problem. Some years ago i compiled e kernel on an 'stable' System, which runs novell netware 3.1 for years. The gcc failes with internal error: signal 11. This was an hardware with PS/2 RAM. One module has another speed (70ns) than the other (60ns), so this was an timing issue of the hardware and not the os or software. Take a look to the memory sub system. More than one module? Same Timing? René Nieuwenhuizen Sysadmin CPB Netherlands Bureau for Economic Policy Analysis -- Aan dit bericht kunnen geen rechten worden ontleend. Het bericht is alleen bestemd voor de geadresseerde. Indien dit bericht niet voor u is bestemd, verzoeken wij u dit onmiddellijk aan ons te melden en de inhoud van het bericht te vernietigen. This message shall not constitute any obligations. This message is intended solely for the addressee. If you have received this message in error, please inform us immediately and delete its contents. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] internal error: signal 11
On Thu, Oct 31, 2002 at 10:52:25AM +0100, René Nieuwenhuizen wrote: Hi, I can reproduce this internal error. When I use rpcclient to do 'deldriver' this panic is generated and the driver is not removed! Is this of any help? Can you setup a 'panic action' in your smb.conf? Set it to '/bin/sleep 9000' and attach to the process with gdb. The grab a 'bt full' from gdb - this will help at lot in chasing it down. Andrew Bartlett -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] internal error: signal 11
At your service (as they used to say in the netherlands) Andrew Bartlett heeft geschreven: On Thu, Oct 31, 2002 at 10:52:25AM +0100, René Nieuwenhuizen wrote: Hi, I can reproduce this internal error. When I use rpcclient to do 'deldriver' this panic is generated and the driver is not removed! Is this of any help? Can you setup a 'panic action' in your smb.conf? Set it to '/bin/sleep 9000' and attach to the process with gdb. The grab a 'bt full' from gdb - this will help at lot in chasing it down. Andrew Bartlett Thanks Andrew for looking into it... René Nieuwenhuizen Sysadmin CPB Netherlands Bureau for Economic Policy Analysis -- Aan dit bericht kunnen geen rechten worden ontleend. Het bericht is alleen bestemd voor de geadresseerde. Indien dit bericht niet voor u is bestemd, verzoeken wij u dit onmiddellijk aan ons te melden en de inhoud van het bericht te vernietigen. This message shall not constitute any obligations. This message is intended solely for the addressee. If you have received this message in error, please inform us immediately and delete its contents. Script started on Thu Oct 31 10:19:13 2002 ]0;rootproliant3:/var/cache/samba[rootproliant3 samba]# gdb /usr/sbin/smbd 21547 GNU gdb Red Hat Linux (5.1.90CVS-5) Copyright 2002 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-redhat-linux... (no debugging symbols found)... Attaching to program: /usr/sbin/smbd, process 21547 Reading symbols from /usr/lib/libcups.so.2...(no debugging symbols found)... done. Loaded symbols for /usr/lib/libcups.so.2 Reading symbols from /lib/libssl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libssl.so.2 Reading symbols from /lib/libcrypto.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypto.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/i686/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/i686/libc.so.6 Reading symbols from /lib/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libdl.so.2 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_nis.so.2...(no debugging symbols found)... done. Loaded symbols for /lib/libnss_nis.so.2 0x420b48a9 in wait4 () from /lib/i686/libc.so.6 (gdb) bt #0 0x420b48a9 in wait4 () from /lib/i686/libc.so.6 #1 0x4213030c in __DTOR_END__ () from /lib/i686/libc.so.6 #2 0x4204a062 in system () from /lib/i686/libc.so.6 #3 0x081497e1 in smb_panic () #4 0x08137af0 in fault_report () #5 signal handler called #6 0x08141ed0 in StrCaseCmp () #7 0x08158dac in get_short_archi () #8 0x0815f185 in delete_printer_driver () #9 0x080e5cc0 in _spoolss_deleteprinterdriver () #10 0x080e0f5c in api_spoolss_deleteprinterdriver () #11 0x080df224 in api_rpcTNP () #12 0x080e38e9 in api_spoolss_rpc () #13 0x080df038 in api_pipe_request () #14 0x080cea7c in process_request_pdu () #15 0x080cec45 in process_complete_pdu () #16 0x080cf005 in write_to_pipe () #17 0x08075b98 in api_fd_reply () #18 0x080765bc in reply_trans () #19 0x080a6279 in switch_message () #20 0x080a631e in construct_reply () #21 0x080a659e in process_smb () #22 0x080a6faa in smbd_process () #23 0x0806a948 in main () #24 0x42017589 in __libc_start_main () from /lib/i686/libc.so.6 (gdb) quit The program is running. Quit anyway (and detach it)? (y or n) n y Detaching from program: /usr/sbin/smbd, process 21547
Re: [Samba] internal error: signal 11
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 30 Oct 2002 [EMAIL PROTECTED] wrote: On Wed, Oct 30, 2002 at 11:35:42AM +, 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 9 cheers, 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- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] internal error: signal 11
On Wed, Oct 30, 2002 at 11:35:42AM +, 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 9 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. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] internal error: signal 11
Ursprüngliche Nachricht Am 30.10.02, 17:56:54, schrieb [EMAIL PROTECTED] zum Thema Re: [Samba] internal error: signal 11: On Wed, Oct 30, 2002 at 11:35:42AM +, 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 9 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. I'll try, but the server already is in production use and I am not always there and cannot foresee when the next problem occurs. So it could take months to get a backtrace. Do you have any other suggestions or any ideas what may have the invalid memory reference? Thanks Gerhard -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] internal error: signal 11
On Wed, Oct 30, 2002 at 10:37:25PM +, Gerhard Vögel wrote: I'll try, but the server already is in production use and I am not always there and cannot foresee when the next problem occurs. So it could take months to get a backtrace. Do you have any other suggestions or any ideas what may have the invalid memory reference? Not without more information I'm afraid, which is what I'm trying to get here. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
