You probably should have a look at (or post pertinent parts of)
your cups errorlog file, which is usually in /var/log/cups/errorlog.
By default the errorlog is fairly terse, so you might have to
adjust LogLevel in your cups.conf file. I usually use
when I'm trying to figure out why something is broken. Don't forget
to restart cupsd after making this change.
On Sat, 04 Jun 2011 12:42:11 -0500 Joy Methew <firstname.lastname@example.org>
>Hello All i am getting this error. "/usr/lib/cups/filter/foomatic-
>Anybody have any idea about this error. Server os is RHEL5.5
>I have done lot`s of Google but not getting proper answer.
>All suggestions are welcome.
>scheduler is running
>system default destination: HP_Laserjet_2605dn
>device for HP_Color_LaserJet_2605dn_188.8.131.52:
>device for HP_Laserjet_2605dn: ipp://184.108.40.206/printers/HP
>HP_Color_LaserJet_2605dn_220.127.116.11 accepting requests since
>Tue 31 May
>2011 02:28:12 PM EDT
>HP_Laserjet_2605dn accepting requests since Tue 31 May 2011
>02:28:12 PM EDT
>printer HP_Color_LaserJet_2605dn_18.104.22.168 is idle. enabled
>31 May 2011 02:28:12 PM EDT
> /usr/lib/cups/filter/foomatic-rip failed
>printer HP_Laserjet_2605dn now printing HP_Laserjet_2605dn-11.
>since Tue 31 May 2011 02:28:12 PM EDT
> recoverable: Network host '22.214.171.124' is busy; will
>retry in 30
>HP_Color_LaserJet_2605dn_126.96.36.199-1 root 1024
>May 2011 11:50:18 AM EDT
>HP_Laserjet_2605dn-3 eitan 332800 Tue 31 May 2011
>HP_Color_LaserJet_2605dn_188.8.131.52-4 root 1024
>May 2011 02:06:11 PM EDT
>HP_Laserjet_2605dn-11 root 17408 Tue 31 May 2011
>redhat-list mailing list
redhat-list mailing list