starting ./directadmin - libmysqlclient.so.16 problem

[arboooz]

Hi,

as ive wrote in the topic, when i attempt to start directadmin service, i see this error:
error while loading shared libraries: libmysqlclient.so.16: cannot open shared object file
Ive found solution for simillar problem but it works only with libmysqlclient.so.15 file. what i supposed to do? install libmysqlclient-dev headers? or maybe reinstall whole app? What kind of data i will lost when i do reinstallation? Iam usining debian 64bits installation.

Please help
Cheers
Adam

[localhost]

Hi,

as ive wrote in the topic, when i attempt to start directadmin service, i see this error:
error while loading shared libraries: libmysqlclient.so.15: cannot open shared object file
Ive found solution for simillar problem but it works only with libmysqlclient.so.15 file. what i supposed to do? install libmysqlclient-dev headers? or maybe reinstall whole app? What kind of data i will lost when i do reinstallation? Iam usining debian 64bits installation.

Please help
Cheers
Adam

ln -s /usr/lib/libmysqlclient.so.16 /usr/lib64/libmysqlclient.so
ln -s /usr/lib64/libmysqlclient.so.15 /usr/lib64/libmysqlclient.so.16
ln -s /usr/lib64/libmysqlclient.so /usr/lib64/libmysqlclient.so.15

I am not sure that this is the solution, your described the problem really bad.

[arboooz]

Sorry for that ive forgot to paste an error :o, now i had updated my post.

It is exacly the same error as they described it here: http://help.directadmin.com/item.php?id=236
but mine is about libmysqlclient.so.16, i had try to update and downgrade mysql version and nothing helps. now i am rebuilding directadmin applicatoin, after that ill try your solutions and see if thats helps

[arboooz]

i can not to make an symbolic links becouse some files an already exists, to help solve this out i put part of my console outputs from /usr/lib folder, down there:

root@xxx:/usr/lib# ll | grep libmysql
lrwxrwxrwx 1 root root 26 maj 18 15:35 libmysqlclient_r.so.15 -> libmysqlclient_r.so.15.0.0
-rw-r--r-- 1 root root 2147984 lut 13 13:46 libmysqlclient_r.so.15.0.0
lrwxrwxrwx 1 root root 29 cze 24 00:52 libmysqlclient.so -> /usr/lib/libmysqlclient.so.16
lrwxrwxrwx 1 root root 24 maj 18 15:35 libmysqlclient.so.15 -> libmysqlclient.so.15.0.0*
-rwxr-xr-x 1 root root 1474856 gru 17 2008 libmysqlclient.so.15.0.0*
lrwxrwxrwx 1 root root 28 cze 24 00:53 libmysqlclient.so.16 -> /usr/lib64/libmysqlclient.so


Now its look little messy

-----------

Ok it looks like i solved it, ive found that i have that file in /usr/local/mysql-5.1.46-linux-x86_64/lib/ folder. When i move that file to /usr/lib directadmin stated sucesful

[localhost]

When this happen? What MySQL version you have? Did you try to re-install mySQL ?

[nobaloney]

The best thing to do if you can't get DirectAdmin to run is to ask DirectAdmin staff (http://www.directadmin.com/support.html) for help.

Jeff

[DirectAdmin Support]

Hello,

I've updated the guide to include the Debian 5 64-bit version (Bottom):
http://help.directadmin.com/item.php?id=236

John

[tristan]

