I am getting thsi error:

Starting MariaDB 10.4.17 database server...
WSREP: Failed to start mysqld for wsrep recovery: '2020-11-23 21:48:20 0 [Note] /usr/sbin/mysqld (mysqld 10.4.17-MariaDB-1:10.4.17+ma
2020-11-23 21:48:20 0 [Note] InnoDB: Using Linux native AIO
2020-11-23 21:48:20 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-11-23 21:48:20 0 [Note] InnoDB: Uses event mutexes
2020-11-23 21:48:20 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-11-23 21:48:20 0 [Note] InnoDB: Number of pools: 1
2020-11-23 21:48:20 0 [Note] InnoDB: Using generic crc32 instructions
2020-11-23 21:48:20 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
2020-11-23 21:48:20 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
2020-11-23 21:48:20 0 [Note] InnoDB: Completed initialization of buffer pool
2020-11-23 21:48:20 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page
2020-11-23 21:48:20 0 [ERROR] InnoDB: Upgrade after a crash is not supported. This redo log was created before MariaDB 10.2.2.
2020-11-23 21:48:20 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2020-11-23 21:48:20 0 [Note] InnoDB: Starting shutdown...
2020-11-23 21:48:21 0 [ERROR] Plugin 'InnoDB' init function returned error.
2020-11-23 21:48:21 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2020-11-23 21:48:21 0 [Note] Plugin 'FEEDBACK' is disabled.
2020-11-23 21:48:21 0 [ERROR] Unknown/unsupported storage engine: innodb
2020-11-23 21:48:21 0 [ERROR] Aborting'

this is my galera config:

# Galera Provider Configuration
# Galera Cluster Configuration
# Galera Synchronization Configuration
# Galera Node Configuration

the first and second node are working fine this 3rd node didnt pick up if I delte the mysql data dir and restart fresh will this third node pick up from the other 2 nodes ?

mariadb Ver 15.1 Distrib 10.4.17-MariaDB, for debian-linux-gnu (aarch64) using readline 5.2 
node3-cluster:~$ exit node1-cluster:~$ mariadb --version 
mariadb Ver 15.1 Distrib 10.1.47-MariaDB, for debian-linux-gnu (aarch64) using readline 5.2 
node2-cluster:~ $ mariadb --version 
mariadb Ver 15.1 Distrib 10.3.25-MariaDB, for debian-linux-gnueabihf (armv7l) using readline 5.2
  • "Upgrade after a crash is not supported. This redo log was created before MariaDB 10.2.2" -- looks to me like there's a version mismatch between your cluster nodes, or may be you upgraded an instance that was not cleanly shut down. – mustaccio Nov 24 '20 at 0:26
  • Well, major and minor version are same but distrib version of this node is ahead of other nodes. My phone is not allowing me to paste – Ciasto piekarz Nov 24 '20 at 0:42
  • @mustaccio I have updated my post, with mariadb versions first one in line is the 3rd node that is failing – Ciasto piekarz Nov 24 '20 at 22:24
  • So, why is there a pre-10.2.2 redo log on the node running MariaDB 10.4.17? And why are you running different versions of MariaDB in your cluster at all? – mustaccio Nov 24 '20 at 22:49
  • Well it ended up different version i am fixing that now but dont know about pre-10.2.2 refo log – Ciasto piekarz Nov 24 '20 at 22:50

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.