Mysql used 5GB (buffers + 400 connections) of memory, but CGI-script some time made heavy load when used many memory and used SWAP. OOM-killer must kill new cgi-forks, wich use many memory, but it kill mysqld and sshd.
2010/8/5 Walter Heck - OlinData.com <li...@olindata.com> > It would be a lot better to make sure your server doesn't turn > OOM-psycho on you. The most common case of this happening is that you > have set the memory-settings in your my.cnf in such a way that it > allows MySQL to use more memory then you have available. Could you > post your my.cnf here by chance? > > Walter Heck > Engineer @ Open Query (http://openquery.com) > > On Fri, Aug 6, 2010 at 02:43, Евгений Килимчук <ekilimc...@gmail.com> > wrote: > > Hello! > > > > I use CentOS 5.4 with LAMP. On the server runs heavy cgi-programs. MySQL > use > > 75% (100% = 8GB) of memory. When cgi programs use more than 25% of memory > > and all SWAP file (8GB), kernel run OOM-Kiler wich kill mysqld procces. > > > > I use: > > > > echo "0" > /proc/sys/vm/swappiness - This allows to reduce using of > SWAP. > > > > I want to use: > > echo "-17" > /proc/`pidof mysqld`/oom_adj - This allows save mysqld when > run > > oom-killer. > > > > Someone used this option? > > > -- Best regards, Eugene Kilimchuk <ekilimc...@gmail.com>