Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What should I do if jobs are getting stuck in the print queue even after restarting spooling?

$ stopsrc -g spooler
$ startsrc -g spooler
$ lpstat -oQUEUENAME | wc -l; sleep 30; lpstat -oQUEUENAME | wc -l

$ oslevel
share|improve this question
What status does the queue have? What status do the jobs in the queue have? – EightBitTony Jun 20 '11 at 23:07
queue=down; jobs=queued – LanceBaynes Jun 21 '11 at 5:51
if i cancel QUEUENAME; then enable QUEUENAME then the QUEUENAME is "ready" but if i print a test page on it it goes down :D? and the test page will be a "queued" job...and it stays there forever.. – LanceBaynes Jun 21 '11 at 5:52
I assume these are remote queues? Can the server ping the printer/device IP address? Is the printer actually on? – EightBitTony Jun 21 '11 at 6:42
ping is ok (0ms, because the ip is on one interface of the server) – LanceBaynes Jun 21 '11 at 7:44

What works in our systems is to disable the queue, make a copy of the print job, then cancel the queued job.

Once you then enable the queue, any other jobs in queue will process successfully. We then resubmit the print job that caused the hang.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.