mysql.i386

CiViX · Unread post by **CiViX** » Sun Dec 16, 2007 8:27 am

My CentOS 5 (x86_64) comes with mysql 5.0.22, but this version has a bug which makes vBulletin crash it all the time, see:

http://bugs.mysql.com/bug.php?id=20260

ART has mysql 5.0.51 which eliminates the vBulletin-problem, but I can't find a mysql.i386-package for this release, which I need.

Do you have such a package, or is there another solution?

Unread post by **scott** » Sun Dec 16, 2007 11:25 am

you want to use the x86_64 build if you're running on an x86_64 box.

CiViX · Unread post by **CiViX** » Sun Dec 16, 2007 11:48 am

Yes, but 4PSA Spam Guardian needs the mysql.i386 in addition to the x86_64-packages to work... The original 5.0.22-packages from CentOS have alle mysql-packages as x86_64, but in addition they have a mysql.i386, probably something to do with compatibility?

[root@web3 conf]# rpm -qa --qf="%{n}-%{v}-%{r}.%{arch}.rpm\n" mysql*
mysql-5.0.22-2.1.0.1.x86_64.rpm
mysql-server-5.0.22-2.1.0.1.x86_64.rpm
mysql-devel-5.0.22-2.1.0.1.i386.rpm
mysql-5.0.22-2.1.0.1.i386.rpm
mysql-devel-5.0.22-2.1.0.1.x86_64.rpm

And a "yum list mysql" gives me:

Installed Packages
mysql.x86_64 5.0.22-2.1.0.1 installed
mysql.i386 5.0.22-2.1.0.1 installed
Available Packages
mysql.x86_64 5.0.51-1.el5.art atomic

So I need this mysql.i386 for you 5.0.51-package. Does that clarify my problem?

Unread post by **scott** » Sun Dec 16, 2007 1:19 pm

Wow, Im shocked that they would do that. They usually do a better job than that. Basically they're forcing you to use a compatibility library because they dont support x86_64.

Yes you might be able to do that with the i386 package, but thats certainly not the optimal configuration. Not your fault though, you're stuck with someone elses design.

CiViX · Unread post by **CiViX** » Sun Dec 16, 2007 6:11 pm

I updated mysql to your 5.0.51 packages. But if I now try to (re)install 4PSA Spam Guardian I get the following errors:

Code: Select all

===> Applying settings to SpamAssassin installation ...
/usr/local/psa/admin/bin/sa_conf: error while loading shared libraries: libmysqlclient.so.15: cannot open shared object file: No such file or directory
/usr/local/psa/admin/sbin/insert_sguardian: error while loading shared libraries: libmysqlclient.so.15: cannot open shared object file: No such file or directory
Error applying settings to SpamAssassin

You said:

Yes you might be able to do that with the i386 package, but thats certainly not the optimal configuration.

What do you mean by that? Should I also install the mysql-5.0.51-1.el5.art.i386.rpm from you repository? If I try that I get:

Code: Select all

error: Failed dependencies:
        libmysqlclient.so.15 is needed by mysql-5.0.51-1.el5.art.i386
        libmysqlclient.so.15(libmysqlclient_15) is needed by mysql-5.0.51-1.el5.art.i386
        libmysqlclient.so.15 is needed by mysql-devel-5.0.51-1.el5.art.i386
        libmysqlclient_r.so.15 is needed by mysql-devel-5.0.51-1.el5.art.i386
        libndbclient.so.2 is needed by mysql-devel-5.0.51-1.el5.art.i386

I don't want to force-install it without knowing if it will break something...?

Unread post by **scott** » Sun Dec 16, 2007 8:56 pm

I would let 4PSA know, since this is a problem with their code

Troy McClure · Unread post by **Troy McClure** » Mon Dec 17, 2007 3:15 pm

Yep, I had this same issue with Total Backup. I had to contact tech support and they had to have access to my box to get it installed. After that, I looked to see what they had installed and it was a bunch of i386 compatibility packages. I have since ditched the program and just do my own backups.