CUPS Printing / Delay
Thanks for all your replies. I now have some additional information to assist any user being able to point me in the right direction.
Thanks for the SCRIPT in this topic, but my printers NEVER stop they just seem to hesitate for a while. When my print jobs seem to stop, if I look on the PRINTERS, they still say they are "active, accepting jobs". They never say "stopped"
On a day to day basis all 45 network printers will print instantaneously as soon as a JOB has been sent. Then, on the ODD occasion a JOB will be sent, but the printer will not output it. The DATA lights are not on, so the JOB is still residing on the Red Hat Enterprise server and not simply stuck in the Printer itself.
The job will eventually come out, with all other jobs that may have accumulated behind it. This delay could be 5 minutes, it could be 30 minutes. totally random. When the printer seems to become active all jobs print as if there was nothing wrong in the first place.
I put the CUPS system into DEBUG mode this morning, and the ONLY error I can see in there (when one of the printers appeared to have hesitated) is the following
[Job 16405] Remote Host did not respond with a command status byte after 300 seconds!!
Can someone explain what this means, and how I overcome it.