Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 658550

Summary: net-analyzer/nagios-check_mysql_health with =dev-db/mariadb-10.1.33-r1: runtime segfault
Product: Gentoo Linux Reporter: Tomáš Mózes <hydrapolic>
Component: Current packagesAssignee: Michael Orlitzky <mjo>
Status: RESOLVED FIXED    
Severity: normal CC: covici, mysql-bugs
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
See Also: https://bugs.gentoo.org/show_bug.cgi?id=666960
Whiteboard:
Package list:
Runtime testing required: ---

Description Tomáš Mózes 2018-06-20 06:21:19 UTC
After upgrading to mariadb 10.1.33-r1, the mysql health check scripts segfaults:

# /usr/lib/nagios/plugins/check_mysql_health --socket /var/run/mysqld/mysqld.sock --mode bufferpool-hitrate 
OK - innodb buffer pool hitrate at 99.80% | bufferpool_hitrate=99.80%;98:;95:;0;100 bufferpool_hitrate_now=100.00%
Segmentation fault

# dmesg
[517917.051223] check_mysql_hea[25427]: segfault at 981b3e9ea8 ip 00007f48855922c9 sp 00007ffe6a100c90 error 4 in libmysqlclient.so.18.4.0[7f4885554000+34a000]
[517918.755398] check_mysql_sel[25442]: segfault at 1e37fd6288 ip 00007fdbdb4542c9 sp 00007fff843bf9a0 error 4 in libmysqlclient.so.18.4.0[7fdbdb416000+34a000]
[517919.276654] check_mysql_hea[25447]: segfault at 80f269d778 ip 00007fec607612c9 sp 00007ffcfb659840 error 4 in libmysqlclient.so.18.4.0[7fec60723000+34a000]
[517923.032301] check_mysql_sel[25503]: segfault at f566543218 ip 00007efe87b262c9 sp 00007fff84b25270 error 4 in libmysqlclient.so.18.4.0[7efe87ae8000+34a000]
[517923.087334] check_mysql_con[25537]: segfault at 6888a6c828 ip 00007f1e9211b2c9 sp 00007ffd60f464b0 error 4 in libmysqlclient.so.18.4.0[7f1e920dd000+34a000]
[517923.126697] check_mysql_hea[25492]: segfault at 60b432ca88 ip 00007fabe22b32c9 sp 00007ffec796e790 error 4 in libmysqlclient.so.18.4.0[7fabe2275000+34a000]
[517923.564266] check_mysql_hea[25547]: segfault at 45babd8a88 ip 00007ff8f023e2c9 sp 00007fff9e3b5a30 error 4 in libmysqlclient.so.18.4.0[7ff8f0200000+34a000]
[517923.652945] check_mysql_com[25669]: segfault at d5325c10e8 ip 00007f826c9862c9 sp 00007ffeb0219080 error 4 in libmysqlclient.so.18.4.0[7f826c948000+34a000]
[517923.708860] check_mysql_hea[25687]: segfault at c1819e1438 ip 00007f25783ae2c9 sp 00007ffefd318250 error 4 in libmysqlclient.so.18.4.0[7f2578370000+34a000]
Comment 1 Brian Evans (RETIRED) gentoo-dev 2018-06-20 12:41:03 UTC
mariadb 10.1.33-r1 does not provided client libraries.  Instead this is shifted to mysql-connector-c.

Did you run revdep-rebuild on libmysqlclient?  The libs are not 100% ABI compatible.
Comment 2 Tomáš Mózes 2018-06-21 06:28:32 UTC
(In reply to Brian Evans from comment #1)
> mariadb 10.1.33-r1 does not provided client libraries.  Instead this is
> shifted to mysql-connector-c.
> 
> Did you run revdep-rebuild on libmysqlclient?  The libs are not 100% ABI
> compatible.

Rebuilding net-analyzer/nagios-check_mysql_health didn't help, but after checking the deps and rebuilding dev-perl/DBD-mysql it works properly now.

Maybe we should add a note about this change?
Comment 3 Brian Evans (RETIRED) gentoo-dev 2018-06-21 12:24:02 UTC
(In reply to Tomáš Mózes from comment #2)
> (In reply to Brian Evans from comment #1)
> > mariadb 10.1.33-r1 does not provided client libraries.  Instead this is
> > shifted to mysql-connector-c.
> > 
> > Did you run revdep-rebuild on libmysqlclient?  The libs are not 100% ABI
> > compatible.
> 
> Rebuilding net-analyzer/nagios-check_mysql_health didn't help, but after
> checking the deps and rebuilding dev-perl/DBD-mysql it works properly now.
> 
> Maybe we should add a note about this change?

There is a note, however the dependency order was not correct and mysql-connector-c has to be scheduled first.  Once I get everything set in ~arch, I'll write up a news article.

MariaDB 10.1.34 has the order corrected for others who install.
Comment 4 Tomáš Mózes 2018-06-21 14:14:29 UTC
Thank you very much!
Comment 5 Brian Evans (RETIRED) gentoo-dev 2018-06-24 21:59:58 UTC
*** Bug 659020 has been marked as a duplicate of this bug. ***
Comment 6 John Covici 2018-06-24 23:33:22 UTC
Worked for me with MySQL-5.7.22 -- wish I had known of this earlier -- wasted lots of time with this one.