# Mysqld crash on 8.0.30 **URL:** \ **Category:** Percona Server for MySQL\ **Created:** [January 11, 2023, 6:07pm UTC](https://forums.percona.com/t/mysqld-crash-on-8-0-30/19574 "2023-01-11T18:07:42Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Chanakya](https://avatars.discourse-cdn.com/v4/letter/c/cab0a1/32.png) [@Chanakya](https://forums.percona.com/u/Chanakya)\ **Post date:** [January 11, 2023, 6:07pm UTC](https://forums.percona.com/t/mysqld-crash-on-8-0-30/19574/1 "2023-01-11T18:07:42Z")
Hi, We are seeing constant database crash with the following error: 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: 0x7fef6c4dd000 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 = 7fef44afcbb0 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(+0xf680) [0x7ff2722ad680] /home/mysqld/sys/8.0.30\_percona/bin/mysqld(PTI\_expr\_with\_alias::itemize(Parse\_context\*, Item\*\*)+0x35) [0x12e4455] /home/mysqld/sys/8.0.30\_percona/bin/mysqld(PT\_select\_item\_list::contextualize(Parse\_context\*)+0x7e) [0xea328e] /home/mysqld/sys/8.0.30\_percona/bin/mysqld(PT\_query\_specification::contextualize(Parse\_context\*)+0x91) [0xea2c21] /home/mysqld/sys/8.0.30\_percona/bin/mysqld(PT\_query\_expression::contextualize(Parse\_context\*)+0x93) [0xea1313] /home/mysqld/sys/8.0.30\_percona/bin/mysqld(PT\_select\_stmt::make\_cmd(THD\*)+0x57) [0xe9acc7] /home/mysqld/sys/8.0.30\_percona/bin/mysqld(LEX::make\_sql\_cmd(Parse\_tree\_root\*)+0x27) [0xf9e157] /home/mysqld/sys/8.0.30\_percona/bin/mysqld(THD::sql\_parser()+0x5a) [0xf43f8a] /home/mysqld/sys/8.0.30\_percona/bin/mysqld(parse\_sql(THD\*, Parser\_state\*, Object\_creation\_ctx\*)+0x127) [0xfc3f77] /home/mysqld/sys/8.0.30\_percona/bin/mysqld(dispatch\_sql\_command(THD\*, Parser\_state\*, bool)+0x2ed) [0xfc904d] /home/mysqld/sys/8.0.30\_percona/bin/mysqld(dispatch\_command(THD\*, COM\_DATA const\*, enum\_server\_command)+0x21dc) [0xfcb9cc] /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(+0x7dd5) [0x7ff2722a5dd5] /lib64/libc.so.6(clone+0x6d) [0x7ff2705f0b3d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (7fef6c477030): SELECT task\_instance.try\_number AS task\_instance\_try\_number, task\_instance.task\_id AS task\_instance\_task\_id, task\_instance.dag\_id AS task\_instance\_dag\_id, task\_instance.run\_id AS task\_instance\_run\_id, task\_instance.map\_index AS task\_instance\_map\_index, task\_instance.start\_date AS task\_instance\_start\_date, task\_instance.end\_date AS task\_instance\_end\_date, task\_instance.duration AS task\_instance\_duration, task\_instance.state AS task\_instance\_state, task\_instance.max\_tries AS task\_instance\_max\_tries, task\_instance.hostname AS task\_instance\_hostname, task\_instance.unixname AS task\_instance\_unixname, task\_instance.job\_id AS task\_instance\_job\_id, task\_instance.pool AS task\_instance\_pool, task\_instance.pool\_slots AS task\_instance\_pool\_slots, task\_instance.queue AS task\_instance\_queue, task\_instance.priority\_weight AS task\_instance\_priority\_weight, task\_instance.operator AS task\_instance\_operator, task\_instance.queued\_dttm AS task\_instance\_queued\_dttm, task\_instance.queued\_by\_job\_id AS task\_instance\_queued\_by\_job\_id, Connection ID (thread ID): 5703208 Status: NOT\_KILLED Please help a workaround. Thanks in advance! ---
**Author:** ![Abhinav\_Gupta](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/abhinav_gupta/32/6262_2.png) [@Abhinav\_Gupta](https://forums.percona.com/u/Abhinav_Gupta)\ **Post date:** [January 12, 2023, 8:53am UTC](https://forums.percona.com/t/mysqld-crash-on-8-0-30/19574/2 "2023-01-12T08:53:50Z")
Try to rebuild the tables (either using ALTER or mydumper/myloader) for all the associated tables which are part of the reported SELECT query. ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [January 12, 2023, 2:29pm UTC](https://forums.percona.com/t/mysqld-crash-on-8-0-30/19574/3 "2023-01-12T14:29:24Z")
@Chanakya In the error message you show, I see this `PTI_expr_with_alias::itemize` as the top line in the backtrace. Can you please execute your SQL but remove all ‘AS’ parts? Execute the query without any aliases. Does that work? If so, put back only 1 ‘AS’ and repeat. Keep doing this until you crash again. Then remove 1 ‘AS’. Does that work? This might be a memory allocation error with too many ‘AS’ parts. ---
**Author:** ![Chanakya](https://avatars.discourse-cdn.com/v4/letter/c/cab0a1/32.png) [@Chanakya](https://forums.percona.com/u/Chanakya)\ **Post date:** [January 12, 2023, 3:16pm UTC](https://forums.percona.com/t/mysqld-crash-on-8-0-30/19574/4 "2023-01-12T15:16:40Z")
@matthewb Here there is no alias, but rest of the error is same. /home/mysqld/sys/8.0.30\_percona/bin/mysqld(PT\_select\_item\_list::contextualize(Parse\_context\*)+0x7b) [0xea328b] /home/mysqld/sys/8.0.30\_percona/bin/mysqld(PT\_query\_specification::contextualize(Parse\_context\*)+0x91) [0xea2c21] /home/mysqld/sys/8.0.30\_percona/bin/mysqld(PT\_query\_expression::contextualize(Parse\_context\*)+0x93) [0xea1313] /home/mysqld/sys/8.0.30\_percona/bin/mysqld(PT\_select\_stmt::make\_cmd(THD\*)+0x57) [0xe9acc7] /home/mysqld/sys/8.0.30\_percona/bin/mysqld(LEX::make\_sql\_cmd(Parse\_tree\_root\*)+0x27) [0xf9e157] /home/mysqld/sys/8.0.30\_percona/bin/mysqld(THD::sql\_parser()+0x5a) [0xf43f8a] /home/mysqld/sys/8.0.30\_percona/bin/mysqld(parse\_sql(THD\*, Parser\_state\*, Object\_creation\_ctx\*)+0x127) [0xfc3f77] /home/mysqld/sys/8.0.30\_percona/bin/mysqld(dispatch\_sql\_command(THD\*, Parser\_state\*, bool)+0x2ed) [0xfc904d] /home/mysqld/sys/8.0.30\_percona/bin/mysqld(dispatch\_command(THD\*, COM\_DATA const\*, enum\_server\_command)+0x21dc) [0xfcb9cc] /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) [0x7fb7b372aea5] /lib64/libc.so.6(clone+0x6d) [0x7fb7b1a73b2d] ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [January 12, 2023, 3:23pm UTC](https://forums.percona.com/t/mysqld-crash-on-8-0-30/19574/5 "2023-01-12T15:23:09Z")
Can you provide the entire query please? ---
**Author:** ![Chanakya](https://avatars.discourse-cdn.com/v4/letter/c/cab0a1/32.png) [@Chanakya](https://forums.percona.com/u/Chanakya)\ **Post date:** [January 12, 2023, 3:31pm UTC](https://forums.percona.com/t/mysqld-crash-on-8-0-30/19574/6 "2023-01-12T15:31:08Z")
SELECT task\_instance.try\_number AS task\_instance\_try\_number, task\_instance.task\_id AS task\_instance\_task\_id, task\_instance.dag\_id AS task\_instance\_dag\_id, task\_instance.run\_id AS task\_instance\_run\_id, task\_instance.start\_date AS task\_instance\_start\_date, task\_instance.end\_date AS task\_instance\_end\_date, task\_instance.duration AS task\_instance\_duration, task\_instance.state AS task\_instance\_state, task\_instance.max\_tries AS task\_instance\_max\_tries, task\_instance.hostname AS task\_instance\_hostname, task\_instance.unixname AS task\_instance\_unixname, task\_instance.job\_id AS task\_instance\_job\_id, task\_instance.pool AS task\_instance\_pool, task\_instance.pool\_slots AS task\_instance\_pool\_slots, task\_instance.queue AS task\_instance\_queue, task\_instance.priority\_weight AS task\_instance\_priority\_weight, task\_instance.operator AS task\_instance\_operator, task\_instance.queued\_dttm AS task\_instance\_queued\_dttm, task\_instance.queued\_by\_job\_id AS task\_instance\_queued\_by\_job\_id, task\_instance.pid AS task\_instance\_pid, task\_instance.executor\_config AS task\_instance\_executor\_config, task\_instance.external\_executor\_id AS task\_instance\_external\_executor\_id, task\_instance.trigger\_id AS task\_instance\_trigger\_id, task\_instance.trigger\_timeout AS task\_instance\_trigger\_timeout, task\_instance.next\_method AS task\_instance\_next\_method, task\_instance.next\_kwargs AS task\_instance\_next\_kwargs, dag\_run\_1.state AS dag\_run\_1\_state, [dag\_run\_1.id](http://dag_run_1.id/) AS dag\_run\_1\_id, dag\_run\_1.dag\_id AS dag\_run\_1\_dag\_id, dag\_run\_1.queued\_at AS dag\_run\_1\_queued\_at, dag\_run\_1.execution\_date AS dag\_run\_1\_execution\_date, dag\_run\_1.start\_date AS dag\_run\_1\_start\_date, dag\_run\_1.end\_date AS dag\_run\_1\_end\_date, dag\_run\_1.run\_id AS dag\_run\_1\_run\_id, dag\_run\_1.creating\_job\_id AS dag\_run\_1\_creating\_job\_id, dag\_run\_1.external\_trigger AS dag\_run\_1\_external\_trigger, dag\_run\_1.run\_type AS dag\_run\_1\_run\_type, dag\_run\_1.conf AS dag\_run\_1\_conf, dag\_run\_1.data\_interval\_start AS dag\_run\_1\_data\_interval\_start, dag\_run\_1.data\_interval\_end AS dag\_run\_1\_data\_interval\_end, dag\_run\_1.last\_scheduling\_decision AS dag\_run\_1\_last\_scheduling\_decision, dag\_run\_1.dag\_hash AS dag\_run\_1\_dag\_hash FROM task\_instance INNER JOIN dag\_run ON dag\_run.dag\_id = task\_instance.dag\_id AND dag\_run.run\_id = task\_instance.run\_id INNER JOIN dag ON task\_instance.dag\_id = dag.dag\_id INNER JOIN dag\_run AS dag\_run\_1 ON dag\_run\_1.dag\_id = task\_instance.dag\_id AND dag\_run\_1.run\_id = task\_instance.run\_id WHERE dag\_run.run\_type != ‘backfill’ AND dag\_run.state != ‘queued’ AND dag.is\_paused = 0 AND task\_instance.state = ‘scheduled’ ORDER BY -task\_instance.priority\_weight, dag\_run.execution\_date LIMIT 36 FOR UPDATE OF task\_instance SKIP LOCKED; ---
**Author:** ![Chanakya](https://avatars.discourse-cdn.com/v4/letter/c/cab0a1/32.png) [@Chanakya](https://forums.percona.com/u/Chanakya)\ **Post date:** [January 12, 2023, 3:32pm UTC](https://forums.percona.com/t/mysqld-crash-on-8-0-30/19574/7 "2023-01-12T15:32:38Z")
Tried it… 🤞 Thank you ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [January 12, 2023, 3:34pm UTC](https://forums.percona.com/t/mysqld-crash-on-8-0-30/19574/8 "2023-01-12T15:34:13Z")
> [@Chanakya](#): > > task\_instance.try\_number AS task\_instance\_try\_number, You said you removed all the aliases, yet there is an alias on just about every column. Please remove all aliases and try the query again. ---
**Author:** ![Chanakya](https://avatars.discourse-cdn.com/v4/letter/c/cab0a1/32.png) [@Chanakya](https://forums.percona.com/u/Chanakya)\ **Post date:** [January 12, 2023, 3:42pm UTC](https://forums.percona.com/t/mysqld-crash-on-8-0-30/19574/9 "2023-01-12T15:42:16Z")
Unfortunately App has no control over the query to modify ☹ Server has abundant memory, is there any parameter that I can tweak to get away from constant crashes ? Also, it started happening in 8.0.30 after upgrading from 8.0.23 ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [January 12, 2023, 3:44pm UTC](https://forums.percona.com/t/mysqld-crash-on-8-0-30/19574/10 "2023-01-12T15:44:39Z")
Run the query manually, first with aliases then without aliases. When you run it manually, does it crash? ---
**Author:** ![Sanjay\_Sheoran](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sanjay_sheoran/32/5351_2.png) [@Sanjay\_Sheoran](https://forums.percona.com/u/Sanjay_Sheoran)\ **Post date:** [January 12, 2023, 4:51pm UTC](https://forums.percona.com/t/mysqld-crash-on-8-0-30/19574/11 "2023-01-12T16:51:42Z")
We tried running manually as it is but its not crashing the DB , seems certain data set is causing the DB crash , the data in these tables is very dynamic as this is airflow backend database Any other suggestion to debug this issue furhert ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [January 12, 2023, 6:38pm UTC](https://forums.percona.com/t/mysqld-crash-on-8-0-30/19574/12 "2023-01-12T18:38:16Z")
Without a repeatable test case, it is hard to debug. I suggest you keep trying the query manually without aliases to see if that is the cause. ---
**Author:** ![Sanjay\_Sheoran](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sanjay_sheoran/32/5351_2.png) [@Sanjay\_Sheoran](https://forums.percona.com/u/Sanjay_Sheoran)\ **Post date:** [January 12, 2023, 7:04pm UTC](https://forums.percona.com/t/mysqld-crash-on-8-0-30/19574/13 "2023-01-12T19:04:27Z")
any known bug around this issue ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [January 12, 2023, 10:17pm UTC](https://forums.percona.com/t/mysqld-crash-on-8-0-30/19574/14 "2023-01-12T22:17:25Z")
You can search here: [https://bugs.mysql.com](https://bugs.mysql.com) ---
**Author:** ![Sanjay\_Sheoran](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sanjay_sheoran/32/5351_2.png) [@Sanjay\_Sheoran](https://forums.percona.com/u/Sanjay_Sheoran)\ **Post date:** [January 12, 2023, 11:05pm UTC](https://forums.percona.com/t/mysqld-crash-on-8-0-30/19574/15 "2023-01-12T23:05:36Z")
we could not find out, do you know any bug for this issue ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [January 13, 2023, 2:35am UTC](https://forums.percona.com/t/mysqld-crash-on-8-0-30/19574/16 "2023-01-13T02:35:33Z")
If you found none on [mysql.com](http://mysql.com) then there’s none reported. You will need a repeatable test case to submit a bug report. You also need to identify the specific version where things stopped working. Roll back to 8.0.23 and confirm there are no issues. Then upgrade to 8.0.24 and check. If no crashes, upgrade to 8.0.25, etc. Doing this will help narrow down when the change to MySQL took place that is affecting your query. ---
**Author:** ![Sanjay\_Sheoran](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sanjay_sheoran/32/5351_2.png) [@Sanjay\_Sheoran](https://forums.percona.com/u/Sanjay_Sheoran)\ **Post date:** [January 13, 2023, 6:00am UTC](https://forums.percona.com/t/mysqld-crash-on-8-0-30/19574/17 "2023-01-13T06:00:09Z")
is it safe to rollback from 8.0.30 to 8.0.23 and if yes, do you have steps ---
**Author:** ![Ankit\_Kapoor1](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ankit_kapoor1/32/8977_2.png) [@Ankit\_Kapoor1](https://forums.percona.com/u/Ankit_Kapoor1)\ **Post date:** [January 13, 2023, 11:06am UTC](https://forums.percona.com/t/mysqld-crash-on-8-0-30/19574/18 "2023-01-13T11:06:33Z")
Hi @Sanjay_Sheoran , Thanks for reaching out. In addition to what my colleagues has responded, please allow me to share my views on this. What I understand is that this particular query ( one you pasted, when being executed from application server ) is crashing your mysql server but when being executed manually, there is no crash . Also, this started post mysql upgradation to 8.0.30. I also understand that you have no control over application server to modify this query. Do you see any corruption related errors in your error log ? Also, have you started facing these crashes post upgradation or after some days of upgradation ? Is there any other query of this table as well being executed from app server ? ---
**Author:** ![Soumyaranjan\_Sahani](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/soumyaranjan_sahani/32/3575_2.png) [@Soumyaranjan\_Sahani](https://forums.percona.com/u/Soumyaranjan_Sahani)\ **Post date:** [January 15, 2023, 6:50am UTC](https://forums.percona.com/t/mysqld-crash-on-8-0-30/19574/19 "2023-01-15T06:50:12Z")
Hi @Ankit_Kapoor1 Yes, Your understanding is correct. We don’t see any corruption related error on error log. Yes Post upgradation to 8.0.30, we are seeing these crashes. ---
**Author:** ![pedapudi\_anisha](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/pedapudi_anisha/32/9011_2.png) [@pedapudi\_anisha](https://forums.percona.com/u/pedapudi_anisha)\ **Post date:** [January 16, 2023, 4:39am UTC](https://forums.percona.com/t/mysqld-crash-on-8-0-30/19574/20 "2023-01-16T04:39:50Z")
hi @Ankit_Kapoor1 Do you have any suggestions in mitigating this issue . [Next page](https://forums.percona.com/t/mysqld-crash-on-8-0-30/19574.md?page=2)