asked on MySQL server running out of memory, could be a bug?
I need to resolve this problem ASAP. Recently I started receiving these error messages (as recorded in /var/log/mysqld.log):
101112 17:48:04 /usr/sbin/mysqld: Out of memory (Needed 41 bytes)
101112 17:58:04 /usr/sbin/mysqld: Out of memory (Needed 8160 bytes)
The problem is, I am quite sure there is enough memory.
my.cnf:
-------
[mysqld]
max_connections = 100
safe-show-database
#log-bin = /var/log/mysql/mysql-bin.l
#binlog-do-db = icloaker_maintenance
server-id=1
log-slow-queries = /var/log/mysql-slow.log
long_query_time = 1
key_buffer_size = 128M
table_cache = 2048
sort_buffer_size = 1M
read_buffer_size = 1M
max_allowed_packet = 16M
tmp_table_size = 300M
max_heap_table_size=64M
myisam_sort_buffer_size = 64M
join_buffer_size = 2M
thread_cache_size = 16
interactive_timeout = 25
wait_timeout = 1800
connect_timeout = 10
max_connect_errors = 10
query_cache_limit = 2M
query_cache_size = 32M
query_cache_type = 1
innodb_buffer_pool_size = 128M
#innodb_log_file_size = 64M
innodb_additional_mem_pool
innodb_flush_log_at_trx_co
[mysqld_safe]
log-error=/var/log/mysqld.
#pid-file=/var/run/mysqld/
--------
Using an application called mysqltuner, I found that mysql is allowed to use roughly 823MB now, while the standard useage is just 460M and there do not seem to be spikes. There are very few concurrent connections according to it too.
The server has enough memory, it is the only VPS on a dedicated server with 2GB RAM.
Memory stats on the hardware node, as reported by "top -M":
Mem: 1975.121M total, 1794.250M used, 180.871M free, 73.145M buffers
Swap: 4094.617M total, 152.000k used, 4094.469M free, 1117.539M cached
Memory stats on the VPS, as reported by "top -M":
Mem: 1975.121M total, 809.543M used, 1165.578M free, 0.000k buffers
Swap: 0.000k total, 0.000k used, 0.000k free, 0.000k cached
As you can see, the VPS is allowed to use 2GB RAM as it is the only running VPS on the dedicated server, it can get it easily without fighting for resources, although it could take a small part from the HW node swap if necessary too.
This server has been running OK for a long time although recently I optimized my.cnf to resolve a similar problem but yesterday it got back.
Both HW node and VPS server are running on CentOS 5 64-bit.
Any ideas are more than welcome!
101112 17:48:04 /usr/sbin/mysqld: Out of memory (Needed 41 bytes)
101112 17:58:04 /usr/sbin/mysqld: Out of memory (Needed 8160 bytes)
The problem is, I am quite sure there is enough memory.
my.cnf:
-------
[mysqld]
max_connections = 100
safe-show-database
#log-bin = /var/log/mysql/mysql-bin.l
#binlog-do-db = icloaker_maintenance
server-id=1
log-slow-queries = /var/log/mysql-slow.log
long_query_time = 1
key_buffer_size = 128M
table_cache = 2048
sort_buffer_size = 1M
read_buffer_size = 1M
max_allowed_packet = 16M
tmp_table_size = 300M
max_heap_table_size=64M
myisam_sort_buffer_size = 64M
join_buffer_size = 2M
thread_cache_size = 16
interactive_timeout = 25
wait_timeout = 1800
connect_timeout = 10
max_connect_errors = 10
query_cache_limit = 2M
query_cache_size = 32M
query_cache_type = 1
innodb_buffer_pool_size = 128M
#innodb_log_file_size = 64M
innodb_additional_mem_pool
innodb_flush_log_at_trx_co
[mysqld_safe]
log-error=/var/log/mysqld.
#pid-file=/var/run/mysqld/
--------
Using an application called mysqltuner, I found that mysql is allowed to use roughly 823MB now, while the standard useage is just 460M and there do not seem to be spikes. There are very few concurrent connections according to it too.
The server has enough memory, it is the only VPS on a dedicated server with 2GB RAM.
Memory stats on the hardware node, as reported by "top -M":
Mem: 1975.121M total, 1794.250M used, 180.871M free, 73.145M buffers
Swap: 4094.617M total, 152.000k used, 4094.469M free, 1117.539M cached
Memory stats on the VPS, as reported by "top -M":
Mem: 1975.121M total, 809.543M used, 1165.578M free, 0.000k buffers
Swap: 0.000k total, 0.000k used, 0.000k free, 0.000k cached
As you can see, the VPS is allowed to use 2GB RAM as it is the only running VPS on the dedicated server, it can get it easily without fighting for resources, although it could take a small part from the HW node swap if necessary too.
This server has been running OK for a long time although recently I optimized my.cnf to resolve a similar problem but yesterday it got back.
Both HW node and VPS server are running on CentOS 5 64-bit.
Any ideas are more than welcome!
MySQL Server
Last Comment
tomfra
ASKER
OK, I think I need to increase the "max memory size" and "virtual memory" for the mysql user so I need to put it into sysctl.conf. What are the names of the switches? I need the names for the "ulimit -m" and "ulimit -j" switches, but cannot find them.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
It seems that after I set the ulimit for the root user and restarted the server, it has become active for the mysql user too. So it seems to be OK now, although I will be monitoring the situation.
ulimit -a
-------
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 16126
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) 524288
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 16126
virtual memory (kbytes, -v) 524288
file locks (-x) unlimited
-------
The max memory size and virtual memory look too low to me. What do you think? And how to increase those values?