We have two sites, one has a Solaris 8 PDC running Samba v3.0.20. The other has a SuSE 9.3 PDC running Samba v3.0.20b. I upgraded them both to Samba v3.0.21, and had similar problems. Profiles were often not being saved and I was getting an INTERNAL ERROR in the Samba log when a user logged in. I eventually had to go back to the previous version of Samba. This is the error on our Solaris PDC: [2005/12/27 11:12:52, 1] smbd/service.c:make_connection_snum(666) jack (194.80.190.32) connect to service testy initially as user testy (uid=1155, gid=20) (pid 13227) [2005/12/27 11:12:53, 0] lib/fault.c:fault_report(36) ==============================================================[2005/12/27 11:12:53, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 10 in pid 13227 (3.0.21) Please read the Trouble-Shooting section of the Samba3-HOWTO [2005/12/27 11:12:53, 0] lib/fault.c:fault_report(39) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2005/12/27 11:12:53, 0] lib/fault.c:fault_report(40) ==============================================================[2005/12/27 11:12:53, 0] lib/util.c:smb_panic2(1554) PANIC: internal error [2005/12/27 11:12:53, 1] smbd/service.c:make_connection_snum(666) jack (194.80.190.32) connect to service netlogon initially as user testy (uid=1155, gid=20) (pid 13231) On SuSE Linux the error had more info: ==============================================================[2005/12/26 12:03:02, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 11 in pid 16007 (3.0.21) Please read the Trouble-Shooting section of the Samba3-HOWTO [2005/12/26 12:03:02, 0] lib/fault.c:fault_report(39) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2005/12/26 12:03:02, 0] lib/fault.c:fault_report(40) ==============================================================[2005/12/26 12:03:02, 0] lib/util.c:smb_panic2(1554) PANIC: internal error [2005/12/26 12:03:02, 0] lib/util.c:smb_panic2(1562) BACKTRACE: 28 stack frames: #0 /home/samba_shark/sbin/smbd(smb_panic2+0x193) [0x59c720] #1 /home/samba_shark/sbin/smbd(smb_panic+0xe) [0x59c588] #2 /home/samba_shark/sbin/smbd [0x58aaac] #3 /home/samba_shark/sbin/smbd [0x58ab08] #4 /lib64/tls/libc.so.6 [0x2aaaab3f4f00] #5 /home/samba_shark/sbin/smbd(lookup_printerkey+0x8f) [0x5c0ae7] #6 /home/samba_shark/sbin/smbd(add_printer_data+0x67) [0x5c1339] #7 /home/samba_shark/sbin/smbd(set_printer_dataex+0xc) [0x4f9ba1] #8 /home/samba_shark/sbin/smbd [0x500ec9] #9 /home/samba_shark/sbin/smbd(_spoolss_setprinter+0x169) [0x5012a9] #10 /home/samba_shark/sbin/smbd [0x4f3204] #11 /home/samba_shark/sbin/smbd(api_rpcTNP+0x20c) [0x521f1e] #12 /home/samba_shark/sbin/smbd(api_pipe_request+0xf6) [0x521c87] #13 /home/samba_shark/sbin/smbd [0x51bff7] #14 /home/samba_shark/sbin/smbd [0x51c1a6] #15 /home/samba_shark/sbin/smbd [0x51c712] #16 /home/samba_shark/sbin/smbd [0x51c901] #17 /home/samba_shark/sbin/smbd(write_to_pipe+0xef) [0x51c876] #18 /home/samba_shark/sbin/smbd [0x450ec4] #19 /home/samba_shark/sbin/smbd [0x451114] #20 /home/samba_shark/sbin/smbd(reply_trans+0xa35) [0x451bca] #21 /home/samba_shark/sbin/smbd [0x498150] #22 /home/samba_shark/sbin/smbd [0x498216] #23 /home/samba_shark/sbin/smbd(process_smb+0x1d0) [0x49853a] #24 /home/samba_shark/sbin/smbd(smbd_process+0x12a) [0x499245] #25 /home/samba_shark/sbin/smbd(main+0x716) [0x609181] #26 /lib64/tls/libc.so.6(__libc_start_main+0xea) [0x2aaaab3e354a] #27 /home/samba_shark/sbin/smbd [0x43cd3a] ============================================================== Below is one of our smb.conf files: [global] workgroup = OURDOMAIN server string = %h log file = /var/log/samba/%m.log log level = 1 syslog = 0 load printers = yes printing = cups printcap name = cups domain master = yes domain logons = yes local master = yes preferred master = yes name resolve order = wins lmhosts host bcast username map = /home/samba/lib/users.map wins support = yes time server = yes os level = 65 encrypt passwords = yes security = user logon script = netlogon.bat logon path = \\%N\profile\%a\%u logon drive = q: [profile] comment = User Profiles path = /home/samba/profile browseable = no guest ok = yes writeable = yes [printers] comment = All Printers path = /home/samba/var/spool/public browseable = no public = yes guest ok = yes writable = no printable = yes [print$] comment = Printer Drivers path = /home/samba/drivers browseable = yes guest ok = yes read only = yes write list = root [homes] comment = Home Directories browseable = yes guest ok = no writable = yes [netlogon] comment = Network Logon Service path = /home/samba/%a/netlogon guest ok = yes writeable = no share modes = no
On Tue, Dec 27, 2005 at 11:33:36AM +0000, Michael Keightley wrote:> > We have two sites, one has a Solaris 8 PDC running Samba v3.0.20. > The other has a SuSE 9.3 PDC running Samba v3.0.20b. > I upgraded them both to Samba v3.0.21, and had similar problems. Profiles were > often not being saved and I was getting an INTERNAL ERROR in the Samba log when > a user logged in. > I eventually had to go back to the previous version of Samba. > This is the error on our Solaris PDC: > > [2005/12/27 11:12:52, 1] smbd/service.c:make_connection_snum(666) > jack (194.80.190.32) connect to service testy initially as user testy (uid=1155, gid=20) (pid 13227) > [2005/12/27 11:12:53, 0] lib/fault.c:fault_report(36) > ==============================================================> [2005/12/27 11:12:53, 0] lib/fault.c:fault_report(37) > INTERNAL ERROR: Signal 10 in pid 13227 (3.0.21) > Please read the Trouble-Shooting section of the Samba3-HOWTO > [2005/12/27 11:12:53, 0] lib/fault.c:fault_report(39) > > From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf > [2005/12/27 11:12:53, 0] lib/fault.c:fault_report(40) > ==============================================================> [2005/12/27 11:12:53, 0] lib/util.c:smb_panic2(1554) > PANIC: internal error > [2005/12/27 11:12:53, 1] smbd/service.c:make_connection_snum(666) > jack (194.80.190.32) connect to service netlogon initially as user testy (uid=1155, gid=20) (pid 13231) > > > On SuSE Linux the error had more info: > > ==============================================================> [2005/12/26 12:03:02, 0] lib/fault.c:fault_report(37) > INTERNAL ERROR: Signal 11 in pid 16007 (3.0.21) > Please read the Trouble-Shooting section of the Samba3-HOWTO > [2005/12/26 12:03:02, 0] lib/fault.c:fault_report(39) > > From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf > [2005/12/26 12:03:02, 0] lib/fault.c:fault_report(40) > ==============================================================> [2005/12/26 12:03:02, 0] lib/util.c:smb_panic2(1554) > PANIC: internal error > [2005/12/26 12:03:02, 0] lib/util.c:smb_panic2(1562) > BACKTRACE: 28 stack frames: > #0 /home/samba_shark/sbin/smbd(smb_panic2+0x193) [0x59c720] > #1 /home/samba_shark/sbin/smbd(smb_panic+0xe) [0x59c588] > #2 /home/samba_shark/sbin/smbd [0x58aaac] > #3 /home/samba_shark/sbin/smbd [0x58ab08] > #4 /lib64/tls/libc.so.6 [0x2aaaab3f4f00] > #5 /home/samba_shark/sbin/smbd(lookup_printerkey+0x8f) [0x5c0ae7]Looks like a printer code bug. Can you compile with -g, add the line panic action = /bin/sleep 999999 to the [global] section of your smb.conf and recreate the crash. Then attach to the crashed smbd process with gdb and type "bt" to get a back-trace. Thanks a lot, Jeremy.