On Thursday 10 May 2007, Les wrote: > On Thu, 2007-05-10 at 16:13 +0100, Anne Wilson wrote: > > On Thursday 10 May 2007, Aaron Konstam wrote: > > > On Thu, 2007-05-10 at 10:11 +0100, Anne Wilson wrote: > > > > On Wednesday 09 May 2007, Aaron Konstam wrote: > > > > > On Wed, 2007-05-09 at 20:45 +0100, Anne Wilson wrote: > > > > > > I sent a large print job to my file/print server, but > > > > > > unfortunately I had a paper jam after page 1. Since then I have > > > > > > not been able to print anything to that printer. The > > > > > > localhost:631 interface shows the printer as stopped, but I am > > > > > > not allowed to re-start it, despite the fact that I entered > > > > > > root's password. > > > > > > > > > > > > Is there any way out of this, or will I have to remove the > > > > > > printer and re-install it? > > > > > > > > > > > > Anne > > > > > > > > > > Have you tried lprm to remove the print file from the printer's > > > > > queue? > > > > > > > > I'd removed the print job, no problem with that, but the printer > > > > remains 'stopped' and cannot be re-started, because root doesn't have > > > > the permission to do that! > > > > > > Here is an abstract from the man lpadmin page. Maybe that info is > > > relevant to your problem. > > > > > > -E > > > Enables the printer and accepts jobs; this is the same as > > > running > > > the accept(8) or cupsaccept(8) and enable(8) or > > > cupsenable(8) programs on the printer. > > > > So, working as root, on the server: > > > > lpadmin [ -E ] [ -h server ] -p printer option(s) > > > > lpadmin -E -p Photo > > lpadmin: Unable to connect to server: Bad file descriptor > > > > and trying it on the local box: > > > > lpadmin -E -h borg.lydgate.lan -p Photo > > lpadmin: Unable to connect to server: Bad file descriptor > > > > Ideas? > > > > Anne > > Hi, Anne, > 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... > > 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 > 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. > > I don't even know where the printer descriptions are held, and never > thought to look. > I don't think I can blame an update this time. For one thing, the printer is on an FC4 box, so cups hasn't been updated for a long time. For another, I had actually completed the first page of the print when the paper-jam caused the problem. I'm reluctant to do the re-install of the printer, just because I hate being beaten :-) but I may have to. It worked last time I got into this sort of mess. Anne
Attachment:
pgprEiri3stjZ.pgp
Description: PGP signature
