<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.12.3">
</HEAD>
<BODY>
On Thu, 2007-05-10 at 16:13 +0100, Anne Wilson wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">On Thursday 10 May 2007, Aaron Konstam wrote:</FONT>
<FONT COLOR="#000000">> On Thu, 2007-05-10 at 10:11 +0100, Anne Wilson wrote:</FONT>
<FONT COLOR="#000000">> > On Wednesday 09 May 2007, Aaron Konstam wrote:</FONT>
<FONT COLOR="#000000">> > > On Wed, 2007-05-09 at 20:45 +0100, Anne Wilson wrote:</FONT>
<FONT COLOR="#000000">> > > > I sent a large print job to my file/print server, but unfortunately I</FONT>
<FONT COLOR="#000000">> > > > had a paper jam after page 1. Since then I have not been able to</FONT>
<FONT COLOR="#000000">> > > > print anything to that printer. The localhost:631 interface shows</FONT>
<FONT COLOR="#000000">> > > > the printer as stopped, but I am not allowed to re-start it, despite</FONT>
<FONT COLOR="#000000">> > > > the fact that I entered root's password.</FONT>
<FONT COLOR="#000000">> > > ></FONT>
<FONT COLOR="#000000">> > > > Is there any way out of this, or will I have to remove the printer</FONT>
<FONT COLOR="#000000">> > > > and re-install it?</FONT>
<FONT COLOR="#000000">> > > ></FONT>
<FONT COLOR="#000000">> > > > Anne</FONT>
<FONT COLOR="#000000">> > ></FONT>
<FONT COLOR="#000000">> > > Have you tried lprm to remove the print file from the printer's queue?</FONT>
<FONT COLOR="#000000">> ></FONT>
<FONT COLOR="#000000">> > I'd removed the print job, no problem with that, but the printer</FONT>
<FONT COLOR="#000000">> > remains 'stopped' and cannot be re-started, because root doesn't have the</FONT>
<FONT COLOR="#000000">> > permission to do that!</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">> Here is an abstract from the man lpadmin page. Maybe that info is</FONT>
<FONT COLOR="#000000">> relevant to your problem.</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">> -E</FONT>
<FONT COLOR="#000000">> Enables the printer and accepts jobs; this is the same as</FONT>
<FONT COLOR="#000000">> running</FONT>
<FONT COLOR="#000000">> the accept(8) or cupsaccept(8) and enable(8) or</FONT>
<FONT COLOR="#000000">> cupsenable(8) programs on the printer.</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">So, working as root, on the server:</FONT>
<FONT COLOR="#000000">lpadmin [ -E ] [ -h server ] -p printer option(s)</FONT>
<FONT COLOR="#000000">lpadmin -E -p Photo</FONT>
<FONT COLOR="#000000">lpadmin: Unable to connect to server: Bad file descriptor</FONT>
<FONT COLOR="#000000">and trying it on the local box:</FONT>
<FONT COLOR="#000000">lpadmin -E -h borg.lydgate.lan -p Photo</FONT>
<FONT COLOR="#000000">lpadmin: Unable to connect to server: Bad file descriptor</FONT>
<FONT COLOR="#000000">Ideas?</FONT>
<FONT COLOR="#000000">Anne</FONT>
</PRE>
</BLOCKQUOTE>
Hi, Anne,<BR>
This happened to me after an update. I had to delete and recreate the printer to get it working again, and even then I had to reboot to make it start working... <BR>
<BR>
Who knows. I got no useful messages from the logs other that messages about the bad file descriptor like you have here. I suspect that a change in CUPS <BR>
forced a modification to the file descriptor that CUPS uses to identify the printer, but the update never updated the description file. Deleting and recreating the printer entry did.<BR>
<BR>
I don't even know where the printer descriptions are held, and never thought to look.<BR>
<BR>
Regards,<BR>
Les H
</BODY>
</HTML>