[MDEV-27513] MariaDB cannot be started with [ERROR] mysqld got signal 6 ; Created: 2022-01-14  Updated: 2022-01-24  Resolved: 2022-01-24

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.3.29
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Alissa H Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: crash, innodb
Environment:

Hosting WordPress website on Google Cloud Platform



 Description   

Hello, I was updating a plugin on my WordPress site and received an email from JetPack saying that my site is down. Since then, I am receiving the error message "Error Establishing Database Connection; Error 3306" and have not been able to get into the site.
I have tried accessing the phpMyAdmin to see if the error was the connection with MySQL. After accessing the phpMyAdmin and entering the correct credentials, I received the error message "mysqli::real_connect(): (HY000/2002): Connection refused".

This is the log message (/opt/bitnami/mariadb/logs/mysqld.log) and it seems like MariaDB cannot be started.
2022-01-12 19:58:41 0 [Note] InnoDB: Completed initialization of buffer pool
2022-01-12 19:58:41 0x7fd5c2048f40 InnoDB: Assertion failure in file /bitnami/blacksmith-sandox/mariadb-10.3.29/storage/innobase/os/os0thread.cc line 140
InnoDB: Failing assertion: ret == 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
220112 19:58:41 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Any help is appreciated!



 Comments   
Comment by Marko Mäkelä [ 2022-01-14 ]

The assertion fails because pthread_create() is failing, that is, a thread could not be created. What does the configuration look like?

Comment by Alissa H [ 2022-01-14 ]

Hi Marko, thanks for looking into this issue. I am not entirely sure what you mean by configuration. How can I get that information?

Comment by Daniel Black [ 2022-01-14 ]

Do you pass a mariadb a configuration in the environment variable MARIADB_EXTRA_FLAGS or configuration file /opt/bitnami/mariadb/conf/my_custom.cnf (ref: https://github.com/bitnami/bitnami-docker-mariadb#readme)?

This is usually going to happen because there are insufficient resources, usually memory, to start the thread.

Comment by Alissa H [ 2022-01-24 ]

Just wanted to let you know that the site came back up in two days. I am
assuming that a plugin update finally completed maybe due to lack of
memory. After the site came back I checked the memory and as you pointed
out it was insufficient, now I have increased the memory and it seems to be
doing fine now.
Thank you and much appreciated. Regards

On Fri, Jan 14, 2022 at 1:55 PM Daniel Black (Jira) <jira@mariadb.org>

Generated at Thu Feb 08 09:53:29 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.