Printer Stops Working with "Remote Host Did Not Respond with Command Status Byte after 300 Seconds!" and "Printer-State=5(stopped)" Errors in the Log (Doc ID 2521312.1)

Last updated on MAY 16, 2020

Applies to:

Symptoms

In /var/log/cups/error_log, the following logs were seen:

D [15/Mar/2019:07:36:04 +0000] [Job 1179448] lpd_command 02 Printer-01
D [15/Mar/2019:07:36:04 +0000] [Job 1179448] Sending command string (17 bytes)...
D [15/Mar/2019:07:36:04 +0000] [Job 1179448] Reading command status...
D [15/Mar/2019:07:36:04 +0000] [Job 1179448] Set job-printer-state-message to "Remote host did not respond with command status byte after 300 seconds!", current level=WARN >>>>>>>>>>>>>>>>>>>>>>>>>>>>
D [15/Mar/2019:07:36:04 +0000] [Job 1179448] lpd_command returning 98
D [15/Mar/2019:07:36:04 +0000] [Job 1179448] Backend returned status 1 (failed)
D [15/Mar/2019:07:36:04 +0000] [Job 1179448] Printer stopped due to backend errors; please consult the error_log file for details.
D [15/Mar/2019:07:36:04 +0000] [Job 1179448] End of messages
D [15/Mar/2019:07:36:04 +0000] [Job 1179448] printer-state=5(stopped) >>>>>>>>>>>>>>>>>>>>
D [15/Mar/2019:07:36:04 +0000] [Job 1179448] printer-state-message="/usr/lib/cups/backend/lpd failed"
D [15/Mar/2019:07:36:04 +0000] [Job 1179448] printer-state-reasons=paused
W [15/Mar/2019:07:36:04 +0000] [Job 1179446] Remote host did not respond with command status byte after 300 seconds!

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.