the following may be useful for most server systems
OOM-killer acts if some process reclaims more and more
memory and the kernel randomly kills unimportant tasks
using hughe memory
in case of a running mysqld the classification unimportant
is nearly all time wrong and can cause hughe damage and
On 04/13/2012 03:17 PM, Reindl Harald wrote:
with one single command you can protect processes from get killed
i started to run this every 15 minutes to make sure it is also
active after restarts
I understand your issue, but isn'there a configuration way to just limit
the memory usage of
Am 13.04.2012 15:47, schrieb Mihamina Rakotomandimby:
On 04/13/2012 03:17 PM, Reindl Harald wrote:
with one single command you can protect processes from get killed
i started to run this every 15 minutes to make sure it is also
active after restarts
I understand your issue, but isn'there
I had this same problem with the OOM for a while. Very frustrating to have
to reboot a server to bring it back to life.
I found out the OOM only ran when the swap file was about 99% full. The
servers I had this problem on had 16GB and 24GB of ram, but only 2GB of
swap. I increased the swap on the
hm - my servers generally have no swap or better said
only a 500 MB swap-file, they are all virtual machines
in a ESXi cluster
you really do not want a VM swapping
this leads in unusaeable performance
in my case the problem was another process eating up all memory
by user-mistake and my hint is
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
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?
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
I can't write my config parameters now.
5 августа 2010 г. 23:02 пользователь Евгений Килимчук
ekilimc...@gmail.comнаписал:
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,
You don't want to mess with OOM too much - you risk it killing off other
useful/critical things, like SSH daemons, the Apache root, what have you.
Add more memory to the box or split the webserver off to another system, I'd
say.
2010/8/5 Евгений Килимчук ekilimc...@gmail.com
I can't write my
When OOM-killer kill mysqld, I had a critical corrupted tables. My database
is a very big. I think Apache with cgi-scripts not critical process in this
story. And sshd is a real true.
6 августа 2010 г. 0:09 пользователь Johan De Meersman
vegiv...@tuxera.beнаписал:
You don't want to mess with
2010/8/5 Евгений Килимчук ekilimc...@gmail.com:
When OOM-killer kill mysqld, I had a critical corrupted tables. My database
is a very big. I think Apache with cgi-scripts not critical process in this
story. And sshd is a real true.
OOM is configurable via the proc filesystem via
2010/8/5 Rob Wultsch wult...@gmail.com:
2010/8/5 Евгений Килимчук ekilimc...@gmail.com:
When OOM-killer kill mysqld, I had a critical corrupted tables. My database
is a very big. I think Apache with cgi-scripts not critical process in this
story. And sshd is a real true.
OOM is configurable
13 matches
Mail list logo
