Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have encountered a weird problem with innodb_buffer_pool_size configuration on 5.5.23-1~dotdeb.0 (Debian):

Whatever new value that I choose in my.cnf for innodb_buffer_pool_size (e.g 3G, 4G, 8000M), after restarting mysql I still get innodb_buffer_pool_size = 128 M.

Values of other my.cnf parameters can be changed without any issue.

I have also checked and have no other my.cnf on the file system other than /etc/mysql/my.dnf. So does this mean that innodb_buffer_pool_size = 128 M is hard-coded at compile time? If so, how can I fix this? If not, what can possibly have caused the problem? Thanks

P.S. I first asked this question at dba forum but people there seem not to have insight about mysql debian package.

share|improve this question
up vote 1 down vote accepted

I needed to put the config WITHIN [mysqld] block in my.cnf to take effect.

more details here

share|improve this answer

Do you have space between the number '128' and 'M'?? Atleast in my mysql installation the space is forbidden between them, altough I checked this only on 5.1.x version.

share|improve this answer
Good point, but there is no spcae in my.cnf. Here I just copied the output of TunningPrimer script. – corev Apr 27 '12 at 9:53

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.