CUPS does not have permission to write error_log

Bug #43298 reported by mannheim
This bug report is a duplicate of:  Bug #41267: cupsys cannot create error_log. Edit Remove
16
Affects Status Importance Assigned to Milestone
cupsys (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Although printing is working fine at the moment, my /var/log/syslog is filled with messages like this:

May 6 15:00:03 localhost cupsd: Unable to open log file "/var/log/cups/error_log" - Permission denied
May 6 15:00:38 localhost last message repeated 84 times
May 6 15:01:43 localhost last message repeated 156 times
May 6 15:02:48 localhost last message repeated 156 times
May 6 15:03:53 localhost last message repeated 156 times

(and so it carries on and on). The file /var/log/cups/error_log has permissions -rw-r--r-- and its owner/group are "root" and "lp". The cupsd process is running with UID "cupsys". If I change the owner of the error_log to "cupsys" then the messages cease. There seems to be a similar problem with access_log. Some files in /var/log/cups/ are owned by cupsys, some by root.

(I have set the logging level to "debug", which explains why cupsd is trying to write so much to the error log file.)

Revision history for this message
mannheim (kronheim) wrote :

I should have said, that I am running the dapper cupsys package version 1.1.99.rc3-0ubuntu2. But a glance at my log files suggests this has been going on for a little while.

Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote :

Please delete all cups logs file and restart cupsys.

Changed in cupsys:
status: Unconfirmed → Needs Info
Revision history for this message
Dennis Kaarsemaker (dennis) wrote :

Rejecting as duplicate

Changed in cupsys:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.