Cant remove printer jobs 2

[Nostradamus]

I´m new to Sco and unix as a whole. This is probably easy fixed.<br>I have an axis print server and a laser printer attached.<br>A user reported difficulties printing.<br>I examined scoadmin:s printer jobs.<br>this is what i found... <br>&nbsp;Job ID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Queue&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Owner&nbsp;&nbsp;&nbsp;&nbsp;Size&nbsp;&nbsp;&nbsp;&nbsp;<br>---------------------------------------------------------------<br>*9laser_q-30897&nbsp;&nbsp;failed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;m031&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5019&nbsp;&nbsp;&nbsp;&nbsp;<br>&nbsp;9laser_q-30898&nbsp;&nbsp;failed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;m031&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5031&nbsp;&nbsp;&nbsp;&nbsp;<br>&nbsp;9laser_q-30900&nbsp;&nbsp;failed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;m031&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5102&nbsp;&nbsp;&nbsp;&nbsp;<br><br>below was several jobs listed.<br>I ran ps - A to see if it helped to do a kill -HUP on the printerdeamon. When I did... all the jobs except the ones above where being printed. I tried deleting the jobs above in scoadmin, but received a rather funny error message. I couldnt delete them since it was to late to do anything <br>Now I wonder... How can I get rid of them?<br>the users can print out regardless but it is rather annoying. Do this jobs affect system performance in any way?

 

[AndyBo]

Rather than sending a kill -HUP, try running (as root) <FONT FACE=monospace>/usr/lib/lpshut</font> followed by <FONT FACE=monospace>/usr/lib/lpsched</font>.&nbsp;&nbsp;This will stop and then restart the printer daemon, and is usually a cleaner way of restarting lp.<br><br>As far as performance goes, these &quot;stuck&quot; jobs shouldn't have any effect.&nbsp;&nbsp;However, we want to get rid of them because, like you say, it is a bit annoying <br><br>The first thing I would do is to try and manually cancel the print jobs.&nbsp;&nbsp;Login as root and use <FONT FACE=monospace>cancel <i>jobid</i></font>.<br><br>If that doesn't work, then there is a problem elsewhere.&nbsp;&nbsp;What is the error message you receive when you try to cancel the print jobs?&nbsp;&nbsp;This will help to give a more accurate answer to the problem.<br><br>Let us know how you get on. <p> <br><a href=mailto: > </a><br><a href= > </a><br>--<br>
0 1 - Just my two bits

 

[Nostradamus]

AndyBo... you are the man! <br>lpshut and lpsched did the work.<br>I never tried the cancel command first though... <br>I know I´ve seen this error once before so it might pop up again. If it does, I´ll &quot;cancel&quot; it. <br><br><br>my mysterious error message...<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Unable to delete job(s).&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br>----------------------------------------------<br>[&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;OK&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;]&nbsp;&nbsp;[ Details... ]&nbsp;&nbsp;[&nbsp;&nbsp;&nbsp;&nbsp;Help&nbsp;&nbsp;&nbsp;&nbsp;]<br><br>under details it said... <br><br>Unable to delete job(s).&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br>UX:cancel: WARNING: Request &quot;9laser_q-30897&quot; is do<br>TO FIX: It is too late to do anything <br><br>You don´t know what could have caused this? <br>Perhaps I can prevent it from happening again.

 

[AndyBo]

The &quot;cancel&quot; command will be what scoadmin was trying to run.&nbsp;&nbsp;It's just that I like folks to know what's going on with their systems, hence the suggestion to run it as root <br><br>The error message is coming from the cancel command being run by scoadmin.&nbsp;&nbsp;For some reason, probably because the lpsched process had got itself confused somehow, &quot;cancel&quot; was not able to cancel the print job.&nbsp;&nbsp;It was probably asking &quot;lpsched&quot; to stop the job and &quot;lpsched&quot; was refusing.<br><br>Stopping and re-starting lpsched using &quot;lpshut&quot; and &quot;lpsched&quot; caused &quot;lpsched&quot; to re-assess exactly where it was at with it's print queues.&nbsp;&nbsp;This cleaned up any problem there may have been, and &quot;cancel&quot; was able to do it's job.<br><br>As to what caused the problem, I've seen this occur many times when a single print job has been cancelled, and that print job was destined for a network printer.&nbsp;&nbsp;When the print job was cancelled, the temporary are that stores network printer jobs is deleted, and you can't do anything else with it...&nbsp;&nbsp;The System V lp system doesn't seem to handle network printers very well.<br><br>I don't know if this was your problem, but it seems similar.<br><br>Anyway, glad it worked <p> <br><a href=mailto: > </a><br><a href= > </a><br>--<br>
0 1 - Just my two bits