Print Queue Disappearing

DISCUSSION Peter 2 participants 3 messages Nov 15, 2002 – Nov 17, 2002

Share & tools

Peter

author

2002-11-15 06:42 UTC #0 lore raw

Hi,

In RH7.3 documents place for printing are being aborted after a certain time and if large documents are being printed printing suddenly stops. When then checking lpq it is empty which is annoying.

This is what I get with lpq at 10:03:
Printer: lpd1@philonline
Queue: 1 printable job
Server: pid 1164 active
Unspooler: pid 1165 active
Status: IF filter 'mf_wrapper' filter msg - 'foomatic-gswrapper: gs
'-dBATCH' '-dSAFER' '-dQUIET' '-dNOPAUSE' '-sDEVICE=epsonc' '-r180x180' '-sOutputFile=/dev/fd/3' '/dev/fd/0' 3>&1 1>&2' at 10:03:00.384
Rank Owner/ID Class Job Files Size Time
active pfheiss@philonline+163 A 163 (STDIN) 861984
10:02:59

and later at 11:43
Printer: lpd1@philonline
Queue: no printable jobs in queue
Server: no server active
Status: job 'pfheiss@philonline+163' error 'aborting operations' at
11:43:00.386
Rank Owner/ID Class Job Files Size Time
error pfheiss@philonline+163 A 163 ERROR: aborting operations

Why would that be? Is there somewhere a clock running to keep documents only so long in the print queue and if so can that be stopped. I found nothing in the HOWTO for printing.

Regards

Signature · 7 lines

Peter

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Ray Olszewski

2002-11-15 17:58 UTC #1 lore raw

I didn't see any other responses, so let me at least tell you that no, there is no "clock" aborting jobs.

What actually is going on is impossible to tell from what you reported, but I'd guess a communication failure between the host and the printer. Without a fairly complete description of the printing setup, I can't really suggest anything specific. If it only occurs with jobs that normally take a long time to print, I'd look for a problem involving interfaction between the printer's own memory and handshaking with the host.

But ... just how slow is this printer? The queue listing you report below says the job that fails is 861984 bytes, which isn't very big at all by today's standards ... yes it is long if it is straight text, but it is minuscule in memory requirements, and not much as a Postscript job. Is the printer really printing this job for an hour and 40 minutes before the problem occurs?

Quoted 27 lines · Peter

Hi,
In RH7.3 documents place for printing are being aborted after a certain time and if large documents are being printed printing suddenly stops. When then checking lpq it is empty which is annoying.
This is what I get with lpq at 10:03:
Printer: lpd1@philonline
Queue: 1 printable job
Server: pid 1164 active
Unspooler: pid 1165 active
Status: IF filter 'mf_wrapper' filter msg - 'foomatic-gswrapper: gs
'-dBATCH' '-dSAFER' '-dQUIET' '-dNOPAUSE' '-sDEVICE=epsonc' '-r180x180' '-sOutputFile=/dev/fd/3' '/dev/fd/0' 3>&1 1>&2' at 10:03:00.384
Rank Owner/ID Class Job Files Size Time
active pfheiss@philonline+163 A 163 (STDIN) 861984
10:02:59
and later at 11:43
Printer: lpd1@philonline
Queue: no printable jobs in queue
Server: no server active
Status: job 'pfheiss@philonline+163' error 'aborting operations' at
11:43:00.386
Rank Owner/ID Class Job Files Size Time
error pfheiss@philonline+163 A 163 ERROR: aborting operations

Quoted 3 lines

Why would that be? Is there somewhere a clock running to keep documents only so long in the print queue and if so can that be stopped. I found nothing in the HOWTO for printing.

--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski -- Han Solo
Palo Alto, California, USA [email protected]
-------------------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Peter

author

2002-11-17 03:26 UTC #2 lore raw

Quoted 6 lines · [email protected] said:

But ... just how slow is this printer? The queue listing you report below says the job that fails is 861984 bytes, which isn't very big at all by today's standards ... yes it is long if it is straight text, but it is minuscule in memory requirements, and not much as a Postscript job. Is the printer really printing this job for an hour and 40 minutes before the problem occurs

The file size does not matter. Even putting a 5Kb size document into the print queue will be aborted after less then 2 hours if not printed.
The mentioned text file of 861984 bytes has about 160 pages. My printer prints about 100 pages an hour of good reading quality (size 9, 110 col). Usually shortly after that printing stops and the print queue is empty. I then have to delete the printed portion to finish printing the rest by which the paginating starts at 1 again.

Here are some outputs of lpq. The print job 778 was from last night and checked this morning. It is aborting the operation and yet can be dequeued. On print job 305 when checked after 50 minutes the Status as well as the Rank had changed. On the Rank it seems to indicates that there is some clock running. After 70 min it says (4200 sec)

lpq
Printer: lpd1@philonline
Queue: 1 printable job
Server: pid 1306 active
Unspooler: pid 1307 active
Status: IF filter 'mf_wrapper' filter msg - 'closed *main::KID3' at
09:23:05.952
Rank Owner/ID Class Job Files Size Time

active pfheiss@philonline+305       A   305 /tmp/xedtmp_1303_0    4172 09:23:02
error  pfheiss@philonline+778       A   778 ERROR: aborting operations

lprm 778
Printer lpd1@philonline:
checking perms 'pfheiss@philonline+778'
dequeued 'pfheiss@philonline+778'

lpq
Printer: lpd1@philonline
Queue: 1 printable job
Server: pid 1306 active
Unspooler: pid 1307 active
Status: waiting for subserver to exit at 10:10:02.799
Rank Owner/ID Class Job Files Size Time
stalled(3157sec) pfheiss@philonline+305 A 305 /tmp/xedtmp_1303_0 4172 09:23:02

lpq
Printer: lpd1@philonline
Queue: 1 printable job
Server: pid 1306 active
Unspooler: pid 1307 active
Status: waiting for subserver to exit at 10:50:02.969
Rank Owner/ID Class Job Files Size Time
stalled(5691sec) pfheiss@philonline+305 A 305 /tmp/xedtmp_1303_0 4172 09:23:02

lpq
Printer: lpd1@philonline
Queue: no printable jobs in queue
Server: no server active
Status: job 'pfheiss@philonline+305' error 'aborting operations' at
11:03:05.964
Rank Owner/ID Class Job Files Size Time
error pfheiss@philonline+305 A 305 ERROR: aborting operations

lprm 305
Printer lpd1@philonline:
checking perms 'pfheiss@philonline+305'
dequeued 'pfheiss@philonline+305

Any explanations?

Regards