GaryWilliams050100
asked on
lpc connect refused
our printserver here works great but from time to time it will stop printing and give the lpc connection refused error. we have found out how to fix the problem but are wondering, is this a problem with just mandrake 7.0(what we use) or is it common to all linux distributions?
Are you talking about the case when there's a "hung print job" in a queue?
ASKER
when we get this message all print functions hang for all printers. the way we fix it is to delete all the spools for the printers and delete the printcap file. then restore them all.
i gues what i want to know is, is there a differance in the way different distributions print? do some have stronger printing functions than others?
i gues what i want to know is, is there a differance in the way different distributions print? do some have stronger printing functions than others?
Sometimes in our system a few jobs get hung up in the printers and then no one is able to print to that printer. What I do is run lpc clean printername This should clean out your hung jobs and allow your users to print. If that fails, try lpc restart printername. That always brings our hung printer back online. We use RedHat 6.1 with Turbo Linux's smaba server for our printserver needs.
Also you can simply delete the hung job, which normally releases the printing services. I most often see this when using networked printers and I suspect it to be a problem with the lpd daemon.
Oddly enough, I am running Mandrake 7.0, and I have the same problem. Everything works for about two weeks, and then suddenly, I get "Error printing to queue lp - Error reason: lpr: connect: Connection refused - Jobs queued, but cannot start daemon"
Of course, the daemon is active. Sending it a SIGHUP doesn't help. The only thing I have been able to do is remove the printer description in /etc/printcap, remove the spool directory, and redefine the printer.
Of course, the daemon is active. Sending it a SIGHUP doesn't help. The only thing I have been able to do is remove the printer description in /etc/printcap, remove the spool directory, and redefine the printer.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Comment accepted as answer