Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#31348 - [cups] cups does not start with systemd, 100% CPU load

Attached to Project: Arch Linux
Opened by Christian Hesse (eworm) - Friday, 31 August 2012, 05:49 GMT
Last edited by Evangelos Foutras (foutrelis) - Saturday, 01 September 2012, 14:53 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


I get these messages in my syslog several times:
systemd[1615]: Failed at step NAMESPACE spawning /usr/sbin/cupsd: Operation not permitted
systemd[1]: cups.service: main process exited, code=exited, status=226
systemd[1]: Unit cups.service entered failed state.

After that log is flooded with this:
systemd[1]: cups.service start request repeated too quickly, refusing to start.

One CPU core is at 100% load, after stopping cups.socket and cups.service everything is fine (except I can not print).

Additional info:
cups 1.6.1-5
systemd 189-3
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Saturday, 01 September 2012, 14:53 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#31301 
Comment by Cristiano Peressini (SleazyCriss) - Friday, 31 August 2012, 10:31 GMT
Same here after the update of this morning where systemd, systemd-tools and libsystemd were merged in a single package systemd.

Before cups wasn't working but now systemd and systemd-journal take about 50-70% of cpu on quadcore cpu!