Cups Error Log Level
Contents |
is the name of the CUPS error log? 1.1.4 Where is the error_log? 1.2 Enabling Logging 1.2.1 How come cups error success the error_log doesn't show much information? 1.2.2 How do I
Cups Error Policy
change the logging level? 1.2.3 After enabling Logging, why are no more error reported to the cups error broken pipe error_log file? 1.3 CUPS Log Errors 1.3.1 Why are there no references to ghostscript in the log? 1.3.2 cupsd: Child exited with status 1! 1.3.3 nginx error log level unable to evaluate datablob 1.3.4 cupsdoprint: relocation error: cupsdoprint: undefined symbol: strlcpy 1.3.5 Warning - hp_psc_950: Bad printcap entry - missing 'sd' or 'client' 1.3.6 /usr/local/sbin/lpdomatic: unable to evaluate datablob 1.3.7 media tray empty 1.3.8 [Job 28] /usr/lib/cups/filter/foomatic-rip: No such file or directory 1.3.9 "/usr/local/var/spool/cups/d00032-001" - Permission denied 1.3.10 Denying user ""
Apache Error Log Level
access to printer? 1.3.11 /usr/bin/foo2zjs-wrapper: line 141: gs: command not found? 1.3.12 Unable to convert file 0 to printable format for job 4! 1.3.13 Couldn't exec foomatic-gswrapper -q? 1.3.14 Error: /invalidfont in findfont? 1.3.15 YOU DO NOT HAVE YOUR FONTS INSTALLED!!? 1.3.16 server-error-service-unavailable? 1.3.17 sh: line 1: hpijs: command not found 1.3.18 Can't find initialization file gs_init.ps? 1.3.19 Unknown device: ijs? 1.3.20 cat: write error: Broken pipe? CUPS' error_log FAQ General Questions In which forum should I ask CUPS-related questions? Either you can use Forum: General Discussion or for better results try the forum related to your specific printer manufacturer. Better is to discuss on the CUPS mailing list/newsgroups on the CUPS web site. What is the error log? This is a file where CUPS writes information about what it is doing. Almost all printing problems can be diagnosed from the error log, so it is the first place to look to start s
Copy Page Delete Page ------------------------ Subscribe User ------------------------ Remove Spam Revert to this revision Package Pages Sync Pages ------------------------ Load Save SlideShow Ubuntu Wiki Login Help DebuggingPrintingProblems Debugging Central This page is part of the debugging series — pages with debugging details php error log level for a variety of Ubuntu packages. Contents Reporting Bugs Printer detection USB printer Parallel mysql error log level port printer Network printer USB -> Parallel adapter CUPS web interface CUPS error_log Troubleshooting Wizard Print Error pop-up window AppArmor Protection
Cups Loglevel
of the printing system Capturing print job data Getting the data which would go to the printer Sending a file to the printer unfiltered PostScript (PDF) printer chokes on the PostScript (PDF) coming from Ubuntu https://wiki.linuxfoundation.org/en/OpenPrinting/Database/ErrorLogFAQ USB printer does not print or prints garbage Problems installing the CUPS package Turboprint Known bugs Reporting Bugs Bugs about printing problems should be assigned to the cups package if you don't know which package they belong to. To report printing bugs preferably use 'ubuntu-bug cups' from a terminal window which will gather useful information about your system related to printing like the version of Ubuntu you use, configured https://wiki.ubuntu.com/DebuggingPrintingProblems printers and the versions of important printing packages installed and automatically attach them to your bug report. You can also add the information after the bug is reported by executing 'apport-collect -p cups BUGNUMBER' where BUGNUMBER is the bug report you want to add information to. Printer detection NOTE: If you have a USB -> Parallel adapter, proceed as for a USB printer and also see the "USB -> Parallel adapter" section below. USB printer Make sure that the printer is connected to your system and powered on. Open a terminal/console and check if the usb kernel modules are loaded: $lsmod|grepusb Unplug the USB printer cable from your computer and enter this command: $tail-f/var/log/syslog Reconnect the USB printer cable, you should see some messages appearing. Press Ctrl-C to stop the logging. Check whether the printer gets correctly detected by the USB subsystem and determine its USB vendor/product IDs and the USB bus and device addresses: $lsusb Note: The USB bus and device addresses change if you turn off or unplug the printer. Please re-run this command if needed. Check whether the device files for the printer get created and the ownerships ("root lp") and permissions (non-HP: "crw-rw-r--", HP: "crw-rw-r--+") correctly set: $ls-l/dev/usb/lp*/dev/bus/usb/*/* Determine the printer's device ID
Documentation EPEL Infrastructure Internationalization Localization Marketing Magazine Package Maintainers Quality Assurance Websites All projects Search Tools What links here Related changes Special pages Printable version Permanent link How to debug printing problems From FedoraProject https://fedoraproject.org/wiki/How_to_debug_printing_problems Jump to: navigation, search Foreword If you are experiencing a problem with printing, please take a look at the common bugs page before filing a bug. If the problem you are seeing is not listed there or none of the workarounds seem to help, please consider filing a bug report to help us make Fedora run better on your hardware. Contents 1 Identifying your problem area 1.1 Printing error log troubleshooter 1.1.1 Getting debug information by other means 1.2 What make and model is my printer? 1.3 Which driver am I using? 1.4 Finding where the problem lies 1.4.1 Application 1.4.2 Document format 1.4.2.1 Running filters by hand 1.4.3 Driver 1.4.3.1 Foomatic 1.4.4 Backend (job transport) 1.4.5 Configuration tool 2 Filing a bug report 2.1 Deciding which component 2.2 Other information to include 2.3 Further reading Identifying your problem error log level area Printing troubleshooter The first thing to try is to run the printing troubleshooter. Install system-config-printer: su -c 'dnf install system-config-printer' Start the Print Settings application, or else you can run it from the command line: system-config-printer Then select Help > Troubleshoot from the menu bar. This will ask a series of questions about the problem you are experiencing, with the aim of finding the reason for the problem. After following this process you will most likely end up with a troubleshoot.txt file. This is the most helpful thing you can add to a bug report. One step in this process is to print a test page. There is a button in the troubleshooter to print a test page for you, but if the problem you are seeing is specific to printing from a certain application, or printing a certain document, just go ahead and print from that application or print that particular document. The print job will appear in the troubleshooting window -- just put a tick in the box next to that print job to say that it is the one you are having trouble with. If the problem was not found automatically you will be given the option to s