From: Rick James Date: March 27 2012 5:58pm Subject: Re: mysqld got signal 6 (problem why bigger than I initially realised) List-Archive: http://lists.mysql.com/mysql/227057 Message-Id: <4F71FFBC.4060809@yahoo-inc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Do you have 12GB of RAM? Is this a 64-bit mysqld? Let's see SHOW VARIABLES LIKE '%buffer%'; SHOW GLOBAL STATUS LIKE 'Max%'; SHOW GLOBAL STATUS LIKE 'Up%'; What is Apache's MaxClients? On 3/27/12 6:25 AM, Brent Clark wrote: > Good day KarthiK.P.R > > Other than the replication settings in '/etc/mysql/conf.d/replication.cnf' and our /etc/mysql/conf.d/custom.cnf > > xyz-web02:/data# cat /etc/mysql/conf.d/custom.cnf > [mysqld] > innodb_file_per_table > bind-address = 0.0.0.0 > datadir = /data > binlog_format=mixed > key_buffer_size=8384512 > max_connections=41 > > The original /etc/mysql/my.cnf is untouched. > > The only other service we have running is DRBD (active / active) and apache, nothing is hitting apache as this is the standby node. > And there is no load, or anything consuming resources. > > Thanks > Brent > > > On 27/03/2012 14:04, P.R.Karthik wrote: >> HI Brent, >> >> Can you please paste your configuration file settings (my.cnf) ? It will help to identify where things went wrong. >> >> Is there any other memory consuming application running on the server beyond mysql ? >> >> Regards, >> KarthiK.P.R >> >> >> >> On Tue, Mar 27, 2012 at 4:17 PM, Brent Clark> wrote: >> >> Hey Guys >> >> Yesterday I sent an email, about '1 client is using or hasn't closed the table properly', but the problem is actually bigger than I realised. >> >> We run Mysql replication, and on the second node, Mysql is crashing with 'mysqld got signal 6' every so often. >> >> Other than the drives, we have replaced the hardware, and still the problem persists. >> >> Googling, I thought it was a memory exhaustion issue, so I started playing with the following variables and values. >> >> key_buffer_size=8384512 >> max_connections=41 >> >> But it still crashes >> >> Mar 27 12:36:53 xyz-web02 mysqld: key_buffer_size=8384512 >> Mar 27 12:36:53 xyz-web02 mysqld: read_buffer_size=131072 >> Mar 27 12:36:53 xyz-web02 mysqld: max_used_connections=3 >> Mar 27 12:36:53 xyz-web02 mysqld: max_threads=41 >> Mar 27 12:36:53 xyz-web02 mysqld: thread_count=1 >> Mar 27 12:36:53 xyz-web02 mysqld: connection_count=1 >> Mar 27 12:36:53 xyz-web02 mysqld: It is possible that mysqld could use up to >> Mar 27 12:36:53 xyz-web02 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 97828 K bytes of memory >> >> xyz-web02:# free -m >> total used free shared buffers cached >> Mem: 12038 11966 71 0 117 11378 >> -/+ buffers/cache: 469 11568 >> Swap: 2047 0 2047 >> >> We running Debian Squeeze 64bit. >> >> I have attached the full crash message. >> >> If anyone can help, I would be *most* grateful (If you are in South Africa, I will buy you a meal, let alone a beer :) >> >> Kindest Regards >> Brent Clark >> >> >> -- >> MySQL General Mailing List >> For list archives: http://lists.mysql.com/mysql >> To unsubscribe: http://lists.mysql.com/mysql >> >> > -- Rick James - MySQL Geek