One of my remote cups clients quit working two days ago. Everything was running fine with my server sharing two printers, (an HP and the pdf generator) out to three notebooks. Two of the other notebooks still work fine. The amd64 machine does not. It now spools the print job and creates about 25 or so copies of it. When I look at the spool on http://localhost:631/jobs I see the print job along with about 25 copies of it. Running top on the local client shows cups using most of the processor resources. The spool on the server (where I am printing to) shows nothing. The other two notebooks have no problem printing to the server. The amd64 machine prints with no problem to the local pdf generator. I have made no modifications to any of the clients' cups config files. I rely on the local clients to pick up the server's boradcasts. I tried googleing around to find a solution, but I can't seem to find any hits.
Update:
Found the problem. It was an issue with hostname resolution on the lan/vpn. The server was broadcasting the printers as available on "ubernet", the server's internal hostname. I just noticed that "ubernet" was resolving to 127.0.0.1 instead of the server's internal IP address. A quick reset of the dns server fixed the problem and all works now. It looks like what was happeneing was cups was trying to find those remote printers and looping back to itself. Since it did not have either of those two printers installed, it just kept trying until it loaded up the queue and crashed itself.
