# Mysqld got signal 11 MySQL 5.7

**URL:** https://forums.percona.com/t/mysqld-got-signal-11-mysql-5-7/22854
**Category:** Percona XtraDB Cluster 5.x
**Created:** [June 15, 2023, 4:36pm UTC](https://forums.percona.com/t/mysqld-got-signal-11-mysql-5-7/22854 "2023-06-15T16:36:58Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![nublaii](https://avatars.discourse-cdn.com/v4/letter/n/a9a28c/32.png) [@nublaii](https://forums.percona.com/u/nublaii)
#### Post date: [June 21, 2023, 7:38pm UTC](https://forums.percona.com/t/mysqld-got-signal-11-mysql-5-7/22854/5 "2023-06-21T19:38:04Z")

</div>

> [@Cluster dies after update with signal 11 error](https://forums.percona.com/t/cluster-dies-after-update-with-signal-11-error/19836):
>
> We just upgraded a small cluster (2 nodes + 1 garbd) from 5.7.39-31.61-1.focal to 5.7.40-31.63-1.focal. We are running ubuntu 20.04, all OS packages up to date. After the update we’ve had the cluster die on us twice y 4 days. On both occasions the error was the same: First one of the nodes dies suddently with a signal 11 11:59:46 UTC - mysqld got signal 11 ; 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, im…

Sounds familiar…

---

_[View the full topic](https://forums.percona.com/t/mysqld-got-signal-11-mysql-5-7/22854)._