Categories
MySQL

MySQL 5.6.17 for Wheezy

After months of work in (slow) progress, I’m glad to announce that packages of MySQL 5.6.17 are now available for Debian 7.4 “Wheezy” on both amd64 and i386 architectures.

This is our first major release of the MySQL 5.6 branch, so be very careful when upgrading your boxes : backup your data first, keep a spare/delayed MySQL slave… And be sure to know in details what’s new in MySQL 5.6 :

  • A better Optimizer
  • InnoDB great new features : online DDL, split kernel mutex, multi-threaded purge, separate flush thread
  • New NoSQL-style memcached APIs
  • Partitioning improvements for querying and managing huge tables
  • Replication now supports multi-threaded slaves, GTID and checksums
  • More data is available through the PERFORMANCE_SCHEMA.

Of course, feedbacks are welcome, as usual.

By the way, sorry for that delay. Among other reasons, I had to deal with the Oracle/MariaDB/Percona – and now WebscaleSQL – dilemma. It’s still not concluded, since MariaDB is now well integrated in Debian Sid and that its 10.x has been declared as GA a few days ago. Stay tuned, some more announcement might be made in the next few weeks on the Dotdeb side.

Enjoy! And if you want to show your support, follow this link… 🙂

90 replies on “MySQL 5.6.17 for Wheezy”

OK, I got it thanks.

I’m glad to hear you study MariaDB && WebscaleSQL.

The performance of WebscaleSQL seams to be really better than MariaDB. So why don’t we wait for the team of MariaDB include the perf optimization of WebscaleSQL ?

Hi
I just shot a goal upgrading to mysql 5.6.17 without knowing it to be that new.
I cannot say what happened, but there seems to be something wrong, since I am able to connect via my postfix mysql connects and also via phpmyadmin web access, but all my other mysql running webpages deny to connect. Any ideas?
Please give me any hints where to search for this issue, since I dont know if that is a php-mysql problem (btw dotdeb 5.4.26 package) or what else could be the cause.

Bonjour,

Et merci.

Chez moi, la mise à jour a fonctionné, mais au redémarrage de mysql j’obtiens les suivantes :
[ERROR] Function ‘innodb’ already exists
[Warning] Couldn’t load plugin named ‘innodb’ with soname ‘ha_innodb.so’.
[ERROR] Function ‘federated’ already exists
[Warning] Couldn’t load plugin named ‘federated’ with soname ‘ha_federated.so’.
[ERROR] Function ‘blackhole’ already exists
[Warning] Couldn’t load plugin named ‘blackhole’ with soname ‘ha_blackhole.so’.
[ERROR] Function ‘archive’ already exists
[Warning] Couldn’t load plugin named ‘archive’ with soname ‘ha_archive.so’.

Avez-vous une idée ?

Merci beaucoup.

MySQL 5.6.17 totally broke my build. I can’t see the deprecated MySQL 5.5 packages anymore – any chance that we can have a smoother transition? Something like the php packages where we can specify which version to install?

Are you able to connect using any mysql user with phpmyadmin? If the issue is user-specific, check if that user doesn’t still have password in old format, which is disabled by default in 5.6. Also some older libraries try to use old authentification scheme during connect which is not supported anymore.

Je me réponds :

“If a plugin is named both using a –plugin-load option and in the mysql.plugin table, the server starts but writes these messages to the error log:
100310 19:15:44 [ERROR] Function ‘plugin_name’ already exists
100310 19:15:44 [Warning] Couldn’t load plugin named ‘plugin_name’
with soname ‘plugin_object_file’.”

