Lp Unable To Print File Client-error-not-found
Contents |
Error: "Unable to print to file: client-error-not-possible" Print jobs transfer from the application to CUPS, but don't print to printer. "too returning ipp client-error-not-possible for create-job many jobs" listed as a reason for failure in the /var/log/cups/error_log sap /usr/bin/lpr: too many active jobs. file. cause The header files of aborted print jobs collect in /var/spool/cups. If too many files cups maxjobs collect there, then jobs will not be received by CUPS. fix Run these commands to resolve this problem. ps -eaf | grep cupsd You will see a process message from host spool usr bin lpr too many active jobs of /usr/sbin/cupsd run by lp rm -f /var/spool/cups/c* This command removes the header files that are left over in the CUPS system. These files will remain if the job is aborted or otherwise didn't print. killall -HUP cupsd This command should kill the CUPS daemon. ps -eaf | grep cupsd This command will verify that
Cups Server Error Client-error-not-possible
/usr/sbin/cupsd is not running. If /usr/sbin/cupsd is still listed with ps grep command from above, then run: kill -9 [pid] The pid (process ID) is listed in the ps grep command from above. Use that number in place of [pid]. ps -eaf | grep cupsd Again, verify that /usr/sbin/cupsd is not running. /usr/sbin/cupsd should not be listed. cupsd This command will start the CUPS daemon. document Document Title: Error: "Unable to print to file: client-error-not-possible" Document ID: 10099373 Solution ID: NOVL103920 Creation Date: 18Oct2005 Modified Date: 18Oct2005 Novell Product Class:Novell Printing Services disclaimer The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information. Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.
Core releases
/var/spool/cups
-0500 On Sun, 2006-04-09 at 01:15 +0200, Colin Brace wrote: > Hi all, > > My printer spontaneously stopped working. Printing a test page from > printer configuration returns this error message: > > "lpr: error - unable to print file: client-error-not-found" > > I tried deleting and recreating the printer profile, even removing > cups with https://support.novell.com/docs/Tids/Solutions/10099373.html rpm -e --nodeps and reinstalling it with yum to no avail. > > A Google search returns various hits, including a post on this list > from last August, >
HCL Search Reviews Search ISOs Go to Page... LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian lpr: unable to print file: client-error-not-found User Name Remember Me? Password Debian This forum is for the discussion of http://www.linuxquestions.org/questions/debian-26/lpr-unable-to-print-file-client-error-not-found-211093/ Debian Linux. Notices Welcome to LinuxQuestions.org, a friendly and active Linux Community. You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, http://osdir.com/ml/printing.cups.general/2004-02/msg00078.html subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today! Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you too many new to LinuxQuestions.org? Visit the following links: Site Howto | Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here. Having a problem logging in? Please visit this page to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, too many active geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Click Here to receive this Complete Guide absolutely free. Search this Thread 07-29-2004, 12:20 PM #1 rickenbacherus Member Registered: Mar 2003 Location: colorado springs. colorado Distribution: Debian-Sid 2.6.24-rt1 Posts: 290 Rep: lpr: unable to print file: client-error-not-found ON the home LAN I have 2 boxes. 'zulu' (192.168.1.101) the print server which can print just fine. The other box 'cromag' (192.168.1.100) cannot print to zulu with this error: lpr -P http://192.168.1.101:631/printers/HP file.txt lpr: unable to print file: client-error-not-found Network printing was working just fine until I did an apt-get upgrade (SID) on zulu. Here's the relevant part of /etc/cups/cupsd.conf which was also working fine and was not overwritten during the upgrade BTW: ## Restrict access to local domain Order Deny,Allow Deny From All Allow From 127.0.0.1 Allow From 192.168.1.100 #Encryption Req
-P socket://192.168.2.13:9100 /etc/samba/smb.conf" is a totaly wrong syntax. It tries to print the document "/etc/samba/smb.conf" on the printer "socket://192.168.2.13:9100". It won't work at all. While you added your Printer to CUPS you gave it a name, if you haven't added it, use the CUPS-Webinterface (http://localhost:631) or the command "/usr/sbin/lpadmin -p printername -E -v socket://192.168.2.13:9100 -m laserjet.ppd". If you have done this then you should be able to print with "lpr -P printername document". And because Samba uses the CUPS-Printcap by default, Samba should automaticly show up with the newly added printer. JG wrote: I used samba 3.0 w/ openldap as a PDC. The Samba setting allows users to authenticate against the LDAP. Maybe I'm misunderstanding the CUPS protocol. I was using a Win2k box as the PDC but I switched over to Samba/LDAP. The printing is the only issue I haven't been able to resolve. On the Win2k box I had the HP 4000 listed as a printer (the printer is remote on a separate IP) so users can download the drivers automatically and spool through the server. I want to do the same thing on the Samba/LDAP PDC. However, when I try to run the lpr command I get the error. My feeling is that the cupsd.conf file is not setup properly. I'm just trying to send a print job from the PDC to the remote printer. This should be difficult but I'm blocked. Cheers, Jason "Christoph Konersmann"