CentOS - Dec 2007 - After 4.6 update: CUPS (via Samba): "'/printers/printers' no good!"

Since updating from 4.5 to 4.6 yesterday, I am getting a lot of CUPS 
errors.  The error.log file is filling up with these messages:

	get_printer_attrs: resource name '/printers/printers' no good!

And the access.log seems to be being polled often too, even in the absence 
of any print jobs submitted.

On my network the CUPS-handled printer is exported from Samba.  Given that 
the Samba RPMs were among those upgraded, I have to wonder what 
printing-related changes might have occurred.  The hal-cups-utils was 
also updated in the course of the upgrade.

I also notice that CUP's ppds.dat and cupsd.conf files have modification 
timestamp from around the time I did the upgrade.

Any advice as to how to fix whatever was broken in the course of doing the 
upgrade?

Thanks.

On Dec 17, 2007 6:59 AM, Steve Snyder <swsnyder at insightbb.com>
wrote:
>
> Any advice as to how to fix whatever was broken in the course of doing the
> upgrade?
After any upgrade it's always good to run

updatedb
locate .rpmsave
locate .rpmnew

and then compare those files to the ones they might have replaced.

On Dec 17, 2007 6:59 AM, Steve Snyder <swsnyder at insightbb.com>
wrote:
> Since updating from 4.5 to 4.6 yesterday, I am getting a lot of CUPS
> errors.  The error.log file is filling up with these messages:
>
>         get_printer_attrs: resource name '/printers/printers' no
good!
>
> And the access.log seems to be being polled often too, even in the absence
> of any print jobs submitted.
>
> On my network the CUPS-handled printer is exported from Samba.  Given that
> the Samba RPMs were among those upgraded, I have to wonder what
> printing-related changes might have occurred.  The hal-cups-utils was
> also updated in the course of the upgrade.
>
> I also notice that CUP's ppds.dat and cupsd.conf files have
modification
> timestamp from around the time I did the upgrade.
>
> Any advice as to how to fix whatever was broken in the course of doing the
> upgrade?
Have you ever sorted this out?  I was also seeing the same message in
the cups error log.  In your smb.conf file, do (or did) you have lines
like:

   printing = cups
   printcap name = cups

If you are still having the issue, try commenting them out.

Akemi