[SOLVED] systemd, systemd-journal constantly at high CPU %age

Question

Hi all,
I've switched a computer to systemd, and everything works nicely. The system is responsive and booting is even faster than before. Yay!
However, both my CPU cores are constantly between 80% and 90%. When I do top in a terminal, I see systemd constantly in the 90%-100% range and systemd-journal in the 60%-100% range, also continuously. My CPU temperature is a lot higher than normal as well (currently at 61.0C)
Is this normal?
Last edited by diederick76 (2012-09-13 06:03:11)

Answer 1

I'm having a similar problem.  I temporarily fixed it by replacing the cupsd.conf with the cupsd.con.default.  Everything ran great, got the printer configured again, journald stopped thrashing my precious SSD by producing millions of these warnings (I didn't wc them, but I was probably getting thousands every second) and all was well.  Until I "shared" the printer again.  Immediately cupsd got locked into restarting thousands of times every second, once again thrashing my cpu and SSD.
Edit:
I guess I should probably share my cupsd.conf.  I didn't manually edit it, I used the web interface:
cat /etc/cups/cupsd.conf
LogLevel warn
SystemGroup sys root
# Allow remote access
Port 631
Listen /var/run/cups/cups.sock
# Share local printers on the local network.
Browsing On
BrowseLocalProtocols dnssd
DefaultAuthType Basic
WebInterface Yes
<Location />
# Allow shared printing...
Order allow,deny
Allow all
</Location>
<Location /admin>
</Location>
<Location /admin/conf>
AuthType Default
Require user @SYSTEM
</Location>
<Policy default>
JobPrivateAccess default
JobPrivateValues default
SubscriptionPrivateAccess default
SubscriptionPrivateValues default
<Limit Create-Job Print-Job Print-URI Validate-Job>
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default CUPS-Get-Devices>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Cancel-Job CUPS-Authenticate-Job>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
</Policy>
<Policy authenticated>
JobPrivateAccess default
JobPrivateValues default
SubscriptionPrivateAccess default
SubscriptionPrivateValues default
<Limit Create-Job Print-Job Print-URI Validate-Job>
AuthType Default
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document>
AuthType Default
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Cancel-Job CUPS-Authenticate-Job>
AuthType Default
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
</Policy>
Edit02:
I should mention that I tried the fix described here:  https://bbs.archlinux.org/viewtopic.php?id=146154
Deiderick:  Have you "shared" your printer?  I suspect that this may be what is causing the problem.
To Mods:  At this point, because the OP's problem has been resolved, and this thread is marked "solved" should I make a new thread?  It is possible that my problem is not identical to the OP's.
As a side note, I ran "journalctl | wc -l"  it took about a minute of maxing out one core to finish.  The final number:  1232889.   I have a feeling that this reflects only a fraction of the warnings that cups produced, seeing as I only allocated limited hd space for journal messages.
Edit03:  After re-reading the etiquette thread, I've decided to start a new thread.  This one is marked "solved" and although very similar, it may not be exactly the same problem that I am having.
Last edited by Convergence (2012-09-23 00:28:14)