[cups] Centos 7.9 cups-1.6.3-51.el7.x86_64 & cups, stalling the transfer of printed files from the client machines to the cups print server

[Gregory P. Ennis]

Everyone,

I have had cups printing services set up for years without having a
problem.  We recently created guest Centos 7.9 machines out of several
of our services on an ESXI hypervisor. The cups print server is not on
the hypervisor and has continued to function independently of ESXI. 

I have been having some problems with our cups printing service for the
last 4 months.  I have a gateway machine that holds the printer
information and is the print server.  The other client  machines on the
network use cups and cups-browsed that are set up to spool the print
jobs to the gateway and then the gateway sends the data stream to the
respective printers.  

The problem I have is that on any of the local machines the print jobs
stall.  I can run lpstat lpt6 for instance which gives me the listing
of the stalled print jobs, but I am not seeing error messages in the
logs either on the local machine or on the gateway print server.

In doing some google searching I found that there was a problem with gh
ghostscript-9.07-31.el7_6.10.x86_64 and ghostscript-cups-9.07-
31.el7_6.10.x86_64 that was apparently fixed.  I am running Centos 7.9
that is fully updated with gs 9.25 on both the local machines and the
gateway.  

The problem is intermittent and appears with various file types pdf,
ps, pcl, and txt.  I have not been able to identify any specific or
consistent association.  

When these printers become disabled the client cups machine gives me
the notice that the printer has been put on pause with the following
notice :

No destination host name supplied by cups-browsed for printer "lpt6",
is cups-browsed running?

systemctl restart cups and cups-browsed does fix the problem, but this
is required to do about once every 60 minutes. This process destroys
the print queue and the print job is lost.

However, taking the printer out of pause via html using localhost:631
restarts the print job to completion. 

If any of you have had this problem I would sure appreciate your help.

Thanks in advance !!!!
-- 
Greg Ennis