mysqlchk xinetd config incorrectly refers to /usr/local/bin/clustercheck instead of /usr/bin/clustercheck

Bug #1000761 reported by Jay Janssen on 2012-05-17
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Percona XtraDB Cluster moved to
Fix Released
Raghavendra D Prabhu

Bug Description

[root@percona1 log]# which clustercheck
[root@percona1 log]# cat /etc/xinetd.d/mysqlchk
# default: on
# description: mysqlchk
service mysqlchk
# this is a config for xinetd, place it in /etc/xinetd.d/
        disable = no
        flags = REUSE
        socket_type = stream
        port = 9200
        wait = no
        user = nobody
        server = /usr/local/bin/clustercheck
        log_on_failure += USERID
        only_from =
        # recommended to put the IPs that need
        # to connect exclusively (security purposes)
        per_source = UNLIMITED

Changed in percona-xtradb-cluster:
assignee: nobody → Ignacio Nin (ignacio-nin)
importance: Undecided → High
Changed in percona-xtradb-cluster:
status: New → Confirmed
Changed in percona-xtradb-cluster:
milestone: none → 5.5.30-23.7.4
assignee: Ignacio Nin (ignacio-nin) → Raghavendra D Prabhu (raghavendra-prabhu)
status: Confirmed → Fix Released

Percona now uses JIRA for bug reports so this bug report is migrated to:

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

Duplicates of this bug

Other bug subscribers