Libmysqlclient.so.18: no version infromation available

[David W]

Hello,

I have installed rfc5766-turn-server on an Ubuntu server and all (allthough i am new to linux) went pretty smooth.
At the moment i am trying to connect the turn server to mysql, for which i have installed mysql-server + workbench (for administration).
Finally i have created the database and added some bogus accounts to test with.
Now when i start the server (or admin application) with the --mysql-userdb parameter i get the error: libmysqlclient.so.18: no version information available (required by turnserver).
I have received no errors while installing mysql or other dependencies, do you know how i can fix this?

Thanks in advance, David.

[Oleg Moskalenko]

David, this is MySQL problem, they screwed something in their setup on Debian systems. There is lot of information on Internet about that, for example:

http://forum.directadmin.com/showthread.php?t=46807

try to follow their recommendations how to fix it.

You can just google " libmysqlclient.so.18: no version information available"

Regards,
Oleg

[David W]

Hi Oleg,

Thanks for your fast response! I have tried some of the options before posting here but could not get it fixed.
After trying some more i have decided to remove mysql completely from the server.
After removal the same message (libmysqlclient) is displayed when starting the turnserver with default settings (no mysql).

Do you have any idea what i have messed up or didn't do (most likely :x) to fix it completely? Or is this expected behavior (can't remember if it was displayed before).

Added, i aim to connect the server to an windows based webserver for use with webrtc. Can you recommend me an authentication scheme for this implementation?

Many thanks, David.


Op dinsdag 3 september 2013 18:57:59 UTC+2 schreef David W:

[Oleg Moskalenko]

David, please see my answers below in the text:

On Tue, Sep 3, 2013 at 11:07 AM, David W <davi...@gmail.com> wrote:

Hi Oleg,

Thanks for your fast response! I have tried some of the options before posting here but could not get it fixed.
After trying some more i have decided to remove mysql completely from the server.
After removal the same message (libmysqlclient) is displayed when starting the turnserver with default settings (no mysql).

The binary image turnserver is compiled with mysql support, in your case. That means that the dynamic linker will always try to find the mysql library, no matter whatever options you will provide.

 

Do you have any idea what i have messed up or didn't do (most likely :x) to fix it completely? Or is this expected behavior (can't remember if it was displayed before).

You did not mess up anything, the mysql package messed up. MySQL is not exactly a public software anymore, it belongs to Oracle now and the people are starting seeing some problems with it.

 

Added, i aim to connect the server to an windows based webserver for use with webrtc. Can you recommend me an authentication scheme for this implementation?

The easiest option I believe would be to browse the Internet, try the proposed solutions and figure it out.

If you absolutely want to try something else, then you have to eliminate mysql from the binary and to use something else (for example, PostgreSQL - it is simpler and better now than MySQL):

1) Remove all traces of mysql packages from your system (optional step).

2) Install required PostgreSQL packets (see the installation instructions).

3) Get a fresh tarballs 2.6.2.1 from the project site and untar it (see the installation instructions).

4) Run the configure script in the following way:

    $ TURN_NO_MYSQL=1 ./configure

5) Run make command.

Now you have a turnserver image that does not rely on any mysql libraries and can be used with PostgreSQL database. Setting PSQL is simpler, and the usage is easier. The performance is the same as with MySQL.

Similarly, you can do the same with Redis.

Regards,
Oleg

[David W]

Hi Oleg,

With your instructions i have setup the server to use redis & have it running smoothly :)
Serves our objective better because of the requirement of generating keys (instead of plain pwds) for the mysql/psql connections.

Thanks alot!, David.

Op dinsdag 3 september 2013 20:35:13 UTC+2 schreef Oleg Moskalenko:

[Oleg Moskalenko]

David, storing plain passwords is a less secure option. Other then that, it must be OK.

Regards,
Oleg