(https://dev.mysql.com/doc/refman/5.6/en/server-plugin-loading.html)

Désolé pour le dérangement.

After some research and having found the PHP Warning: mysql_connect(): Connection using old (pre-4.1.1) authentication protocol refused (client option ‘secure_auth’ enabled) in ‘…’ error, I was able to find some webpages with information, which are
http://mysqlblog.fivefarmers.com/2012/05/30/why-your-pre-4-1-client-wont-like-mysql-5-6/
and
http://www.cyberciti.biz/faq/mysql-change-user-password/

With this I could solve my old pre 4.1 passwort issues easily by changing the passwords.

With PHPMyAdmin, just go the the “Privileges” tab.
Edit the user containing username and the host you want to use with.
In the “Change Password” box below, you can choose whether using password or no.
The best solution is to make new passwords with the new hash 4.1 length, eg.
mysql> SET PASSWORD FOR user@localhost = OLD_PASSWORD(‘oldPasswd’);
else choose “MySQL 4.0 Compatible” and “Go”.

Thank you dotdeb and Marki! 🙂

I expect my prev post hanging in spam delay, therefore I just mention to have that solved.
In the meanwhile, after having sorted out the old password thing with passing connects, there still is that issue about PHP error.log warnings: “PHP Warning: mysql_connect(): Headers and client library minor version mismatch. Headers:50535 Library:50617 in ””, which seems to ask for a recomiled PHP to a version compiled with MySQL 5.6.

After upgrading, MySQL won’t start anymore.
When trying to restart, I’v got:
“[ ok ] Stopping MySQL database server: mysqld.
[….] Starting MySQL database server: mysqldNo directory, logging in with HOME=/”

No idea why. I search through the log, but cannot find any solution.
Is there somthing to do in order to fix it quickly?

@Achim : maybe you can be more specific and give us some relevant lines of your MySQL log files to diagnose the problem.

If you still want to downgrade to 5.5, packages come from Debian. You can provide the version explicitely, eg. “apt-get install mysql-server-5.5 mysql-server-core-5.5”

@nyro : I mean something else could prevent MySQL from starting. Take a deeper look at your log files to get the specific error, we’ll help you then : /var/log/syslog, /var/log/mysql*

Yes, but my MySQL didn’t start at all. I just found the solution actually: the configuration table_cache was renamed in 5.5 version into table_open_cache…
Updating my configuration and i’ts ok. Thanks again for your grat work!

I ran in the same issue as nyro. Since I use chef for provisioning it was as easy as upgrading the mysql cookbook (which was updated recently). So in my eyes it is a configuration issue of my.cnf somewhere but I haven’t digged deeper into it.

I still get these error:

Starting MySQL database server: mysqldNo directory, logging in with HOME=/
[FAIL. . . . . . . . . . . . failed!

I’ve tried nyro sugestion but it didn’t work.

I ran debian 7.4 on KVM

please help?

Graca

@graca : a lot of reasons could prevent MySQL from starting, such as deprecated configuration variables. Take a look at your log files (/var/log/syslog, /var/log/mysql*) to get more details. Maybe we can help then.

After upgrading to MySQL 5.6 the following errors appear in the logs and the server does not come up:

[Note] Plugin ‘FEDERATED’ is disabled.
[ERROR] Function ‘innodb’ already exists
[Warning] Couldn’t load plugin named ‘innodb’ with soname ‘ha_innodb.so’.
[ERROR] Function ‘federated’ already exists
[Warning] Couldn’t load plugin named ‘federated’ with soname ‘ha_federated.so’.
[ERROR] Function ‘blackhole’ already exists
[Warning] Couldn’t load plugin named ‘blackhole’ with soname ‘ha_blackhole.so’.
[ERROR] Function ‘archive’ already exists
[Warning] Couldn’t load plugin named ‘archive’ with soname ‘ha_archive.so’.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.7
InnoDB: Using Linux native AIO
InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file ./ib_logfile0 is of different size 0 50331648 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
[ERROR] Plugin ‘InnoDB’ init function returned error.
[ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
[ERROR] Unknown/unsupported storage engine: InnoDB
[ERROR] Aborting

@Gaten, “The performance of WebscaleSQL seams to be really better than MariaDB.” – any compare benchmarks?

I fixed it by using the my.cnf from the package, I think I need to re-check my old config again, but surely this is my.cnf problem, not something from the package.

After I upgraded my mysql to 5.6 i run into a small problem with PHP.
I got the following message in my logs: PHP Warning: mysql_connect(): Headers and client library minor version mismatch
libmysqlclient is also the current version here from dotdeb as is PHP 5.4
While the message above is not a big problem, I could solve it by using dem PHP MySQL Native Driver package php5-mysqlnd and everthing works just fine.
But there is one exception: The zabbix web frontend depends on php5-mysql and so I cannot use the PHP Mysql Native driver on my zabbix server.
I think it is more a problem of the PHP package as php5-mysqlnd does not say that it is a full replacement for the php5-mysql package.

hi, made an apt-get upgrade as usual.
it upgraded to mysql 5.6 itself. perhaps as mentioned by someone other there shoud be two repos… one for 5.6 and one for 5.5 to avoid problems

after upgrading i have some problem:
– first i fixed dirty because i suddenly ran into “errno: 24 – Too many open files”
– second i have no fix fo is the already mentioned anaoying problem/warning with “Headers and client library minor version mismatch. Headers:50535 Library:50617” (PHP 5.5.10-1~dotdeb.1)

There won’t be a separate repo for MySQL 5.6 because you can choose to install explicitely mysql-server-5.5 or mysql-server-5.6. About the library version warning, I’ll write a note about it.

After the update I was seeing a ‘fatal error’ from mysql_upgrade in the logs.

Traced this to mysql_upgrade not being able to login to the server. A line in /etc/mysql/debian-start has changed, now it says:

MYUPGRADE=”/usr/bin/mysql_upgrade”

whereas the line before upgrade was

MYUPGRADE=”/usr/bin/mysql_upgrade –defaults-extra-file=/etc/mysql/debian.cnf”

Changing the line back fixed the error.

Did something go wrong with my upgrade or is this a bug?

I have same problem to start mysql after upgrade to 5.6.
I fix config my.cfg and directive table_cache ( in 5.5) to table_open_cache (in 5.6) and now mysql can start.

Please can you help?
2014-04-07 11:06:33 14475 [Note] Plugin ‘FEDERATED’ is disabled.
2014-04-07 11:06:33 14475 [ERROR] Function ‘innodb’ already exists
2014-04-07 11:06:33 14475 [Warning] Couldn’t load plugin named ‘innodb’ with soname ‘ha_innodb.so’.
2014-04-07 11:06:33 14475 [ERROR] Function ‘federated’ already exists
2014-04-07 11:06:33 14475 [Warning] Couldn’t load plugin named ‘federated’ with soname ‘ha_federated.so’.
2014-04-07 11:06:33 14475 [ERROR] Function ‘blackhole’ already exists
2014-04-07 11:06:33 14475 [Warning] Couldn’t load plugin named ‘blackhole’ with soname ‘ha_blackhole.so’.
2014-04-07 11:06:33 14475 [ERROR] Function ‘archive’ already exists
2014-04-07 11:06:33 14475 [Warning] Couldn’t load plugin named ‘archive’ with soname ‘ha_archive.so’.
2014-04-07 11:06:33 14475 [Note] InnoDB: Using atomics to ref count buffer pool pages

I do not have plugin-load line in /etc/mysql/my.cnf

Note also:

“log_slow_queries” needs to change to “slow_query_log” or mysqld won’t start – nor does it seem to log anything useful in syslog regarding this either.

To use log_slow_query, replace all instances of log_slow_query to this:

slow_query_log = 1
slow_query_log_file = /var/log/mysql/slow-queries.log

Hello,

I have recently upgraded to MySQL 5.6.17 and everything is running fine (apart from some problems with froxlor). However, I am always getting the following Message in my logs when I startup the Server:

Apr 8 19:58:13 mail /etc/mysql/debian-start[8939]: FATAL ERROR: Upgrade failed

I made a manual mysql_upgrade -uroot -p, which ran trough successfully – so I don’t know why MySQL is trying to run an Upgrade everytime?

@Kevin and others who are having these errors in the log file:

[ERROR] Function ‘innodb’ already exists
[Warning] Couldn’t load plugin named ‘innodb’ with soname ‘ha_innodb.so’.
etc.

Clean your `plugin` table in your `mysql` database, e.g: with the following MySQL command:

TRUNCATE `mysql`.`plugin`;

Then restart MySQL server and the errors in the log file will be gone.

@dotdeb-user and others who are having the “Too many open files” problem:

Add the following lines to your /etc/security/limits.conf file:

* soft nofile 32768
* hard nofile 65536
root soft nofile 32768
root hard nofile 65536

Save the file. Log out from your Linux server then log back in and then restart MySQL server.

For more info, see:
https://wied.it/blog/increase-max-open-files-in-debian-squeeze-too-many-open-files-ulimit-n-limits-conf.html
It applies to Debian Wheezy, too.

Yeah, but for me this part of the MySQL documentation applied (from your link):
“server attempts to obtain as many as the system will permit”

On my Wheezy server the op.system permitted only 1024 files to be opened by any given user (including root, mysql, etc.) and I wanted to increase this op.system imposed limit, because:
(also from the official docs you have linked:) the default value of open_files_limit (if otherwise not specified) is minimum 5000 which is more than 1024.

After having upgraded 2 debian Wheezy and 4 windows mysql5.5 to 5.6 servers I suggest the following procedure:

backup the 5.5 database

stop (shutdown) the server

change/add the following settings in ini file

1. set innodb_force_recovery=3
2. set sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER
3. set explicit_defaults_for_timestamp
4. remove innodb_additional_mem_pool_size if any
5. remove innodb_locks_unsafe_for_binlog if any

replace the binaries (for Wheezy that means uninstall 5.5 and install 5.6)

delete the log_bin files (very important)

start the server

shut down the server

remove the setting: innodb_force_recovery=3 or set it to innodb_force_recovery=0

start the server

run mysql_upgrade

next start of the server should not show errors

Would id be possible to parse an /etc/default/mysql to slightly alter the mysql starting environment?

Zoltan gives us a good example of one of this possible alteration, for example by setting ulimit -n . This should be better to keep an global limit low (in limits.conf) and increase it especially for mysql, no?

etc/mysql/debian-start[8939]: FATAL ERROR: Upgrade failed. On every start. Should I be concerned? Mysql_upgrade did seem to work when i manually ran it

Hello,

i read all your post and try many solution but my mysql doen’t want start :

this is my error file when i start

“`
140415 09:30:34 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2014-04-15 09:30:34 17916 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)

2014-04-15 09:30:34 17916 [Note] Plugin ‘FEDERATED’ is disabled.
2014-04-15 09:30:34 17916 [ERROR] Function ‘innodb’ already exists
2014-04-15 09:30:34 17916 [Warning] Couldn’t load plugin named ‘innodb’ with soname ‘ha_innodb.so’.
2014-04-15 09:30:34 17916 [ERROR] Function ‘federated’ already exists
2014-04-15 09:30:34 17916 [Warning] Couldn’t load plugin named ‘federated’ with soname ‘ha_federated.so’.
2014-04-15 09:30:34 17916 [ERROR] Function ‘blackhole’ already exists
2014-04-15 09:30:34 17916 [Warning] Couldn’t load plugin named ‘blackhole’ with soname ‘ha_blackhole.so’.
2014-04-15 09:30:34 17916 [ERROR] Function ‘archive’ already exists
2014-04-15 09:30:34 17916 [Warning] Couldn’t load plugin named ‘archive’ with soname ‘ha_archive.so’.
2014-04-15 09:30:34 17916 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-04-15 09:30:34 17916 [Note] InnoDB: The InnoDB memory heap is disabled
2014-04-15 09:30:34 17916 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-04-15 09:30:34 17916 [Note] InnoDB: Compressed tables use zlib 1.2.7
2014-04-15 09:30:34 17916 [Note] InnoDB: Using Linux native AIO
2014-04-15 09:30:34 17916 [Note] InnoDB: Not using CPU crc32 instructions
2014-04-15 09:30:34 17916 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-04-15 09:30:34 17916 [Note] InnoDB: Completed initialization of buffer pool
2014-04-15 09:30:34 17916 [Note] InnoDB: Highest supported file format is Barracuda.
2014-04-15 09:30:35 17916 [Note] InnoDB: 128 rollback segment(s) are active.
2014-04-15 09:30:35 17916 [Note] InnoDB: Waiting for purge to start
2014-04-15 09:30:35 17916 [Note] InnoDB: 5.6.17 started; log sequence number 1923532
2014-04-15 09:30:35 17916 [Note] Server hostname (bind-address): ‘127.0.0.1’; port: 3306
2014-04-15 09:30:35 17916 [Note] – ‘127.0.0.1’ resolves to ‘127.0.0.1’;
2014-04-15 09:30:35 17916 [Note] Server socket created on IP: ‘127.0.0.1’.
2014-04-15 09:30:35 17916 [ERROR] Can’t start server: Bind on TCP/IP port: Cannot assign requested address
2014-04-15 09:30:35 17916 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2014-04-15 09:30:35 17916 [ERROR] Aborting

2014-04-15 09:30:35 17916 [Note] Binlog end
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘partition’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_SYS_DATAFILES’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_SYS_TABLESPACES’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_SYS_FOREIGN_COLS’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_SYS_FOREIGN’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_SYS_FIELDS’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_SYS_COLUMNS’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_SYS_INDEXES’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_SYS_TABLESTATS’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_SYS_TABLES’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_FT_INDEX_TABLE’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_FT_INDEX_CACHE’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_FT_CONFIG’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_FT_BEING_DELETED’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_FT_DELETED’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_FT_DEFAULT_STOPWORD’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_METRICS’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_BUFFER_POOL_STATS’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_BUFFER_PAGE_LRU’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_BUFFER_PAGE’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_CMP_PER_INDEX_RESET’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_CMP_PER_INDEX’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_CMPMEM_RESET’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_CMPMEM’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_CMP_RESET’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_CMP’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_LOCK_WAITS’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_LOCKS’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘INNODB_TRX’
2014-04-15 09:30:35 17916 [Note] Shutting down plugin ‘InnoDB’
2014-04-15 09:30:35 17916 [Note] InnoDB: FTS optimize thread exiting.
2014-04-15 09:30:35 17916 [Note] InnoDB: Starting shutdown…
2014-04-15 09:30:37 17916 [Note] InnoDB: Shutdown completed; log sequence number 1923542
2014-04-15 09:30:37 17916 [Note] Shutting down plugin ‘ARCHIVE’
2014-04-15 09:30:37 17916 [Note] Shutting down plugin ‘PERFORMANCE_SCHEMA’
2014-04-15 09:30:37 17916 [Note] Shutting down plugin ‘BLACKHOLE’
2014-04-15 09:30:37 17916 [Note] Shutting down plugin ‘MEMORY’
2014-04-15 09:30:37 17916 [Note] Shutting down plugin ‘CSV’
2014-04-15 09:30:37 17916 [Note] Shutting down plugin ‘MRG_MYISAM’
2014-04-15 09:30:37 17916 [Note] Shutting down plugin ‘MyISAM’
2014-04-15 09:30:37 17916 [Note] Shutting down plugin ‘sha256_password’
2014-04-15 09:30:37 17916 [Note] Shutting down plugin ‘mysql_old_password’
2014-04-15 09:30:37 17916 [Note] Shutting down plugin ‘mysql_native_password’
2014-04-15 09:30:37 17916 [Note] Shutting down plugin ‘binlog’
2014-04-15 09:30:37 17916 [Note] /usr/sbin/mysqld: Shutdown complete

140415 09:30:37 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
“`

my my.cnf

“`
#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# – “/etc/mysql/my.cnf” to set global options,
# – “~/.my.cnf” to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with –help to get a list of available options and with
# –print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain “#” chars…
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port = 3306
socket = /var/run/mysqld/mysqld.sock

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket = /var/run/mysqld/mysqld.sock
nice = 0

[mysqld]
#
# * Basic Settings
#
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
lc-messages-dir = /usr/share/mysql
skip-external-locking
explicit_defaults_for_timestamp
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address = 127.0.0.1
#
# * Fine Tuning
#
max_allowed_packet = 16M
thread_stack = 192K
thread_cache_size = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover-options = BACKUP
#max_connections = 100
table_open_cache = 64
#thread_concurrency = 10
#
# * Query Cache Configuration
#
query_cache_limit = 1M
query_cache_size = 16M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
# As of 5.1 you can enable the log at runtime!
#general_log_file = /var/log/mysql/mysql.log
#general_log = 1
#
# Error logging goes to syslog due to /etc/mysql/conf.d/mysqld_safe_syslog.cnf.
#
# Here you can see queries with especially long duration
#slow_query_log = 1
#slow_query_log_file = /var/log/mysql/mysql-slow.log
#long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
# other settings you may need to change.
#server-id = 1
#log_bin = /var/log/mysql/mysql-bin.log
expire_logs_days = 10
max_binlog_size = 100M
#binlog_do_db = include_database_name
#binlog_ignore_db = include_database_name
#
# basic loggin
log-error = /var/log/mysql/error.log
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
#
# It seems that we need this for successful mysql-5.1 -> mysql-5.6 upgrade
innodb_data_file_path=ibdata1:10M:autoextend

#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI “tinyca”.
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem

[mysqldump]
quick
quote-names
max_allowed_packet = 16M

[mysql]
#no-auto-rehash # faster start of mysql but no tab completition

[isamchk]
key_buffer = 16M

#
# * IMPORTANT: Additional settings that can override those from this file!
# The files must end with ‘.cnf’, otherwise they’ll be ignored.
#
!includedir /etc/mysql/conf.d/

“`

thx if you can help me

You have to check the error message that the port 3306 is already used – may be your older server is still runing. Try to set 3307 for change,
The other thing is the 127.0.0.1 binding. Do you really want to use it – it is only for local use not from another computer.

Hello!
How i can enable memchache? In /usr/lib/mysql/plugin/ i do not see libmemcached.so plugin. How i can install this plugin and use?

Hi Guillaume,

Today 2 of my servers reboot and both mysql couldn’t restart because of the following error :

mysqld: unknown option ‘–explicit_defaults_for_timestamp’

I deleted the line “explicit_defaults_for_timestamp” from my.cnf to soluve this problem.
I don’t know why the error occurred only now.

I forgot to say that it was 2 clean install from mysql 5.6 directly, not an upgrade from mysql 5.5

I’m running Debian Wheezy will all updates

I also encountered the same issue regarding the startup with the following happening:

root@hydrogen:/server/log/sql# /etc/init.d/mysql start
Starting MySQL database server: mysqldNo directory, logging in with HOME=/
. . . . . . . . . . . . . . failed!

Checking the logs i saw the following:

2014-04-26 01:37:41 6239 [Note] Plugin ‘FEDERATED’ is disabled.
2014-04-26 01:37:41 6239 [Note] Plugin ‘InnoDB’ is disabled.
2014-04-26 01:37:41 6239 [Note] Plugin ‘partition’ is disabled.
2014-04-26 01:37:41 6239 [ERROR] Unknown/unsupported storage engine: InnoDB
2014-04-26 01:37:41 6239 [ERROR] Aborting

Since I had InnoDB disabled specifically in the config as below:

skip-external-locking
skip-name-resolve
skip-host-cache
skip-partition
skip-symbolic-links
skip-innodb

I simply had to comment out/remove the ‘skip-innodb’ in the configuration
to have it up and running again.

TL:DR;
If you’re trying to disable InnoDB in mysql-5.6 the service won’t go up.
If you have no use for InnoDB then go ahead and dimension it down
to not use memory for buffering datasets back and forth.

Sidenote: Thanks for your effort providing mysql-5.6, Guillaume.P! Much appreciated!

Hi

I found /root/.mysql_history having unwanted numbers
http://bugs.mysql.com/bug.php?id=72108

On other place I found someone say:
In order to solve this problem we need to configure mysql source with –without-readline parameter.

And btw I was using this new 5.6 on a Parellels VPS. Now after a very long uptime, the server was restarted and crashed, since the upgrade removed upstart and changed init to sysvinit. Please note this somewhere to people on VPS, to check having the latest Parallels versions running to support things like this.

I am still trying to get rid of blackholes.so etc error notes.

I set max_connections = 400 in my.cnf but it’s still showing max_connections = 214 in SHOW VARIABLES.

I got something strange. A record being deleted in a table but normally a trigger does NOT allow it. I can’t reproduce the bug. I don’t know if it’s my code, my setting, this build of mysql. I never append for 1 year.

Does anyone experience something similar ?

Debian 7.4 64bits
Mysql 5.6 @dotdeb
Innodb tables

Forget what I said below. The problem is not coming from Mysql. I have no row missing. My mistake.

Today apt-get upgrade wants to “downgrade” mysql :

The following packages will be upgraded:
mysql-client-5.5 mysql-server-5.5 mysql-server-core-5.5

I’m already using 5.6 @dotdeb

Debian 7.4 64bits

I got the same error about the unknown option when I updated via apt-get to “mysql Ver 14.14 Distrib 5.5.37, for debian-linux-gnu (x86_64) using readline 6.2” Its not a dot-deb version (or at least I dont think it is) but your comment is the only detail on google I could find that gave an actual solution. Thanks.

My conclusion was I didnt install mysql-client-5.6 from dotdeb as I imaged, but mysql-client-5.5 from the debian package. Maybe you did the same.

Solved it. Apparently I had both of the installed. apt-get remove –purge mysql-client-5.5 mysql-server-5.5 mysql-server-core-5.5

did the trick for me.

LOTS of problems with this release, also on a clean wheezy install. Please do your homework better! Cost me a few hours today to fix this f*up package.

arggh, definitely still problems with debian-start script, man, what a mess this mysql BS is today, even dotdeb f* up ghe packages, horrible. Please fix the debian-start issue, thanks.

Guillaume, please delete those comments. This guy only adds noise and nobody gets anything out of them.

@Annoyed user : ok, could you please be more specific and could we have a useful feedback from you? First describe your environment (distribution, architecture, sources.list), provide your config files, check your log files for any relevant error, so that we can help you dealing with your LOTS of problems and get MySQL 5.6 work on your box.

Thanks in advance.

olala@box:# apt-get -V install mysql-server-5.6
Reading package lists… Done
Building dependency tree
Reading state information… Done
E: Unable to locate package mysql-server-5.6
E: Couldn’t find any package by regex ‘mysql-server-5.6’

I cannot install MySQL 5.6 help! 🙁

How I can disable unnecessary storage engines?
I have already disable a few engines:

skip-innodb
skip-blackhole
skip-federated
skip-archive

But for Memory and CSV engines when I try to add skip-csv or skip-memory, the server won’t to start.
I only need MyISAM and probably InnoDB in the future.

i run coomand:
mysqldump -q -u user -ppassword -h localhost gmdb | gzip -c > $BACKUP_MYSQL_DIR\-gracemax.sql.gz

and i get massage “Warning: Using a password on the command line interface can be insecure.”
how do disable it?
i have the mysql – 5.6.17-1~dotdeb.1

@Kenn Ejima : last time I took a look at MySQL’s packages, it was actually one monolithic package that was not fully compatible with the Debian packaging policy. I have to take a further look before giving any technical opinion on these new packages, but Oracle collaborating with Debian/Ubuntu devs should bring some good things.

FYI, my plan is to publish MariaDB 10.0 on Dotdeb, along with MySQL 5.6, for Wheezy, with seamless migration, based on Debian’s unstable packaging schemes.

check in your /etc/passwd
make sure mysql line holds /var/lib/mysql as home (not /undifined as it happened to me)
mysql:x:113:124:MySQL Server,,,:/var/lib/mysql:/bin/false

about open file limits, I struggled a bit and seems like it need open_files_limit directive to be specified in my.cnf (this wasn’t the case with mysql5.5 in my case)
adding
open_files_limit = 16000

soleved the isue [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)

./mysql start
[….] Starting MySQL database server: mysqldNo directory, logging in with HOME=/

And after that my KVM VPS si shuting down automaticaly, need to boot manual from VPS CP.

Hi, thanx for your great work, shouldn’t it be like that?
file /etc/mysql/debian-start:

MYUPGRADE=”/usr/bin/mysql_upgrade –defaults-extra-file=/etc/mysql/debian.cnf”

without credentials mysql_upgrade is failing, so we see in log every mysql start:
FATAL ERROR: Upgrade failed

Andreas reported it first, I have it in my log also – clean mysql 5.6 installation, not upgrade.

Hi Guys,

Wheezy install with mysql 5,6, having issues with the main Debian repos trying to downgrade to mysql 5.5. Anyway to specifically add only the mysql 5.6 repos without the core dotdeb:

deb http://packages.dotdeb.org wheezy all
deb-src http://packages.dotdeb.org wheezy all

Sources.list
deb http://ftp.de.debian.org/debian/ wheezy main contrib non-free
deb-src http://ftp.de.debian.org/debian/ wheezy main contrib non-free

deb http://security.debian.org/ wheezy/updates main contrib non-free
deb-src http://security.debian.org/ wheezy/updates main contrib non-free

# wheezy-updates, previously known as ‘volatile’
deb http://ftp.de.debian.org/debian/ wheezy-updates main contrib non-free
deb-src http://ftp.de.debian.org/debian/ wheezy-updates main contrib non-free

# DotDeb
#deb http://packages.dotdeb.org wheezy all
#deb-src http://packages.dotdeb.org wheezy all
deb http://packages.dotdeb.org wheezy-php55 all
deb-src http://packages.dotdeb.org wheezy-php55 all

Comments are closed.