Signed in as root, here is the output:
# lpstat -a
Queue Dev Status Job Files User PP % Blks
Cp Rnk
------- ----- --------- --- ------------------ ---------- ---- -- -----
--- ---
lp0 lp0 READY
par1 lp1 READY
lp3 lp3 READY
lp4 lp4 READY
lp5 lp5 RUNNING 851 STDIN.22776 jimmy 36 74 65
1 1
lp6 lp6 READY
I have tried the following:
cancel 851
cancel 75851
qcan -x 851
disable lp5
disable -c lp5
qadm -K lp5:lp5
qpri -# 851 -a 18
I am unable to change anything about this.
Suggestions?
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
Try :
stopsrc -s qdaemon
rm /var/spool/lpd/qdir/*
rm /var/spool/qdaemon/*
startsrc -s qdaemon
Marcelo Veiga
Before you do this, you might NOT want to clear out all of
/var/spool/lpd/qdir. You will end up trashing all print jobs that exist
on the system. You should be able to just remove the file(s) with lp5
in the filename. If you want to preserve the other jobs in the lp5
queue then rm the file with the oldest date with lp5 as part of the
name.
I assume that there is a problem with the printer hardware. Usually AIX
won't hold onto a job like it did unless it can't get to the device. I
imagine the printer was disconnected, turned off or has a bad cable.
-- Walsh
--
Walsh Brown
Sometimes I sit and think...sometimes I just sit.
> Signed in as root, here is the output:
> # lpstat -a
> Queue Dev Status Job Files User PP % Blks
> Cp Rnk
> ------- ----- --------- --- ------------------ ---------- ---- -- -----
> --- ---
> lp0 lp0 READY
> par1 lp1 READY
> lp3 lp3 READY
> lp4 lp4 READY
> lp5 lp5 RUNNING 851 STDIN.22776 jimmy 36 74 65
> 1 1
> lp6 lp6 READY
> I have tried the following:
> cancel 851
> cancel 75851
> qcan -x 851
> disable lp5
> disable -c lp5
> qadm -K lp5:lp5
> qpri -# 851 -a 18
> I am unable to change anything about this.
You cannot change a job unless you are a) the owner of the job, b) a member
of the printq group, or c) root. You cannot change a printer unless you
are b) or c).
Chris Mattern
qcan, cancel, etc. just turn around and invoke enq so there may be some
benefit to bypassing the "middleman". What cancelling does is sends a
SIGTERM to the print queue's backend program so a job not cancelling might
mean the backend program for that queue is trapping that signal.
Best regards,
Paul
Walsh Brown wrote:
> In article <7k6fof$218$1...@nnrp1.deja.com>,
> mve...@my-deja.com wrote:
> > In article <7k67pu$ugq$1...@nnrp1.deja.com>,
I have also had bad luck with 'stopsrc' in the past because it wouldn't
restart subsequently and I had to reboot. I did not, however, nix the
bad print queue jobs after running 'stopsrc' (with the appropriate
parameters, of course). I'll try that should the need arise again in
the future.
Yes, the queue would probably be in the DOWN state, BUT if the problem
occured during the printing of the job, then it would stay RUNNING. Now
that I am thinking about it, what type of flow control are you using on
the printer? Maybe your printer is sending a "flow stop" (dropping a
line or sending an xoff) and not sending a "flow start" to the port.
Maybe the printer is using xon/xoff flow control and a xoff gets
inadvertantly sent through the data stream and causes the printer to
stop and wait for a corresponding xon. Does this problem seem to occur
on longer running print jobs? Is it always specific to this lp port or
does it happen, at one time or another, to all of your lp ports? What
type of printer is it (line, laser or plotter?) and how is it connected
(serially or parallel)?
Just some thoughts...
-- Walsh
--
Walsh Brown
Sometimes I sit and think...sometimes I just sit.
Good luck,
Mike Wig
Karl Jones <kjo...@dbs1.com> wrote in article
<7k67pu$ugq$1...@nnrp1.deja.com>...
> In AIX 4.3, I have a job which lpstat shows as running.
>
> Signed in as root, here is the output:
> # lpstat -a
> Queue Dev Status Job Files User PP % Blks
> Cp Rnk
> ------- ----- --------- --- ------------------ ---------- ---- -- -----
> --- ---
> lp0 lp0 READY
> par1 lp1 READY
> lp3 lp3 READY
> lp4 lp4 READY
> lp5 lp5 RUNNING 851 STDIN.22776 jimmy 36 74 65
> 1 1
> lp6 lp6 READY
>
> I have tried the following:
> cancel 851
> cancel 75851
> qcan -x 851
> disable lp5
> disable -c lp5
> qadm -K lp5:lp5
> qpri -# 851 -a 18
>
> I am unable to change anything about this.
>
> Suggestions?
Walsh Brown wrote:
> In article <7k6fof$218$1...@nnrp1.deja.com>,
> mve...@my-deja.com wrote:
> > In article <7k67pu$ugq$1...@nnrp1.deja.com>,
> > Try :
> >
> > stopsrc -s qdaemon
> > rm /var/spool/lpd/qdir/*
> > rm /var/spool/qdaemon/*
> > startsrc -s qdaemon
> >
> > Marcelo Veiga
> >
> > Sent via Deja.com http://www.deja.com/
> > Share what you know. Learn what you don't.
> >
>
> Before you do this, you might NOT want to clear out all of
> /var/spool/lpd/qdir. You will end up trashing all print jobs that exist
> on the system. You should be able to just remove the file(s) with lp5
> in the filename. If you want to preserve the other jobs in the lp5
> queue then rm the file with the oldest date with lp5 as part of the
> name.
>
> I assume that there is a problem with the printer hardware. Usually AIX
> won't hold onto a job like it did unless it can't get to the device. I
> imagine the printer was disconnected, turned off or has a bad cable.
>
> -- Walsh
>
> --
> Walsh Brown
>
> Sometimes I sit and think...sometimes I just sit.
>
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.
I had a similar problem with 4.3 with one of our printers. Occasionally I
wouldn't be able to cancel a print job. Got ahold of IBM and they had me
change the flow control on the system and on the printer from xon/xoff to
dtr. You might want to give that a try if it is an option.
MARK