Having the same problem on a freshly installed DirectAdmin server, Debian 5 64bit as well. The solution from the kb (http://help.directadmin.com/item.php?id=236) didn't work, still the "cannot open shared object file" when trying to start DirectAdmin. Any other clues?

[DirectAdmin Support]

Check the license OS in your clients section, to make sure it's set to 64-bit Debian, and not 32-bit. Beyond that, we may need to take a look. If you'd like us to check, send us your info (https://www.directadmin.com/clients/safesubmit.php)

John

[tristan]

Just checked that again, it's Debian 5.0 64-bit as well. Just submitted the info for this server via that form.

[DirectAdmin Support]

Hello,

Solution to run
ldconfigso that the system library linker took another look at the libraries it had, thus found the newly installed mysql lib.
I've added that command to the guide for clarification.

John

[tristan]

Ok great but now I receive this error when trying to recompile iconv:


/sbin/ldconfig: /usr/local/mysql/lib/libndbclient.so.2 is not a symbolic link
/sbin/ldconfig: /usr/local/mysql/lib/libmysqlclient.so.15 is not a symbolic link
/sbin/ldconfig: /usr/local/mysql/lib/libmysqlclient_r.so.15 is not a symbolic link

And when trying to recompile php afterwards, it will stop at:


/bin/sh /usr/local/directadmin/custombuild/php-5.3.3/libtool --silent --preserve-dup-deps --mode=compile gcc -Iext/mysqli/ -I/usr/local/directadmin/custombuild/php-5.3.3/ext/mysqli/ -DPHP_ATOM_INC -I/usr/local/directadmin/custombuild/php-5.3.3/include -I/usr/local/directadmin/custombuild/php-5.3.3/main -I/usr/local/directadmin/custombuild/php-5.3.3 -I/usr/local/directadmin/custombuild/php-5.3.3/ext/date/lib -I/usr/local/directadmin/custombuild/php-5.3.3/ext/ereg/regex -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/local/include/freetype2 -I/usr/local/mysql/include -I/usr/local/directadmin/custombuild/php-5.3.3/ext/sqlite3/libsqlite -I/usr/local/directadmin/custombuild/php-5.3.3/TSRM -I/usr/local/directadmin/custombuild/php-5.3.3/Zend -I/usr/local/include -g -O2 -fvisibility=hidden -c /usr/local/directadmin/custombuild/php-5.3.3/ext/mysqli/mysqli.c -o ext/mysqli/mysqli.lo
/bin/sh /usr/local/directadmin/custombuild/php-5.3.3/libtool --silent --preserve-dup-deps --mode=compile gcc -Iext/mysqli/ -I/usr/local/directadmin/custombuild/php-5.3.3/ext/mysqli/ -DPHP_ATOM_INC -I/usr/local/directadmin/custombuild/php-5.3.3/include -I/usr/local/directadmin/custombuild/php-5.3.3/main -I/usr/local/directadmin/custombuild/php-5.3.3 -I/usr/local/directadmin/custombuild/php-5.3.3/ext/date/lib -I/usr/local/directadmin/custombuild/php-5.3.3/ext/ereg/regex -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/local/include/freetype2 -I/usr/local/mysql/include -I/usr/local/directadmin/custombuild/php-5.3.3/ext/sqlite3/libsqlite -I/usr/local/directadmin/custombuild/php-5.3.3/TSRM -I/usr/local/directadmin/custombuild/php-5.3.3/Zend -I/usr/local/include -g -O2 -fvisibility=hidden -c /usr/local/directadmin/custombuild/php-5.3.3/ext/mysqli/mysqli_api.c -o ext/mysqli/mysqli_api.lo
/bin/sh /usr/local/directadmin/custombuild/php-5.3.3/libtool --silent --preserve-dup-deps --mode=compile gcc -Iext/mysqli/ -I/usr/local/directadmin/custombuild/php-5.3.3/ext/mysqli/ -DPHP_ATOM_INC -I/usr/local/directadmin/custombuild/php-5.3.3/include -I/usr/local/directadmin/custombuild/php-5.3.3/main -I/usr/local/directadmin/custombuild/php-5.3.3 -I/usr/local/directadmin/custombuild/php-5.3.3/ext/date/lib -I/usr/local/directadmin/custombuild/php-5.3.3/ext/ereg/regex -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/local/include/freetype2 -I/usr/local/mysql/include -I/usr/local/directadmin/custombuild/php-5.3.3/ext/sqlite3/libsqlite -I/usr/local/directadmin/custombuild/php-5.3.3/TSRM -I/usr/local/directadmin/custombuild/php-5.3.3/Zend -I/usr/local/include -g -O2 -fvisibility=hidden -c /usr/local/directadmin/custombuild/php-5.3.3/ext/mysqli/mysqli_prop.c -o ext/mysqli/mysqli_prop.lo
/bin/sh /usr/local/directadmin/custombuild/php-5.3.3/libtool --silent --preserve-dup-deps --mode=compile gcc -Iext/mysqli/ -I/usr/local/directadmin/custombuild/php-5.3.3/ext/mysqli/ -DPHP_ATOM_INC -I/usr/local/directadmin/custombuild/php-5.3.3/include -I/usr/local/directadmin/custombuild/php-5.3.3/main -I/usr/local/directadmin/custombuild/php-5.3.3 -I/usr/local/directadmin/custombuild/php-5.3.3/ext/date/lib -I/usr/local/directadmin/custombuild/php-5.3.3/ext/ereg/regex -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/local/include/freetype2 -I/usr/local/mysql/include -I/usr/local/directadmin/custombuild/php-5.3.3/ext/sqlite3/libsqlite -I/usr/local/directadmin/custombuild/php-5.3.3/TSRM -I/usr/local/directadmin/custombuild/php-5.3.3/Zend -I/usr/local/include -g -O2 -fvisibility=hidden -c /usr/local/directadmin/custombuild/php-5.3.3/ext/mysqli/mysqli_nonapi.c -o ext/mysqli/mysqli_nonapi.lo
In file included from /usr/local/directadmin/custombuild/php-5.3.3/ext/mysqli/php_mysqli_structs.h:57,
from /usr/local/directadmin/custombuild/php-5.3.3/ext/mysqli/mysqli_api.c:33:
/usr/local/mysql/include/my_global.h:364:24: error: asm/atomic.h: No such file or directory
In file included from /usr/local/directadmin/custombuild/php-5.3.3/ext/mysqli/php_mysqli_structs.h:57,
from /usr/local/directadmin/custombuild/php-5.3.3/ext/mysqli/mysqli.c:33:
/usr/local/mysql/include/my_global.h:364:24: error: asm/atomic.h: No such file or directory
In file included from /usr/local/directadmin/custombuild/php-5.3.3/ext/mysqli/php_mysqli_structs.h:57,
from /usr/local/directadmin/custombuild/php-5.3.3/ext/mysqli/mysqli_prop.c:30:
/usr/local/mysql/include/my_global.h:364:24: error: asm/atomic.h: No such file or directory
make: *** [ext/mysqli/mysqli.lo] Error 1
make: *** Waiting for unfinished jobs....
In file included from /usr/local/directadmin/custombuild/php-5.3.3/ext/mysqli/php_mysqli_structs.h:57,
from /usr/local/directadmin/custombuild/php-5.3.3/ext/mysqli/mysqli_nonapi.c:32:
/usr/local/mysql/include/my_global.h:364:24: error: asm/atomic.h: No such file or directory
make: *** [ext/mysqli/mysqli_prop.lo] Error 1
make: *** [ext/mysqli/mysqli_api.lo] Error 1
make: *** [ext/mysqli/mysqli_nonapi.lo] Error 1

*** The make has failed, do you want to try to make again? (y,n):

[DirectAdmin Support]

Hello,

What version of mysql is that? I've found a reported bug:
http://bugs.mysql.com/bug.php?id=28456

The solution says not to use asm/atomic.h.. .which is what php is using.

More searches found:
http://directadmin.com/forum/showthread.php?p=185919

For a quick fix, I'd say try php 5.2.

As for the ldconfig messages, I'm not sure if those are just warnings and not actual errors. In any case, our Debian 5 64-bit box looks like this in the /usr/local/mysql/lib
debian5-64:/usr/local/mysql/lib# ll libmysqlclient*
-rw-r--r-- 1 mysql mysql 9698414 2009-12-16 12:39 libmysqlclient.a
-rwxr-xr-x 1 mysql mysql 1076 2009-12-16 12:39 libmysqlclient.la
-rw-r--r-- 1 mysql mysql 9768178 2009-12-16 12:39 libmysqlclient_r.a
-rwxr-xr-x 1 mysql mysql 1130 2009-12-16 12:39 libmysqlclient_r.la
lrwxrwxrwx 1 mysql mysql 26 2010-01-23 03:41 libmysqlclient_r.so -> libmysqlclient_r.so.16.0.0
lrwxrwxrwx 1 mysql mysql 26 2010-01-23 03:41 libmysqlclient_r.so.16 -> libmysqlclient_r.so.16.0.0
-rwxr-xr-x 1 mysql mysql 5328629 2009-12-16 12:39 libmysqlclient_r.so.16.0.0
lrwxrwxrwx 1 mysql mysql 24 2010-01-23 03:41 libmysqlclient.so -> libmysqlclient.so.16.0.0
lrwxrwxrwx 1 mysql mysql 24 2010-01-23 03:41 libmysqlclient.so.16 -> libmysqlclient.so.16.0.0
-rwxr-xr-x 1 mysql mysql 5287554 2009-12-16 12:39 libmysqlclient.so.16.0.0which has mysql 5.1.42.

John

[tristan]

About the ldconfig messages:


pegasus:/usr/local/mysql/lib# ls -al libmysqlclient*
-rw-r--r-- 1 mysql mysql 9702798 2010-05-05 17:34 libmysqlclient.a
-rw-r--r-- 1 mysql mysql 9754912 2010-05-05 17:35 libmysqlclient_r.a
-rwxr-xr-x 1 mysql mysql 5361392 2010-05-05 17:35 libmysqlclient_r.so
-rwxr-xr-x 1 mysql mysql 5361392 2010-05-05 17:35 libmysqlclient_r.so.15
-rwxr-xr-x 1 mysql mysql 5361392 2010-05-05 17:35 libmysqlclient_r.so.15.0.0
-rwxr-xr-x 1 mysql mysql 5328274 2010-05-05 17:34 libmysqlclient.so
-rwxr-xr-x 1 mysql mysql 5328274 2010-05-05 17:34 libmysqlclient.so.15
-rwxr-xr-x 1 mysql mysql 5328274 2010-05-05 17:34 libmysqlclient.so.15.0.0
-rwxr-xr-x 1 root root 5287554 2010-06-25 08:24 libmysqlclient.so.16

So indeed no symlinks, any way to fix this without breaking anything?

I need php 3.3 for a project on this server so please let me know when this will be fixed in CustomBuild.

[mr.applesauce]

Why is so.16 owned by root but everything else is owned by mysql? Why not try chown and see if it works.

[tristan]

Why is so.16 owned by root but everything else is owned by mysql? Why not try chown and see if it works.

I think because I entered the steps as proposed by the kb as root and not as the mysql user.

[Marwen]

Hello,

I've updated the guide to include the Debian 5 64-bit version (Bottom):
http://help.directadmin.com/item.php?id=236

John

When i do this the directadmin himself works fine.
no error messages.

mysql works also without problem.

but :)

my installed vbb board make database errors after this.
all other databases work fine.

error message i get
mysql_connect() [<a href='function.mysql-connect'>function.mysql-connect</a>]: Headers and client library minor version mismatch. Headers:50509 Library:50142

only a custombuild ./build all fix this.

but after that i get again.

/usr/local/directadmin/dataskq: /usr/local/mysql/lib/libmysqlclient.so.16: no version information available (required by /usr/local/directadmin/dataskq)

any ideas ?


i use:
debian 5 64bit
php5.3.6
mysql5.5.9

[zEitEr]

You probably need to recompile PHP.

[Marwen]

yes. but same error.

without the libmysqlclient fix the
VBB forum and Kayako Database works.

but not the DA.
/usr/local/directadmin/dataskq: /usr/local/mysql/lib/libmysqlclient.so.16: no version information available (required by /usr/local/directadmin/dataskq)

with the fix.

the DA and the Kayako Database works
but not the VBB forum :(

its a loop :)

[DirectAdmin Support]

Hello,

There are 2 issues there:

1)
/usr/local/directadmin/dataskq: /usr/local/mysql/lib/libmysqlclient.so.16: no version information available (required by /usr/local/directadmin/dataskq) Confirm that you've actually got the Debian 5 64-bit binaries:
cd /usr/local/directadmin
./directadmin oThe Debain 5 64-bit binaries are compiled again MySQL 5.1. It may be needed to use the mysql 5.1 version to get rid of that error.

