Config file my.cnf is missing in default percona-server-server-5.5 installation from oneiric repository

Asked by Cyrille on 2012-02-02

When installing the percona-server-server-5.5 package using the apt repository for Ubuntu 11.10 (oneiric), no configuration file 'my.cnf' is installed under /etc/mysql/.

Is there a reason not to provide this configuration file? Or is it a bug in the package?

I'm aware of the existence of Percona's online configuration tool. But I am convinced a default configuration should always be installed after a clean and fresh installation. Moreover xtrabackup is expecting it and will therefor fail by default.

Question information

English Edit question
Percona Server moved to Edit question
No assignee Edit question
Last query:
Last reply:
Cyrille (cyrille-bartholomee) said : #1

Checked some of the deb files in your repository. I found out that the common package for version 5.1.59 contains a my.cnf under /etc/mysql. Though all 5.5.19 common packages and several for other 5.5 versions I checked do not contain this file. I can see the folder structure /etc/mysql/conf.d, but the my.cnf file is missing.

Cyrille (cyrille-bartholomee) said : #2

This is the error message I get when performing xtrabackup after a default 5.5 installation:

xtrabackup: Error: Please set parameter 'datadir'
innobackupex: fatal error: no 'mysqld' group in MySQL options
innobackupex: fatal error: OR no 'datadir' option in group 'mysqld' in MySQL options

Alexey Kopytov (akopytov) said : #3

Right, we don't ship my.cnf with Percona Server packages deliberately, see

Regarding the xtrabackup issue, you can either specify the data directory explicitely with xtrabackup --datadir, or create your own my.cnf and pass it to xtrabackup with the --defaults-file option.

Cyrille (cyrille-bartholomee) said : #4

I read the post you mentioned, but there is no clear explanation why my.cnf is not shipped by default. This means a clean installation of Percona is partially broken until manual intervention. Of course I know I have to check my configuration after installation, but that is not a valid argument for leaving a default configuration out. Moreover I think installation of Percona should be like standard MySQL installation as close as possible, although I know Percona is not MySQL.

One more thing. I found out about the missing configuration when upgrading my Percona installation from 5.1 to 5.5 in my testing environment. Purging the old 5.1 installation files removed the my.cnf file. I have this habit of keeping my system clean and tidy (as every administrator should), and purge old not used packages. Purging maybe not the best practice, but it is only in this case of cross package dependency it is causing trouble.

Hope my considerations can help to improve your products.

Alexey Kopytov (akopytov) said : #5


The reason for not shipping any default my.cnf with Percona Server is that there is no one-size-fits-all configuration. So we don't want users shooting themselves in the foot with inappropriate defaults, and instead let them create their own configuration (for example, by copying and adjusting one of the examples in the doc directory),

But thanks for the feedback, much appreciated. Please post your thoughts to the bug report I referenced. Having it one place may help us to reconsider the original decision.

Joshua Myhre (cloud-f) said : #6

I started a page to help the people who find them selves in the Percona "my.cnf" or "my.ini" debacle:

"Right, we don't ship my.cnf with Percona Server packages deliberately, see"

Why not link to a guide or user manual which could provide those who do not know the exact cure behind creating the "missing" my.cnf or my.ini file? I understand the "CYA" approach Percona has taken, but IMO has fallen short with providing instructions on how to work around or fix those who install Percona and find out after the fact they do not include a standard my.cnf or y.ini file. It almost appears via Google searching and at the main wensite that Percona is avoiding this "Oh by the way" issue or taking an approach being that if you do not know, then you should not be using Percona.

You get results such:

Taken from a Google search:

Generated using the search tool at Percona & MySQL Performance Blog:

Percona even has answered threads about this topic in their own forums:

Cyrille (cyrille-bartholomee) said : #7

A greater concern is those upgrading from 5.1 to 5.5, purging the 5.1 installation and as a result of that finding their my.cnf has been deleted. Myabe purging installed packages is not the best thing to do, but I tend to keep my systems clean and tidy.

Although I know Percona != MySQL, I also know people using it are mostly used to MySQL installations. Therefor I think your statement "then you should not be using Percona" is quite offensive. So far you still did not provide any valid reason not to provide a default my.cnf and this last one is the worst of all.

Can you help with this problem?

Provide an answer of your own, or ask Cyrille for more information if necessary.

To post a message you must log in.