> From [EMAIL PROTECTED] Tue Sep 19 18:27:42 2000
> From: "Blom, Wayne" <[EMAIL PROTECTED]>
> To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
> Subject: LPRng: Subprocess stalling
> Date: Wed, 20 Sep 2000 09:57:23 +0930
>
> I am asking this question by way of covering all bases.
>
> Currently we have LPRng 3.6.19 installed. Everything seems to be working
> very well except one particular printer.
>
> This is a label printer hanging off a print server. There are a number of
> these but this particular one tends to lock up at least once per day,
> frequently more. There is no problem with the other printers in a similar
> configuration. There appears to be nothing wrong with the cabling, the
> printer (although we are going to swap that today), the printserver (we are
> going to swap this after the printer) or the processing.
>
> What we do find is that the subprocess has stalled. eg;
>
> root_# lpq -Pp-undrcv6
> Printer: lp68@u-underdale3 (dest pr1@ps-udale5) 'p-undrcv6'
> Queue: 17 printable jobs
> Server: pid 27426 active
> Unspooler: pid 27425 active
> Status: waiting for subserver to exit at 09:34:18.066
> Rank Owner/ID Class Job Files Size Time
> stalled(65219sec) root@u-underdale3+253 A 253 (stdin) 248
> 15:11:32
> 2 root@u-underdale3+825 A 825 (stdin) 273
> 15:16:49
> 3...
> 4...
> 5...
> 6...
> etc
>
> By killing the subprocess the jobs complete...
>
> root_# lpc status lp68
> Printer Printing Spooling Jobs Server Subserver Redirect
> Status/(Debug)
> lp68@u-underdale3 enabled enabled 17 27426 27425
> root_# kill -9 27425
>
> Leaving the process and resetting the printer and printserver does not clear
> it up, but after killing the subprocess a new one starts and the printing
> resumes.
>
> Are there any known issues with this version for this type of lock up? Any
> other suggestions?
>
> Thanks
> Wayne Blom
> System Specialist
> Technical Development Healthcare
> F H Faulding & Co Limited
> Ground Floor
> 1 Station St
> Hindmarsh SA 5007
> Ph: +61 8 8241 8334
> FAX: +61 8 8241 8357
> Mobile: +61 0419 808 496
> Email: [EMAIL PROTECTED]
This is usually the case with a filter process that does not exit.
There are several possibilities:
a) The filter is waiting for status back that it never gets,
and does not have a 'smart timeout' that will tell it to
give up.
b) The filter has done a 'close' on a socket but the socket does
not close. This is rare, but happens when you have set 'sock_linger'
to a long value OR the very bad 'wait forever' value.
c) You have a hardware device that has a low level device driver that does
not finish the close until it flushes its buffers.
What is the actual device?
What is your printcap?
What filter are you using?
Patrick Powell Astart Technologies,
[EMAIL PROTECTED] 9475 Chesapeake Drive, Suite D,
Network and System San Diego, CA 92123
Consulting 858-874-6543 FAX 858-279-8424
LPRng - Print Spooler (http://www.astart.com)
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
