Alex de Vaal
2004-Apr-28 15:23 UTC
[Samba] Bug report 3.0.2a; INTERNAL ERROR: Signal 11 in smbd; PANIC: internal error
Dear Samba team, I?d like to a report a bug (INTERNAL ERROR: Signal 11 in smbd) that I encountered with Samba after uploading printer drivers to the PRINT$ share, while I was configuring the ?Printing Defaults? in the ?Advanced? tab. Here?s the overview of the Samba server I use: RHL9, Samba 3.0.2a compiled with MIT 1.3.1-7 and CUPS. Samba is a domain member in a Windows 2003 ADS. No local Linux users. The shares are working OK for the ADS users. The CUPS queues are RAW queues. Essential info (not complete) of smb.conf [global] workgroup = TEST realm = TEST.COM server string = %h server (Samba %v) security = ADS password server = * socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 printcap name = cups domain master = No dns proxy = No idmap uid = 10000-20000 idmap gid = 10000-20000 template homedir = /data/hom/%U template shell = /bin/bash printer admin = root, '@TEST.COM\Domain Admins' printing = cups oplocks = No level2 oplocks = No [printers] comment = All Printers path = /var/spool/samba guest ok = Yes printable = Yes browseable = No [print$] comment = Printer Driver Download Area path = /etc/samba/drivers write list = root, '@TEST.COM\Domain Admins' force user = root guest ok = Yes Workstation used: Windows XP SP1a English. The user that I used for uploading the printer drivers and configuring the printer is member of Domain Admins. Uploading of the printer driver on the printer share went Ok. After the upload of the printer driver I opened the ?Advanced? button to change the ?Printing Defaults? First I changed the orientation from Portrait to Landscape (as in the HOWTO). After that I changed the paper size. At that time I saw in the /var/lib/messages file (also in /var/lib/samba/<ip address XP ws>.log) the following messages: Apr 20 18:16:57 dussel smbd[2601]: call_nt_transact_ioctl(0x90100): Currently not implemented. Apr 20 18:17:10 dussel smbd[2601]: Added printer driver. Print driver name: HP LaserJet 4200 PCL 5e. Print driver OS: WIN2K. Administrator name: TEST\deadmin. Apr 20 18:17:26 dussel nmbd[1508]: [2004/04/20 18:17:26, 0] nmbd/nmbd_namequery.c:query_name_response(101) Apr 20 18:17:26 dussel nmbd[1508]: query_name_response: Multiple (2) responses received for a query on subnet 10.20.63.151 for name TEST<1d>. Apr 20 18:17:26 dussel nmbd[1508]: This response was from IP 10.20.63.40, reporting an IP address of 10.20.63.40. Apr 20 18:20:26 dussel smbd[2601]: [2004/04/20 18:20:26, 0] lib/fault.c:fault_report(36) Apr 20 18:20:26 dussel smbd[2601]: ============================================================== Apr 20 18:20:26 dussel smbd[2601]: [2004/04/20 18:20:26, 0] lib/fault.c:fault_report(37) Apr 20 18:20:26 dussel smbd[2601]: INTERNAL ERROR: Signal 11 in pid 2601 (3.0.2a) Apr 20 18:20:26 dussel smbd[2601]: Please read the appendix Bugs of the Samba HOWTO collection Apr 20 18:20:26 dussel smbd[2601]: [2004/04/20 18:20:26, 0] lib/fault.c:fault_report(39) Apr 20 18:20:26 dussel smbd[2601]: ============================================================== Apr 20 18:20:26 dussel smbd[2601]: [2004/04/20 18:20:26, 0] lib/util.c:smb_panic(1400) Apr 20 18:20:26 dussel smbd[2601]: PANIC: internal error Apr 20 18:20:26 dussel smbd[2601]: [2004/04/20 18:20:26, 0] lib/util.c:smb_panic(1408) Apr 20 18:20:26 dussel smbd[2601]: BACKTRACE: 26 stack frames: Apr 20 18:20:26 dussel smbd[2601]: #0 smbd(smb_panic+0x11c) [0x81c3d6c] Apr 20 18:20:26 dussel smbd[2601]: #1 smbd [0x81b24a2] Apr 20 18:20:26 dussel smbd[2601]: #2 /lib/tls/libc.so.6 [0x420275c8] Apr 20 18:20:26 dussel smbd[2601]: #3 /lib/tls/libc.so.6(malloc+0x8b) [0x4207335b] Apr 20 18:20:26 dussel smbd[2601]: #4 smbd(tdb_unpack+0x13b) [0x81d98ab] Apr 20 18:20:26 dussel smbd[2601]: #5 smbd [0x81e9c9e] Apr 20 18:20:26 dussel smbd[2601]: #6 smbd [0x81ea8a5] Apr 20 18:20:26 dussel smbd[2601]: #7 smbd(get_a_printer+0x126) [0x81ebbf6] Apr 20 18:20:26 dussel smbd[2601]: #8 smbd(_spoolss_getprinterdata+0x256) [0x8120256] Apr 20 18:20:26 dussel smbd[2601]: #9 smbd [0x811640f] Apr 20 18:20:26 dussel smbd[2601]: #10 smbd(api_rpcTNP+0x159) [0x814b239] Apr 20 18:20:26 dussel smbd[2601]: #11 smbd(api_pipe_request+0xaf) [0x814afff] Apr 20 18:20:26 dussel smbd[2601]: #12 smbd [0x81446f6] Apr 20 18:20:26 dussel smbd[2601]: #13 smbd [0x8144a49] Apr 20 18:20:26 dussel smbd[2601]: #14 smbd [0x8144c8b] Apr 20 18:20:26 dussel smbd[2601]: #15 smbd [0x8144e8c] Apr 20 18:20:26 dussel smbd[2601]: #16 smbd(write_to_pipe+0xf2) [0x8144de2] Apr 20 18:20:26 dussel smbd[2601]: #17 smbd [0x8089e1e] Apr 20 18:20:26 dussel smbd[2601]: #18 smbd(reply_trans+0x54b) [0x808a7eb] Apr 20 18:20:26 dussel smbd[2601]: #19 smbd [0x80c85a6] Apr 20 18:20:26 dussel smbd[2601]: #20 smbd [0x80c8779] Apr 20 18:20:26 dussel smbd[2601]: #21 smbd(process_smb+0x8f) [0x80c898f] Apr 20 18:20:26 dussel smbd[2601]: #22 smbd(smbd_process+0x167) [0x80c95d7] Apr 20 18:20:26 dussel smbd[2601]: #23 smbd(main+0x4bf) [0x822fd2f] Apr 20 18:20:26 dussel smbd[2601]: #24 /lib/tls/libc.so.6(__libc_start_main+0xe4) [0x42015574] Apr 20 18:20:26 dussel smbd[2601]: #25 smbd(ldap_msgfree+0x8d) [0x8077061] Apr 20 18:20:26 dussel smbd[2601]: Apr 20 18:20:27 dussel smbd[2666]: [2004/04/20 18:20:27, 0] smbd/connection.c:register_message_flags(220) Apr 20 18:20:27 dussel smbd[2666]: register_message_flags: tdb_fetch failed Apr 20 18:20:39 dussel smbd[2666]: [2004/04/20 18:20:39, 0] I have 4 print shares (with the same printer driver), so I saw the same messages appear while I was changing the Printing Defaults on all printer shares. The ?INTERNAL ERROR: Signal 11 in smbd? error appeared as well in my test environment as in my ?live? environment. The utilization of the RHL9 server went up a little after 4 panic messages, but after a reboot the utilization was normal. The good news is however that everything seems to work fine!!! Windows XP workstations get their Samba printer shares (+ drivers + appropriate configuration) in their local "Printers and Faxes" from the logon script and they can print from Office. However my log files are flooded with ?register_message_flags: tdb_fetch failed? messages all the time when users print something or when they login (but no "INTERNAL ERROR: Signal 11 in smbd" messages anymore). Subjoined an example when a user login: [2004/04/21 16:23:19, 1] smbd/service.c:make_connection_snum(705) 10.20.63.86 (10.20.63.86) connect to service print$ initially as user root (uid=0, gid=0) (pid 10299) [2004/04/21 16:23:38, 1] smbd/service.c:close_cnum(887) 10.20.63.86 (10.20.63.86) closed connection to service print$ [2004/04/21 16:24:14, 0] smbd/connection.c:register_message_flags(220) register_message_flags: tdb_fetch failed [2004/04/21 16:24:43, 0] smbd/connection.c:register_message_flags(220) register_message_flags: tdb_fetch failed tdbbackup on all samba tdb files doesn?t help! (I used the ?locate .tdb? command to locate all the tdb files). If more info is required, please let me know. -- Regards, Alex de Vaal.
Jeramy Eling
2004-Apr-28 15:48 UTC
[Samba] Bug report 3.0.2a; INTERNAL ERROR: Signal 11 in smbd; PANIC: internal error
Your not alone on this one, I have had the same issue with samba 3.0.2a and 3.0.3rc1. I have logged it in bugzilla but have not heard anything on the matter. Jez -----Original Message----- From: samba-bounces+jeramy.eling=britax-pmg.com@lists.samba.org [mailto:samba-bounces+jeramy.eling=britax-pmg.com@lists.samba.org]On Behalf Of Alex de Vaal Sent: 28 April 2004 16:22 To: samba@lists.samba.org Subject: [Samba] Bug report 3.0.2a; INTERNAL ERROR: Signal 11 in smbd;PANIC: internal error Dear Samba team, I'd like to a report a bug (INTERNAL ERROR: Signal 11 in smbd) that I encountered with Samba after uploading printer drivers to the PRINT$ share, while I was configuring the "Printing Defaults" in the "Advanced" tab. Here's the overview of the Samba server I use: RHL9, Samba 3.0.2a compiled with MIT 1.3.1-7 and CUPS. Samba is a domain member in a Windows 2003 ADS. No local Linux users. The shares are working OK for the ADS users. The CUPS queues are RAW queues. Essential info (not complete) of smb.conf [global] workgroup = TEST realm = TEST.COM server string = %h server (Samba %v) security = ADS password server = * socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 printcap name = cups domain master = No dns proxy = No idmap uid = 10000-20000 idmap gid = 10000-20000 template homedir = /data/hom/%U template shell = /bin/bash printer admin = root, '@TEST.COM\Domain Admins' printing = cups oplocks = No level2 oplocks = No [printers] comment = All Printers path = /var/spool/samba guest ok = Yes printable = Yes browseable = No [print$] comment = Printer Driver Download Area path = /etc/samba/drivers write list = root, '@TEST.COM\Domain Admins' force user = root guest ok = Yes Workstation used: Windows XP SP1a English. The user that I used for uploading the printer drivers and configuring the printer is member of Domain Admins. Uploading of the printer driver on the printer share went Ok. After the upload of the printer driver I opened the "Advanced" button to change the "Printing Defaults" First I changed the orientation from Portrait to Landscape (as in the HOWTO). After that I changed the paper size. At that time I saw in the /var/lib/messages file (also in /var/lib/samba/<ip address XP ws>.log) the following messages: Apr 20 18:16:57 dussel smbd[2601]: call_nt_transact_ioctl(0x90100): Currently not implemented. Apr 20 18:17:10 dussel smbd[2601]: Added printer driver. Print driver name: HP LaserJet 4200 PCL 5e. Print driver OS: WIN2K. Administrator name: TEST\deadmin. Apr 20 18:17:26 dussel nmbd[1508]: [2004/04/20 18:17:26, 0] nmbd/nmbd_namequery.c:query_name_response(101) Apr 20 18:17:26 dussel nmbd[1508]: query_name_response: Multiple (2) responses received for a query on subnet 10.20.63.151 for name TEST<1d>. Apr 20 18:17:26 dussel nmbd[1508]: This response was from IP 10.20.63.40, reporting an IP address of 10.20.63.40. Apr 20 18:20:26 dussel smbd[2601]: [2004/04/20 18:20:26, 0] lib/fault.c:fault_report(36) Apr 20 18:20:26 dussel smbd[2601]: ============================================================== Apr 20 18:20:26 dussel smbd[2601]: [2004/04/20 18:20:26, 0] lib/fault.c:fault_report(37) Apr 20 18:20:26 dussel smbd[2601]: INTERNAL ERROR: Signal 11 in pid 2601 (3.0.2a) Apr 20 18:20:26 dussel smbd[2601]: Please read the appendix Bugs of the Samba HOWTO collection Apr 20 18:20:26 dussel smbd[2601]: [2004/04/20 18:20:26, 0] lib/fault.c:fault_report(39) Apr 20 18:20:26 dussel smbd[2601]: ============================================================== Apr 20 18:20:26 dussel smbd[2601]: [2004/04/20 18:20:26, 0] lib/util.c:smb_panic(1400) Apr 20 18:20:26 dussel smbd[2601]: PANIC: internal error Apr 20 18:20:26 dussel smbd[2601]: [2004/04/20 18:20:26, 0] lib/util.c:smb_panic(1408) Apr 20 18:20:26 dussel smbd[2601]: BACKTRACE: 26 stack frames: Apr 20 18:20:26 dussel smbd[2601]: #0 smbd(smb_panic+0x11c) [0x81c3d6c] Apr 20 18:20:26 dussel smbd[2601]: #1 smbd [0x81b24a2] Apr 20 18:20:26 dussel smbd[2601]: #2 /lib/tls/libc.so.6 [0x420275c8] Apr 20 18:20:26 dussel smbd[2601]: #3 /lib/tls/libc.so.6(malloc+0x8b) [0x4207335b] Apr 20 18:20:26 dussel smbd[2601]: #4 smbd(tdb_unpack+0x13b) [0x81d98ab] Apr 20 18:20:26 dussel smbd[2601]: #5 smbd [0x81e9c9e] Apr 20 18:20:26 dussel smbd[2601]: #6 smbd [0x81ea8a5] Apr 20 18:20:26 dussel smbd[2601]: #7 smbd(get_a_printer+0x126) [0x81ebbf6] Apr 20 18:20:26 dussel smbd[2601]: #8 smbd(_spoolss_getprinterdata+0x256) [0x8120256] Apr 20 18:20:26 dussel smbd[2601]: #9 smbd [0x811640f] Apr 20 18:20:26 dussel smbd[2601]: #10 smbd(api_rpcTNP+0x159) [0x814b239] Apr 20 18:20:26 dussel smbd[2601]: #11 smbd(api_pipe_request+0xaf) [0x814afff] Apr 20 18:20:26 dussel smbd[2601]: #12 smbd [0x81446f6] Apr 20 18:20:26 dussel smbd[2601]: #13 smbd [0x8144a49] Apr 20 18:20:26 dussel smbd[2601]: #14 smbd [0x8144c8b] Apr 20 18:20:26 dussel smbd[2601]: #15 smbd [0x8144e8c] Apr 20 18:20:26 dussel smbd[2601]: #16 smbd(write_to_pipe+0xf2) [0x8144de2] Apr 20 18:20:26 dussel smbd[2601]: #17 smbd [0x8089e1e] Apr 20 18:20:26 dussel smbd[2601]: #18 smbd(reply_trans+0x54b) [0x808a7eb] Apr 20 18:20:26 dussel smbd[2601]: #19 smbd [0x80c85a6] Apr 20 18:20:26 dussel smbd[2601]: #20 smbd [0x80c8779] Apr 20 18:20:26 dussel smbd[2601]: #21 smbd(process_smb+0x8f) [0x80c898f] Apr 20 18:20:26 dussel smbd[2601]: #22 smbd(smbd_process+0x167) [0x80c95d7] Apr 20 18:20:26 dussel smbd[2601]: #23 smbd(main+0x4bf) [0x822fd2f] Apr 20 18:20:26 dussel smbd[2601]: #24 /lib/tls/libc.so.6(__libc_start_main+0xe4) [0x42015574] Apr 20 18:20:26 dussel smbd[2601]: #25 smbd(ldap_msgfree+0x8d) [0x8077061] Apr 20 18:20:26 dussel smbd[2601]: Apr 20 18:20:27 dussel smbd[2666]: [2004/04/20 18:20:27, 0] smbd/connection.c:register_message_flags(220) Apr 20 18:20:27 dussel smbd[2666]: register_message_flags: tdb_fetch failed Apr 20 18:20:39 dussel smbd[2666]: [2004/04/20 18:20:39, 0] I have 4 print shares (with the same printer driver), so I saw the same messages appear while I was changing the Printing Defaults on all printer shares. The "INTERNAL ERROR: Signal 11 in smbd" error appeared as well in my test environment as in my "live" environment. The utilization of the RHL9 server went up a little after 4 panic messages, but after a reboot the utilization was normal. The good news is however that everything seems to work fine!!! Windows XP workstations get their Samba printer shares (+ drivers + appropriate configuration) in their local "Printers and Faxes" from the logon script and they can print from Office. However my log files are flooded with "register_message_flags: tdb_fetch failed" messages all the time when users print something or when they login (but no "INTERNAL ERROR: Signal 11 in smbd" messages anymore). Subjoined an example when a user login: [2004/04/21 16:23:19, 1] smbd/service.c:make_connection_snum(705) 10.20.63.86 (10.20.63.86) connect to service print$ initially as user root (uid=0, gid=0) (pid 10299) [2004/04/21 16:23:38, 1] smbd/service.c:close_cnum(887) 10.20.63.86 (10.20.63.86) closed connection to service print$ [2004/04/21 16:24:14, 0] smbd/connection.c:register_message_flags(220) register_message_flags: tdb_fetch failed [2004/04/21 16:24:43, 0] smbd/connection.c:register_message_flags(220) register_message_flags: tdb_fetch failed tdbbackup on all samba tdb files doesn't help! (I used the "locate .tdb" command to locate all the tdb files). If more info is required, please let me know. -- Regards, Alex de Vaal. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba