What about MariaDB 10.0? I don't see a "libs" package.
On 04/09/2015 11:54 AM, Gilles Gagniard wrote:
Hello,
I think this is actually linked to the recent mariadb upgrade, not because of
mariadb-server, but because of mariadb-libs ie the client side.
Here is where it fails (there is a "could not allocate MySQL4 connection" error
in the logs) :
https://github.com/inverse-inc/sope/blob/6452ca58fbd7ee4850ae06bd7228a4feeb21441b/sope-gdl1/MySQL/MySQL4Channel.m#L143
mysql_init() is just doing some client-side initialization (such as setting up
threads on so on), which fails.
No actual connection attempt has been done yet ! This is done at a later stage
by mysql_real_connect().
So here is the list of workarounds that can be ruled out :
- This is not related to credentials or privileges or actual database content
(we have not even tried to connect to the mysql server at this stage)
- Changing the server to older/newer mariadb or even mysql cannot help with
this issue (same reason than above)
The only thing that could actually be tried is to downgrade mariadb-libs to
5.5.35 which is the client sogo uses.
Gilles
Le Jeudi 9 Avril 2015 16:28 CEST, Alessandro Briosi <[email protected]> a écrit:
Il 09/04/2015 15:03, Jeroen Beerstra ha scritto:
The only thing I haven't tried is mysql, postgresql and mariadb both have the
same problem. So I don't think it's related to changes in recent mariadb
Just a wild guess here (or a long shot if you prefere :P ).
Could it be that the name resolution is not pointing to the correct
host, or that the daemons for some reason are listening only on
localhost (127.0.0.1) so the connection fails?
Have you tried with the host IP?
Ciao.
Alessandro
--
[email protected]
https://inverse.ca/sogo/lists
--
[email protected]
https://inverse.ca/sogo/lists
