Shulou(Shulou.com)05/31 Report--

What this article shares with you is about the building of PXC, which the editor thinks is very practical, so I share it with you to learn. I hope you can get something after reading this article.

Unable to start the first node

2017-11-18T15:53:00.732400Z 0 [Note] WSREP: gcomm: connecting to group 'zrz', peer' 192.168.1.101 WSREP'

2017-11-18T15:53:00.733049Z 0 [Note] WSREP: (8dec793b, 'tcp://0.0.0.0:4567') connection established to 8dec793b tcp://192.168.1.101:4567

2017-11-18T15:53:00.733073Z 0 [Warning] WSREP: (8dec793b, 'tcp://0.0.0.0:4567') address' tcp://192.168.1.101:4567' points to own listening address, blacklisting

2017-11-18T15:53:03.733022Z 0 [Note] WSREP: (8dec793b, 'tcp://0.0.0.0:4567') connection to peer 8dec793b with addr tcp://192.168.1.101:4567 timed out, no messages seen in PT3S

2017-11-18T15:53:03.733131Z 0 [Warning] WSREP: no nodes coming from prim view, prim not possible

2017-11-18T15:53:03.733151Z 0 [Note] WSREP: Current view of cluster as seen by this node

View (view_id (NON_PRIM,8dec793b,1))

Memb {

8dec793b,0

}

Joined {

}

Left {

}

Partitioned {

}

)

2017-11-18T15:53:04.233267Z 0 [Warning] WSREP: last inactive check more than PT1.5S ago (PT3.50093S), skipping check

2017-11-18T15:53:33.736202Z 0 [Note] WSREP: Current view of cluster as seen by this node

View ((empty))

2017-11-18T15:53:33.736368Z 0 [ERROR] WSREP: failed to open gcomm backend connection: 110: failed to reach primary view: 110 (Connection timed out)

At gcomm/src/pc.cpp:connect (): 158

2017-11-18T15:53:33.736383Z 0 [ERROR] WSREP: gcs/src/gcs_core.cpp:gcs_core_open (): 208: Failed to open backend connection:-110( Connection timed out)

2017-11-18T15:53:33.736618Z 0 [ERROR] WSREP: gcs/src/gcs.cpp:gcs_open (): 1463: Failed to open channel 'zrz' at' gcomm://192.168.1.101':-110 (Connection timed out)

2017-11-18T15:53:33.736631Z 0 [ERROR] WSREP: gcs connect failed: Connection timed out

