CUPS log files flooding

[Lord of Gore]

mark wrote:
> Margaret Doll wrote:
>   
>> The changes that I found on the cupsd.conf file included:
>>
>> The configuration file that I had been using successfully included
>>
>> #Port 80
>> #Port 443
>> Port 631
>>
>>     
> Right. AFAIK, you need that.
>
>   
>> The new configuration file had the following entry for each printer
>>
>> <Location /printers/gc-hp201>
>> Order Deny,Allow
>> Deny From All
>> Allow From 127.0.0.1
>> AuthType None
>> Allow from Al
>> </Location>l
>>
>>     
> Probably should be one. I dunno if a port statement should be there. Also, was
> there a typo, or is that actually Allow from Al (and, if so, who's Al? <g>,
> rather than All.
>   
Maybe I am late but hey, better late than never? Hope it will serve you 
good.

The second l is (wrongfully :) ) after </Location>.
I would try
#cd /var
#du --max-depth 1 -H

and check where is the problem
> 	mark
>   
>> On Sep 12, 2008, at 1:27 PM, Margaret Doll wrote:
>>
>>     
>>> On Sep 12, 2008, at 1:22 PM, mark wrote:
>>>
>>>       
>>>> Margaret Doll wrote:
>>>>         
>>>>> I have a cron job that deletes the spool cups jobs every night.
>>>>>
>>>>> I made no changes in the system except to add a few users since the
>>>>> updates and the time the problem began to occur.
>>>>>
>>>>> We are also running samba and named on the system.
>>>>>           
>>>> When up2date did the updating, did it update some configuration files?
>>>>
>>>>     mark
>>>>         
>>> I  think you hit on the problem.  I changed back to the
>>> cupsd.conf.save.  access_log is
>>> still getting the
>>>
>>>       
>>>>>>>> localhost - - [05/Sep/2008:14:20:18 -0400] "POST / HTTP/1.1" 200 192
>>>>>>>> localhost - - [05/Sep/2008:14:20:18 -0400] "POST / HTTP/1.1" 200 192
>>>>>>>>                 
>>> messages.  However, /var switched from 71% full to 51% full.
>>>
>>> I will now look and see what changed in cupsd.conf.  I will get back
>>> to you.
>>>
>>> Thanks.
>>>
>>>       
>>>>> On Sep 12, 2008, at 1:06 PM, mark wrote:
>>>>>
>>>>>           
>>>>>> Margaret Doll wrote:
>>>>>>             
>>>>>>> I did my last update today using up2date.   The update that  I did on
>>>>>>> August 28th included the updates that changed this system.  I do have
>>>>>>> ten other RedHat system at various versions;  I don't see the
>>>>>>> problem on
>>>>>>> the other systems.
>>>>>>>
>>>>>>> The errors in the /var/log/cups/access_log  have always been
>>>>>>>
>>>>>>> localhost - - [05/Sep/2008:14:20:18 -0400] "POST / HTTP/1.1" 200 192
>>>>>>> localhost - - [05/Sep/2008:14:20:18 -0400] "POST / HTTP/1.1" 200 192
>>>>>>>
>>>>>>> However, after the last upgrade this access_log is large very quickly
>>>>>>> and fills up the
>>>>>>> /var partition.  I have turned off the LogLevel on
>>>>>>> cups to none, so access_log has stopped growing.
>>>>>>>
>>>>>>> There is also something else going on as well.
>>>>>>>
>>>>>>> /var is still filling up.  I know that the log and named
>>>>>>> directories in
>>>>>>> /var contain the files that are growing.
>>>>>>>               
>>>>>> <snip>
>>>>>> Could it be that the spool files are not being deleted?
>>>>>>
>>>>>>   mark
>>>>>>
>>>>>> -- 
>>>>>> redhat-list mailing list
>>>>>> unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
>>>>>> https://www.redhat.com/mailman/listinfo/redhat-list
>>>>>>             
>>>> -- 
>>>> redhat-list mailing list
>>>> unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
>>>> https://www.redhat.com/mailman/listinfo/redhat-list
>>>>         
>>> -- 
>>> redhat-list mailing list
>>> unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
>>> https://www.redhat.com/mailman/listinfo/redhat-list
>>>       
>
>