pxc xinetd issues with debian my.cnf location

Bug #1276076 reported by Thomas C.
6
This bug affects 1 person
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-extra-file=/etc/my.cnf -nNE --connect-timeout=10 --user=USER --password=PASS -e 'SHOW STATUS LIKE '\''wsrep_local_state'\'';'

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

Revision history for this message
Raghavendra D Prabhu (raghavendra-prabhu) wrote :

@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!

Revision history for this message
Thomas C. (mick27-t) wrote :

Additionally, I find bit a bit of a constrain to have to either fill no extra args, or all of them.

I don't care about logging clustercheck for example, but since I have to enter an alternate my.cnf I have to fill all the fields.

i don't know if that can be taken care of here, but having -config / -log, etc arguments would be nice.

Revision history for this message
Thomas C. (mick27-t) wrote :

hell if I am pointed wher eto, I am sure I can do it

Revision history for this message
Raghavendra D Prabhu (raghavendra-prabhu) wrote :

Symlinking is the simplest workaround, however, for the logging you can for instance use /dev/null as the destination. For others (except user/pass) you can provide the default values.

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1601

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.