Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
-
10.5.9
-
Platform : Drupal 9
OS : Redhat Enterprise Linux Server 7.6 on VMWare (Version)
Language : PHP 7.3.15
Web Server : Apache 2.4.6
Database : MariaDB 10.5.9 with Galera Cluster
Search Engine : Solr 6.6.5
BIG-IP Virtual Edition: Linux 3.10.0-514.26.2.el7.ve.x86_64: BIG-IP software release 13.1.3.2, build 0.0.4
BIG-IP Virtual Edition: Linux 3.10.0-514.26.2.el7.ve.x86_64: BIG-IP software release 13.1.3.2, build 0.0.4
we are on a three node cluster environment.Platform : Drupal 9 OS : Redhat Enterprise Linux Server 7.6 on VMWare (Version) Language : PHP 7.3.15 Web Server : Apache 2.4.6 Database : MariaDB 10.5.9 with Galera Cluster Search Engine : Solr 6.6.5 BIG-IP Virtual Edition: Linux 3.10.0-514.26.2.el7.ve.x86_64: BIG-IP software release 13.1.3.2, build 0.0.4 BIG-IP Virtual Edition: Linux 3.10.0-514.26.2.el7.ve.x86_64: BIG-IP software release 13.1.3.2, build 0.0.4 we are on a three node cluster environment.
Description
After recent upgrade, all of sudden The MariaDB database is getting crashed on first VM, and one of the two databases were also getting crashed on second VM. To resolve impact, we had to stop the remaining database on second VM, edit the /data/database/mysql/grastate.dat file on first VM to say it's safe to bootstrap, bring up the database on First VM with a new cluster, and then start the databases on second VM.
Attaching the core dumps here.
Please let us know if the above description is not clear.