-
-
Notifications
You must be signed in to change notification settings - Fork 14.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Journalctl spam with 1/sec 'cupsd[1394]: Expiring subscriptions' #195090
Comments
Experiencing this too.... weird |
I disabled avahi to work around this, but I'm not happy about it. |
I just noticed the same issue on my desktop. |
I've also gone the route of disabling avahi for the time being. In a discourse thread here: |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/cupsd-messages-littering-logs/20015/7 |
Fixes NixOS/nixpkgs#195090. NixOS systems with Avahi enabled would previously spam the journal with this log message once a second: this hides that spam behind the log level.
Patch message is in that file; also submitted upstream but that will probably take a while, so this is a stopgap until then.
Two observations: https://sourcegraph.com/github.com/OpenPrinting/cups/-/blob/scheduler/main.c?L978-985 looks buggy. I expect something like However, more importantly for NixOS: epoll_wait on my system always gets called with a timeout of 1 second. It would be interesting what select_timeout returns. I run Cups on a laptop and don't want extra unnecessary wakeups. It would be nice, if I could just gdb-attach to cupsd and "b select_timeout" but I haven't figured out how I use cupsd debug symbols yet to inspect the "why" variable that is conveniently set by select_timeout. Also for some weird reason, on my system restarting cups twice fixes the issue, at least temporarily. |
I managed to rebuild my cupsd with debugging symbols. But sadly, the spam is gone! Does somebody know how to trigger the spam? Restarting avahi-daemon.service nor dbus.service does the trick. |
OpenPrinting/cups#578 has been merged upstream last week, that should solve this issue. Thanks @ckiee! |
Note that OpenPrinting/cups#578 doesn't actually fix the problem but rather only suppresses the message. |
Upstream received a fix in OpenPrinting/cups#767. It's very new so not yet released. |
Should have been fixed by #256378. |
will it be in 23.11? @pwaller |
It's on nixos-unstable now so I believe so. |
It was also backported to 23.05 in #257637. |
Describe the bug
A clear and concise description of what the bug is.
Steps To Reproduce
Steps to reproduce the behavior:
journalctl
Expected behavior
No log spam.
Additional context
Here is my NixOS configuration which I could identify as 'obviously' relating to printing. So far as I know, printing and scanning work fine.
Notify maintainers
cc @matthewbauer
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result.Note, I'm using flakes and don't have any channels configured.
The text was updated successfully, but these errors were encountered: