2013-03-14T05:56:18ZFluxBBhttps://bbs.archlinux.org/viewtopic.php?id=159555OK, I found out what was wrong. The Avahi service cups needed is actually called avahi-daemon.service, and it was not enabled. I've enabled that and cups.service, and everything is working properly again. The problem must have started when I was tweaking my printer's configuration and I enabled printer sharing--avahi is needed for that, but since it wasn't properly enabled in systemd, cups was freaking out and bogging down journald with all the errors. The only thing I don't understand is why the journals didn't show this problem until today.]]>https://bbs.archlinux.org/profile.php?id=433832013-03-14T05:56:18Zhttps://bbs.archlinux.org/viewtopic.php?pid=1243925#p1243925Thanks for the tip ilkyest, but it didn't make any difference to the systemd-journald problem.

However, I looked at journalctl again and found it cluttered with CUPS failures:

Sometimes ago, I was presencing a very laggy acces, but I use "mechanic HDDs". And make it better with this. Until new kernel, this were succesfull

]]>https://bbs.archlinux.org/profile.php?id=339382013-03-13T03:16:05Zhttps://bbs.archlinux.org/viewtopic.php?pid=1243401#p1243401I started noticing this problem a few days ago, but I thought it was because I was running too much with too little RAM. But when running nothing more than a KDE desktop, my CPU usage bounces between 50% and 100%, making things laggy. It looks like systemd-journald is to blame, as it is using 50% of the CPU. This is an AMD Phenom II dual core, so this definitely shouldn't be happening. I noticed journal logs were more than 2 GB, so I deleted everything within /var/log/journal/. Rebooted, no change, so I disabled journal storage, but that did not solve the problem.Nothing in the logs looks like a problem to me:

I am using a two or three year old SSD, so maybe it has gotten some bad sectors? But that doesn't explain why journald still bricks things when it isn't logging anything. The install is 10 months old, and I switched from init to systemd around October. Is there anything I can do, short of reinstalling?