Hi,

On 17.02.2019 11:38, Tapani Tarvainen wrote:
> Hi,
> 
> 1. Confirmed. Seems to happen randomly about twice a month or so.

Ok, I'm not alone. ;-)

> 2. My first guess of the cause is that as logwatch runs at
>    the same time as logrotate it causes a race condition:
> 
> # fcrontab -l|grep log
> 2019-02-17 12:32:01  INFO listing root's fcrontab
> 01 * * * *      /usr/sbin/logrotate /etc/logrotate.conf
> 01 0 * * *      /usr/local/bin/logwatch > /var/log/logwatch/`date -I -d yesterday`; \
>                 LOGWATCH_KEEP=$(sed -ne 's/^LOGWATCH_KEEP=\([0-9]\+\)$/\1/p' /var/ipfire/logging/settings); \
>                 find /var/log/logwatch/ -ctime +${LOGWATCH_KEEP=56} -exec rm -f '{}' ';'
> 
> Try changing the minute value in logwatch to 02 or maybe 03 to be on the safe side.

Done. Changed to "03". We'll see.

> Incidentally, why is logrotate being run every hour? Wouldn't daily be enough?

No idea. Better granularity?

Best,
Matthias

> 
> Tapani
> 
> 
> On Sun, Feb 17, 2019 at 10:22:26AM +0100, Matthias Fischer (matthias.fischer(a)ipfire.org) wrote:
>> 
>> Hi,
>> 
>> I discovered something weird:
>> 
>> >From time to time 'logwatch' does not create a daily log.
>> 
>> E.g.:
>> The file '/var/log/logwatch/2019-14-26' exists, but size = 0 Bytes.
>> 
>> The same happened yesterday with '/var/log/logwatch/2019-02-16':
>> 0 Bytes.
>> 
>> After running...
>> 
>> /usr/local/bin/logwatch > /var/log/logwatch/`date -I -d yesterday`; \
>> LOGWATCH_KEEP=$(sed -ne 's/^LOGWATCH_KEEP=\([0-9]\+\)$/\1/p'
>> /var/ipfire/logging/settings); \
>> find /var/log/logwatch/ -ctime +${LOGWATCH_KEEP=56} -exec rm -f '{}' ';'
>> 
>> ...manually from console, file was created, everything looks ok.
>> 
>> 1. Can anyone confirm?
>> 
>> 2. With which parameter could I change the starting time "01 0 * * *" so
>> that this doesn't happen again? I'm searching, but can't find a grip on
>> this...
>> 
>> Best,
>> Matthias
>