Bug 2233078 - cupsd spamming the journal
Summary: cupsd spamming the journal
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: cups
Version: 38
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Zdenek Dohnal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-21 11:07 UTC by Patrick O'Callaghan
Modified: 2023-10-07 01:22 UTC (History)
2 users (show)

Fixed In Version: cups-2.4.7-1.fc39 cups-2.4.7-1.fc38 cups-2.4.7-1.fc37
Clone Of:
Environment:
Last Closed: 2023-09-26 00:18:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Patrick O'Callaghan 2023-08-21 11:07:41 UTC
cupsd logs "Expiring subscriptions..." every second to the journal. The messages themselves don;t say anything useful and there is no obvious way of stopping it. The man page for subscriptions.conf(5) is unhelpful, but states that "This file is not intended to be edited or managed manually".


Reproducible: Always

Steps to Reproduce:
1.Boot system with cupsd enabled
2.Monitor the journal

Actual Results:  
The journal is cluttered with repeated messages from CUPS at 1-second intervals, making the rest of the journal hard to read without filtering.

Expected Results:  
CUPS should be silent unless it has something useful (i.e. actionable) to say.

This has been going on over several releases of Fedora and other Linux distros. Some online comments say that the root problem is a timing issue in CUPS itself, but I've no idea if this is true. It's just very annoying.

Comment 1 Zdenek Dohnal 2023-08-23 14:55:57 UTC
Hi,

this should be fixed in the next upstream release, which I hope to release soon and put it into Fedora.

Comment 2 Zdenek Dohnal 2023-08-23 14:56:25 UTC
Temporary remedy is to restart cups service.

Comment 3 Patrick O'Callaghan 2023-08-23 15:41:32 UTC
(In reply to Zdenek Dohnal from comment #1)
> Hi,
> 
> this should be fixed in the next upstream release, which I hope to release
> soon and put it into Fedora.

Thanks.

Comment 4 Patrick O'Callaghan 2023-08-23 15:43:12 UTC
(In reply to Zdenek Dohnal from comment #2)
> Temporary remedy is to restart cups service.

That has no effect.

Comment 5 Zdenek Dohnal 2023-08-23 16:19:43 UTC
You can try stopping and starting the service (sometimes this helped me) or, which was the last resort, stop cups, cleanup /var/spool/cups of 'd' and 'c' files and start cups.

Comment 6 Patrick O'Callaghan 2023-08-23 21:36:34 UTC
(In reply to Zdenek Dohnal from comment #5)
> You can try stopping and starting the service (sometimes this helped me) or,
> which was the last resort, stop cups, cleanup /var/spool/cups of 'd' and 'c'
> files and start cups.

That did it, thanks (and /var/spool/cups had a *lot* of old files in it).

Comment 7 Fedora Update System 2023-09-21 16:49:38 UTC
FEDORA-2023-351208aa08 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-351208aa08

Comment 8 Fedora Update System 2023-09-21 16:50:55 UTC
FEDORA-2023-96519dc6fd has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-96519dc6fd

Comment 9 Fedora Update System 2023-09-21 16:52:13 UTC
FEDORA-2023-904f92af98 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-904f92af98

Comment 10 Fedora Update System 2023-09-22 01:40:59 UTC
FEDORA-2023-351208aa08 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-351208aa08`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-351208aa08

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2023-09-22 02:03:43 UTC
FEDORA-2023-904f92af98 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-904f92af98`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-904f92af98

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 12 Fedora Update System 2023-09-22 02:29:57 UTC
FEDORA-2023-96519dc6fd has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-96519dc6fd`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-96519dc6fd

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 13 Patrick O'Callaghan 2023-09-22 10:59:20 UTC
(In reply to Fedora Update System from comment #12)
> FEDORA-2023-96519dc6fd has been pushed to the Fedora 38 testing repository.
> Soon you'll be able to install the update with the following command:
> `sudo dnf upgrade --enablerepo=updates-testing --refresh
> --advisory=FEDORA-2023-96519dc6fd`
> You can provide feedback for this update here:
> https://bodhi.fedoraproject.org/updates/FEDORA-2023-96519dc6fd
> 
> See also https://fedoraproject.org/wiki/QA:Updates_Testing for more
> information on how to test updates.

Thanks. Testing this now.

Comment 14 Fedora Update System 2023-09-26 00:18:34 UTC
FEDORA-2023-351208aa08 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2023-09-26 01:22:00 UTC
FEDORA-2023-96519dc6fd has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2023-10-07 01:22:18 UTC
FEDORA-2023-904f92af98 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.