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

service mysql start command is cleaning up all the files under /var/lib/mysql

sriharv1sriharv1 EntrantCurrent User Role Novice
Hello,

We are using 2 node Galera cluster ,Found out that one of mysql instance was down hence issued service mysql start on the node where mysql services was down
Instead of starting mysql services and adding in to the cluster .MYSQL cleaned up all the files under /var/lib/mysql. I am trying to understand when starting the cluster why mysql services is deleting all the files. Getting the following message in logs. Any idea on what could be the reason.

{code}
removed `/var/lib/mysql/mysql.sock'
removed `/var/lib/mysql/ib_logfile0'
removed `/var/lib/mysql/ibdata1'
removed `/var/lib/mysql/aria_log.00000001'
removed `/var/lib/mysql/aria_log_control'
removed `/var/lib/mysql/mysql-bin.index'
removed `/var/lib/mysql/mysql-bin.000001'
WSREP_SST: [ERROR] Cleanup after exit with status:1 (20190405 04:42:09.364)
WSREP_SST: [INFO] Removing the sst_in_progress file (20190405 04:42:09.367)
190405 4:42:09 [ERROR] WSREP: Process completed with error: wsrep_sst_xtrabackup-v2 --role 'joiner' --address '10.190.123.70' --auth 'replication:replication' --datadir '/var/lib/mysql/' --defaults-file '/etc/my.cnf' --parent '110290': 1 (Operation not permitted)
190405 4:42:09 [ERROR] WSREP: Failed to read uuid:seqno from joiner script.
190405 4:42:09 [ERROR] WSREP: SST failed: 1 (Operation not permitted)
190405 4:42:09 [ERROR] Aborting

190405 4:42:11 [Note] WSREP: Closing send monitor...
{code}
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.