On 09/20 11:13, Sebastian Reitenbach wrote: > > On Saturday, September 20, 2014 20:53 CEST, Jeremy Evans <jer...@openbsd.org> > wrote: > > > On 09/20 07:30, Sebastian Reitenbach wrote: > > > Hi, > > > > > > upgraded my puppet server from short before mysql->mariadb switch, > > > running on i386,, and there I have to run: > > > > > > I'm having puppet-dashboard running on that host, which uses mysql > > > database. > > > cd /var/www/puppet-dashboard && sudo -u _puppet-dashboard rake18 > > > RAILS_ENV=production db:migrate --trace > > > > If I had to guess, this is because in the change from mysql -> mariadb, > > libmysqlclient now depends on libpthread. As ruby 1.8 doesn't link with > > libpthread, you need to use LD_PRELOAD=libpthread.so when running ruby > > 1.8 if you want to load any ruby extension that links with > > libmysqlclient. > > You seem to be right, using LD_PRELOAD indeed helps. > Now is the question, how this is fixed best, generally in ruby18, > or would it be enough to link ruby-mysql against libpthread?
If you want to not have to use LD_PRELOAD, you have to link the executable against libpthread, not the extension file. I don't think that's appropriate, considering the current status of ruby 1.8. A better fix to your issue is upgrading puppet-dashboard to support ruby 1.9+. A fork exists that supposedly has ruby 1.9+ compatibility: https://github.com/sodabrew/puppet-dashboard Thanks, Jeremy
