Hide Forgot
Description of problem: We are using a HP Color Laserjet cm2320fxi. Intermittently, print jobs to this printer fail, for no clear reason. The printer is used from the network in this configuration: - The printer is accessible over the local network. It is not attached directly to any PC. - A linux printserver is set up (currently running Fedora 15) that drives the printer. - All other PC's (a mixture of F15 and F16 installs) send their print jobs to the linux printserver which is then responsible for handling the actual printing. The failures can happen from any PC. I failed to find a pattern so far. The problem has been going on for some months now. Sometimes the printer works fine for days, sometimes it simply fails several times in a row. In most cases, the print failure results in the printer (not the server, the printer itself) completely rebooting and the cups print queue is paused on the print server. I first thought it was a hardware problem, so I have ordered a replacement unit. After a couple of days this replacement unit showed the exact same behaviour, so I'm back to debugging on the software level. I will attach the log of one such failed job. Version-Release number of selected component (if applicable): (On the printserver) cups-1.4.8-5.fc15.i686, hplip-3.11.10-5.fc15.i686 (On the f16 clients) cups-1.5.0-22.fc16.i686 hplip-3.11.10-7.fc16.i686 How reproducible: Not with every print job, but several times a week. Steps to Reproduce: I wish I knew. Some print jobs trigger the failure, others don't. Actual results: The print job fails. Usually the printer goes through a complete reset cycle and the cups queue is paused. However after resuming the print queue, the failed job usually prints fine anyway. Expected results: Error-free printing. Any help on this problem is more than welcome. I'm almost tearing my hair out because I can't find a clear cause. Please let me know what additional information can be helpful in debugging this.
Created attachment 549430 [details] Excerpt from the cups error_log on the print server for a failed job
Thanks for the error_log. From the following line prnt/backend/hp.c 625: ERROR: 5012 device communication error! it seems like hp backend problem (5012 is HPMUD_R_IO_ERROR). I'm not sure what other info would help us debugging the problem but we could find the following useful: - Output from printing troubleshooter https://fedoraproject.org/wiki/Printing/Debugging#Printing_troubleshooter - error_log from successful print job (for comparing) - error_log for a failed job with log level set to debug2 https://fedoraproject.org/wiki/Printing/Debugging#Getting_debug_information_by_other_means - Eventually I could build a hplip package for you with debugging messages enabled for that backend. It would require uncommenting some defines in source code. The work-around for the problem could (not sure with this as I never tried using other backend with HP printer) be using other backend than hp, e.g. JetDirect: socket://ip-address-or-hostname:9100
(In reply to comment #2) > - Eventually I could build a hplip package for you with debugging messages > enabled for that backend. It would require uncommenting some defines in source > code. You can find it here http://koji.fedoraproject.org/koji/taskinfo?taskID=3614301 Assuming that the problem could be reproduced from other PC (configuring printing directly to the printer, not via server) you don't need to test this on the server.
Sorry for the delay in response. I have been kept pretty busy the last couple of months. I went to the koji page, but I don't understand how to work from there. Am I supposed to find an rpm package there, that I can download and install ? Or should I download an srpm and first build it locally ? I know how to do that, but it's unclear to me what I should take from the koji page to start with. It would help me a lot of you could briefly explain this, or point me at an explanation somewhere online.
It was a scratch-build which means that the built packages were automatically deleted after some time (not sure, but probably couple of weeks). I need to build it once more. Do you want F15 or F16 build this time ?
F16. I don't have any F15 systems anymore.
F16 scratch-build with debug messages for hp backend turned on: http://koji.fedoraproject.org/koji/taskinfo?taskID=3960290 I usually download all the rpms into one directory and run: su -c 'yum --nogpgcheck localupdate *.rpm'
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping