pxc xinetd issues with debian my.cnf location
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
5.5 |
Fix Released
|
Undecided
|
Unassigned | |||
5.6 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I upgraded today to pxc 5.6 GA, from the RC version on Debian.
It brought down my haproxy front-end as there seem to be a change in the clustercheck script.
I ran the script in debug, and ended up having the mysql command like this :
mysql --defaults-
My systems being debian, /etc/my.cnf was nowhere to be found, as it is in /etc/mysql/my.cnf
I see a new xinetd file, that has some more options than previously, ie server_args where I can specify the user/pass -and- the location of the my.cnf.
This was not set as it was previously not required.
I don't know if this is something that has to be changed before packaging, or if some kind of distro check script is needed ?
Workarounds:
- configure server__args or,
- ln -s /etc/mysql/my.cnf /etc/my.cnf
@Thomas,
Thank you for reporting this issue.
Yes, with recent changes in clustercheck and mysqlchk xinetd
config, the sixth parameter passed in server_args is mandatory if
/etc/my.cnf doesn't exist.
So, as you have mentioned, either pass cnf file as sixth
parameter of clustercheck in server_args or link cnf file to
/etc/my.cnf.
======= ======= ======= ======= ======= =====
I will also document this in errata.
Thanks again!