The alternative is to try the debian 6 64-bit binaries, as they have been compiled against mysql 5.5.


2)
error message i get
mysql_connect() [<a href='function.mysql-connect'>function.mysql-connect</a>]: Headers and client library minor version mismatch. Headers:50509 Library:50142That wouldn't have anything to do with the DA version you're running. That only applies to the version of mysql you're running, and what version of mysql you had when php was compiled. As zEitEr mentioned, recompiling php would solve that.

John

[dlong500]

Hello,

Solution to run
ldconfigso that the system library linker took another look at the libraries it had, thus found the newly installed mysql lib.
I've added that command to the guide for clarification.

John
I have the same libmysqlclient.so.16 problem and the method listed in the help file is not working for me (i.e. nothing changes). I have Debian 6.0 x64 and do have the correct DA binaries/license. I've tried creating a soft link like the help page says and also tried a hard link with no difference. All file permissions are correct and the link is owned by mysql.

It appears that the ldconfig command is not recognizing the link as it does not show up in the cache (ldconfig -p). Any ideas?

[remikk]

Solution from http://help.directadmin.com/item.php?id=236 doesn't work for me.
I have Debian 6.0 64bit.

After I update mysql from custombuild I have:



/usr/local/directadmin/directadmin o
/usr/local/directadmin/directadmin: error while loading shared libraries: libmysqlclient.so.16: cannot open shared object file: No such file or directory


