Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
logrotate: file size changed while zipping
1,460 views
Skip to first unread message
Slavko
Jul 26, 2012, 4:50:02 AM7/26/12
to
Hi all,
in last days (perhaps weeks) i get daily mail from cron's logrotate task
with this:
/etc/cron.daily/logrotate:
gzip: stdin: file size changed while zipping
I was no success to find any solution and i am not able to identify what
logrotate's job is produced this. I tried to check the logs, but perhaps i
find bad string - i don't k now. I tried to run logrotate from shell, but
nothing was written to console.
Please, can someone help me to identify the source of this message?
regards
--
Slavko
http://slavino.sk
in last days (perhaps weeks) i get daily mail from cron's logrotate task
with this:
/etc/cron.daily/logrotate:
gzip: stdin: file size changed while zipping
I was no success to find any solution and i am not able to identify what
logrotate's job is produced this. I tried to check the logs, but perhaps i
find bad string - i don't k now. I tried to run logrotate from shell, but
nothing was written to console.
Please, can someone help me to identify the source of this message?
regards
--
Slavko
http://slavino.sk
Camaleón
Jul 26, 2012, 11:30:01 AM7/26/12
to
On Thu, 26 Jul 2012 10:42:30 +0200, Slavko wrote:
> in last days (perhaps weeks) i get daily mail from cron's logrotate task
> with this:
>
> /etc/cron.daily/logrotate:
> gzip: stdin: file size changed while zipping
The error seems coming from "zip.c" library. Have you installed the stock
> in last days (perhaps weeks) i get daily mail from cron's logrotate task
> with this:
>
> /etc/cron.daily/logrotate:
> gzip: stdin: file size changed while zipping
version?
Also, have you edited any of the logrotate routines at "/etc/logrotate.d/
*" or have you added a self-made one?
> I was no success to find any solution and i am not able to identify what
> logrotate's job is produced this. I tried to check the logs, but perhaps
> i find bad string - i don't k now. I tried to run logrotate from shell,
> but nothing was written to console.
>
> Please, can someone help me to identify the source of this message?
the official packages with no other editions/configurations made by you,
I would consider in filing a bug report.
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/jurn9u$tcf$1...@dough.gmane.org
Slavko
Jul 26, 2012, 12:50:02 PM7/26/12
to
Hi,
Dňa Thu, 26 Jul 2012 15:21:34 +0000 (UTC) Camaleón <noel...@gmail.com>
napísal:
> On Thu, 26 Jul 2012 10:42:30 +0200, Slavko wrote:
>
> > in last days (perhaps weeks) i get daily mail from cron's logrotate
> > task with this:
> >
> > /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? My gzip is from official repo:
LANG=C aptpo gzip
gzip:
Installed: 1.5-1.1
Candidate: 1.5-1.1
Version table:
*** 1.5-1.1 0
500 http://ftp.cz.debian.org/debian/ testing/main amd64 Packages
100 /var/lib/dpkg/status
> 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.
> 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? Or is there way
to disable particular logrotate routine? Or some another way? I don't
know...
Dňa Thu, 26 Jul 2012 15:21:34 +0000 (UTC) Camaleón <noel...@gmail.com>
napísal:
> On Thu, 26 Jul 2012 10:42:30 +0200, Slavko wrote:
>
> > in last days (perhaps weeks) i get daily mail from cron's logrotate
> > task with this:
> >
> > /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?
LANG=C aptpo gzip
gzip:
Installed: 1.5-1.1
Candidate: 1.5-1.1
Version table:
*** 1.5-1.1 0
500 http://ftp.cz.debian.org/debian/ testing/main amd64 Packages
100 /var/lib/dpkg/status
> Also, have you edited any of the logrotate routines at "/etc/logrotate.d/
> *" or have you added a self-made one?
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.
> 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.
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? Or is there way
to disable particular logrotate routine? Or some another way? I don't
know...
Camaleón
Jul 26, 2012, 2:00:01 PM7/26/12
to
On Thu, 26 Jul 2012 18:45:12 +0200, Slavko wrote:
> Dňa Thu, 26 Jul 2012 15:21:34 +0000 (UTC) Camaleón <noel...@gmail.com>
> napísal:
(...)
> Dňa Thu, 26 Jul 2012 15:21:34 +0000 (UTC) Camaleón <noel...@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?
> 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.
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?
that has not been compressed (if all the logs are placed here, of course).
> Or is there way to disable particular logrotate routine?
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...
tell :-?
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Slavko
Jul 26, 2012, 3:20:02 PM7/26/12
to
Hi,
Dňa Thu, 26 Jul 2012 17:53:36 +0000 (UTC) Camaleón <noel...@gmail.com>
napísal:
> >> 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 :-?
i understand why you ask.
> > 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).
OK, i have ungziped files from three routines, i will check them one by
one daily - i am patient, to identify the one which causes the problem :-)
I have ungziped some other files too, but they are empty, and i think,
that empty files are not rotated.
I will report the result after checking these three (or all, if will be
needed) files - if i do not forget to do the modification, then after
three (or after 16 days).
> > 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.
yes, the "nocompress" is for me, thanks
> > Or some another way? I don't know...
>
> If there are no more clues about the warning at the syslog, hard to
> tell :-?
i find nothing useful there.
Dňa Thu, 26 Jul 2012 17:53:36 +0000 (UTC) Camaleón <noel...@gmail.com>
napísal:
> >> 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 :-?
> > 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).
one daily - i am patient, to identify the one which causes the problem :-)
I have ungziped some other files too, but they are empty, and i think,
that empty files are not rotated.
I will report the result after checking these three (or all, if will be
needed) files - if i do not forget to do the modification, then after
three (or after 16 days).
> > 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 :-?
Slavko
Jul 27, 2012, 11:20:02 AM7/27/12
to
Hi,
Dňa Thu, 26 Jul 2012 21:11:09 +0200 Slavko <li...@slavino.sk> napísal:
> I will report the result after checking these three (or all, if will be
> needed) files - if i do not forget to do the modification, then after
> three (or after 16 days).
it seems, that i was success on the first attempt :-)
I changed "compress" to "nocompress" in /etc/logrotate.d/tor and no
message from logrotate in my daily mail (i have another messages here,
but they are wanted). It is strange for me, because i have the tor daemon
disabled and i use it only sometime and from my user session (from
vidalia).
It needs more inspection now, but when will be sure, that this is not by my
mistake, i will fill the bugreport. Now there are two files:
ls -l /var/log/tor/
celkom 4,0K
-rw-r----- 1 debian-tor adm 0 júl 7 10:24 log
-rw-r--r-- 1 debian-tor adm 3,5K júl 6 19:37 log.1
The old one (log.1) is from my fist attempts, and all dates in it are
dated at "Jul 06". By my opinion, there can be problem with combination
the "notifempty" and "delaycompress". Another possible source can be the
"create 0640 debian-tor adm" option and the older file with the 644
permissions (not changed by me), but i don't know if this can be problem.
I will do more checks, but any help is welcome :-)
Camaleón, thanks for help
--
Slavko
http://slavino.sk
Dňa Thu, 26 Jul 2012 21:11:09 +0200 Slavko <li...@slavino.sk> napísal:
> I will report the result after checking these three (or all, if will be
> needed) files - if i do not forget to do the modification, then after
> three (or after 16 days).
I changed "compress" to "nocompress" in /etc/logrotate.d/tor and no
message from logrotate in my daily mail (i have another messages here,
but they are wanted). It is strange for me, because i have the tor daemon
disabled and i use it only sometime and from my user session (from
vidalia).
It needs more inspection now, but when will be sure, that this is not by my
mistake, i will fill the bugreport. Now there are two files:
ls -l /var/log/tor/
celkom 4,0K
-rw-r----- 1 debian-tor adm 0 júl 7 10:24 log
-rw-r--r-- 1 debian-tor adm 3,5K júl 6 19:37 log.1
The old one (log.1) is from my fist attempts, and all dates in it are
dated at "Jul 06". By my opinion, there can be problem with combination
the "notifempty" and "delaycompress". Another possible source can be the
"create 0640 debian-tor adm" option and the older file with the 644
permissions (not changed by me), but i don't know if this can be problem.
I will do more checks, but any help is welcome :-)
Camaleón, thanks for help
--
Slavko
http://slavino.sk
Camaleón
Jul 27, 2012, 1:10:01 PM7/27/12
to
On Fri, 27 Jul 2012 17:18:22 +0200, Slavko wrote:
> Dňa Thu, 26 Jul 2012 21:11:09 +0200 Slavko <li...@slavino.sk> napísal:
>
>> I will report the result after checking these three (or all, if will be
>> needed) files - if i do not forget to do the modification, then after
>> three (or after 16 days).
>
> it seems, that i was success on the first attempt :-)
>
> I changed "compress" to "nocompress" in /etc/logrotate.d/tor and no
> message from logrotate in my daily mail (i have another messages here,
> but they are wanted). It is strange for me, because i have the tor
> daemon disabled and i use it only sometime and from my user session
> (from vidalia).
Tor daemon can be disabled but still the logrotate routine is being
> Dňa Thu, 26 Jul 2012 21:11:09 +0200 Slavko <li...@slavino.sk> napísal:
>
>> I will report the result after checking these three (or all, if will be
>> needed) files - if i do not forget to do the modification, then after
>> three (or after 16 days).
>
> it seems, that i was success on the first attempt :-)
>
> I changed "compress" to "nocompress" in /etc/logrotate.d/tor and no
> message from logrotate in my daily mail (i have another messages here,
> but they are wanted). It is strange for me, because i have the tor
> daemon disabled and i use it only sometime and from my user session
> (from vidalia).
executed on a daily basis.
But now you say, that makes the error message ever weirder because the
only thing I can see making "gzip" outputing "file size changed while
zipping" is that there are files opened (in use) but if Tor is stopped,
nothing is logged and there should be no changes at the log file that is
going to be compressed :-?
> It needs more inspection now, but when will be sure, that this is not by
> my mistake, i will fill the bugreport. Now there are two files:
>
> ls -l /var/log/tor/
> celkom 4,0K
> -rw-r----- 1 debian-tor adm 0 júl 7 10:24 log
> -rw-r--r-- 1 debian-tor adm 3,5K júl 6 19:37 log.1
>
> The old one (log.1) is from my fist attempts, and all dates in it are
> dated at "Jul 06". By my opinion, there can be problem with combination
> the "notifempty" and "delaycompress". Another possible source can be the
> "create 0640 debian-tor adm" option and the older file with the 644
> permissions (not changed by me), but i don't know if this can be
> problem.
>
> I will do more checks, but any help is welcome :-)
logrotate routine for tor.
> Camaleón, thanks for help
You're welcome. Glad you finally discovered the noisy script :-)
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Pertti Kosunen
Aug 18, 2013, 5:10:02 AM8/18/13
to
On Thu, 26 Jul 2012 10:42:30 +0200, Slavko wrote:
> in last days (perhaps weeks) i get daily mail from cron's logrotate task
> with this:
>
> /etc/cron.daily/logrotate:
> gzip: stdin: file size changed while zipping
I had this too over a year on testing/unstable. I did put --verbose to
> with this:
>
> /etc/cron.daily/logrotate:
> gzip: stdin: file size changed while zipping
logrotate, it seems samba nmbd is causing it.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702201
There is already bug reported about it.
From Cron message:
rotating pattern: /var/log/samba/log.nmbd weekly (7 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/samba/log.nmbd
log needs rotating
rotating log /var/log/samba/log.nmbd, log->rotateCount is 7
dateext suffix '-20130818'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
renaming /var/log/samba/log.nmbd.7.gz to /var/log/samba/log.nmbd.8.gz
(rotatecount 7, logstart 1, i 7),
renaming /var/log/samba/log.nmbd.6.gz to /var/log/samba/log.nmbd.7.gz
(rotatecount 7, logstart 1, i 6),
renaming /var/log/samba/log.nmbd.5.gz to /var/log/samba/log.nmbd.6.gz
(rotatecount 7, logstart 1, i 5),
renaming /var/log/samba/log.nmbd.4.gz to /var/log/samba/log.nmbd.5.gz
(rotatecount 7, logstart 1, i 4),
renaming /var/log/samba/log.nmbd.3.gz to /var/log/samba/log.nmbd.4.gz
(rotatecount 7, logstart 1, i 3),
renaming /var/log/samba/log.nmbd.2.gz to /var/log/samba/log.nmbd.3.gz
(rotatecount 7, logstart 1, i 2),
renaming /var/log/samba/log.nmbd.1.gz to /var/log/samba/log.nmbd.2.gz
(rotatecount 7, logstart 1, i 1),
renaming /var/log/samba/log.nmbd.0.gz to /var/log/samba/log.nmbd.1.gz
(rotatecount 7, logstart 1, i 0),
old log /var/log/samba/log.nmbd.0.gz does not exist
renaming /var/log/samba/log.nmbd to /var/log/samba/log.nmbd.1
creating new /var/log/samba/log.nmbd mode = 0644 uid = 0 gid = 0
running postrotate script
compressing log with: /bin/gzip
gzip: stdin: file size changed while zipping
removing old log /var/log/samba/log.nmbd.8.gz
End of /var/log/samba/log.nmbd.1.gz:
[2013/08/18 06:25:03, 0] nmbd/nmbd.c:128(nmbd_sig_hup_handler)
Got SIGHUP dumping debug info.
[2013/08/18 06:25:03, 0] nmbd/nmbd_workgroupdb.c:276(dump_workgroups)
dump_workgroups()
dump workgroup on subnet 10.0.0.1: netmask= 255.255.255.0:
WORKGROUP(1) current master browser = FIREWALL
FIREWALL 40849a03 (firewall server)
SERVER 40801a03 ()
[2013/08/18 06:25:03, 0] nmbd/nmbd_workgroupdb.c:276(dump_workgroups)
dump_workgroups()
dump workgroup on subnet UNICAST_SUBNET: netmask= 10.0.0.1:
WORKGROUP(1) current master browser = UNKNOWN
FIREWALL 40819a03 (firewall server)
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Slavko
Aug 18, 2013, 2:30:02 PM8/18/13
to
Hi,
I am sorry for blank post - my mistake.
Dňa 18.08.2013 11:00 Pertti Kosunen wrote / napísal(a):
Not daily, but cca 5 days from week. If you will search, you will find a
thread here, where i was asking about this, but without solution.
I was trying to disable gzipping in logrotate config files, to identify
which file is doing it for some weeks, but i was not able to identify
source of problem - then i am not able to decide to which package report
the bug (i have some custom changes and i am not sure if they are not
source). Then i decide, that this must to see someone, who has more
knowledge about this...
I am sorry for blank post - my mistake.
Dňa 18.08.2013 11:00 Pertti Kosunen wrote / napísal(a):
> On Thu, 26 Jul 2012 10:42:30 +0200, Slavko wrote:
>> in last days (perhaps weeks) i get daily mail from cron's logrotate task
>> with this:
>>
>> /etc/cron.daily/logrotate:
>> gzip: stdin: file size changed while zipping
I have no samba installed, but I have this message for a long time too.
>> in last days (perhaps weeks) i get daily mail from cron's logrotate task
>> with this:
>>
>> /etc/cron.daily/logrotate:
>> gzip: stdin: file size changed while zipping
Not daily, but cca 5 days from week. If you will search, you will find a
thread here, where i was asking about this, but without solution.
I was trying to disable gzipping in logrotate config files, to identify
which file is doing it for some weeks, but i was not able to identify
source of problem - then i am not able to decide to which package report
the bug (i have some custom changes and i am not sure if they are not
source). Then i decide, that this must to see someone, who has more
knowledge about this...
0 new messages