Announcement

Announcement Module
Collapse
No announcement yet.

Problem with HAproxy and PXC

Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Problem with HAproxy and PXC

    Hello all,

    I have followed all the documents on setting up HAproxy to work with PXC. I am currently having an issues with the HAproxy seeing that the nodes are on line and in sync. If I run clustercheck from each PXC node I get output like this:

    [mysqladm@centos ~]$ clustercheck
    HTTP/1.1 200 OK
    Content-Type: text/plain
    Connection: close
    Content-Length: 40

    Percona XtraDB Cluster Node is synced.

    But if I run this command from my HAproxy server I am getting an error that the cluster is not in sync.

    [wayne@rose-lab4 ~]$ telnet 192.168.1.60 9200
    Trying 192.168.1.60...
    Connected to 192.168.1.60.
    Escape character is '^]'.
    HTTP/1.1 503 Service Unavailable
    Content-Type: text/plain
    Connection: close
    Content-Length: 44

    Percona XtraDB Cluster Node is not synced.
    Connection closed by foreign host.

    This is what I see in the messages file on each of my PXC nodes:

    Mar 6 13:49:32 centos xinetd[2659]: START: mysqlchk pid=3842 from=::ffff:192.168.1.63
    Mar 6 13:49:32 centos xinetd[2659]: EXIT: mysqlchk status=1 pid=3842 duration=0(sec)

    I am googled around looking for an answer and I have yet to find anything. Here is what the mysqlchk looks like in /etc/xinetd.d:

    # 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/bin/clustercheck
    log_on_failure += USERID
    only_from = 192.168.1.63
    # recommended to put the IPs that need
    # to connect exclusively (security purposes)
    per_source = UNLIMITED

    Thanks for any information you can send me way.

    Wayne.

  • #2
    is your xinet.d process running on the cluster nodes?

    Comment


    • #3
      Yup and I see it logging these messages to the messages file: Mar 6 13:49:32 centos xinetd[2659]: START: mysqlchk pid=3842 from=::ffff:192.168.1.63
      Mar 6 13:49:32 centos xinetd[2659]: EXIT: mysqlchk status=1 pid=3842 duration=0(sec)

      Comment

      Working...
      X