[code]
/usr/local/mysql/lib# ls -l libmysqlclient*
-rw-r--r-- 1 mysql mysql 14762606 05-11 20:10 libmysqlclient.a
lrwxrwxrwx 1 mysql mysql 16 06-17 10:05 libmysqlclient_r.a -> libmysqlclient.a
lrwxrwxrwx 1 mysql mysql 17 06-17 10:05 libmysqlclient_r.so -> libmysqlclient.so
lrwxrwxrwx 1 mysql mysql 17 06-17 10:05 libmysqlclient_r.so.18 -> libmysqlclient.so
lrwxrwxrwx 1 mysql mysql 17 06-17 10:05 libmysqlclient_r.so.18.0.0 -> libmysqlclient.so
lrwxrwxrwx 1 mysql mysql 20 06-17 10:05 libmysqlclient.so -> libmysqlclient.so.18
lrwxrwxrwx 1 root mysql 20 06-17 10:28 libmysqlclient.so.16 -> libmysqlclient.so.18
lrwxrwxrwx 1 mysql mysql 24 06-17 10:05 libmysqlclient.so.18 -> libmysqlclient.so.18.0.0
-rwxr-xr-x 1 mysql mysql 6842027 05-11 20:10 libmysqlclient.so.18.0.0
[code]

Could you help me?

[remikk]

Solution for Debian 6 64bit doesn't work for me.


cd /usr/local/mysql/lib
ln -s libmysqlclient.so.18 libmysqlclient.so.16
ldconfig

I had to delete link libmysqlclietn.so.16 and download this file from http://files.directadmin.com/services/debian_5.0_64/libmysqlclient.so.16
Then everything works.

