These print jobs perchance aren't being piped through a postprocessing filter such as mpage are they?
We had massive problems here with excessive stall times (several hours) in a lab of 30 PCs with a LPRng machine servicing two HP 4MV's.
We finally tracked it down to a 'bestpath="$bestpath | mpage -2o' directive in the master filter, which was intended to force all print jobs to 2-up (orders from above). It did a pretty fine job too, until more than a few students started printing out several jobs simultaneously. Then the stalls began. Removing the mpage directive fixed it.
Good luck, Greg
Andrew Gray wrote:
We keep getting print jobs hanging up in our print queue. The original problem is caused by our HP 8150DNs doing that 79.00FE error stuff (which we still haven't found a solution for, but seems to be lessened by upgrading to the newest firmware and to the newest drivers, but it is not eliminiated).
The queue reports: Server Printer: [EMAIL PROTECTED] (dest [EMAIL PROTECTED]) (serving sage) Queue: 1 printable job Server: pid 2954 active Unspooler: pid 4236 active Status: sending data file 'dfA058A311G28' to [EMAIL PROTECTED] at 23:21:22.670 Filter_status: done at 23:19:21.830 Rank Owner/ID Class Job Files Size Time stalled(25971sec) irenavms A 58 flashnornand.pdf 315486 22:51:39 done sithlord A 19 http://www.carmforu 270137 22:40:59 Active connection from 131.216.22.15 lpd Service
Server Printer: [EMAIL PROTECTED] (dest [EMAIL PROTECTED]) (serving sage) Queue: 1 printable job Server: pid 882 active Unspooler: pid 883 active Status: sending str '^B121 cfA240A311G10' to [EMAIL PROTECTED] at 22:07:56.644 Filter_status: done at 22:05:56.624 Rank Owner/ID Class Job Files Size Time stalled(30354sec) [EMAIL PROTECTED] A 240 MATLAB 32696 22:05:55 done ezag A 238 MATLAB 33391 22:05:39 JetDirect lpd: no jobs queued on the port Raw
Now, I know what happened to both of these printers, and they were turned off and back on to reset them. Why on earth are the queues remaining stalled for hours upon hours on end? We have much shorter time-outs defined in the lpd.conf file:
# Purpose: stalled job timeout # default stalled_time=120 (INTEGER) stalled_time=60 # Purpose: timeout for read/write lpr IO operations # default send_job_rw_timeout=6000 (INTEGER) send_job_rw_timeout=120 # Purpose: exit linger timeout to wait for socket to close # default exit_linger_timeout=600 (INTEGER) exit_linger_timeout=60
It would seem to me it should be impossible for the queues to get hung up for more than a few minutes, but they are. This is with LPRng-3.8.6 (newer versions with the options we use cause the tools not to work) under Solaris 8 (fully patched).
--- Andrew Gray Systems Administrator University of Nevada, Las Vegas College of Engineering
-- ------------------------------------------------------------- Greg Trounson Programmer / Analyst Dept. of Maths and Stats, University of Otago PO. Box 56, Dunedin tel: 64-3-4797739 New Zealand ----------------=[ [EMAIL PROTECTED] ]=----------------
----------------------------------------------------------------------------- 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. -----------------------------------------------------------------------------
