Hi Kevin, I see...
That's why you rotate asterisk logs everytime this message occurs.. it makes sense. Unfortunately, in my case, it was the CDR CSV files tha reached that size, so rotating logs was just worsening my situation, since asterisk started to generate rotated log files every few seconds because of that. Is there a way to rotate CDR CSV files via Asterisk, or should I handle this outside Asterisk? Thanks! Dov ----- Original Message ----- From: "Kevin P. Fleming" <[EMAIL PROTECTED]> To: "Asterisk Users Mailing List - Non-Commercial Discussion" <[email protected]> Sent: Thursday, February 09, 2006 2:01 PM Subject: Re: [Asterisk-Users] asterisk logger - urgent!!! > Dov Bigio wrote: > > > Any way, if any developers are reading this, I don't think that rotating > > asterisk logs is the best way to handle this problem! > > Maybe a more user-friendly message could be logged, infoming which file > > reached the 2.0GB. > > Unfortunately when we receive SIGFSZ from the kernel, we have no way to > know which file caused it. The assumption in Asterisk is that the only > files we write to that will ever reach that size are log files. If any > other file does, there will be trouble, as you have seen. > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > Asterisk-Users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > > _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