[ldjnetworks]

I ran into the same issues. I'm not running 64 bit but this solved it for me on Debian 6, 32-bit.



cd /usr/local/mysql/lib
rm -f libmysqlclient.so.16




apt-get update
apt-get install libmysqlclient16

[nango]

I update DA from 3.8 to last after some minutes DA login page was not available and I tried to restart DA service with no result.
I have CentOS X86_64. Ther error is:

/usr/local/directadmin/directadmin: error while loading shared libraries: /usr/lib64/libmysqlclient.so.16: file too short


ldconfig: File /usr/lib64/libmysqlclient.so.16 is empty, not checked.
The help (http://help.directadmin.com/item.php?id=236) was not useful for me.

[Xtracy]

Hi,

I've updated DirectAdmin from 1.38.4 to 1.39 (through the control panel) and now DA won't start.

When I try to start it from the shell I get:


service directadmin start
Starting DirectAdmin: /usr/local/directadmin/directadmin:
error while loading shared libraries: libmysqlclient.so.16:
cannot open shared object file: No such file or directory [FAILED]



I've checked (and tried) the help but without resolve.

I also tried linking so.15 to so.16 but then get the following error:


Starting DirectAdmin: /usr/local/directadmin/directadmin:
/usr/lib64/libmysqlclient.so.16: version `libmysqlclient_16'
not found (required by /usr/local/directadmin/directadmin) [FAILED]


(using CentOS 5.5, 64bit)

[nango]

My Problem Solver by:
Update Mysql from 5.0 to 5.1 with custom build. then rebuild php. update (http://help.directadmin.com/item.php?id=29) DA manual.

[nango]

Hi Xtracy
I had this problem today exactly. heck my above solution.

[klaasvaak]

same problem here
centos 64 bit -> updates directadmin to 1.39 and directadmin wont start anymore.

from command line i saw
Starting DirectAdmin: /usr/local/directadmin/directadmin: error while loading sh
ared libraries: libmysqlclient.so.16: cannot open shared object file: No such fi
le or directory

here what i did

1. updates my sql to mysql=5.1 with the custombuild
2. then i rebuild php
3. then cd /usr/local/directadmin
./directadmin p
cd scripts
./update.sh
/etc/init.d/directadmin restart

and then from
:2222/CMD_SHOW_SERVICES full reboot

and directadmin 1.39 is running again.

[Xtracy]

Hi,

Thank you for your replies, unfortunatly I can't upgrade to mySQL 5.1 at the moment.

[simmer]

Got the same problem, fixes don't work for me on Centos 5.5 x64


wget -O /usr/lib64/libmysqlclient.so.15 http://files.directadmin.com/services/es_5.0_64/libmysqlclient.so.15
chmod 755 /usr/lib64/libmysqlclient.so.15
ldconfig

/usr/lib64/libmysqlclient.so.16: file too short

[binarygrind]

same problem here
centos 64 bit -> updates directadmin to 1.39 and directadmin wont start anymore.

from command line i saw
Starting DirectAdmin: /usr/local/directadmin/directadmin: error while loading sh
ared libraries: libmysqlclient.so.16: cannot open shared object file: No such fi
le or directory

here what i did

1. updates my sql to mysql=5.1 with the custombuild
2. then i rebuild php
3. then cd /usr/local/directadmin
./directadmin p
cd scripts
./update.sh
/etc/init.d/directadmin restart

and then from
:2222/CMD_SHOW_SERVICES full reboot

and directadmin 1.39 is running again.

Woot! Thanks, now DA is backup and running.

[yonatanp]

Got the same problem, fixes don't work for me on Centos 5.5 x64


wget -O /usr/lib64/libmysqlclient.so.15 http://files.directadmin.com/services/es_5.0_64/libmysqlclient.so.15
chmod 755 /usr/lib64/libmysqlclient.so.15
ldconfig



same issue here


directadmin]# ./directadmin o
./directadmin: error while loading shared libraries: libmysqlclient.so.16: cannot open shared object file: No such file or directory
# service directadmin start
Starting DirectAdmin: /usr/local/directadmin/directadmin: error while loading shared libraries: libmysqlclient.so.16: cannot open shared object file: No such file or directory
[FAILED]

uname -i
x86_64


centos 5.6
mysql 5.0
php-cgi 5.2-latest

can't update to 5.1 due to compatibility issues.

[DirectAdmin Support]

Hello,

I found that the CentOS 5 64-bit binaries were linked to libmysqlclient.so.16 when they might have not been before. I'm going to rebuild them and force them not to link to it (they'll have internal mysql code instead).
Once I release 1.39.1, use this guide (http://help.directadmin.com/item.php?id=29) to grab the new version.

John

[yonatanp]

Hi john,
thank you for the prompt replay,
i have rolled back the binary on the server for now to 1.38.4

looking forward for updates.

Have a good day/night :)

[DirectAdmin Support]

Hello,

The CentOS 5 64-bit binary package is now in the system. You can use the mentioned guide to get these new binaries (1.39.1).

John

[nobaloney]

John,

Hopefully you'll announce when the new binaries are ready for install from the control panel; I (and I'd presume others) will wait until all is sorted out.

Thanks.

Jeff

[jw00dy]

Thank you for this fix. I have upgraded to 1.39.1 and it's working as it should now. DA is running now and I don't have any errors.

[chenpang]

hi!
on my debian(32 bits) system,the error is :
error while loading shared libraries: libmysqlclient.so.18: cannot open shared object file: No such file or directory
i type the command and it work pertect!
# ln -s /usr/local/mysql/lib/libmysqlclient.so.18 /usr/lib/libmysqlclient.so.18
(suppose your MYSQL is installed in /usr/local)
chenpang

[nealdxmhost]

I am in the middle of setting up a server with Ubuntu 10.04 64 bit and I too am having this problem as well during the install. During the first run and when it spit out the error message it told me that I needed to do the following;

apt-get install libdb4.8-dev libperl-dev libsasl2-dev

So I did that and ran setup again and then it did this;

./directadmin: error while loading shared libraries: libmysqlclient.so.16: cannot open shared object file: No such file or directory

So then I followed the suggestion posted here http://help.directadmin.com/item.php?id=236 and did this;

wget -O /usr/local/mysql/lib/libmysqlclient.so.16 http://files.directadmin.com/services/debian_5.0_64/libmysqlclient.so.16
chmod 755 /usr/local/mysql/lib/libmysqlclient.so.16
ldconfig

Now I am running setup again and I will keep you posted.

[mean]

Starting DirectAdmin: /usr/local/directadmin/directadmin: /usr/lib/libmysqlclient.so.16: version `libmysqlclient_16' not found (required by /usr/local/directadmin/directadmin)

or

./directadmin: error while loading shared libraries: libmysqlclient.so.16: cannot open shared object file: No such file or directory

you can fix:
wget -O /usr/lib64/libmysqlclient.so.16 http://files.directadmin.com/services/debian_5.0_64/libmysqlclient.so.16
or http://help.directadmin.com/item.php?id=236

[dlong500]

you can fix:
wget -O /usr/lib64/libmysqlclient.so.16 http://files.directadmin.com/services/debian_5.0_64/libmysqlclient.so.16
or http://help.directadmin.com/item.php?id=236

I don't know if there is something different based on platform (I'm using Debian 6 x64) or just something wrong with that file hosted by DA, but when I tried using the file from http://files.directadmin.com/services/debian_6.0/libmysqlclient.so.16 it didn't work. I had to pull the libmysqlclient.so.16 file out of the following location on my system to get things to work:
/usr/local/mysql-5.5.9-linux2.6-x86_64/lib/libmysqlclient.so.16

