1831275 Members
2937 Online
110022 Solutions
New Discussion

jetadmin spooler queues

 
SOLVED
Go to solution
jerry1
Super Advisor

jetadmin spooler queues

I had to move a
/var/spool/lp/request/
to
/var/spool/lp/request/.tmp
to debug a problem.
Now the jobs in the queue will not re-process
after moving them back into the new queue.

Does anyone know how to re-process these jobs.

lpstat does not see them anymore.
4 REPLIES 4
Kevin Wright
Honored Contributor

Re: jetadmin spooler queues

You may have to re-enable the printer to read the queue..just a thought.

enable printername

or if you can, restart lpshched.
A. Clay Stephenson
Acclaimed Contributor

Re: jetadmin spooler queues

First make absolutely certain that the owner and group are correct. The directory must be owner lp and group lp with 755 permissions.
That should be enough to fix you although your may need to issue an "enable printername" command. I would also issue an "accept printername" command. If that doesn't work then do an lpshut and an lpsched. Finally, examine /var/spool/lp/log for any messages after issueing another lp command.

If it ain't broke, I can fix that.
Mark Grant
Honored Contributor
Solution

Re: jetadmin spooler queues

Alternatively just re-submit them, after all, you have the thing to be printed in your .tmp directory.

If you do this, there is a small file of similar name to the print, for each print which you can safely delete. Just "lp -d "
Never preceed any demonstration with anything more predictive than "watch this"
jerry1
Super Advisor

Re: jetadmin spooler queues

Thanks for the help guys.

I had tried enable, disable, accept. no go.
I unfortunatly cannot do an lpshut lpsched
on the production system with some 200+ printers. That would not be good.
I didn't think of resubmitting them though.
I will have to keep that one in mind.

The short of it is. The next day they were
all gone. ???