Re: [squid-users] SQUID Logrotate problem

 On Mon, 18 Jul 2011 15:28:54 +0200, Railic Njegos wrote:
> On Mon, Jul 18, 2011 at 2:15 PM, Amos Jeffries <squid3_at_treenet.co.nz>
> wrote:
>> On 18/07/11 23:02, Railic Njegos wrote:
>>>
>>> On Mon, Jul 18, 2011 at 12:57 PM, John Doe<jdmls_at_yahoo.com>  wrote:
>>>>
>>>> From: Railic Njegos<railic.njegos_at_gmail.com>
>>>>
>>>>> i have problem, after uprade CentOS 5.5 to 5.6, Logrotate don't
>>>>> work
>>>>> on two proxy servers. I have installed :
>>>>> On first server , squid logs never rotated, config is here
>>>>> On second server squid logs rotated every day . Config :
>>>>> Before upgrade i have this  config and all working nice.
>>>>> Can someone help me ?
>>>>
>>>> If you compare the two configuration files from your post, they
>>>> are
>>>> identical...
>>>> Only difference with mines is the delaycompress.
>>>>
>>>> JD
>>>>
>>>
>>> I know. But before upgrade this configuration working. But, they
>>> are
>>> behave diferently
>>> after upgrade. In other word,  no one now is not working well.
>>>
>>> Njegos
>>
>> Please explain the part about "don't work".
>>
>> Multiple log files with some empty?
>>  * check for logfile_rotate directive. Must be set to 0 when an
>> external log
>> rotation software is used. Default if unset is >0.
>>
>> Squid failing to answer query afterwards?
>>  * check for crashes on -k rotate in the new version
>>
>> Amos
>> --
>> Please be using
>>  Current Stable Squid 2.7.STABLE9 or 3.1.14
>>  Beta testers wanted for 3.2.0.9
>>
>
> On first server logs never rotated. And first log file become big.
> When I rotate manually, i don't have any error.

 Sounds like the problem is in logrotate. The squid -k rotate with
 logfile_rotate 0 just closes the logs and reopens whatever is now using
 the filenames. logrotate is fully responsible for moving the file and
 creating a new one ready for the squid re-open to shift to.

 Check for file permissions.

 Amos
Received on Mon Jul 18 2011 - 22:33:33 MDT