[Spce-user] kamailio-proxy.log error - mysql lost connection

John Murray john.murray at skyracktelecom.com
Tue May 28 10:22:22 EDT 2013


Tmpsfs is a good idea. RAM is cheap, it works for me.



-----Original Message-----
From: spce-user-bounces at lists.sipwise.com
[mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Andreas Granig
Sent: 28 May 2013 15:01
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] kamailio-proxy.log error - mysql lost connection


On 05/28/2013 02:53 PM, Jeremie Chism wrote:
> What you will see is the load rise then registrations drop and users 
> that are authorized on the system getbanned. Ultimately you will end 
> up with a drive that is unreadable. This has stopped with sas drives.

One of the reasons for the high disk i/o is because kamailio-proxy is
logging *a lot*. It's good to have it in case something goes wrong, but
we're currently trying to move the most important messages (what comes in,
what gets rewritten to what, what goes out and where) to log level "notice"
and raise the default log level to notice as well to lower the disk output.

Also, there are some tricks we're currently trying to write the proxy logs
(info, notice) to tmpfs and sync them back to disk in the night via
logrotate. It would require more RAM, but would also significantly lower the
disk throughput.

Other than that, you can configure rsyslog to log to an external syslog

I'd be interested in your views of these approaches.


Spce-user mailing list
Spce-user at lists.sipwise.com

More information about the Spce-user mailing list