Having an ongoing issue with the Printing. The server has 4 printers on it. 3 are Laniers one is an HP 4100. The problem with it is that the print jobs don''t go away, ever. Unless I manually clear the CUPS folder and restart cups and samba, the jobs never go away. Eventually, the queue fills up and people can no longer print. That is, until I clear it out as described above. To confuse things further, ONLY the Lanier printers (Lanier & Ricoh are the same company for those of you that didn''t know it) have this problem, the HP does not. I''ve changed rights, checked to see if "save jobs" is set (it''s not) and can''t seem to figure out the cause and/or solution to this problem. I''ve applied all of the updates for Centos 3.4 and still no fix. HELP!!!! Thanks Scott
On Fri, 2005-03-18 at 09:53, Scott Heisler wrote:> Having an ongoing issue with the Printing. The server has 4 printers on > it. 3 are Laniers one is an HP 4100. The problem with it is that the > print jobs don''t go away, ever. Unless I manually clear the CUPS folder > and restart cups and samba, the jobs never go away. Eventually, the > queue fills up and people can no longer print. That is, until I clear > it out as described above. To confuse things further, ONLY the Lanier > printers (Lanier & Ricoh are the same company for those of you that > didn''t know it) have this problem, the HP does not. I''ve changed > rights, checked to see if "save jobs" is set (it''s not) and can''t seem > to figure out the cause and/or solution to this problem. I''ve applied > all of the updates for Centos 3.4 and still no fix. > > HELP!!!!Ok, how are these printers rigged up? Are you using socket, lpd, ipp, etc for sending print jobs to the printers? Also, are the clients printing to them via samba? Does this happen when you try a job from the command line? Are the jobs actually printing?
Thanks for the reply.. Here is the answer to your questions: 1.) Printers are network printers setup via TCP on their assigned port 2.) Printers were setup first as Unix Raw printers from X-Windows using the print configuration tool 3.) Then printers were shared out via Samba. 4.) Jobs are printing fine until the queue reaches around 1000 jobs, then it tells the user that there''s no more disk space. There''s plenty of disk space but I think it''s a quantity issue, not a space issue On a side note, the problem appears to be more samba-related. Yesterday, if you looked at the printers from a Windows workstation, one printer had 1004 print jobs, another had 480, and the last had 120. The ones with 480 and 120 still worked. Anyway, when I went into the CUPS folder in /var/spool/cups, there were only 283 files in there. I deleted these files, restarted CUPS. The Windows workstations still saw the same number of jobs. I restarted Samba and ALL of the jobs went away and printing resumed for the main printer (the one with 1004 jobs). It takes the client 3-4 days to get to the 1000+ jobs point so it''s quite an issue. Thanks for any help! Scott -----Original Message----- From: centos-bounces@caosity.org [mailto:centos-bounces@caosity.org] On Behalf Of Kurt Bechstein Sent: Friday, March 18, 2005 9:03 AM To: CentOS discussion and information list Subject: Re: [Centos] Cups or Samba issue with print jobs On Fri, 2005-03-18 at 09:53, Scott Heisler wrote:> Having an ongoing issue with the Printing. The server has 4 printers > on it. 3 are Laniers one is an HP 4100. The problem with it is that > the print jobs don''t go away, ever. Unless I manually clear the CUPS > folder and restart cups and samba, the jobs never go away. > Eventually, the queue fills up and people can no longer print. That > is, until I clear it out as described above. To confuse things > further, ONLY the Lanier printers (Lanier & Ricoh are the same company> for those of you that didn''t know it) have this problem, the HP does > not. I''ve changed rights, checked to see if "save jobs" is set (it''s > not) and can''t seem to figure out the cause and/or solution to this > problem. I''ve applied all of the updates for Centos 3.4 and still nofix.> > HELP!!!!Ok, how are these printers rigged up? Are you using socket, lpd, ipp, etc for sending print jobs to the printers? Also, are the clients printing to them via samba? Does this happen when you try a job from the command line? Are the jobs actually printing? _______________________________________________ CentOS mailing list CentOS@caosity.org http://lists.caosity.org/mailman/listinfo/centos
this is an on-again off-again samba issue. There have been several threads about it. Check RHEL bugzilla for it. Scott Heisler wrote:> Thanks for the reply.. Here is the answer to your questions: > > 1.) Printers are network printers setup via TCP on their assigned port > 2.) Printers were setup first as Unix Raw printers from X-Windows using > the print configuration tool > 3.) Then printers were shared out via Samba. > 4.) Jobs are printing fine until the queue reaches around 1000 jobs, > then it tells the user that there''s no more disk space. There''s plenty > of disk space but I think it''s a quantity issue, not a space issue > > On a side note, the problem appears to be more samba-related. > Yesterday, if you looked at the printers from a Windows workstation, one > printer had 1004 print jobs, another had 480, and the last had 120. The > ones with 480 and 120 still worked. Anyway, when I went into the CUPS > folder in /var/spool/cups, there were only 283 files in there. I > deleted these files, restarted CUPS. The Windows workstations still saw > the same number of jobs. I restarted Samba and ALL of the jobs went > away and printing resumed for the main printer (the one with 1004 jobs). > > It takes the client 3-4 days to get to the 1000+ jobs point so it''s > quite an issue. > > Thanks for any help! > > > Scott > > > -----Original Message----- > From: centos-bounces@caosity.org [mailto:centos-bounces@caosity.org] On > Behalf Of Kurt Bechstein > Sent: Friday, March 18, 2005 9:03 AM > To: CentOS discussion and information list > Subject: Re: [Centos] Cups or Samba issue with print jobs > > On Fri, 2005-03-18 at 09:53, Scott Heisler wrote: > >>Having an ongoing issue with the Printing. The server has 4 printers >>on it. 3 are Laniers one is an HP 4100. The problem with it is that >>the print jobs don''t go away, ever. Unless I manually clear the CUPS >>folder and restart cups and samba, the jobs never go away. >>Eventually, the queue fills up and people can no longer print. That >>is, until I clear it out as described above. To confuse things >>further, ONLY the Lanier printers (Lanier & Ricoh are the same company > > >>for those of you that didn''t know it) have this problem, the HP does >>not. I''ve changed rights, checked to see if "save jobs" is set (it''s >>not) and can''t seem to figure out the cause and/or solution to this >>problem. I''ve applied all of the updates for Centos 3.4 and still no > > fix. > >>HELP!!!! > > > Ok, how are these printers rigged up? Are you using socket, lpd, ipp, > etc for sending print jobs to the printers? Also, are the clients > printing to them via samba? Does this happen when you try a job from > the command line? Are the jobs actually printing? > > > _______________________________________________ > CentOS mailing list > CentOS@caosity.org > http://lists.caosity.org/mailman/listinfo/centos > > _______________________________________________ > CentOS mailing list > CentOS@caosity.org > http://lists.caosity.org/mailman/listinfo/centos > . >-- Computer Housecalls, Networks, Security, Web Design: http://www.emmanuelcomputerconsulting.com My "Foundation" verse: Isa 54:17 No weapon that is formed against thee shall prosper; and every tongue that shall rise against thee in judgment thou shalt condemn. This is the heritage of the servants of the LORD, and their righteousness is of me, saith the LORD. -- carpe ductum -- "Grab the tape" CDTT (Certified Duct Tape Technician) Linux user #322099 Machines: 206822 256638 276825 http://counter.li.org/
Hmm, that is an interesting one. Only thing that comes to my mind is to setup the print command option in samba. If you are using cups something like the following should work. print command = lp -c -d%p -oraw; rm %s %p = corresponding printer name %s = spool file Check out this option in the man page to make sure it fits in your case, but basically it submits the job and then does the rm on the spool file automatically. Only thing I can think of off hand. I''ll post if I can come up with something else.
What version of SAMBA are you using? You also might want to look at the permissions on the spool directory and make sure they are set correctly. Karl Banasky Computer System Analyst Email kbanasky@heatcon.com
As per another message hereabouts, this is an issue that comes and goes according to what samba patches you have installed! It also seems to not happen on some systems at all. I have 4 servers running Centos 3.3 - the main one had this problem, it went away with a samba update and came back with another recent one! On the other hand, an old Gateway PIII-500 in another office has never had the problem. I don''t print to the other two systems. Here''s a response I got when I last posted about this in Feb: Sounds like this: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145639 which seems to be a samba bug introduced in 3.0.4 (?), still there in 3.0.9, and apparently fixed in 3.0.11 (or possibly cvs HEAD, not sure). There''s a patch on that bug report that seems to fix it for most people anyway - we''re about to try it on one of our RHEL3 boxes.