I need to install mysql 5.6 on my ubuntu machine for development reasons (the newest version contains features that I need to incorporate into some web projects). But I am having some issues. I've been following this tutorial which is not specific for version 5.6 but I figured it would be about the same: http://www.ovaistariq.net/490/a-step-by-step-guide-to-upgrading-to-mysql-5-5/

I'm not sure if i'm setting up my /etc/my.cnf file properly. Here is what I have:

# Example MySQL config file for large systems.
# This is for a large system with memory = 512M where the system runs mainly
# MySQL.
# MySQL programs look for option files in a set of
# locations which depend on the deployment platform.

# You can copy this option file to one of those
# locations. For information about these locations, see:
# http://dev.mysql.com/doc/mysql/en/option-files.html
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.

# The following options will be passed to all MySQL clients
#password   = your_password
port        = 3306
socket      = /var/run/mysqld/mysqld.sock

# Here follows entries for some specific programs

# The MySQL server
port        = 3306
socket      = /var/run/mysqld/mysqld.sock
key_buffer_size = 256M
max_allowed_packet = 1M
table_open_cache = 256
sort_buffer_size = 1M
read_buffer_size = 1M
read_rnd_buffer_size = 4M
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size= 16M
pid_file    = /usr/local/mysql/data/dev.pid
basedir         = /usr/local/mysql
datadir         = /usr/local/mysql/data
tmpdir          = /tmp
log_error       = /var/log/mysql/error.log
user        = mysql

# Try number of CPU's*2 for thread_concurrency
thread_concurrency = 8

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!

# Replication Master Server (default)
# binary logging is required for replication

# binary logging format - mixed recommended

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id   = 1

# Replication Slave (comment out master section to use this)
# To configure this host as a replication slave, you can choose between
# two methods :
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
#    the syntax is:
#    MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#    where you replace <host>, <user>, <password> by quoted strings and
#    <port> by the master's port number (3306 by default).
#    Example:
#    MASTER_USER='joe', MASTER_PASSWORD='secret';
# OR
# 2) Set the variables below. However, in case you choose this method, then
#    start replication for the first time (even unsuccessfully, for example
#    if you mistyped the password in master-password and the slave fails to
#    connect), the slave will create a master.info file, and any later
#    change in this file to the variables' values below will be ignored and
#    overridden by the content of the master.info file, unless you shutdown
#    the slave server, delete master.info and restart the slaver server.
#    For that reason, you may want to leave the lines below untouched
#    (commented) and instead use CHANGE MASTER TO (see above)
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id       = 2
# The replication master for this slave - required
#master-host     =   <hostname>
# The username the slave will use for authentication when connecting
# to the master - required
#master-user     =   <username>
# The password the slave will authenticate with when connecting to
# the master - required
#master-password =   <password>
# The port the master is listening on.
# optional - defaults to 3306
#master-port     =  <port>
# binary logging - not required for slaves, but recommended

# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = /usr/local/mysql/data
#innodb_data_file_path = ibdata1:10M:autoextend
#innodb_log_group_home_dir = /usr/local/mysql/data
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
#innodb_buffer_pool_size = 256M
#innodb_additional_mem_pool_size = 20M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 64M
#innodb_log_buffer_size = 8M
#innodb_flush_log_at_trx_commit = 1
#innodb_lock_wait_timeout = 50

max_allowed_packet = 16M

# Remove the next comment character if you are not familiar with SQL

key_buffer_size = 128M
sort_buffer_size = 128M
read_buffer = 2M
write_buffer = 2M


When I try to run

mysqld --skip-grant-tables --user=mysql

I get this error:

The program 'mysqld' can be found in the following packages:
 * mysql-server-core-5.1
 * mysql-cluster-server-5.1
Try: sudo apt-get install <selected package>

When i try to stop the server, I get this:

* MySQL server PID file could not be found!

When I try to start:

Starting MySQL
.. * The server quit without updating PID file (/usr/local/mysql/data/dev.pid).

I am assuming I am not editing the my.cnf file properly, but i'm completely lost. Otherwise I have followed the instructions perfectly and I have made sure that the previous mysql 5.1 version was completely removed from the system.


For the mysqld error, you may need to make sure that the binaries are in your $PATH. Try checking using which mysqld.

If it is not on your path, you should add it to your profile (if you're using bash, this will probably be ~/.bash_profile):

export PATH=/path/to/mysql/bin:$PATH

As for the PID error, you might check /var/log/mysql/error.log to see if it gives you any hints as to what's wrong, but I have a feeling that it may be that the user the MySQL server is running under does not have permissions to write to the PID file, so make sure that it's owned by the mysql user (or the equivalent for your distro).

  • The path was exported. I am upgrading from version 5.1 to 5.6 so I already had an existing mysql user. Is it possible that I had previously set a password to the mysql user and its not working because I am not supplying a password? Any way to check that and change the password if necessary?
    – ryandlf
    Jan 18 '12 at 16:29

The problem sounds like you are using the wrong PATH variable in regards to your mysql installation. Maybe try using the full path of your mysqld-binary.

I have also written a post on how to upgrade mysql provided with ubuntu 12.04. Have a look at it on http://www.peterchen.net/2013/02/20/en-how-to-install-mysql-5-6-on-ubuntu-12-04-precise/. Hope this will help you as it covers mysql 5.6 and not the old mysql 5.5.


I don't fancy myself a MySQL Server Admin super-hero, but I think @bhamby has it right. It seems like you had some kind of partial install of one version of MySQL that somehow broke the previous version you were running.

Also noteworthy: http://dev.mysql.com/doc/refman/5.6/en/upgrading.html

MySQL recommends that you "incrementally update" between major release versions: i.e. from MySQL 5.1 to 5.5, from 5.5 to 5.6, and 5.6 to 5.7, (and so on?)

This is not a requirement if you're starting from a fresh install and haven't started or ported over another pre-existing database, obviously, but it seems relevant to the post as far as troubleshooting issues goes since it seems like you are trying to jump from 5.1 to 5.6 without going to 5.5 first.

Your my.cnf file doesn't look too crazy or anything, but you might have issues with your current data and log files needing to be purged. I usually stop MySQL server first, and then delete them when upgrading or changing the log file size.

I believe these are usually in "/var/lib/mysql/" for Ubuntu (but don't quote me on this):


After hours of fiddling (and a few image restores) I found a pretty simple step-by-step process for upgrading from MySQL 5.5 to 5.6 on my DO cloud-hosted VM running Ubuntu 14.03 that has worked well for my local VirtualBox VM's running 15.04 and 15.10 too.


I followed this guide to make a super easy "just copy / paste the CLI commands" guide for people who are working from a fresh Ubuntu 14 or 15 install, that typically comes with MySQL 5.5 "out of the box". The process for upgrading to MySQL 5.7 is very similar, though updating your APT repository MySQL default to use MySQL 5.7 is a slightly different than in previous versions. I hope this helps anyone else with similar issues while upgrading MySQL versions.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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