Hi, i have got a Samba server ( currently 3.0.5 ) together with CUPS 1.1.9. running as a print server for a load of Windows 2000 / XP clients. This setup worked well for several months until about three weeks ago ( Samba 3.0.4 at that time ). Now all of a sudden i'm getting Samba crashes for those clients that try to access the 'printers and faxes' on the Samba server. In Windows the list of printers on the server permanently refreshes, because Samba is crashing all the time. It is still possible to print and even to upload drivers to the printers on the Samba server but theses crashes are nonetheless very annoying. I've already tried to delete the pdb's in /var/lock/samba to reset all printing related information but that did not help. Thanks for your help ! Regards, Ulf Dettmer P.S. This is a log entry of a typical 'printer panic'. Please mail me if you need the whole level 5 log. [2004/08/04 07:59:22, 0] lib/fault.c:fault_report(36) ==============================================================[2004/08/04 07:59:22, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 11 in pid 19529 (3.0.5) Please read the appendix Bugs of the Samba HOWTO collection [2004/08/04 07:59:22, 0] lib/fault.c:fault_report(39) ==============================================================[2004/08/04 07:59:22, 0] lib/util.c:smb_panic2(1398) PANIC: internal error [2004/08/04 07:59:22, 0] lib/util.c:smb_panic2(1406) BACKTRACE: 24 stack frames: #0 /usr/sbin/smbd(smb_panic2+0x18c) [0x81a2830] #1 /usr/sbin/smbd(smb_panic+0x10) [0x81a26a2] #2 /usr/sbin/smbd [0x819263e] #3 /usr/sbin/smbd [0x8192693] #4 /lib/libc.so.6 [0x402ddbf8] #5 /usr/sbin/smbd(_spoolss_rfnpcnex+0x19e) [0x8116ef1] #6 /usr/sbin/smbd [0x810dacf] #7 /usr/sbin/smbd(api_rpcTNP+0x200) [0x81386d9] #8 /usr/sbin/smbd(api_pipe_request+0xd2) [0x8138459] #9 /usr/sbin/smbd [0x8132a38] #10 /usr/sbin/smbd [0x8132c14] #11 /usr/sbin/smbd [0x8132e91] #12 /usr/sbin/smbd [0x8133048] #13 /usr/sbin/smbd(write_to_pipe+0xd7) [0x8132fcc] #14 /usr/sbin/smbd [0x8089c35] #15 /usr/sbin/smbd [0x8089e0e] #16 /usr/sbin/smbd(reply_trans+0xb97) [0x808aa17] #17 /usr/sbin/smbd [0x80ca154] #18 /usr/sbin/smbd [0x80ca1e6] #19 /usr/sbin/smbd(process_smb+0x1d6) [0x80ca505] #20 /usr/sbin/smbd(smbd_process+0x158) [0x80caff1] #21 /usr/sbin/smbd(main+0x769) [0x8200e5a] #22 /lib/libc.so.6(__libc_start_main+0xce) [0x402c9d3e] #23 /usr/sbin/smbd(strcpy+0x49) [0x80785b1]
On Wed, Aug 04, 2004 at 09:04:27AM +0200, Ulf Dettmer wrote:> Hi, > i have got a Samba server ( currently 3.0.5 ) together with CUPS 1.1.9. > running as a print server for a load of Windows 2000 / XP clients. This > setup worked well for several months until about three weeks ago ( > Samba 3.0.4 at that time ). Now all of a sudden i'm getting Samba > crashes for those clients that try to access the 'printers and faxes' on > the Samba server. In Windows the list of printers on the server > permanently refreshes, because Samba is crashing all the time. It is > still possible to print and even to upload drivers to the printers on > the Samba server but theses crashes are nonetheless very annoying. > I've already tried to delete the pdb's in /var/lock/samba to reset all > printing related information but that did not help. > Thanks for your help ! > Regards, Ulf Dettmer > > P.S. > This is a log entry of a typical 'printer panic'. Please mail me if you > need the whole level 5 log. > > [2004/08/04 07:59:22, 0] lib/fault.c:fault_report(36) > ==============================================================> [2004/08/04 07:59:22, 0] lib/fault.c:fault_report(37) > INTERNAL ERROR: Signal 11 in pid 19529 (3.0.5) > Please read the appendix Bugs of the Samba HOWTO collection > [2004/08/04 07:59:22, 0] lib/fault.c:fault_report(39) > ==============================================================> [2004/08/04 07:59:22, 0] lib/util.c:smb_panic2(1398) > PANIC: internal error > [2004/08/04 07:59:22, 0] lib/util.c:smb_panic2(1406) > BACKTRACE: 24 stack frames: > #0 /usr/sbin/smbd(smb_panic2+0x18c) [0x81a2830] > #1 /usr/sbin/smbd(smb_panic+0x10) [0x81a26a2] > #2 /usr/sbin/smbd [0x819263e] > #3 /usr/sbin/smbd [0x8192693] > #4 /lib/libc.so.6 [0x402ddbf8] > #5 /usr/sbin/smbd(_spoolss_rfnpcnex+0x19e) [0x8116ef1]I think this is something Jerry fixed in the SVN tree. Try out the 3.0.6rccXX releases later this week. They were delayed due to the security fixes on 3.0.5. Jeremy.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ulf Dettmer wrote: | #4 /lib/libc.so.6 [0x402ddbf8] | #5 /usr/sbin/smbd(_spoolss_rfnpcnex+0x19e) [0x8116ef1] Are you running a prerelease of XP sp2 on the client ? cheers, jerry - --------------------------------------------------------------------- Alleviating the pain of Windows(tm) ------- http://www.samba.org GnuPG Key ----- http://www.plainjoe.org/gpg_public.asc "If we're adding to the noise, turn off this song"--Switchfoot (2003) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBFaDsIR7qMdg1EfYRAiUhAJ9VRi5pgIf+CqULV1m4hcWdyhbtfwCdGPff e9RWbSu8A9M5Dh8ReZ+2v3w=WK50 -----END PGP SIGNATURE-----
Hi ! I've just installed Samba 3.0.6 RC2 and it's working again. Great work ! cheers, Ulf Ulf Dettmer schrieb:> Hi, > i have got a Samba server ( currently 3.0.5 ) together with CUPS 1.1.9. > running as a print server for a load of Windows 2000 / XP clients. This > setup worked well for several months until about three weeks ago ( > Samba 3.0.4 at that time ). Now all of a sudden i'm getting Samba > crashes for those clients that try to access the 'printers and faxes' on > the Samba server. In Windows the list of printers on the server > permanently refreshes, because Samba is crashing all the time. It is > still possible to print and even to upload drivers to the printers on > the Samba server but theses crashes are nonetheless very annoying. > I've already tried to delete the pdb's in /var/lock/samba to reset all > printing related information but that did not help. > Thanks for your help ! > Regards, Ulf Dettmer > > P.S. > This is a log entry of a typical 'printer panic'. Please mail me if you > need the whole level 5 log. > > [2004/08/04 07:59:22, 0] lib/fault.c:fault_report(36) > ==============================================================> [2004/08/04 07:59:22, 0] lib/fault.c:fault_report(37) > INTERNAL ERROR: Signal 11 in pid 19529 (3.0.5) > Please read the appendix Bugs of the Samba HOWTO collection > [2004/08/04 07:59:22, 0] lib/fault.c:fault_report(39) > ==============================================================> [2004/08/04 07:59:22, 0] lib/util.c:smb_panic2(1398) > PANIC: internal error > [2004/08/04 07:59:22, 0] lib/util.c:smb_panic2(1406) > BACKTRACE: 24 stack frames: > #0 /usr/sbin/smbd(smb_panic2+0x18c) [0x81a2830] > #1 /usr/sbin/smbd(smb_panic+0x10) [0x81a26a2] > #2 /usr/sbin/smbd [0x819263e] > #3 /usr/sbin/smbd [0x8192693] > #4 /lib/libc.so.6 [0x402ddbf8] > #5 /usr/sbin/smbd(_spoolss_rfnpcnex+0x19e) [0x8116ef1] > #6 /usr/sbin/smbd [0x810dacf] > #7 /usr/sbin/smbd(api_rpcTNP+0x200) [0x81386d9] > #8 /usr/sbin/smbd(api_pipe_request+0xd2) [0x8138459] > #9 /usr/sbin/smbd [0x8132a38] > #10 /usr/sbin/smbd [0x8132c14] > #11 /usr/sbin/smbd [0x8132e91] > #12 /usr/sbin/smbd [0x8133048] > #13 /usr/sbin/smbd(write_to_pipe+0xd7) [0x8132fcc] > #14 /usr/sbin/smbd [0x8089c35] > #15 /usr/sbin/smbd [0x8089e0e] > #16 /usr/sbin/smbd(reply_trans+0xb97) [0x808aa17] > #17 /usr/sbin/smbd [0x80ca154] > #18 /usr/sbin/smbd [0x80ca1e6] > #19 /usr/sbin/smbd(process_smb+0x1d6) [0x80ca505] > #20 /usr/sbin/smbd(smbd_process+0x158) [0x80caff1] > #21 /usr/sbin/smbd(main+0x769) [0x8200e5a] > #22 /lib/libc.so.6(__libc_start_main+0xce) [0x402c9d3e] > #23 /usr/sbin/smbd(strcpy+0x49) [0x80785b1] >
Possibly Parallel Threads
- failing to get AD users (getent passwd DMYDOM\a-sdettmer)
- failing to get AD users (getent passwd DMYDOM\a-sdettmer)
- Samba seem to work fine but "cannot find my workgroup"
- Is "vfs objects = acl_tdb" allowed?
- Samba seem to work fine but "cannot find my workgroup"