# mySQL DB crashing

**URL:** <https://forums.percona.com/t/mysql-db-crashing/20316>\
**Category:** Uncategorized\
**Tags:** percona\
**Created:** [February 27, 2023, 10:44am UTC](https://forums.percona.com/t/mysql-db-crashing/20316 "2023-02-27T10:44:27Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Anisha](https://avatars.discourse-cdn.com/v4/letter/a/8dc957/32.png) [@Anisha](https://forums.percona.com/u/Anisha)\
**Post date:** [February 27, 2023, 10:44am UTC](https://forums.percona.com/t/mysql-db-crashing/20316/1 "2023-02-27T10:44:27Z")

</div>

Hi Team,

We are facing with DB crashing frequently in 8.0.30 percona version.

Below are the errors reported during crash .

01:04:20 UTC - mysqld got signal 11 ;  
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.

Build ID: Not Available  
Server Version: 8.0.30-22 Percona Server (GPL), Release 22, Revision 7e301439b65

Thread pointer: 0x7f906801e000  
Attempting backtrace. You can use the following information to find out  
where mysqld died. If you see no messages after this, something went  
terribly wrong…  
stack\_bottom = 7f9087ef8bb0 thread\_stack 0x100000  
/home/mysqld/sys/8.0.30\_percona/bin/mysqld(my\_print\_stacktrace(unsigned char const\*, unsigned long)+0x3d) [0x206883d]  
/home/mysqld/sys/8.0.30\_percona/bin/mysqld(print\_fatal\_signal(int)+0x30f) [0x114a4af]  
/home/mysqld/sys/8.0.30\_percona/bin/mysqld(handle\_fatal\_signal+0xc5) [0x114a585]  
/lib64/libpthread.so.0(+0xf630) [0x7f919eeee630]  
/home/mysqld/sys/8.0.30\_percona/bin/mysqld(Prepared\_statement::trace\_parameter\_types()+0xb4) [0xff5a84]  
/home/mysqld/sys/8.0.30\_percona/bin/mysqld(Prepared\_statement::prepare\_query()+0x184) [0xff90d4]  
/home/mysqld/sys/8.0.30\_percona/bin/mysqld(Prepared\_statement::prepare(char const\*, unsigned long, Item\_param\*\*)+0x82a) [0xffa1fa]  
/home/mysqld/sys/8.0.30\_percona/bin/mysqld(mysqld\_stmt\_prepare(THD\*, char const\*, unsigned int, Prepared\_statement\*)+0xb6) [0xffac96]  
/home/mysqld/sys/8.0.30\_percona/bin/mysqld(dispatch\_command(THD\*, COM\_DATA const\*, enum\_server\_command)+0xfd8) [0xfca7c8]  
/home/mysqld/sys/8.0.30\_percona/bin/mysqld(do\_command(THD\*)+0x282) [0xfcc862]  
/home/mysqld/sys/8.0.30\_percona/bin/mysqld() [0x113a880]  
/home/mysqld/sys/8.0.30\_percona/bin/mysqld() [0x253e925]  
/lib64/libpthread.so.0(+0x7ea5) [0x7f919eee6ea5]  
/lib64/libc.so.6(clone+0x6d) [0x7f919d22fb2d]

Trying to get some variables.  
Some pointers may be invalid and cause the dump to abort.  
Query (xxx ): insert into xxxx (xx , xxx, xxx) values (?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?),(?, ?, ?  
Connection ID (thread ID): 763267  
Status: NOT\_KILLED

Please help us make Percona Server better by reporting any  
bugs at [https://bugs.percona.com/](https://bugs.percona.com/)

05:01:20 UTC - mysqld got signal 11 ;  
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.

Build ID: Not Available  
Server Version: 8.0.30-22 Percona Server (GPL), Release 22, Revision 7e301439b65

Thread pointer: 0x7f9a3001e000  
Attempting backtrace. You can use the following information to find out  
where mysqld died. If you see no messages after this, something went  
terribly wrong…  
stack\_bottom = 7f9b0121abb0 thread\_stack 0x100000  
/home/mysqld/sys/8.0.30\_percona/bin/mysqld(my\_print\_stacktrace(unsigned char const\*, unsigned long)+0x3d) [0x206883d]  
/home/mysqld/sys/8.0.30\_percona/bin/mysqld(print\_fatal\_signal(int)+0x30f) [0x114a4af]  
/home/mysqld/sys/8.0.30\_percona/bin/mysqld(handle\_fatal\_signal+0xc5) [0x114a585]  
/lib64/libpthread.so.0(+0xf630) [0x7f9b537c9630]  
/lib64/libc.so.6(+0x1565da) [0x7f9b51b625da]  
/home/mysqld/sys/8.0.30\_percona/bin/mysqld(String::append(char const\*, unsigned long)+0xa1) [0x11230e1]  
/home/mysqld/sys/8.0.30\_percona/bin/mysqld(Prepared\_statement::insert\_parameters(String\*, bool, PS\_PARAM\*)+0x16f) [0xffbf9f]  
/home/mysqld/sys/8.0.30\_percona/bin/mysqld(Prepared\_statement::set\_parameters(String\*, bool, PS\_PARAM\*)+0x33) [0xffc853]  
/home/mysqld/sys/8.0.30\_percona/bin/mysqld(mysqld\_stmt\_execute(THD\*, Prepared\_statement\*, bool, unsigned long, PS\_PARAM\*)+0x10e) [0xffd3ce]  
/home/mysqld/sys/8.0.30\_percona/bin/mysqld(dispatch\_command(THD\*, COM\_DATA const\*, enum\_server\_command)+0x104d) [0xfca83d]  
/home/mysqld/sys/8.0.30\_percona/bin/mysqld(do\_command(THD\*)+0x282) [0xfcc862]  
/home/mysqld/sys/8.0.30\_percona/bin/mysqld() [0x113a880]  
/home/mysqld/sys/8.0.30\_percona/bin/mysqld() [0x253e925]  
/lib64/libpthread.so.0(+0x7ea5) [0x7f9b537c1ea5]  
/lib64/libc.so.6(clone+0x6d) [0x7f9b51b0ab2d]

Trying to get some variables.  
Some pointers may be invalid and cause the dump to abort.  
Query (0): Connection ID (thread ID): 4674  
Status: NOT\_KILLED

---

<div class="post-metadata">

**Author:** ![Marcelo\_Altmann](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/marcelo_altmann/32/11299_2.png) [@Marcelo\_Altmann](https://forums.percona.com/u/Marcelo_Altmann)\
**Post date:** [February 27, 2023, 11:00am UTC](https://forums.percona.com/t/mysql-db-crashing/20316/2 "2023-02-27T11:00:56Z")

</div>

Hi @Anisha .

It seems that you are been affected by [[PS-8589] Crashing with signal 11 - Percona JIRA](https://jira.percona.com/browse/PS-8589) .  
Please upgrade to Percona Server for MySQL 8.0.31-23.

---

<div class="post-metadata">

**Author:** ![Anisha](https://avatars.discourse-cdn.com/v4/letter/a/8dc957/32.png) [@Anisha](https://forums.percona.com/u/Anisha)\
**Post date:** [February 27, 2023, 11:09am UTC](https://forums.percona.com/t/mysql-db-crashing/20316/3 "2023-02-27T11:09:44Z")

</div>

Hi @Marcelo_Altmann ,

Is this known issue in 8.0.30 version ?

---

<div class="post-metadata">

**Author:** ![Anisha](https://avatars.discourse-cdn.com/v4/letter/a/8dc957/32.png) [@Anisha](https://forums.percona.com/u/Anisha)\
**Post date:** [February 27, 2023, 11:17am UTC](https://forums.percona.com/t/mysql-db-crashing/20316/4 "2023-02-27T11:17:20Z")

</div>

Provided [[PS-8589] Crashing with signal 11 - Percona JIRA](https://jira.percona.com/browse/PS-8589) .  
is of replica crash.

Here my Primary database is crashing due to mentioned error.

Can you confirm if it is applicable here too ?

---

<div class="post-metadata">

**Author:** ![Marcelo\_Altmann](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/marcelo_altmann/32/11299_2.png) [@Marcelo\_Altmann](https://forums.percona.com/u/Marcelo_Altmann)\
**Post date:** [February 27, 2023, 1:58pm UTC](https://forums.percona.com/t/mysql-db-crashing/20316/5 "2023-02-27T13:58:19Z")

</div>

Yes it happens on source server too.
