[cups.general] Several issues configuring a Solaris10 CUPS client

[Eli Kleinman]

We are running into several issues configuring a Solaris10 CUPS client
talking to 2 Solaris10 CUPS servers (print1 & print2) in an HA
configuration (i.e. with the same 300 printers defined on each system).

The sequence of events is as follows:

1) CUPS is started on print1. The GUI correctly shows all 300 printers.

2) CUPS is started on print2. The GUI shows 600 printers, including the
300 defined on print1. Also, print1 now shows 600 printers, including
300 from print2. So far all is good.

3) CUPS is started on client1. The GUI variously shows either 300
printers (what I expect to see) or 600 printers.
If it shows 300 printers, the Device URI for all printers is variously
one of the following:
*Device URI:* ipp://print[1/2].xxx.com:631/printers/<printer_name>
*Device URI:* file:///dev/null
Why is this the case?

If it shows 600 printers, the same printer appears twice with the
following Device URIs:*
Device URI:* socket://<printer_name>.xxx.com
*Device URI:* ipp://print2.xxx.com:631/printers/<printer_name>
Why aren't the printers recognized as being the same an collated in some
instances?
Why wouldn't the first Device URI show
ipp://print1.xxx.com:631/printers/<printer_name>?

4) CUPS is stopped on one of the servers (print1 or print2). The GUI
shows 300 printers on the remaining server. However, client1 variously
has either all the 300 printers correctly defined, or it may have
anything under 300, or 0 printers. Frequently also, the printers on
client1 will just disappear over time. Snoops & trusses show that the
cups process on the server are correctly broadcasting the printer info,
and the client is correctly receiving them, but somehow ignoring them.
Logs do not give any other info. Restarting the CUPS process on either
the server or the client fixes the problem.
Why is client1 unable to reconfigure itself with the broadcast
information received from the server that is up?
Why would printers on the client randomly disappear over time, even
though the client and server appear to be communicating?
Why is this fixed automagically as soon as the CUPS process is restarted?


This is a new set up - all the machines are on the same subnet and are
not being used for anything else.

Relevant info in the cupsd.conf file on Servers
----------------------------------------------
LogLevel info
SystemGroup sys root
Listen localhost:631
Listen print1.xxx.com:631
Listen /print/cups/var/run/cups/cups.sock
# Show shared printers on the local network.
Browsing On
BrowseAddress 192.9.200.255
BrowseOrder allow,deny
BrowseAllow all
BrowseInterval 60
BrowseTimeout 300
ImplicitClasses On
Printcap

Relevant info in the cupsd.conf file on Client
---------------------------------------------
LogLevel info
SystemGroup sys root
Listen localhost:631
Listen client1.xxx.com:631
Listen /print/cups/var/run/cups/cups.sock
ImplicitClasses On
Printcap

Thanks,
-Eli

-- 
Eli Kleinman
B&H Photo Video, Inc.
420 9TH Avenue
New York, NY 10001 USA
Phone: 212-239-7500 Ext.2154
Email: elik at bhphoto.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cups.org/pipermail/cups/attachments/20071024/1e826a62/attachment-0001.html>