maria-discuss team mailing list archive

[Sergei Golubchik <serg@xxxxxxxxxxx>]

Hi, Tom!

On Sep 06, Tom Ryan wrote:
> 
> Sep 6 14:37:59 node-2 mysqld[1846]: stack_bottom = 0x7f3271446dd8 thread_stack 0x49000
> Sep 6 14:37:59 node-2 mysqld[1846]: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x5644f71dcf4e]
> Sep 6 14:37:59 node-2 mysqld[1846]: /usr/sbin/mysqld(handle_fatal_signal+0x307)[0x5644f6c70b07]
> Sep 6 14:37:59 node-2 mysqld[1846]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7f33e141d890]
> Sep 6 14:37:59 node-2 mysqld[1846]: /usr/sbin/mysqld(handler_index_cond_check+0x8d)[0x5644f6c7b1fd]
> Sep 6 14:37:59 node-2 mysqld[1846]: /usr/sbin/mysqld(+0x566623)[0x5644f6973623]
> Sep 6 14:37:59 node-2 mysqld[1846]: /usr/sbin/mysqld(+0xbb4ba8)[0x5644f6fc1ba8]

This looks truncated. Could you post a complete stack trace please?

And please tell exactly what binaries you're using. Version,
architecture, Linux distribution.

> This is getting old and is unlike our usual mariadb experience.
> 
> Looking at the jira for 10.4.8, it appears to fix many problems in
> 10.4 and I'm hopeful it solves this.
> 
> In the meantime, any ideas or suggestions for things to look for?

10.4.8 should be out any day now. But if I'd know more about the crash,
I could tell whether it's fixed there or not.

Regards,
Sergei