Our print server (linux 2.2.19, Debian unstable, with the 2.2.3a-6 package)
had a bit of trouble yesterday, and after getting everything back up and
working, printing is now broken. I can print from the commandline, but not
through samba.
From a 2000 client, I can see the printer shares, but can't ever actually
print to them ("Could not start print job.") If I open the server in
Network Neighbourhood, and browse the 'Printers' share, I get errors on
the
samba server (signal 11 in smbd), and can no longer access the server
without restarting samba -- "Remote Procedure call failed."
I can post the logs if need be, as well as the printer config, just
wondering if anyone has any ideas beforehand. I did a quick check through
the archives, but couldn't find anything.
We had some problems with printing and I had to delete the /var/cache/samba/printing.tdb file and then restart samba. Everything was fine after that. What clued me in was that the printing.tdb file was far larger than the other *.tdb files in the /var/cache/samba directory. You might check it. On Wed, 2002-04-24 at 14:20, Damian Gerow wrote:> Our print server (linux 2.2.19, Debian unstable, with the 2.2.3a-6 package) > had a bit of trouble yesterday, and after getting everything back up and > working, printing is now broken. I can print from the commandline, but not > through samba. > > From a 2000 client, I can see the printer shares, but can't ever actually > print to them ("Could not start print job.") If I open the server in > Network Neighbourhood, and browse the 'Printers' share, I get errors on the > samba server (signal 11 in smbd), and can no longer access the server > without restarting samba -- "Remote Procedure call failed." > > I can post the logs if need be, as well as the printer config, just > wondering if anyone has any ideas beforehand. I did a quick check through > the archives, but couldn't find anything. > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba-- =================================================================George Farris Computer Support Cowichan farrisg@mala.bc.ca Malaspina University-College A conclusion is simply the place where you got tired of thinking. ------- Electronic Frontier Foundation http://www.eff.org -------
At 01:44 PM 4/24/2002, George Farris wrote:>We had some problems with printing and I had to delete the >/var/cache/samba/printing.tdb file and then restart samba. Everything >was fine after that. > >What clued me in was that the printing.tdb file was far larger than the >other *.tdb files in the /var/cache/samba directory. > >You might check it.I've tried a complete uninstall and re-install of the samba packages, to no avail. Also just tried to delete it, and the same problem still happens, with a re-creation of printing.tdb (8k in size).
On Wed, 24 Apr 2002, Damian Gerow wrote:> Our print server (linux 2.2.19, Debian unstable, with the 2.2.3a-6 > package) had a bit of trouble yesterday, and after getting everything > back up and working, printing is now broken. I can print from the > commandline, but not through samba. > > From a 2000 client, I can see the printer shares, but can't ever > actually print to them ("Could not start print job.") If I open the > server in Network Neighbourhood, and browse the 'Printers' share, I get > errors on the samba server (signal 11 in smbd), and can no longer access > the server without restarting samba -- "Remote Procedure call failed."Check the level 10 debug log just before the crash (search for BUGS) and see if there is a reference to *SMBSERV[ER]. We fixed a bug related to this error logging just after the 2.2.3a release. You might want to try the SAMBA_2_2 cvs code (since you are running debian unstable anyways) :-) There's scripts for creating *.deb in packaging/debian/ cheers, jerry --------------------------------------------------------------------- Hewlett-Packard http://www.hp.com SAMBA Team http://www.samba.org -- http://www.plainjoe.org "Sam's Teach Yourself Samba in 24 Hours" 2ed. ISBN 0-672-32269-2 --"I never saved anything for the swim back." Ethan Hawk in Gattaca--
At 03:17 PM 4/24/2002, Gerald Carter wrote:>Check the level 10 debug log just before the crash (search for >BUGS) and see if there is a reference to *SMBSERV[ER]. We fixed >a bug related to this error logging just after the 2.2.3a release. >You might want to try the SAMBA_2_2 cvs code (since you are running debian >unstable anyways) :-) There's scripts for creating *.deb in >packaging/debian/On loglevel=10 and debuglevel=10, nothing shows up about SMBSERV(ER). But I'll co the current CVS code, and see if I can get the new version printing again. Thanks.
Do you also have LPRng installed on this box? Did you have to reinstall it? If so, look to see if the links between lpr, lpd, lpc, lprm, etc. in the LPRng install dir (/usr/local/bin, /usr/local/sbin on my OBSD box) and /usr/bin, /usr/sbin. If they weren't, I think you get similar problems. Jim> -----Original Message----- > From: Damian Gerow [mailto:damian@sentex.net] > Sent: Wednesday, April 24, 2002 2:20 PM > To: samba@lists.samba.org > Subject: [Samba] Printing troubles > > > Our print server (linux 2.2.19, Debian unstable, with the > 2.2.3a-6 package) > had a bit of trouble yesterday, and after getting everything > back up and > working, printing is now broken. I can print from the > commandline, but not > through samba. > > From a 2000 client, I can see the printer shares, but can't > ever actually > print to them ("Could not start print job.") If I open the server in > Network Neighbourhood, and browse the 'Printers' share, I get > errors on the > samba server (signal 11 in smbd), and can no longer access the server > without restarting samba -- "Remote Procedure call failed." > > I can post the logs if need be, as well as the printer config, just > wondering if anyone has any ideas beforehand. I did a quick > check through > the archives, but couldn't find anything. > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba >
I'm going to look into CVS'ing my current 2.2.3a box. I have several oddities that hopefully will be fixed with the updated code. Fingers crossed.... Jim> -----Original Message----- > From: Damian Gerow [mailto:damian@sentex.net] > Sent: Monday, April 29, 2002 8:21 AM > To: samba@lists.samba.org > Subject: RE: [Samba] Printing troubles > > > At 11:10 AM 4/29/2002, Van Sickler, Jim wrote: > >Do you also have LPRng installed on this box? Did you have to > >reinstall it? If so, look to see if the links between > >lpr, lpd, lpc, lprm, etc. in the LPRng install dir > >(/usr/local/bin, /usr/local/sbin on my OBSD box) and > >/usr/bin, /usr/sbin. If they weren't, I think you get > >similar problems. > > I probably should have posted this to the list, but upgrading > to the latest > CVS code fixed the trouble. > > Before I sent anything to the samba group, I went from LPRng > to straight > lpd to CUPS back to LPRng, checking binaries and purging all > configuration > between every change. > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba >
Source upgrade - I don't think there's a 2.2.3a package for OpenBSD 3.1 yet; I don't think I've got the expertise to build it for them...;-( Jim> -----Original Message----- > From: Damian Gerow [mailto:damian@sentex.net] > Sent: Monday, April 29, 2002 9:17 AM > To: Van Sickler, Jim > Subject: RE: [Samba] Printing troubles > > > At 12:14 PM 4/29/2002, Van Sickler, Jim wrote: > >I'm going to look into CVS'ing my current 2.2.3a box. > >I have several oddities that hopefully will be fixed > >with the updated code. > > > >Fingers crossed.... > > Are you doing a source upgrade, or building a package? >
So much for easy cvs...I'm behind a firewall/proxy. The cvs login goes okay, then aborts with "no route to host". Any idea how to make this work? Jim> -----Original Message----- > From: Damian Gerow [mailto:damian@sentex.net] > Sent: Monday, April 29, 2002 9:17 AM > To: Van Sickler, Jim > Subject: RE: [Samba] Printing troubles > > > At 12:14 PM 4/29/2002, Van Sickler, Jim wrote: > >I'm going to look into CVS'ing my current 2.2.3a box. > >I have several oddities that hopefully will be fixed > >with the updated code. > > > >Fingers crossed.... > > Are you doing a source upgrade, or building a package? >