# pt-online-schema-change cause mysqld restart

**URL:** <https://forums.percona.com/t/pt-online-schema-change-cause-mysqld-restart/6933>\
**Category:** Percona Toolkit\
**Created:** [March 28, 2019, 4:11am UTC](https://forums.percona.com/t/pt-online-schema-change-cause-mysqld-restart/6933 "2019-03-28T04:11:01Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![peng19832](https://avatars.discourse-cdn.com/v4/letter/p/7993a0/32.png) [@peng19832](https://forums.percona.com/u/peng19832)\
**Post date:** [March 28, 2019, 4:11am UTC](https://forums.percona.com/t/pt-online-schema-change-cause-mysqld-restart/6933/1 "2019-03-28T04:11:01Z")

</div>

environment：  
OS：Red Hat Enterprise Linux Server release 6.5 (Santiago)  
MySQL version：5.7.22  
Questions：I use pt-online-schema-change to cause the mysqld service to restart when adding an index in a table with 50 million records.

[mysqld.err.txt](https://forums.percona.com/uploads/short-url/qXa3fKjtKgaMbRiH8MUppwEuinJ.txt) (43 KB)

 ![crash-log.png](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/2X/a/a80a67da654dbc23896062173c2517f5623e5e17.png)

 ![crash-sql.png](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/2X/2/2f388e376386e43fe33cb18892b88a8a789afa7a.png)

---

<div class="post-metadata">

**Author:** ![peng19832](https://avatars.discourse-cdn.com/v4/letter/p/7993a0/32.png) [@peng19832](https://forums.percona.com/u/peng19832)\
**Post date:** [April 17, 2019, 3:28am UTC](https://forums.percona.com/t/pt-online-schema-change-cause-mysqld-restart/6933/2 "2019-04-17T03:28:45Z")

</div>

Someone has encountered this situation or how to solve it.

---

<div class="post-metadata">

**Author:** ![carlos.salguero](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/carlos.salguero/32/20_2.png) [@carlos.salguero](https://forums.percona.com/u/carlos.salguero)\
**Post date:** [April 17, 2019, 5:35am UTC](https://forums.percona.com/t/pt-online-schema-change-cause-mysqld-restart/6933/3 "2019-04-17T05:35:20Z")

</div>

Hello,

pt-online-schema-change runs regular queries (in a complex sequence, I know) so it shouldn’t cause MySQL to crash.  
From the attached error log I see this:

```auto
019-03-28T08:09:24.905320Z 0 [ERROR] Function 'validate_password' already exists
2019-03-28T08:09:24.905374Z 0 [ERROR] Couldn't load plugin named 'validate_password' with soname 'validate_password.so'.
2019-03-28T08:09:24.925899Z 0 [ERROR] Function 'validate_password' already exists
2019-03-28T08:09:24.925967Z 0 [Warning] Couldn't load plugin named 'validate_password' with soname 'validate_password.so'.
2019-03-28T08:09:24.926381Z 0 [Warning] Plugin validate_password reported: 'Dictionary file not specified'

```

and more: at the beginning of the error log it says signal 11. That’s a MySQL internal error.

```auto
08:07:45 UTC - mysqld got signal 11 ;

```

I only saw a similar error on MySQL 8 having empty users and roles and that was causing a different program ([minimum\_permissions](https://github.com/Percona-Lab/minimum_permissions)) to fail after MySQL crashed with a signal 11.  
Could you verify that there are no invalid/empty users in your db?

Regards

---

<div class="post-metadata">

**Author:** ![peng19832](https://avatars.discourse-cdn.com/v4/letter/p/7993a0/32.png) [@peng19832](https://forums.percona.com/u/peng19832)\
**Post date:** [April 19, 2019, 4:10am UTC](https://forums.percona.com/t/pt-online-schema-change-cause-mysqld-restart/6933/4 "2019-04-19T04:10:32Z")

</div>

> [@carlos.salguero;53918](#):
>
> Hello,
> 
> pt-online-schema-change runs regular queries (in a complex sequence, I know) so it shouldn’t cause MySQL to crash.  
> From the attached error log I see this:
> 
> ```auto
> 019-03-28T08:09:24.905320Z 0 [ERROR] Function 'validate_password' already exists
> 2019-03-28T08:09:24.905374Z 0 [ERROR] Couldn't load plugin named 'validate_password' with soname 'validate_password.so'.
> 2019-03-28T08:09:24.925899Z 0 [ERROR] Function 'validate_password' already exists
> 2019-03-28T08:09:24.925967Z 0 [Warning] Couldn't load plugin named 'validate_password' with soname 'validate_password.so'.
> 2019-03-28T08:09:24.926381Z 0 [Warning] Plugin validate_password reported: 'Dictionary file not specified'
> 
> ```
> 
> and more: at the beginning of the error log it says signal 11. That’s a MySQL internal error.
> 
> ```auto
> 08:07:45 UTC - mysqld got signal 11 ;
> 
> ```
> 
> I only saw a similar error on MySQL 8 having empty users and roles and that was causing a different program ([minimum\_permissions](https://github.com/Percona-Lab/minimum_permissions)) to fail after MySQL crashed with a signal 11.  
> Could you verify that there are no invalid/empty users in your db?
> 
> Regards

Do these two have an impact?  
Can you post the page of the bug you mentioned,?  
Thank you.

| mysql.session | localhost | \*THISISNOTAVALIDPASSWORDTHATCANBEUSEDHERE |  
| mysql.sys | localhost | \*THISISNOTAVALIDPASSWORDTHATCANBEUSEDHERE |

---

<div class="post-metadata">

**Author:** ![carlos.salguero](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/carlos.salguero/32/20_2.png) [@carlos.salguero](https://forums.percona.com/u/carlos.salguero)\
**Post date:** [July 11, 2019, 6:35am UTC](https://forums.percona.com/t/pt-online-schema-change-cause-mysqld-restart/6933/5 "2019-07-11T06:35:47Z")

</div>

I cannot find the error reported to MySQL team, sorry.