2017-11-18T15:53:33.736636Z 0 [ERROR] WSREP: Provider/Node (gcomm://192.168.1.101) failed to establish connection with cluster (reason: 7)

2017-11-18T15:53:33.736641Z 0 [ERROR] Aborting

2017-11-18T15:53:33.736651Z 0 [Note] Giving 0 client threads a chance to die gracefully

2017-11-18T15:53:33.736656Z 0 [Note] WSREP: Waiting for active wsrep applier to exit

2017-11-18T15:53:33.736659Z 0 [Note] WSREP: Service disconnected.

2017-11-18T15:53:33.736664Z 0 [Note] WSREP: Waiting to close threads.

2017-11-18T15:53:38.736758Z 0 [Note] WSREP: Some threads may fail to exit.

2017-11-18T15:53:38.736807Z 0 [Note] Binlog end

2017-11-18T15:53:38.737048Z 0 [Note] / usr/local/mysql/bin/mysqld: Shutdown complete

Main description of the problem: error log prompt failed to join the node successfully

Reason: the first node needs to specify itself to start as a cluster when it starts.

Solution: start by adding-- wsrep-new-cluster parameter. The officially specified bootstrap-pxc parameter does not take effect.

The second node cannot join

2017-11-19T15:55:29.227793Z 0 [ERROR] WSREP: Process completed with error: wsrep_sst_xtrabackup-v2-- role 'donor'-- address' 192.168.1.103 -binlog 'mysql-bin'-- gtid' df47a753-cd3d-11e7-85b5-66f48d655632 virtual: 32 (Broken pipe)

2017-11-19T15:55:29.227868Z 0 [ERROR] WSREP: Command did not run: wsrep_sst_xtrabackup-v2-- role 'donor'-- address' 192.168.1.103 -binlog 'mysql-bin'-- gtid' df47a753-cd3d-11e7-85b5-66f48d655632 purl 0'

Problem description: unable to transfer SST successfully

Under the mysql/bin directory, execute wsrep_sst_xtrabackup-v2-- role 'donor'-- address' 192.168.1.103 donor'-- 192.168.1.103-- socket'/ data/mysql/3306/tmp/mysql3306.sock'-- datadir'/ data/mysql/3306/data/'-- defaults-file'/ data/mysql/3306/my.cnf'-- defaults-group-suffix'--binlog 'mysql-bin'-- gtid' df47a753-cd3d-11e7-85b5-66f48d655632u0'

Tip:

Which: no socat in (/ usr/sbin:/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/usr/local/mysql/bin:/usr/local/pxc/bin:/root/bin)

Reason: lack of dependent component socat

Solution: yum-y install socat

When can I join the second one?

2017-11-19T15:15:11.735984Z 2 [Note] WSREP: New cluster view: global state: 50970ac2-cc82-11e7-8b90-c716227b4ac7:0, view# 8: Primary, number of nodes: 2, my index: 0, protocol version 3

2715-2017-11-19T15:15:11.735993Z 2 [Warning] WSREP: Gap in state sequence Need state transfer.

2716-2017-11-19T15:15:11.736057Z 0 [Note] WSREP: Initiating SST/IST transfer on JOINER side (wsrep_sst_rsync-- role 'joiner'-- address' 192.168.1.102'--datadir'/ data/mysql/3306/data/'-- defaults-file'/ data/mysql/3306/my.cnf'-- defaults-group-suffix''--parent '3104'-- binlog 'mysql-bin')

2717:which: no lsof in (/ usr/sbin:/sbin:/usr/local/Percona-XtraDB-Cluster-5.7.18-rel15-29.20.1.Linux.x86_64.ssl101/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/usr/local/mysql/bin:/root/bin)

2718-2017-11-19T15:15:11.874860Z 0 [ERROR] WSREP: Failed to read 'ready' from: wsrep_sst_rsync-- role 'joiner'-- address' 192.168.1.102'--datadir'/ data/mysql/3306/data/'-- defaults-file'/ data/mysql/3306/my.cnf'-- defaults-group-suffix'--parent '3104'-binlog 'mysql-bin'

2719: Read:''lsof' not found in PATH'

2720-2017-11-19T15:15:11.874912Z 0 [ERROR] WSREP: Process completed with error: wsrep_sst_rsync-- role 'joiner'-- address' 192.168.1.102'--datadir'/ data/mysql/3306/data/'-- defaults-file'/ data/mysql/3306/my.cnf'-- defaults-group-suffix'--parent '3104'-- binlog 'mysql-bin': 2 (No such file or directory)

2721-2017-11-19T15:15:11.874964Z 2 [ERROR] WSREP: Failed to prepare for 'rsync' SST Unrecoverable.

2722-2017-11-19T15:15:11.874987Z 2 [ERROR] Aborting

2723-

2724-2017-11-19T15:15:11.874993Z 2 [Note] Giving 2 client threads a chance to die gracefully

Problem description: unable to transfer SST

Reason: lack of dependent component lsof

Solution: yum-y install lsof

Suggestion: 1. Start stand-alone first, change the root account, and create the sst transfer account, then start the first node.

two。 If the xtrabackup-v2 transmission always reports errors, you can use rsync instead and comment out the auth line

3. The second and third node failed to start. You can violently delete the files under the data directory and reinitialize them.

4. You can delete the two cluster information files starting with g under the data directory and restart to try to troubleshoot

The port 4567 of the 5.telnet master node determines whether the mysqld service of the network and the master node is normal.

6. Libaiorecoveryopenssl can also be considered to install

These are the problems of PXC building, and the editor believes that there are some knowledge points that we may see or use in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.