Am 04.10.2012 um 03:21 schrieb Lonnie Abelbeck: > > On Oct 3, 2012, at 7:43 PM, Michael Knill wrote: > >> Thanks Lonnie. >> >> Are you sure that Asterisk logs to syslog by default. > > Yes. The default is /stat/etc/asterisk/logger.conf, compare that to your > logger.conf . > >> From what I could see, Asterisk was managing the rotation of its own log >> files? >> >> Anyway, if I did want to capture logs for a while to debug a problem, what >> is the best way to do it? >> I could set up persistlog=yes to log to the kd or I could use a syslog >> server. > > Yes, the best would be to set PERSISTLOG=yes which would link /var/log -> > /mnt/kd/log to keep lots of logging.
Alternative: In Buildroot there is a separate "logrotate" package, which could be used only for such cases when you need a separate Asterisk verbose/debug log file, it could also compress (and optionally move the file to /mnt/kd/) at a given size. I guess it could be triggered over cron. (Not sure about the WCHAR dependency) > Lonnie > > >> Michael Knill > >> On 04/10/2012, at 9:58 AM, Lonnie Abelbeck wrote: >> >>> Michael, >>> >>> It just so happens, we have doubled the default /var size limit from 5MB to >>> 10MB in the next release to be 1.0.5 . >>> >>> On an alix board it is probably better to leave that at the default, but >>> for 512MB RAM and larger systems you can adjust the /tmp and /var size >>> limits >>> >>> For example: >>> -- >>> VAR_SIZE="20000k" >>> TMP_SIZE="15000k" >>> -- >>> defined in your /mnt/kd/rc.conf.d/user.conf file. But, only define either >>> of these if you really need to. >>> >>> The asterisk logs go to syslog by default (logger.conf), and they are >>> rotated to work well within the 5MB limit. >>> >>> The defaults that AstLinux ships with should work well with the default >>> /var and /tmp size limits. If not, please let us know what file is growing >>> too large. >>> >>> Lonnie >>> >>> >>> On Oct 3, 2012, at 5:31 PM, Michael Knill wrote: >>> >>>> Yes I did a bad thing. I set Asterisk logging to verbose because I was >>>> trying to catch a problem that was occurring and of course it filled up my >>>> logs. >>>> The only problem that seemed to occur was that Asterisk generated emails >>>> were not being sent. PS the test email worked? >>>> The only solution was to reboot the system after I cleared out the logs. >>>> >>>> Anyway I have some questions that I would like to discuss: >>>> >>>> 1) Can I increase the size of /var in a 256M ALIX and what should I go to? >>>> 2) Is there something in logger.conf that I should be doing to better >>>> manage the Asterisk log files? >>>> 3) Does anyone do anything differently with the log files e.g. specific >>>> cron jobs. >>>> >>>> Regards >>>> Michael Knill Michael http://www.mksolutions.info
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________ Astlinux-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [email protected].
