On occasion, we get a printer that becomes disabled, and jobs begin to queue up. When the issue is resolved, we re-enable the printer and usually all the jobs print out.
However, sometimes the first job never prints, but the others do. The cups interface shows the job is stopped. IfI restart the job in the cups interface, it prints.
Is there a way to determine, via the command line, if a print job is in the stopped state, or a queue has jobs in this state. Also, is there a way to restart the job if its stopped.
We are running centos 5.3 and cups 1.3.7. Any help would be appreciated.
_____________________________________ "He's no failure. He's not dead yet." William Lloyd George
At Wed, 12 Aug 2009 16:00:17 -0400 CentOS mailing list centos@centos.org wrote:
Content-Class: urn:content-classes:message
On occasion, we get a printer that becomes disabled, and jobs begin to queue up. When the issue is resolved, we re-enable the printer and usually all the jobs print out.
However, sometimes the first job never prints, but the others do. The cups interface shows the job is stopped. IfI restart the job in the cups interface, it prints.
Is there a way to determine, via the command line, if a print job is in the stopped state, or a queue has jobs in this state. Also, is there a way to restart the job if its stopped.
lpstat -- printer, queue, and job status lp -- queue or alter print jobs cancel -- cancels print jobs
Documentation is available:
man lpstat man lp man cancel
We are running centos 5.3 and cups 1.3.7. Any help would be appreciated.
"He's no failure. He's not dead yet." William Lloyd George
MIME-Version: 1.0
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Thanks for the help. There is a way to get the information, but its ugly. Was hoping for a more straight forward method.
If a printer is down, I can us lpstat -l printer name to determine if a job is stopped, but I could not figure out a way to easily determine the status of jobs in the queue, such as stopped, processing, queued.
_____________________________________ "He's no failure. He's not dead yet." William Lloyd George -----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Robert Heller Sent: Wednesday, August 12, 2009 6:12 PM To: CentOS mailing list Cc: CentOS@centos.org Subject: Re: [CentOS] cups / cli stopped print jobs problem
At Wed, 12 Aug 2009 16:00:17 -0400 CentOS mailing list centos@centos.org wrote:
Content-Class: urn:content-classes:message
On occasion, we get a printer that becomes disabled, and jobs begin to queue up. When the issue is resolved, we re-enable the printer and usually all the jobs print out.
However, sometimes the first job never prints, but the others do. The cups interface shows the job is stopped. IfI restart the job in the
cups
interface, it prints.
Is there a way to determine, via the command line, if a print job is
in
the stopped state, or a queue has jobs in this state. Also, is there
a
way to restart the job if its stopped.
lpstat -- printer, queue, and job status lp -- queue or alter print jobs cancel -- cancels print jobs
Documentation is available:
man lpstat man lp man cancel
On Thu, Aug 13, 2009 at 9:51 AM, Blackburn, Marvin mblackburn@glenraven.com wrote:
Thanks for the help. There is a way to get the information, but its ugly. Was hoping for a more straight forward method.
If a printer is down, I can us lpstat -l printer name to determine if a job is stopped, but I could not figure out a way to easily determine the status of jobs in the queue, such as stopped, processing, queued.
I have the same problem.
Run
lpq
to see the status of the jobs.
lprm #job
to remove print #job.
This does not help, however, to understand why the printer just randomly stops printing. I have noticed that pdflatex seems to generate some pdf files that Evince cannot print, but Adobe acroread can open & print them. My working hypothesis is that Evince or the gtk print interface or CUPS fail on one of these jobs from Evince, and then the whole print regime is hung. If you have ideas, I'd be delighted to hear it.
pj