Print Jobs Do Not Immediately Fail Over Using cups-browsed in RHEL 7
Issue
-
When the first CUPS Server is down and a job is queued to a one of the printers on the client server, the job fails and the printer is paused. There is no attempt to schedule the printer on the second server. If we wait several minutes and re-enable the printer it is successfully scheduled on the remaining print server.
-
When printing to two remote nodes specified in
cups-browsed.confunderBrowsePollsettings, when one of the nodes is shutdown or unavailable, it's not reliably failing over to the second node. Error received is:printer forsythb5 disabled since Thu 15 Oct 2020 10:53:29 AM EDT - No destination host name supplied by cups-browsed for printer "forsythb5", is cups-browsed running?
Environment
- Red Hat Enterprise Linux (RHEL) 7.7 and later versions
- Common Unix Printing System (CUPS) 1.6.3
cups-filters-1.0.35-26.el7_7.1
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