Just FYI, the files ARE different in size, so for whatever reason the one hosted by DA didn't work whereas the one in the above location did. Maybe the one hosted at DA for Debian 6 is only for 32bit platforms. If that's the case then I guess the 64bit version needs to be hosted as well.

For a more detailed thread on trying to get to the bottom of problems specifically in Debian 6.0 x64 (including this one) see http://directadmin.com/forum/showthread.php?t=41529

[DirectAdmin Support]

Hello,

The linking really shouldn't be needed. It usually means that something else is out of place.

1) Check your Clients Section (https://www.directadmin.com/clients) to ensure the OS set for your license matches the OS that you're using.
Related: http://help.directadmin.com/item.php?id=318

2) Use the default values for the install to avoid these types of issue (as installing older versions of mysql can also cause linking issues, as DA is linked against the default version set in the install pack)

3) Check your binaries (once running/fixed):
cd /usr/local/directadmin
./directadmin oJohn

[dlong500]

Hello,

The linking really shouldn't be needed. It usually means that something else is out of place.

1) Check your Clients Section (https://www.directadmin.com/clients) to ensure the OS set for your license matches the OS that you're using.
Related: http://help.directadmin.com/item.php?id=318

2) Use the default values for the install to avoid these types of issue (as installing older versions of mysql can also cause linking issues, as DA is linked against the default version set in the install pack)

3) Check your binaries (once running/fixed):
cd /usr/local/directadmin
./directadmin oJohn

But there isn't anything "out of place" in my system. I have the correct OS set on my license as "Debian 6 64" and I'm only changing a couple settings in options.conf (certainly nothing crazy). Please see http://www.directadmin.com/forum/showthread.php?t=41529 for a list of things I've encountered on a clean Debian 6 x64 install.

To make sure I'm crystal clear about all this, here is my process from start to finish:

1) Install Debian 6 x64 with debian-6.0.2.1-amd64-i386-netinst.iso
2) Update Apt repository

