I have experienced this too... lpc kill usually gets the queue going again, but as you can imagine is not the solution. I'm hoping tat upgrading will solve the problem, but yes I have definitely seen it... It seems more prone to occuring on load-banlance queues. Have you noticed that as well?
---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | | Ryan Novosielski - Jr. UNIX Systems Admin |$&| |__| | | |__/ | \| _| | [EMAIL PROTECTED] - 732/235.4473 (5-4473) \__/ Univ. of Med. and Dent. | IST/ACS - Robert Wood Johnson MS - S-B11 On Wed, 10 Oct 2001 [EMAIL PROTECTED] wrote: > Hi All. :) > > We're running LPRng version 3.7.4 on RedHat (7.0 or thereabouts) > > We have a somewhat complicated printcap file, with various queues > bouncing to other queues, and a couple doing splitting for load- > balancing. > > (I think that all works okay, but if you think it's relevant, I > can send large chunks of the printcap file.) > > We also run a homegrown accounting system using postgres, which > has been fine for a long time. > > My PROBLEM (which is not limited to the more complicated queues): > > Some of the print queues have started "hanging". lpq shows: > Printer: prl4 is prl4.raw@localhost > Printer: prl4.raw@print 'HP LaserJet 4000TN, RC-4092' > Queue: 2 printable jobs > Server: pid 23980 active > Filter_status: (of) done at 17:07:41.897 > Rank Owner/ID Class Job Files Size Time > 1 yvonne@george+612 A 612 prl4_out_of_order 2589 09:31:21 > > lpc: > lpc>status prl4 > Printer Printing Spooling Jobs Server Subserver Redirect Status/(Debug) > prl4.raw@print enabled enabled 2 23980 none > > The queue refuses to go "active" regardless of lpc stop/disable/enable/starts. > Another one was slightly less stubborn, and eventually re-activates after > an arbitrary number of lpc commands. This problem was new on Friday, when > I made some changes to the printcap file, which affected one of the printers > but not the other. > > Has anyone seen this? Related to a bug in this version of lprng? Config > error? > > Some interesting stuff from the logs: > > /var/log/messages: > ... (Server)[22908]: prl3: Open_gdbm: cannot lock 'db.prl3' - Interrupted system call > ... (Worker - Print)[1264]: pr07.raw: Wait_for_pid: OF filter died with signal >'Hangup' > > /lpd/prm020/log: (this one does load-balancing) > ... prm020.raw: Open_dgbm: open of DB file 'db.prm020.raw' failed, File open >error(plus the Open_gdbm one here too) > > None of these errors appear directly related - they appeared during the > time I was making changes and testing, but have gone again. > > > > Thanks in advance > Glen > > -- > Glen Davison [EMAIL PROTECTED] > Computer System Administrator phone: +61 2 9385 7018 > Maths, UNSW fax: +61 2 9385 7123 > > ----------------------------------------------------------------------------- > YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST > The address you post from MUST be your subscription address > > If you need help, send email to [EMAIL PROTECTED] (or lprng-requests > or lprng-digest-requests) with the word 'help' in the body. For the impatient, > to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] > with: | example: > subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED] > unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED] > > If you have major problems, send email to [EMAIL PROTECTED] with the word > LPRNGLIST in the SUBJECT line. > ----------------------------------------------------------------------------- > ----------------------------------------------------------------------------- YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST The address you post from MUST be your subscription address If you need help, send email to [EMAIL PROTECTED] (or lprng-requests or lprng-digest-requests) with the word 'help' in the body. For the impatient, to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] with: | example: subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED] unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED] If you have major problems, send email to [EMAIL PROTECTED] with the word LPRNGLIST in the SUBJECT line. -----------------------------------------------------------------------------
