I ran into the strange problem that a totally non-asterisk log went
over the 2GB limit (yes, still using 32-bit OS) so the system sent a
SIGXFSZ signal. Even though it wasn't an asterisk log, asterisk
responded to the signal and went into the "log rotation loop" anyway.
I killed logging on the of
# This script asks asterisk to rotate its logs on its own.
postrotate
/usr/sbin/asterisk -rx "logger rotate"
endscript
is what we use and it seems to be just fine.
(logger reload reopens the log files, where logger rotate,
rotates then then reopens)
Matt Florell wrote:
Welcome
Welcome to the club. That drove me crazy for a few hours one day until
I realized that the Master.csv in cdr-custom was being written to(and
not being rotated by anything) even though I never enabled it in the
logger.conf.
I added it to my rotate script and all is fine now.
MATT---
On 6/9/06,
I have one system that went totally crazy on me.
It went into an infinite loop rotating * message and log files.
From the asterisk console I kept seeing the message about re-loading
logger.conf over and over and it just kept creating more and more files.
I baby set many different * boxes all runni
