Bug#734084: marked as done (cups: cupsd resubmitted print jobs on logrotate action / did not recognize successful printing)
Your message dated Tue, 26 Apr 2016 16:35:24 +0100
with message-id <26042016162946.3f2a7f58e654@desktop.copernicus.demon.co.uk>
and subject line Re: Bug#734084: cups: cupsd resubmitted print jobs on logrotate action / did not recognize successful printing
has caused the Debian Bug report #734084,
regarding cups: cupsd resubmitted print jobs on logrotate action / did not recognize successful printing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
734084: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734084
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: cups: cupsd resubmitted print jobs on logrotate action / did not recognize successful printing
- From: Will Aoki <waoki@umnh.utah.edu>
- Date: Fri, 3 Jan 2014 09:26:39 -0700
- Message-id: <20140103162639.GJ20237@umnh.utah.edu>
Package: cups
Version: 1.5.3-5+deb7u1
Severity: normal
I discovered this morning that a computer running CUPS and using printers
advertised from another CUPS server has been resending print jobs whenever its
logs are rotated. The remote server was printing the job, but it would
remain in the queue on the local server.
The page_log looks like this:
rtc-xxxxxxx xxxxx 273 [03/Jan/2014:07:59:54 -0700] 1 1 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
rtc-xxxxxxx xxxxx 273 [03/Jan/2014:07:59:54 -0700] total 0 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
rtc-xxxxxxx xxxxx 273 [03/Jan/2014:07:59:55 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
rtc-xxxxxxx xxxxx 273 [03/Jan/2014:07:59:56 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
rtc-xxxxxxx xxxxx 273 [03/Jan/2014:07:59:58 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:01 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:06 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:14 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:16 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:19 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:19 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:21 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:26 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:34 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:35 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:36 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:38 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:42 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
The error log contains messages like this:
E [03/Jan/2014:07:59:46 -0700] Failed to update TXT record for Lexmark International Lexmark E260dn @ xxxxxxxxxxxx.utah.edu: -2
E [03/Jan/2014:07:59:46 -0700] Failed to update TXT record for test-e260dn @ xxxxxxxxxxxx.utah.edu: -2
E [03/Jan/2014:07:59:51 -0700] SLPReg of "Lexmark-E260dn" failed with status -20!
E [03/Jan/2014:07:59:51 -0700] SLPReg of "test-e260dn" failed with status -20!
E [03/Jan/2014:08:00:22 -0700] SLPReg of "Lexmark-E260dn" failed with status -20!
E [03/Jan/2014:08:00:22 -0700] SLPReg of "test-e260dn" failed with status -20!
E [03/Jan/2014:08:00:54 -0700] SLPReg of "Lexmark-E260dn" failed with status -20!
E [03/Jan/2014:08:00:54 -0700] SLPReg of "test-e260dn" failed with status -20!
referring to a completely different printer which was, at one time, attached to
the local machine via USB. There's no mention of the printer this problem was
observed on.
After deleting the job and the disconnected & apparently-unrelated printer, I
was not able to reproduce this problem again, even when printing the same file.
I verified that the PostScript being sent was the same. I saved the contents of
/var/log/cups, /var/cache/cups and /var/spool/cups from before I deleted
anything, so I do have these files available for investigation.
-- System Information:
Debian Release: 7.3
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages cups depends on:
ii adduser 3.113+nmu3
ii bc 1.06.95-2+b1
ii cups-client 1.5.3-5+deb7u1
ii cups-common 1.5.3-5+deb7u1
ii cups-filters 1.0.18-2.1
ii cups-ppdc 1.5.3-5+deb7u1
ii debconf [debconf-2.0] 1.5.49
ii dpkg 1.16.12
ii ghostscript 9.05~dfsg-6.3+deb7u1
ii libavahi-client3 0.6.31-2
ii libavahi-common3 0.6.31-2
ii libc-bin 2.13-38
ii libc6 2.13-38
ii libcups2 1.5.3-5+deb7u1
ii libcupscgi1 1.5.3-5+deb7u1
ii libcupsimage2 1.5.3-5+deb7u1
ii libcupsmime1 1.5.3-5+deb7u1
ii libcupsppdc1 1.5.3-5+deb7u1
ii libdbus-1-3 1.6.8-1+deb7u1
ii libgcc1 1:4.7.2-5
ii libgnutls26 2.12.20-7
ii libgssapi-krb5-2 1.10.1+dfsg-5+deb7u1
ii libkrb5-3 1.10.1+dfsg-5+deb7u1
ii libldap-2.4-2 2.4.31-1+nmu2
ii libpam0g 1.1.3-7.1
ii libpaper1 1.1.24+nmu2
ii libslp1 1.2.1-9
ii libstdc++6 4.7.2-5
ii libusb-1.0-0 2:1.0.11-1
ii lsb-base 4.1+Debian8+deb7u1
ii poppler-utils 0.18.4-6
ii procps 1:3.3.3-3
ii ssl-cert 1.0.32
Versions of packages cups recommends:
ii avahi-daemon 0.6.31-2
ii colord 0.1.21-1
ii foomatic-filters 4.0.17-1
ii ghostscript-cups 9.05~dfsg-6.3+deb7u1
ii printer-driver-gutenprint 5.2.9-1
Versions of packages cups suggests:
ii cups-bsd 1.5.3-5+deb7u1
pn cups-pdf <none>
ii foomatic-db 20120523-1
ii hplip 3.12.6-3.1+deb7u1
ii printer-driver-hpcups 3.12.6-3.1+deb7u1
ii smbclient 2:3.6.6-6+deb7u2
ii udev 175-7.2
-- debconf information:
cupsys/raw-print: true
cupsys/backend: ipp, ipp14, lpd, socket, usb, snmp, dnssd
--- End Message ---
--- Begin Message ---
- To: 734084-done@bugs.debian.org
- Subject: Re: Bug#734084: cups: cupsd resubmitted print jobs on logrotate action / did not recognize successful printing
- From: Brian Potkin <claremont102@gmail.com>
- Date: Tue, 26 Apr 2016 16:35:24 +0100
- Message-id: <26042016162946.3f2a7f58e654@desktop.copernicus.demon.co.uk>
- In-reply-to: <20140103162639.GJ20237@umnh.utah.edu>
- References: <20140103162639.GJ20237@umnh.utah.edu>
On Fri 03 Jan 2014 at 09:26:39 -0700, Will Aoki wrote:
> Package: cups
> Version: 1.5.3-5+deb7u1
> Severity: normal
>
> I discovered this morning that a computer running CUPS and using printers
> advertised from another CUPS server has been resending print jobs whenever its
> logs are rotated. The remote server was printing the job, but it would
> remain in the queue on the local server.
>
> The page_log looks like this:
>
> rtc-xxxxxxx xxxxx 273 [03/Jan/2014:07:59:54 -0700] 1 1 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
> rtc-xxxxxxx xxxxx 273 [03/Jan/2014:07:59:54 -0700] total 0 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
> rtc-xxxxxxx xxxxx 273 [03/Jan/2014:07:59:55 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
> rtc-xxxxxxx xxxxx 273 [03/Jan/2014:07:59:56 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
> rtc-xxxxxxx xxxxx 273 [03/Jan/2014:07:59:58 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
> rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:01 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
> rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:06 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
> rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:14 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
> rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:16 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
> rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:19 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
> rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:19 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
> rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:21 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
> rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:26 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
> rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:34 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
> rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:35 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
> rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:36 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
> rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:38 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
> rtc-xxxxxxx xxxxx 273 [03/Jan/2014:08:00:42 -0700] total 5 - localhost xxxxxxxxxxxxxxxxxxxxx.pdf - -
>
> The error log contains messages like this:
>
> E [03/Jan/2014:07:59:46 -0700] Failed to update TXT record for Lexmark International Lexmark E260dn @ xxxxxxxxxxxx.utah.edu: -2
> E [03/Jan/2014:07:59:46 -0700] Failed to update TXT record for test-e260dn @ xxxxxxxxxxxx.utah.edu: -2
> E [03/Jan/2014:07:59:51 -0700] SLPReg of "Lexmark-E260dn" failed with status -20!
> E [03/Jan/2014:07:59:51 -0700] SLPReg of "test-e260dn" failed with status -20!
> E [03/Jan/2014:08:00:22 -0700] SLPReg of "Lexmark-E260dn" failed with status -20!
> E [03/Jan/2014:08:00:22 -0700] SLPReg of "test-e260dn" failed with status -20!
> E [03/Jan/2014:08:00:54 -0700] SLPReg of "Lexmark-E260dn" failed with status -20!
> E [03/Jan/2014:08:00:54 -0700] SLPReg of "test-e260dn" failed with status -20!
>
> referring to a completely different printer which was, at one time, attached to
> the local machine via USB. There's no mention of the printer this problem was
> observed on.
>
> After deleting the job and the disconnected & apparently-unrelated printer, I
> was not able to reproduce this problem again, even when printing the same file.
> I verified that the PostScript being sent was the same. I saved the contents of
> /var/log/cups, /var/cache/cups and /var/spool/cups from before I deleted
> anything, so I do have these files available for investigation.
Hello Will, thank you for your report. Support for Wheezy has now come
to an end. There has also been quite a number of changes in integrating
Avahi into CUPS so it is likely the issue has gone away. Should it be
reproducible on the present testing/unstable please feel free to submit
a new report.
Regards,
Brian.
--- End Message ---
Reply to: