text: Red Hat Bugzilla – Bug 505807
  Canceled jobs spontaneously re-appear
  Last modified: 2009-08-10 07:50:05 EDT
  Every large print job sent through the box running CUPS since updating it to Fedora 11 results in CUPS error "Unable to send trailing nul to printer" and at the printer, the job prints to about page 15, and then starts over again.
  I have cups-1.4-0.b2.18.fc11.x86_64.
  Boy, I don't know.. CUPS is acting really STUPID since updating to the latest. Jobs that were canceled are magically re-appearing, queues are getting frozen in "processing" when nothing is being processed.. Jobs printing halfway then starting over.. LPR socket errors, and none of this was happening before the update!
  I'd like to see the TCP traffic between the CUPS server and the printer. Please run this command, as root:
  tcpdump -s0 -U -w lpr.pcap -n host ${HOST}
  replacing ${HOST} with the IP address of the printer, i.e. the hostname part of the lpd://${HOST}/... device URI.
  Once tcpdump is running, print a large job to the printer so that the 'Unable to send trailing nul to printer' error occurs, then cancel the job and stop tcpdump (press control+C in that terminal window).
  Then attach the lpr.pcap file to this bug report using the 'Add an attachment' link. Thanks.
  The job is stuck at 2%.. how long before CUPS will give up?
  Without knowing the nature of the problem it's hard to say I'm afraid. Is it behaving differently now, and not giving you the 'trailing nul' error?
  Created attachment 348301 [details]
  packet capture
  Wasn't always the 'trailing nul' anyway, as I said, since I upgraded.. Jobs get stuck in processing, or LPR error.. Some jobs that were canceled seem to re-appear on their own.. I'm going to stop the tcpdump now and attach it.. Looking at the traffic in wireshark, it looks like cups quit sending.. at least all the traffic I see is coming FROM the printer not going to it.
  This job DOES infact say "unable to send trailing nul to printer" - But only AFTER I canceled it.
  The printer's TCP buffer is full (173.626 seconds in), and the window is never opened up again. I don't know why it does that rather than failing the job.
  So given that this worked fine in Fedora 10 (right?) we'll need to look at how the PostScript we're sending to the printer has changed between Fedora 10 and Fedora 11.
  How is your job submitted? Is it from an application running on Fedora 11, or from some other machine on the network?
  Right, I don't recall ever having problems printing large jobs in Fedora 10.. This job is being sent from a windows client via samba.
  The test job resulted in no pages output at all. At 16 Pages/Min I would think I would have seen page 1 after ~174 seconds..
  This test job, despite having been CANCELED by me, and confirmed thru the web interface as no longer listed.. Is back. With a status of "pending" and an error "/usr/lib/cups/backend/lpd failed" This is what I'm talking about when I say canceled jobs are coming back to life.
  1. Please attach /var/log/cups/error_log* in case there are any clues about why the job restarted.
  2. I have prepared a new set of CUPS packages (1.4-0.rc1.3.fc11) and would like to know whether these problems are still present.
  Here it is:
  Please download all of the x86_64 RPM files, then update cups like this (as root):
  rpm -Fvh cups-*1.4-0.rc1.3.fc11*.rpm
  You shouldn't need to reboot or restart CUPS (updating the packages will restart it).
  Let me know whether (a) LPD printing works, and (b) cancelled jobs are restarted.
  Created attachment 348431 [details]
  All CUPS error logs
  rpm -Fvh cups-*1.4-0.rc1.3.fc11*.rpm installs only cups and cups-libs; Is that expected?
  The first thing I notice is, in the web interface there are now jobs showing on the "active jobs" page with a status of canceled. These jobs are as old as last Saturday. Shouldn't they be in the "completed jobs" page?
  There may be multiple issues here that are leading me off track.. This test job I've been using (a 276-page PDF) also fails to print directly from windows. Could be a problem with the latest adobe reader- I've seen that happen before. However that still does not explain why these canceled jobs are re-appearing. I'm going to change the summary for this report, and just focus on that, OK?
  All canceled jobs are shown on the "completed jobs" page. Some of those are also shown on the "active jobs" page.
  (In reply to comment #15)
  > I'm going to change the summary for this report, and just focus on that, OK?
  Good idea.
  What does this say when you paste it into a terminal window?:
  python <<EOF
  import cups, pprint
  pprint.pprint (cups.Connection().getJobs())
  EOF
  (In reply to comment #17)
  > What does this say when you paste it into a terminal window?:
  >
  > python <<EOF
  > import cups, pprint
  > pprint.pprint (cups.Connection().getJobs())
  > EOF
  {161: {'job-k-octets': 80574,
  'job-media-sheets-completed': 0,
  'job-name': u'smbprn.00000001 181761.pdf',
  'job-originating-user-name': u'192.168.1.12\\blueh2o',
  'job-preserved': True,
  'job-printer-uri': u'ipp://arturo:631/printers/OptraR',
  'job-priority': 50,
  'job-state': 7,
  'time-at-completed': 1244946374,
  'time-at-creation': 1244723428,
  'time-at-processing': 1244848177},
  167: {'job-k-octets': 29,
  'job-media-sheets-completed': 1,
  'job-name': u'smbprn.00000001 Nero Cover Designer',
  'job-originating-user-name': u'192.168.1.12\\blueh2o',
  'job-preserved': True,
  'job-printer-uri': u'ipp://arturo:631/printers/OptraR',
  'job-priority': 50,
  'job-state': 7,
  'time-at-completed': 1245241987,
  'time-at-creation': 1245093965,
  'time-at-processing': 1245093991}}
  >
  {'attributes-charset': u'utf-8',
  'attributes-natural-language': u'en-us',
  'document-count': 1,
  'document-format': u'application/vnd.cups-raw',
  'job-hold-until': u'no-hold',
  'job-id': 167,
  'job-k-octets': 29,
  'job-media-progress': 0,
  'job-media-sheets-completed': 1,
  'job-more-info': u'ipp://localhost:631/jobs/167',
  'job-name': u'smbprn.00000001 Nero Cover Designer',
  'job-originating-host-name': u'192.168.1.12',
  'job-originating-user-name': u'192.168.1.12\\blueh2o',
  'job-preserved': True,
  'job-printer-state-message': u'',
  'job-printer-state-reasons': [u'none'],
  'job-printer-up-time': 1245419832,
  'job-printer-uri': u'ipp://arturo:631/printers/OptraR',
  'job-priority': 50,
  'job-sheets': [u'none', u'none'],
  'job-state': 7,
  'job-state-reasons': u'job-canceled-by-user',
  'job-uri': u'ipp://localhost:631/jobs/167',
  'job-uuid': u'urn:uuid:414e2b81-9fa8-3a27-5732-133cb85bd384',
  'printer-uri': u'ipp://localhost/printers/OptraR',
  'time-at-completed': 1245241987,
  'time-at-creation': 1245093965,
  'time-at-processing': 1245093991}
  Interestingly, both jobs 161 and 167 have had this happen:
  error_log:67:E [15/Jun/2009:15:26:31 -0400] [Job 167] Unable to convert file 1 to printable format!
  error_log-20090614:316:E [12/Jun/2009:19:09:37 -0400] [Job 161] Unable to convert file 1 to printable format!
  ...which seems odd as they are raw jobs.
  This is something in common with bug #507442. Both jobs 161 and 167 had been restarted, and in bug #507442 the job had been stopped due to lack of authentication, then restarted using CUPS-Authenticate-Job.
  Perhaps something screwy is going on with CUPS's mechanism for restarting jobs.
  I've just built a CUPS package that will log some useful information (at log level 'error') when it is unable to convert a file. Please install it, and watch for the problem to reappear. When it does, please attach the error_log file here.
  I'm hoping to see something like:
  E [15/Jun/2009:15:26:31 -0400] [Job 167] Unable to convert file 1 to printable format!
  E [15/Jun/2009:15:26:31 -0400] [Job 167] Required: application/vnd.cups-raw -> printer/OptraR
  E [15/Jun/2009:15:26:31 -0400] [Job 167] Available:
  application/octet-stream -> application/vnd.cups-raw (-)
  E [15/Jun/2009:15:26:31 -0400] [Job 167] Available: application/pdf -> application/vnd.cups-postscript (pdftops)
  ...
  listing all of the available filters and the MIME type transformations they perform.
  Oh, I meant to hold off posting that until the package had actually built... I'll add a link here when it's finished.
  Here it is:
  Created attachment 349125 [details]
  CUPS error log
  Well the canceled jobs disappeared from the active page.. I couldn't get the same error (yet) but I did get errors. I'm not sure what to make of them.
  Well, that last job seems to have given the printer a hissy-fit. I can't reset it, and it's not even responding to ping anymore. I'll have to continue this testing later as I am not anywhere near the printer to physically reset it.
  Those errors are from the printer not accepting the job correctly.
  Have you seen the "Unable to convert file" error message again since using the package from comment #23?
  No, I have not.
  OK. Well, nothing in particular has changed that would prevent the problem, so presumably it's still there. I'll leave this in NEEDINFO until you spot it again. Thanks for helping to track this down!
  I actually saw this myself today but was unable to reproduce it.