[HPADM] Fwd: RE: [SUMMARY] Re: lp spooler hung on specific queue

Thanks all. Most of the replies are 'YES'. However the tricky issue is to get the correct driver to work work with JetDirect LPSpooler software. When add a non-hp printer to the LPspooler queue, JetDirect software will not recognize non-hp printers. We have to work around to get the correct genetic driver for it. Thanks again.

Ben


From: Ben Le [mailto:ble@xxxxxxx]
Sent: Tuesday, December 13, 2005 9:12 AM
To: hpux-admin@xxxxxxxxxxxxx
Subject: [HPADM] Re: lp spooler hung on specific queue

Hi List,

In addition to Connie's comment, I have another question that related to HP-UX LPSpooler. My IT team is debating whether or not we have to use HP network printer to work with LPSpooler? At the current, we use HP printers for our network production printing through DNS. Some departments have decided to go with non-HP printers. Will non-HP printers work with HP-UX LPSpooler (lp command)? Thanks.

Ben

At 07:09 AM 12/13/2005, Connie.Zolg@xxxxxxxx wrote:

Thanks to David Lodge, Marc Ahrendt, Dan Zucker, Bill Hassel, Jeff Lightner, Kevin O'Donovan, Allan Marillier <grin>

We have officially requested that the outsourcers install an external JetDirect card on any printer that they are using for our application.
Also, I have created additional queues for the same printer to use until they get this done.

Thanks all for your input - it was very helpful!

Thanks ...

Connie Zolg
Dana Corporation
Global Information Technology Group
connie.zolg@xxxxxxxx
419.482.2158
419.367.2827  (cell)


Connie.Zolg@xxxxxxxx
Sent by: hpux-admin-owner@xxxxxxxxxxxxx

12/09/2005 10:44 AM
To
hpux-admin@xxxxxxxxxxxxx
cc
Subject
[HPADM] lp spooler hung on specific queue





We are running HPUX 11.0 and are having issues with the lp spooler. When a large number of reports go to a specific queue, it hangs.  I have checked kernel parms (maxuprc, nproc, nfile, ninode) and all seem to be plenty large enough. The user disables/enables this particular queue fairly frequently when it stops printing - usually works. About once a week it doesn't. We end up moving the reports to a disabled queue, then moving everything in /var/spool/lp/request/queueid  to another server and printing them in groups of about 100. If we try to print everything at once, it hangs there also.

This appears to be a volume problem, but we can't find anything more to change in the system in order to accomodate this large volume of reports (there were around 800 the last time it "broke".)
Suggestions to the user:
 - don't put thru so many at once - they can't seem to control this
 - get more printers to split up the load -  we can't force this - it's an application that has been outsourced to someone else, although we are still supporting the server that it runs on.

Any suggestions would be greatly appreciated.

Thanks ...

Connie Zolg
Dana Corporation
Global Information Technology Group
connie.zolg@xxxxxxxx
419.482.2158
419.367.2827  (cell)

__________________________________________________Benjamin Le
Sr. Systems Administrator
Technology Solutions Services
Portland Community College http://www.pcc.edu
Voice:(503)-977-4736   Fax:(503)-977-8124

__________________________________________________
Benjamin Le
Sr. Systems Administrator
Technology Solutions Services
Portland Community College http://www.pcc.edu
Voice:(503)-977-4736   Fax:(503)-977-8124