[SLE] deleting failed print jobs from queue.
my bjc1000 was working fine for 2 days, then for no explicable reason, does nothing. no matter what i try to do to get rid of failed printjobs in the queue they keep popping back up. i try uninstalling plp, aps disconnecting printer cable, shutting down, restarting, reinstalling plp & aps, then make new printer settings in yast, shutting down, reconnect cable, restarting... the printjobs still stay. tried that several times, doing something different every time. never had the problems of deleting the failed printjobs with my old bjc250, now using bjc1000. any alternative ideas to wiping out the old queues? -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
bleury wrote:
any alternative ideas to wiping out the old queues?
Did you try lprm? Nick -- -------------------------------------------------- Nick Zentena "Microsoft has unjustifiably jeopardized the stability and security of the operating system." U.S. District Judge Thomas Penfield Jackson Nov 5/1999 -------------------------------------------------- -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
yes, and it doesn't remove them. i have over 20 jobs built up, all with the number 0. Nick Zentena wrote:
bleury wrote:
any alternative ideas to wiping out the old queues?
Did you try lprm?
Nick
-- -------------------------------------------------- Nick Zentena "Microsoft has unjustifiably jeopardized the stability and security of the operating system." U.S. District Judge Thomas Penfield Jackson Nov 5/1999 --------------------------------------------------
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
lpq -P queue Printer 'queue' does not exist! lprm -P queue # lpr: fatal error: no printcap entry for printer queue. but there is! in rc: start_lpd=yes though in klpq it many lines of jobs all #'ed zero. bleury wrote:
yes, and it doesn't remove them. i have over 20 jobs built up, all with the number 0.
lpq
Nick Zentena wrote:
bleury wrote:
any alternative ideas to wiping out the old queues?
Did you try lprm?
Nick
-- -------------------------------------------------- Nick Zentena "Microsoft has unjustifiably jeopardized the stability and security of the operating system." U.S. District Judge Thomas Penfield Jackson Nov 5/1999 --------------------------------------------------
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
bleury wrote:
lpq -P queue Printer 'queue' does not exist!
lprm -P queue # lpr: fatal error: no printcap entry for printer queue.
but there is!
in rc: start_lpd=yes
though in klpq it many lines of jobs all #'ed zero.
Here's something Jim Hatridge sent me once that proved helpful: Problems There are very few things that can go wrong when printing a file. Most of your headaches will come when you are first setting up your printer system. As normal at times you will need to stop a print job. If it is still in the print que it is no problem at all. If it is still in the que you can type "lprm" this will remove the active job. Using the "-" option (i.e. lprm -) it will remove all of your print jobs in the que. By adding the job number (i.e. lprm 10) it will only delete that one. It should be noted that only the uperuser (ie root) can delete the whole que or someone else's print jobs. The big problem comes in when you have a large print job to delete and lpq (the que) says it's empty. As long as lpq says it's empty lprm will not work, remember it only works on the que. What to do when the que is empty? First turn off the printer to save paper and ink. Normally this will not cause any errors on the monitor. You may get an out-of-paper or printer-offline error in /var/log/messages file, no problem. Now try the lpc command. Using the "lpc clean all" command with option will delete all unprintable jobs with their data and control files. Unfortunately this only works if the files were bad to begin with. If they are fine, you just changed your mind, then we have problems. The final solution is to go into the spool and delete the files by hand. As root cd over to /var/spool, when you list the files you will find at least 3 difference dir's for each printer. There is one dir for the printer's ascii files, one for the PS files, and one for raw data. Now cd to the correct dir, in this dir you should find two files for each print job one fd00000000 and the other cd00000000. The first is the data file, ie what you wanted printed and the other is the control file, ie how you wanted it printed. Both of these must be deleted, "rm cd00000000". While in this dir you should find a lock file, delete it. This should clear your print job out of the system. Now to be on the safe side, in root do "lpc restart all". This will start new daemons and clear any old files out of each print pool. At this point put your printer back on line. It should print a few more lines, whatever was in it's buffer and then top. You will need to reset it. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
this bjc1000 doesn't even have a power button. though it doesn't throw paper, like some do. i think it's in the buffer and won't leave. tried everything i can think of for 20 hours plus. tried many things the var/spool files, and no go. no matter how many times i tell myself to install the whole darn thing- just can't do it. here now i crazy gone have and shall pulls the plug on this whole install. David Bellows wrote:
bleury wrote:
lpq -P queue Printer 'queue' does not exist!
lprm -P queue # lpr: fatal error: no printcap entry for printer queue.
but there is!
in rc: start_lpd=yes
though in klpq it many lines of jobs all #'ed zero.
Here's something Jim Hatridge sent me once that proved helpful:
Problems
There are very few things that can go wrong when printing a
file. Most of your headaches will come when you are first setting
up your printer system.
As normal at times you will need to stop a print job. If it
is still in the print que it is no problem at all. If it is still
in the que you can type "lprm" this will remove the active job.
Using the "-" option (i.e. lprm -) it will remove all of your
print jobs in the que. By adding the job number (i.e. lprm 10) it
will only delete that one. It should be noted that only the
superuser (ie root) can delete the whole que or someone else's
print jobs.
The big problem comes in when you have a large print job to
delete and lpq (the que) says it's empty. As long as lpq says
it's empty lprm will not work, remember it only works on the que.
What to do when the que is empty?
First turn off the printer to save paper and ink. Normally
this will not cause any errors on the monitor. You may get an
out-of-paper or printer-offline error in /var/log/messages file,
no problem.
Now try the lpc command. Using the "lpc clean all" command
with option will delete all unprintable jobs with their data and
control files. Unfortunately this only works if the files were
bad to begin with. If they are fine, you just changed your mind,
then we have problems.
The final solution is to go into the spool and delete the
files by hand. As root cd over to /var/spool, when you list the
files you will find at least 3 difference dir's for each printer.
There is one dir for the printer's ascii files, one for the PS
files, and one for raw data. Now cd to the correct dir, in this
dir you should find two files for each print job one fd00000000
and the other cd00000000. The first is the data file, ie what you
wanted printed and the other is the control file, ie how you
wanted it printed. Both of these must be deleted, "rm
cd00000000". While in this dir you should find a lock file,
delete it. This should clear your print job out of the system.
Now to be on the safe side, in root do "lpc restart all". This
will start new daemons and clear any old files out of each print
spool. At this point put your printer back on line. It should
print a few more lines, whatever was in it's buffer and then
stop. You will need to reset it.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (3)
-
bfootdav@bellsouth.net
-
imagicra@azstarnet.com
-
zentena@hophead.dyndns.org