aptitude update
3) Per DA installation guide, install the following:

aptitude install gcc g++ make flex bison openssl libssl-dev perl perl-base perl-modules libperl-dev libaio1 libaio-dev

At this point the system is running perfectly. There are no errors or warnings running aptitude and no packages are listed as broken. Now to install DA.

4)

cd /root
wget http://www.directadmin.com/setup.sh
chmod 755 setup.sh
5) In order to get DA to use my pre-made options.conf from the start (as others have in the forums) and to set a couple of custom config files, run the following:

mkdir /usr/local/directadmin/
mkdir /usr/local/directadmin/custombuild/
mkdir /usr/local/directadmin/custombuild/custom/
mkdir /usr/local/directadmin/custombuild/custom/phpmyadmin/
wget -O /usr/local/directadmin/custombuild/custom/phpmyadmin/config.inc.php <external location of php config file>
wget -O /usr/local/directadmin/custombuild/options.conf <external location of options.conf>
chmod 644 /usr/local/directadmin/custombuild/custom/phpmyadmin/config.inc.php
chmod 644 /usr/local/directadmin/custombuild/options.conf
echo 1.2 > /root/.custombuild
/root/setup.sh <userid> <licenseid> hostname eth0 <ip>


Here is my options.conf file for review:

#PHP settings. default_php possible values - 5 or 6, php5_ver - 5.2 or 5.3
default_php=5
php5_ver=5.3
php5_cli=yes
php5_cgi=no
php6_cli=no
php6_cgi=no
php_ini=yes
#Possible values - recommended or dist
php_ini_type=recommended
zend=no

#Possible values - 5.0, 5.1, 5.5
mysql=5.5
mysql_inst=yes
mysql_backup=yes

#Possible values - 1.3, 2.0 or 2.2
apache_ver=2.2

#Web applications
phpmyadmin=yes
atmail=no
squirrelmail=no
roundcube=no
uebimiau=no

#Mail options
exim=no
spamassassin=no
mail-header-patch=yes
dovecot=no
eximconf=no

#Statistics
awstats=no
webalizer=yes

#FTP options
proftpd=no
pureftpd=yes

#Jailed shell
jail=no

#Custombuild options
custombuild=1.2
autover=yes
bold=yes
clean=yes
cleanapache=yes
clean_old_tarballs=no
clean_old_webapps=yes
downloadserver=files.directadmin.com

#Cron settings
cron=no
email=<email address removed>
notifications=yes
da_autoupdate=no
updates=no
webapps_updates=yes

clamav=no
mailman=no
ioncube=no
mysql_backup_dir=/usr/local/directadmin/custombuild/mysql_backups
autoconf=yes
automake=yes
libtool=yes

At this point, DA is NOT fully installed because it is looking for libmysqlclient.so.16 but Custombuild installed libmysqlclient.so.18 as part of MySQL 5.5.15. Because of this, I then have to do the following:

6)

cd /usr/local/mysql/lib
rm -f libmysqlclient.so.16
cp /usr/local/mysql-5.5.9-linux2.6-x86_64/lib/libmysqlclient.so.16 /usr/local/mysql/lib/libmysqlclient.so.16
chmod 755 libmysqlclient.so.16
ldconfig

7) Now that the old library is there, we re-run DA setup

/root/setup.sh <userid> <licenseid> hostname eth0 <ip>

