logrotate has a problem with MM 2.1.x because the qrunners operate a daemons and as a consequence do not close the files they are logging to. This leads to the problem you are observing. This is not a problem with MM alone. Anything that runs as a damon typically has to be HUP'ed after the rotation to prevent the problem.

Try extending the command logrotate uses to stop mailmanctl before the rotate and start it again after the rotate has been done or restart mailmanctl immediately after the rotation..

On Thursday, October 9, 2003, at 07:47 pm, John Dennis wrote:

You didn't say on what type and version the system is, which is
important because things like log file rollovers aren't really part of
mailman proper but rather are done as part of the system specific
installation. I do know that for a while we (Red Hat) had a bug with log
file rotation in our RPM, that was fixed about 6 months ago. However the
bug I'm aware of does not seem like what you are describing. The bug we
fixed would keep generating new files with an extra digit appended to it
till it eventually filled the file system, e.g. the file log would
become log.1, then log.1.1, then log.1.1.1 rather than log.2. Exact
details may vary as I'm going from memory.


Best thing for you to do is let us know the exact type of system, the
contents of /etc/logrotate.conf and /etc/logrotate.d/mailman (assuming
you have a system with this version of logrotate.

HTH,

John


On Thu, 2003-10-09 at 14:14, Nadim Shaikli wrote:
I've noticed some weird happenings with Mailman (v-2.1.2). As expected
on the first of each month all the log files get rolled over (so vette
becomes vette.1 and bounce becomes bounce.1, etc). Every so often I see
files that are created but are not used. For instance, I'm looking at
my log directory and can see,


  -rw-rw-r--    1 list     list            0 Oct  1 06:27 post
  -rw-rw-r--    1 list     list      4819198 Oct  9 08:57 post.1
  -rw-rw-r--    1 list     list       632841 Sep 10 07:59 post.2.gz

all the current posts are still making it to 'post.1' for some reason
and not simply 'post'.  Mind you in September they were making it to
the normal 'post' file.

Is this a known problem and is there a work-around or a means to fix
this sans restarts.  I did notice this happening on other files as
well (subscribe, error, etc) - the problem resolves itself if you
restart mailman.

Regards,

- Nadim


__________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com

_______________________________________________
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-developers
--
John Dennis <[EMAIL PROTECTED]>


_______________________________________________ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers



_______________________________________________
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-developers

Reply via email to