Solved

lpc connect refused

Posted on 2000-05-01
7
606 Views
Last Modified: 2013-12-15
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?
0
Comment
Question by:GaryWilliams050100
7 Comments
 
LVL 40

Expert Comment

by:jlevie
ID: 2771306
Are you talking about the case when there's a "hung print job" in a queue?
0
 

Author Comment

by:GaryWilliams050100
ID: 2773620
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?
0
 

Expert Comment

by:ddurbin050400
ID: 2778168
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.
0
Enabling OSINT in Activity Based Intelligence

Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

 
LVL 40

Expert Comment

by:jlevie
ID: 2778794
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.
0
 

Expert Comment

by:rclayton
ID: 2964431
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.
0
 
LVL 8

Accepted Solution

by:
akeh earned 75 total points
ID: 3007959
There's obviously a problem with
lpr/lpd/lpc in Mandrake 7.0.
http://www.linuxworld.com/linuxworld/lw-2000-03/f_lw-03-penguin_2.html
suggests that you install an older
version of the lpr package.
0
 

Author Comment

by:GaryWilliams050100
ID: 3010994
Comment accepted as answer
0

Featured Post

Why You Should Analyze Threat Actor TTPs

After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

Join & Write a Comment

1. Introduction As many people are interested in Linux but not as many are interested or knowledgeable (enough) to install Linux on their system, here is a safe way to try out Linux on your existing (Windows) system. The idea is that you insta…
The purpose of this article is to fix the unknown display problem in Linux Mint operating system. After installing the OS if you see Display monitor is not recognized then we can install "MESA" utilities to fix this problem or we can install additio…
Connecting to an Amazon Linux EC2 Instance from Windows Using PuTTY.
This demo shows you how to set up the containerized NetScaler CPX with NetScaler Management and Analytics System in a non-routable Mesos/Marathon environment for use with Micro-Services applications.

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now