Re: logrotate: file size changed while zipping

[Camaleón <noelamac@gmail.com>]

On Thu, 26 Jul 2012 18:45:12 +0200, Slavko wrote:

> Dňa Thu, 26 Jul 2012 15:21:34 +0000 (UTC) Camaleón <noelamac@gmail.com>
> napísal:

(...)

>> > /etc/cron.daily/logrotate:
>> > gzip: stdin: file size changed while zipping
>> 
>> The error seems coming from "zip.c" library. Have you installed the
>> stock version?
> 
> I am not sure, are you mean the gzip package? 

Yup.

> My gzip is from official repo:
> 
> LANG=C aptpo gzip
> gzip:
>   Installed: 1.5-1.1

(...)

Okay.

>> Also, have you edited any of the logrotate routines at
>> "/etc/logrotate.d/ *" or have you added a self-made one?
> 
> Yes, i have modified (one) and my own (two) routines there, but i have
> them a long time before this message appears. They are untouched a long
> time too. I check this now, and they last changes are some months ago
> (both modified & custom) - march and older. The newest one is
> /etc/logrotate.d/tor from 2012-07-06.

I never got that message, that's why I asked. Anyway, I wonder how common 
can be the above warning :-?
 
>> If the warning can be reproduced consistently (every day) and you have
>> the official packages with no other editions/configurations made by
>> you, I would consider in filing a bug report.
> 
> Yes, they are daily here. Filling bugreport is no problem for me, but
> first i want (need) to identify the source of this message, as you
> properly pointed, they can come from my own or customized routines
> (probably not, because they was a long time untouched).
> 
> Can i check this by finding the ungzipped old log files? 

Yes. There has to be at least one file under "/var/log/" (and sub-dirs) 
that has not been compressed (if all the logs are placed here, of course).

> Or is there way to disable particular logrotate routine? 

Well, I suppose you can comment out ("#") the whole code block for the 
desired file under "/etc/logrotate.d/*" or simply adding "nocompress" 
option instead to find out the culprit.

> Or some another way? I don't know...

If there are no more clues about the warning at the syslog, hard to 
tell :-?

Greetings,

-- 
Camaleón