Tim, this is the additional bug report you requested for this "Remote host did not accept data file" error message: E [07/Jul/2009:08:44:05 -0400] [Job 212] Remote host did not accept data file (2) D [07/Jul/2009:08:44:35 -0400] [Job 212] printer-state-message="Remote host did not accept data file (2)" Just to reiterate what I've already told you, the printer seems to be behaving as though it cannot accept any more data despite the job size being much smaller than the available memory. Please leave me your instructions for attaching the data and I will post it to this bug report.
Thanks. What you need to do to grab the data file that CUPS receives is: 1. Run this: cupsctl -U root PreserveJobFiles=Yes 2. Send the print job from the client 3. ls -1 /var/spool/cups/d?????-001 | tail -n1 That will show the name of a file in the CUPS spool directory. Please attach that file to this bug report. Thanks!
Created attachment 350923 [details] Job file resuling in error That's it? Simple! As it happens, I already have PreserveJobFiles turned on..
Thank you. Did you say that a few of the pages are printed? How many?
No pages were output for this job. The printer just said "Busy" the whole time.
*** Bug 512037 has been marked as a duplicate of this bug. ***
Just adding a note that this is a spin-off from bug #505807. Device is Lexmark Optra R+.
FWIW: I just printed attachment 350923 [details] from Comment #2 without any problems with "lp -oraw d00212-001" on a Lexmark C530dn under cups-1.4-0.rc1.7.fc11.x86_64
Matt, do *any* jobs succeed? If so, is there anything you can think of that distinguishes the successful jobs from the unsuccessful ones?
Smaller jobs will print. I guess I need to buy a C530dn, huh? Seriously, I'll begin more intensive testing for a possible error with the printer itself.
I'm going to swap out the memory on my printer and see if that has any effect. Incidentally I have found some posts by people who seem to have the same issue but I can't locate them. http://osdir.com/ml/printing.cups.bugs/2004-11/msg00023.html
Things seem much more even tempered using socket rather than LPR, perhaps I'll just change to that. There's still issues printing PDF's but I have a suspicion that acrobat reader has something to do with that. I have not seen this error again after changing to socket on port 9100. I'm OK with closing it until such time as the error happens again.