Thanks for each of your inputs.
It was not a configuration issue as odbcinst.ini does not reference the
mysql subdirectory.
Rather than use Alexander's url, I ran:
yum -y install centos-release-openstack-ocata
yum -y install mariadb-server
...the cloud repository provides the properly pathed file.
# repoquery -l mariadb-server mariadb-libs | grep lib64 | grep
libmysqlclient
/usr/lib64/mysql/libmysqlclient.so.18
/usr/lib64/mysql/libmysqlclient.so.18.0.0
I installed this and isql was crashing. But (unlike the mariadb.com
repository,) is did install:
/usr/lib64/mysql/libmysqlclient.so
...in the appropriate subdirectory.
However my asterisk server is still running and it still has that file
open. I don't know if this keeps new processes referencing the .so file
that is open in ram. I'm not sure how the package manager addresses such
issues. Does it run ldconfig as part of the installation and defer
resolving issues till the involved files are closed?
For the moment I have again undoed the installation
I was waiting to post this till things were slow enough to restart
processes, run ldconfig, etc... Perhaps I need to do the install when no
odbc|maria|mysql files are open.
But this is the current state of things, and I will post the outcome later.
John
On Tue, Oct 31, 2017 at 2:52 PM, Gordon Messmer <gordon.messmer@xxxxxxxxx>
wrote:
> On 10/30/2017 12:22 PM, John Harragin wrote:
>
>> [root@ec-ast yum.repos.d]# ldd /usr/lib64/libmyodbc5w.so | grep -iE
>> "my|maria"
>> libmysqlclient.so.18 => /usr/lib64/mysql/libmysqlclient.so.18
>> (0x00007f3dfb34c000)
>> [root@ec-ast yum.repos.d]# repoquery -l MariaDB-server MariaDB-client
>> MariaDB-commo MariaDB-shared galera boost-program-options jemalloc rsync
>> lsof | grep lib64 | grep libmysqlclient
>> /usr/lib64/libmysqlclient.so.18
>>
>
> If the MariaDB packages provide the library in /usr/lib64, what provides
> the lib in /usr/lib64/mysql? (It looks like you have a library conflict)
>
> rpm -qf /usr/lib64/mysql/*
>
> More than likely, you can resolve the problem by removing the package that
> provides the files in /usr/lib64/mysql/. However, as Alexander pointed
> out, this isn't a problem with the CentOS packages, and you're more likely
> to get useful information if you address this question to the vendor of the
> broken package.
>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> https://lists.centos.org/mailman/listinfo/centos
>
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
