Issue

• Encountered the error "Unable to write print data: Broken pipe" once in awhile while printing to network printer via socket connection
• I've had a problem with jetdirect HP printers losing connection with the error: "Unable to write print data: Broken pipe" (in Windows the printers could still be used)
• Unable to write print data: Broken pipe
• We have a printer that continually goes into a stopped state due to a broken pipe
• Printing test pages from either the GTK Window or the CUPS web interface seems to cause it to alternate between getting stuck in "pending" and "broken pipe"
• The printer stops working frequently with the error "Unable to write print data: Broken pipe". how can I stop the error occurring?
• Printers going disabled with "Unable to write print data: Broken pipe" errors
• certain print jobs fail "Backend returned status 1 (failed)"

• All but a handful of hundreds of printers work. The ones that don't work get disabled after some minutes with a message similar to:

  printer U001 disabled since Thu 06 Sep 2012 04:53:31 PM CDT -
          Unable to write print data: Broken pipe
  

• Print jobs are randomly ending with the following error every day:

  E [17/Aug/2012:09:03:29 +0200] [Job 35840] Unable to send trailing nul to printer: Broken pipe
  

• When I try to print from Linux I get this error in cups "Unable to write print data: Broken pipe." This is a new printer. It used to be connected through a VPN and now it's connected through an MPLS connection. We are able to telnet to the printer and also use the web interface from both machines.

• Recently when printing large documents, we've been receiving the error

  Unable to send trailing nul to printer: Broken pipe
  Remote host did not accept data file (32)