Hi, I have a problem printing to a HP LaserJet 3030 connected to the network via a HP JetDirect printserver from a CentOS 5 workstation.
The configuration went fine, although I don't know exactly anymore which tool I used. I believe I used CentOS's standard system-config-printer. Now when I boot the workstation, and try to print something to the HP, this fails resulting in several entries in /var/log/messages like: hp_LaserJet_3030?ip=192.168.93.12: invalid message: No log handling enabled - turning on stderr logging : prnt/hpijs/hplip_api.c 183 hp_LaserJet_3030?ip=192.168.93.12: INFO: open device failed; will retry in 30 seconds... hp_LaserJet_3030?ip=192.168.93.12: invalid message: Cannot find module (IP-MIB): At line 0 in (none) Cannot find module (IF-MIB): At line 0 in (none) Cannot find module (TCP-MIB): At line 0 in (none) Cannot find module (UDP-MIB): At line 0 in (none) Cannot find module (HOST-RESOURCES-MIB): hp_LaserJet_3030?ip=192.168.93.12: INFO: open device failed; will retry in 30 seconds... hp_LaserJet_3030?ip=192.168.93.12: invalid message: N-SCHEDULE-MIB): At line 0 in (none) Cannot find module (UCD-SNMP-MIB): At line 0 in (none) Cannot find module (UCD-DEMO-MIB): At line 0 in (none) Cannot find module (SNMP-TARGET-MIB): At line 0 in (none) Cannot find module (NET-SNMP-AGEN hp_LaserJet_3030?ip=192.168.93.12: INFO: open device failed; will retry in 30 seconds... The print job remains in the queue. In another test, when I try to open the hp-toolbox after a reboot, but BEFORE trying to print, I get these error messages on the command line (and /var/log/messages): python: hp-toolbox[3522]: warning: Unknown message type python: hp-toolbox[3522]: warning: Unknown message type And the toolbox will show the printer with a red cross (printer not available or something ?) If I then close the hp-toolbox, and open it again, the errors have disappeared and the printer is shown as online. And moreover, I can print to it !? Moreover, I can continue to print without any problems until the next reboot. Then the story start all over again. So it appears I have a workaround for the problem, but I would like to know the cause and fix it. The workaround is useful for me as sysadmin. The users of this workstation are simple computer users, not powerusers. They can grasp simple tasks, but this workaround will be complicated and frustrating to them. Any idea what goes on here ? I did some additional tests: * When printing failed, I opened the KDE control panel, removed the blocked job and tried to print a test page from there. This worked, although I don't know why. After this testpage, I could print normally to the printer also. * When printing failed, I launched the cups web interface, removed the blocked job and restarted the printer via the interface. Afterwards I could print normally. All this seems to suggest that something goes wrong at boot time when starting hplip and cups. I already tried delaying the cups startup to allow more time for hplip to complete, but this didn't seem to help very much. Any help or tip is greatly appreciated... Thank you, Geert ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ HPLIP-Help mailing list HPLIP-Help@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hplip-help
