Link to home
Start Free TrialLog in
Avatar of winstont
winstont

asked on

linux print job truncates

Hi experts

I am using lprng on Redhat 8 and a kyocera FS1010.  Printing is alright for small files, i.e. less than 170 pages.  Beyond this, the printing stops anywhere.  Any suggestion?

Thanks in advance!
winston

PS  I am only printing text files.  So I prefer to use lprng, but I will consider changing lprng if there is no other choice.
Avatar of noci
noci

Does your disk where the spool area resides fill up?

/var/spool/lp* ???

use df several time during printing ....
Avatar of winstont

ASKER

No.  The disk has plenty of space free, more 80% still free.
How much is 80%, 80% of a few GB is quite a lot, 80% of 50MB is only 40MB... and if all data get converted a few times
using Ghostscript etc. stuff can get quite large.

And if /tmp is used how much space is there available..., please do check available disk space during printing.

(Do you use Disk Quota?  )
btw did you check your logfiles?

syslog (daemon log) and the logfiles within the lpd spool area?
If possible, add RAM to the printer. What type of interface are you using? Is it the parralel port? If so, also check the port's settings in the Server's BIOS. It may need a BiDirectional or EPP/ECP setting, and not just the standard LPT setting which would only talk in one direction.
/home, /usr and /var have 8.6GB, 3.2GB and 18.7GB free space, respectively.

Log files doesn't contain any error.
Yes, the printer is connected to the parallel port.  I'll check the BIOS setting.  But, how does the BIOS affect the printing to drop out?  I thought, if ever, the setting will get the printing to work or not to work, but not affect the printing more than half way - 170 pages out of 212 pages.
ASKER CERTIFIED SOLUTION
Avatar of rindi
rindi
Flag of Switzerland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Even if the lpt is set in one direction, there are IIRC 4 lines back to the computer, of which Ready, Paperout, Error are at least 3 of them.
You are correct in that no extended data can be sent to the host, but a select set of status values can be sent. Without ready the computer
has to hold transmission.

http://www.fapo.com/porthist.htm

According to this there are 4 control and 5 status lines.

A print job exceeding 18Gb is highly unlikely

Can you modify your cupsd.conf file and add LogLevel DEBUG
to it, or modify the LogLevel line to become debug?
BTW how big is /tmp???, what if an underlying converter needs some space there and runs out of it..
please do a monitor of all diskspace with df while printing the large file.

The reprint the file, maybe more messages a re given then,
into the logfile.

There is a DEBUG2 level, I hope that's not really needed.

I am just using lprng.  Is the LogLevel debug available in lprng?

I don't have a separate filesystem for /tmp, which then belongs to /, and this is 800MB free.  The file is just over 1MB.

Ooops differen question...; I had a blonde-moment  ;-)....

Also lprng works differently,

cups works basicly as a postscript processor..., upfront to
postscript and if need backend to the actual printer....

lprng works more like the lpr modules...
build a filter chain to convert from input to output in  one go.

There is not a lot of errors mentioned on the lprng mailing list in this direction. The only likewise one I found was a reference that
a using the lpd protocol to a network printer doesn't work well, and that la link to port 9100 works better.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial