Not the answer you need?
Register and ask your own question!

ERROR! MySQL (Percona XtraDB Cluster) server startup failed

NPXDBClsNPXDBCls EntrantCurrent User Role Novice
Hello All,
I am new to Percona XtraDB Cluster, so thank you in advance for any help.
I have a 3 cluster nodes.
the 1st node I started with /etc/init.d/mysql bootstrap-pxc
the 2nd node I tried starting with /etc/init.d/mysql start --- this one is failing. :(
the 3rd node I started with /etc/init.d/mysql start

Background, All 3 are VM clients, the 3 nodes were moved to a new VM server.
after the new nodes were started, I am started running rsync on the new nodes to pull the data daily while the cluster is running still on the old VM servers.

to clarify the OLD VM are still live on the old VMWare.

the new VMs are up and running and I am running rsync on the new VM to get the current data from the OLD VMs.

On the new VMs, on the primary node, I am able to start by running bootstrap-pxc, on the 3rd node I am able to start without any problems. The 2nd node is refusing to start.
191125 13:00:54 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
191125 13:00:54 mysqld_safe WSREP: Running position recovery with --log_error='/var/lib/mysql/wsrep_recovery.7KUYXU' --pid-file='/var/lib/mysql/cgi-dbc2.com-recover.pid'
2019-11-25 13:00:55 0 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
2019-11-25 13:00:55 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
191125 13:00:59 mysqld_safe WSREP: Recovered position a344a92f-65f8-11e4-8105-f7bf7501c52e:84041533
Log of wsrep recovery (--wsrep-recover):
2019-11-25 13:00:55 7144 [Note] Plugin 'FEDERATED' is disabled.
2019-11-25 13:00:55 7fc834d147e0 InnoDB: Warning: Using innodb_locks_unsafe_for_binlog is DEPRECATED. This option may be removed in future releases. Please use READ COMMITTED transaction isolation level instead, see http://dev.mysql.com/doc/refman/5.6/en/set-transaction.html.
2019-11-25 13:00:55 7144 [Note] InnoDB: Using atomics to ref count buffer pool pages
2019-11-25 13:00:55 7144 [Note] InnoDB: The InnoDB memory heap is disabled
2019-11-25 13:00:55 7144 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-11-25 13:00:55 7144 [Note] InnoDB: Memory barrier is not used
2019-11-25 13:00:55 7144 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-11-25 13:00:55 7144 [Note] InnoDB: Using Linux native AIO
2019-11-25 13:00:55 7144 [Note] InnoDB: Using CPU crc32 instructions
2019-11-25 13:00:55 7144 [Note] InnoDB: Initializing buffer pool, size = 20.0G
2019-11-25 13:00:56 7144 [Note] InnoDB: Completed initialization of buffer pool
2019-11-25 13:00:56 7144 [Note] InnoDB: Highest supported file format is Barracuda.
2019-11-25 13:00:56 7144 [Note] InnoDB: 128 rollback segment(s) are active.
2019-11-25 13:00:56 7144 [Note] InnoDB: Waiting for purge to start
2019-11-25 13:00:56 7fc286bfd700 InnoDB: Error: page 3 log sequence number 272095898921
InnoDB: is in the future! Current system log sequence number 272094296184.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-11-25 13:00:56 7fc286bfd700 InnoDB: Error: page 290 log sequence number 272095840933
InnoDB: is in the future! Current system log sequence number 272094296184.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
........ snipped



Help me, please

Comments

  • tsvenblatsvenbla Entrant Inactive User Role Novice
    Hi!

    Have you tried to just delete all contents under on node 2 and start it up again? That way, SST should kick in and copy everything from node 1 or 3.
  • NPXDBClsNPXDBCls Entrant Current User Role Novice
    After removing /var/lib/mysql/grastate.dat, then I was able to start mysql, ty
Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.