Did this article resolve your question/issue?



Printing job failed with error 140 on RHEL 7.4


TitlePrinting job failed with error 140 on RHEL 7.4
URL NamePrinting-job-failed-with-error-140-on-RHEL-7-4
Article Number000110865
EnvironmentProduct: OpenEdge
Version: 11.6.4
OS: Red Hat Enterprise 7.4
Question/Problem Description
Printing job failed with error 140 on RHEL 7.4
Error 140 when a print job takes more than a couple seconds
Steps to Reproduce1.
Output to printer.
display "hello".
pause 10 no-message.
output close.

for file in `cat testlp`
echo $file
sleep 1
done | lp -dwe.PREM -s
Clarifying Information
Same procedure works on RHEL 5 and OE 10 when specify  Timeout 0 in cupsd.conf.
Network printer in local LAN and under same VLAN.

Error Message** Pipe to subprocess has been broken. (140)
Defect/Enhancement Number
RedHat printer configuration.
Remove the Timeout 0 line from the cupsd.conf file.
Or specify a different value.
Timeout 1w 
Timeout 1d 
Timeout 1h 
Timeout 5m 
Timeout 300 

The Timeout directive controls the amount of time to wait before an active HTTP or IPP request times out in seconds (no suffix), minutes ("m" suffix), hours ("h" suffix), days ("d" suffix), or weeks ("w" suffix). 
The default timeout is 5m (five minutes).
Last Modified Date4/9/2018 5:49 PM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.