Dear piler users,
it appears that 0.1.24 has some issues on platforms, eg. on centos.
I'd like to share my latest findings to help you resolving this
showstopper problem.
I used the latest master branch which has only some minor bugfixes
over the final 0.1.24 (they are basically the same from the point
of this problem).
#1: I installed a centos 6.4 x64 box, with stock 5.1 mysql packages
from
centos. Both piler daemon and pilerget work as expected, no segfaults,
etc.
#2: Then I removed the mysql 5.1 packages, downloaded 5.5.34 rpms from
the dev.mysql.com site, recompiled piler, then right after starting it
I experienced a segfault. According to the syslog files the problem
occured in the libmysqlclient.so.18.0.0 library (from mysql 5.5.34):
centos kernel: piler[7579]: segfault at 118 ip 00007f83545efeb2 sp
00007fffa3d10620 error 4 in
libmysqlclient.so.18.0.0[7f83545c0000+2d9000]
I believe that there must be something wrong with the mysql library
5.5.34
int the rpm package. The code is unchanged and it works with mysql 5.1,
but
fails with 5.5.34.
Note that I use 5.5.x without any problem on other platforms, eg.
percona-5.5.27
on slackware 32 bit without any issues (ok, it's a bit different than
the stock
mysql from oracle).
So if you have centos 6.x I recommend you either to stick to the stock
mysql
packages (=5.1.x at this time), or if you need the features of mysql
5.5.x,
then download the mariadb client library
(https://downloads.mariadb.org/client-native/1.0.0/).
In this case use the latest master branch as it has support for the
mariadb library.
To enable it instead of specifying --with-database=mysql use
--with-database=mariadb
Best regards,
Janos
