Re: [ic] Thousands of error logs in .gz format

["Ron Phipps" <takedown@cdsnet.net>]

Hello Warren,

Check /etc/logrotate.d/minivend

I ran into this same problem and it was becase the log configuration was set
to rotate * instead of filename.log.  So when it does the rotation it not
only rotates the current weeks log it also goes and rotates all the previous
rotations.  Here is what my minivend file looks like:

/var/log/minivend/error.log {
        rotate 4
        weekly
        compress
}

/var/log/minivend/legalednet.error.log {
        rotate 4
        weekly
        compress
}

/var/log/minivend/caseetc.error.log {
        rotate 4
        weekly
        compress
}

This will keep 4 weeks of error logs.  When it rotates for the 5th week it
bumps the last log off and moves every log up one.  So right now a directory
listing in the log dir returns:

-rw-rw----    1 minivend minivend    38532 Oct  6 12:08 caseetc.error.log
-rw-rw----    1 minivend minivend     2961 Oct  1 01:59
caseetc.error.log.1.gz
-rw-rw----    1 minivend minivend     3100 Sep 24 03:36
caseetc.error.log.2.gz
-rw-rw----    1 minivend minivend     6200 Sep 17 03:31
caseetc.error.log.3.gz
-rw-rw----    1 minivend minivend      380 Sep  9 21:05
caseetc.error.log.4.gz
-rw-------    1 minivend minivend      503 Oct  2 22:30 error.log
-rw-------    1 minivend minivend      440 Sep 26 22:03 error.log.1.gz
-rw-------    1 minivend minivend      319 Sep 20 19:07 error.log.2.gz
-rw-------    1 minivend minivend     6731 Sep 15 21:48 error.log.3.gz
-rw-------    1 minivend minivend       32 Sep  3 04:02 error.log.4.gz
-rw-rw----    1 minivend minivend      530 Oct  4 06:58 legalednet.error.log
-rw-rw----    1 minivend minivend      163 Sep 25 13:29
legalednet.error.log.1.gz
-rw-rw----    1 minivend minivend       43 Sep 17 04:02
legalednet.error.log.2.gz
-rw-rw----    1 minivend minivend       43 Sep 10 04:02
legalednet.error.log.3.gz
-rw-rw----    1 minivend minivend       43 Sep  3 04:02
legalednet.error.log.4.gz

Mike, could you fix the minivend file that gets distributed with the RPM
install and maybe point the user to modify the file or make it part of the
makecat process to update that file?

Thanks!
-Ron

-----Original Message-----
From: Warren Odom <warren-odom@stenocall.com>
To: Interchange-users@minivend.com <Interchange-users@minivend.com>
Date: Friday, October 06, 2000 9:46 AM
Subject: [ic] Thousands of error logs in .gz format


>I can't find anything in the archives on this.
>
>In June I started experimenting with Minivend (4.04), and in mid-August I
>downloaded and installed Interchange (4.5.5) to try it also.  Both were
>installed using RPMs on Red Hat.  This is still a development environment.
>
>Today I discovered I have 232 "log" files from Interchange and over 42,000
>of them from Minivend, dating back to September 3.  These are in the same
>directories as their respective error.log files, but the names go like
this:
>
>-rw-------    1 intercha intercha       37 Sep  3 04:03 error.log.3.gz.4.gz
>-rw-------    1 intercha intercha       72 Sep  3 04:03
>error.log.2.gz.1.gz.4.gz
>-rw-------    1 intercha intercha       42 Sep  3 04:03
>error.log.1.gz.2.gz.4.gz
>-rw-rw----    1 intercha intercha       43 Sep  3 04:03
>barry.error.log.3.gz.4.gz
>-rw-rw----    1 intercha intercha       84 Sep  3 04:03
>barry.error.log.2.gz.1.gz.4.gz
>-rw-rw----    1 intercha intercha       48 Sep  3 04:03
>barry.error.log.1.gz.2.gz.4.gz
>-rw-rw----    1 intercha intercha      145 Sep  3 04:03
>barry.error.log.1.gz.1.gz.1.gz.4.gz
>-rw-------    1 intercha intercha      395 Sep  6 08:27
>error.log.1.gz.1.gz.1.gz.4.gz
>-rw-rw----    1 intercha intercha      137 Sep 10 04:06
>barry.error.log.2.gz.1.gz.1.gz.3.gz
>-rw-rw----    1 intercha intercha       48 Sep 10 04:06
>barry.error.log.1.gz.3.gz.3.gz
>-rw-rw----    1 intercha intercha       92 Sep 10 04:06
>barry.error.log.1.gz.2.gz.1.gz.3.gz
>-rw-rw----    1 intercha intercha       53 Sep 10 04:06
>barry.error.log.1.gz.1.gz.2.gz.3.gz
>
>and so on.  The files appear to be created in bunches, and mostly (but not
>always) shortly after 4 AM.  cron jobs start at 4 AM, and backups at 4:30,
>but I haven't added anything new recently.  The vast majority of files are
>created on Sunday mornings, so I looked at the weekly crons, but it appears
>there's only a run of makewhatis.
>
>Many of the .gz files are zero length.  The others give either binary
>garbage, or an "unexpected end of file" when I try to gunzip them.
>error.log has no errors in it.
>
>So what could cause MV/IC to create these files, and how do I, to put it
>politely, discontinue it?
>
>            Thanks -- Warren
>
>
>_______________________________________________
>Interchange-users mailing list
>Interchange-users@www.minivend.com
>http://www.minivend.com/mailman/listinfo/interchange-users
>


_______________________________________________
Interchange-users mailing list
Interchange-users@www.minivend.com
http://www.minivend.com/mailman/listinfo/interchange-users