Ok, so now DA is installed, but there are still the other issues. As you can see from my options.conf file, Exim has been set as "no", but the already installed Exim in Debian is now broken (see the other thread I mentioned earlier for details). Also, the libz issue is present and must be resolved (also mentioned in the other thread (http://www.directadmin.com/forum/showthread.php?t=41529)).

Please advise.

[DirectAdmin Support]

Try it with all default install options (don't specify anything for custombuild). The likely cause is:
mysql_inst=yeswhich is not a default option. Worry about installing a different copy of mysql after.

I do now recall needing to run some re-linking code in the update.sh for debian when DA is being updated.
After the install, try:
cd /usr/local/directadmin/scripts
./update.shwhich does a few checks on lib 16 vs 18. If you want to check the code, it's at the bottom of the update.sh, then finish with the "./directadmin i; ./directadmin p;"

This is likely the same as what you were running anyway, in which case, it would be a bug, and would need to be added to the installer, instead of just the updater. But this only applies to the case where mysql is updated before DA is installed (which should be allowed).

Snip from the update.sh:
#debian if MySQL 5.5.11+
#april 21, 2011
if [ -e /etc/debian_version ]; then
if [ -e /usr/local/directadmin/directadmin ]; then
COUNT=`ldd /usr/local/directadmin/directadmin | grep -c libmysqlclient.so.16`
if [ "${COUNT}" -eq 1 ]; then
if [ ! -e /usr/local/mysql/lib/libmysqlclient.so.16 ] && [ -e /usr/local/mysql/lib/libmysqlclient.so.18 ]; then
echo "*** Linking libmysqlclient.so.16 to libmysqlclient.so.18";
ln -s libmysqlclient.so.18 /usr/local/mysql/lib/libmysqlclient.so.16
ldconfig
fi
fi
COUNT=`ldd /usr/local/directadmin/directadmin | grep -c libmysqlclient.so.18`
if [ "${COUNT}" -eq 1 ]; then
if [ ! -e /usr/local/mysql/lib/libmysqlclient.so.18 ] && [ -e /usr/local/mysql/lib/libmysqlclient.so.16 ]; then
echo "*** Linking libmysqlclient.so.18 to libmysqlclient.so.16";
ln -s libmysqlclient.so.16 /usr/local/mysql/lib/libmysqlclient.so.18
ldconfig
fi
fi
fi
fiJohn

[dlong500]

Try it with all default install options (don't specify anything for custombuild).

Thanks for your suggestions John.

I've been experimenting a bit over the past couple days with the install scripts and I think I've come across a bug that explains the Exim issue I've been having. I can't find any place in the initial install scripts that is ever checking the exim setting in options.conf. It is trying to uninstall Exim and then compiling and reinstalling no matter what the options.conf setting is. Note that the build script (for updating) does seem to check the setting, but an initial install is hosing the distribution's existing Exim installation. Can you look into this?

On a lesser note, it looks like it is also trying to install GD with "apt-get -y install gd" (which doesn't exist) rather than "apt-get -y install libgd2-xpm".

Thanks.

[DirectAdmin Support]

Hello,
It is trying to uninstall Exim and then compiling and reinstalling no matter what the options.conf setting is.1) I'm not seeing that... Note that custombuild isn't the main installer for exim. The main spot that exim is installed is:
/usr/local/directadmin/scripts/exim.sh

using the package in:
/usr/local/directadmin/scripts/packages

The custombuild default for exim is no, and I've not heard of any issues where "build" is ignoring the options.conf value... perhaps I'm missing something. Exim in custombuild is for version updates. The exim.sh is for the initial install, so the exim.sh will always happen. Using "no" in custombuild just means you don't want custombuild to update it. It will always be install anyway.

2) The apt-get gd install attempt can likely be ignored, as it's more for other OS's.
The script uses "gd" as a universal name/index. Other items are named correctly, but I dont think the missing gd module is hurting anything.

John

[dlong500]

Hello,1) I'm not seeing that... Note that custombuild isn't the main installer for exim. The main spot that exim is installed is:
/usr/local/directadmin/scripts/exim.sh

using the package in:
/usr/local/directadmin/scripts/packages

The custombuild default for exim is no, and I've not heard of any issues where "build" is ignoring the options.conf value... perhaps I'm missing something. Exim in custombuild is for version updates. The exim.sh is for the initial install, so the exim.sh will always happen. Using "no" in custombuild just means you don't want custombuild to update it. It will always be install anyway.

I guess I'm just a little confused because, when you install DirectAdmin, you choose between Custombuild and CustomApache, so it seemed logical to think that the initial installer would follow the same options.conf settings.

Regardless, can you list any specific reasons that Exim needs to be compiled and installed by your script during a DA installation? Are there some special features that the pre-installed Exim from Debian doesn't provide? Since I'm not using my DA box for any email functionality except for scripts that need an outgoing mailserver it seems to me like the existing Exim install would work fine. Just one less thing that I need to maintain apart from the distribution's package management.

Thanks for any insight into the issue. I'm not opposed to manually editing the installer script myself (I've already tested several changes), but then I'd have to re-edit it every time you update the script if I want to install on a clean machine again.

[DirectAdmin Support]

Hello,
can you list any specific reasons that Exim needs to be compiled and installed by your script during a DA installation?The only reason you'd use custombuild for exim is to update to a new version where applicable. Doing it during the actual install isn't usually recommended (leave it as "no")since we already include binaries which should work fine, are installed already anyway, and exim is one of the more difficult packages to compile due to it's dependencies (usually takes a few tries to meet it's specific needs (http://help.directadmin.com/item.php?id=125))... any failure on the first try aborts the whole DA install.. hence best to do it after everything else is done, and only if you need to.

The debian packages likely do have all required features that DA needs (mainly just the perl option), however, what it doesn't have is the same compile settings for things like log names and uid/gid values for the spool directory (I believe it uses "exim" while we use "mail"). So the pre-installed package tends to not match up completely.

John

[dlong500]

Going back to the main point of this thread (which is the libmysqlclient problem), I just saw in the DA changelog the following entry:
http://www.directadmin.com/features.php?id=1232

This explains that DA has been updated to not link to any MySQL libraries at compile time for the CentOS 5 x64 platform. This is exactly the same issue that many of us have experienced with various versions of Debian (mine being Debian 6.0 x64). Can this not be done for Debian as well?