Join 1M+ other developers and:
- Get help and share knowledge in Q&A
- Subscribe to topics of interest
- Get courses & tools that help you grow as a developer or small business owner
How to restore Mysql Galera Cluster after upgrade Ubuntu 18
I followed this guide to start mysql cluster with 2 nodes: Galera Digital Ocean
Everything works fine until I upgrade APT and forget to ignore Galera&Mysql package.
root@prod-1:/home/bar# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: linux-headers-4.15.0-132 linux-headers-4.15.0-132-generic linux-image-4.15.0-132-generic linux-modules-4.15.0-132-generic linux-modules-extra-4.15.0-132-generic Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up mysql-wsrep-server-5.7 (5.7.33-25.25-1ubuntu18.04) ... Skipping profile in /etc/apparmor.d/disable: usr.sbin.mysqld Job for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -xe" for details. dpkg: error processing package mysql-wsrep-server-5.7 (--configure): installed mysql-wsrep-server-5.7 package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of mysql-wsrep-5.7: mysql-wsrep-5.7 depends on mysql-wsrep-server-5.7 (= 5.7.33-25.25-1ubuntu18.04); however: Package mysql-wsrep-server-5.7 is not configured yet. dpkg: error processing package mysql-wsrep-5.7 (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: mysql-wsrep-server-5.7 mysql-wsrep-5.7 E: Sub-process /usr/bin/dpkg returned an error code (1) root@prod-1:/home/bar#
It happens in 2 nodes and I cannot start my cluster anymore.
What I have to do to fix this issue.
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.×