Bug 206075
Summary: | CUPS flooding access_log | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Glenn Zazulia <bugzilla-fedora> |
Component: | cups | Assignee: | Tim Waugh <twaugh> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-10-23 12:46:33 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Glenn Zazulia
2006-09-11 20:02:51 UTC
This: http://cups.org/newsgroups.php?s1+gcups.bugs+v4+T0+Qaccess_log+flood is not related. It refers to the polling mode of eggcups, which is a fallback used only when D-BUS is unavailable. This polling mode does not cause 5000 lines/minute logging. This URL: http://svn.debian.org/wsvn/pkg-cups...n/?rev=154&sc=1 seems incomplete, so I cannot comment on it. Looks like this bug is a duplicate of another one that has been reported (bug #205619), but just to be sure: do you see high CPU load when this occurs? I have more information. In fact, I seem to have solved my problem. First, though, to answer your question: yes, I was seeing high CPU load (the cups process was hogging around 90% of the CPU) when this occured, and I needed to stop the cups service in order to free up the CPU and stop the logging, of course. Also, certain client commands like "lpq" or the "Default Print" applet (/usr/bin/gnome-default-printer) would hang and need to be killed. Now, what I did to set things right: I removed my previous PRD file(s) from /etc/cups/ppd and cleared out the /etc/cups/printers.conf and then re-added/configured my printer using the web-based admin interface (http://localhost:631). I also restored my cupsd.conf file to match the default version that comes with the rpm distribution, though the various cupsd.conf settings tried were never the cause of the problem. I'm fairly certain that the previous PRD file was the culprit. I had upgraded systems from FC4 and at the same time upgraded hardware (though kept the same architecture). The printer is the same, but it is now connected over USB instead of the parallel port. Since fixing the PRD, the access_log now shows only one record every 5 minutes or so (not consistently, but varying from maybe 3-10 minutes). I assume this is due to the normal behavior of samba and/or eggcups, etc. Printing is working fine both locally and over samba (ie. from remote Windows clients). So, all is well now. (Of course, it's probably still worth looking into the prevention of run-away log floods -- even due to misconfigurations.) Sorry, one last side-note: the reason I didn't immediately think to replace the PRD file is that the printer was actually working fine for some time after setting up my FC5 system -- I had been printing successfully both locally and over samba. Then on 9/7/06, when I last ran a "yum update" and upgraded cups to version 1.2.3, I started noticing the problem with the cups access_log filling up my /var filesystem. |