Hi, could you attach the error log to know why the service start failed? Le 24/03/2015 11:49, Daniel Cialdella Converti a écrit :
Today, another error
+ invoke-rc.d mysql start Job for mysql.service failed. See 'systemctl status mysql.service' and 'journalctl -xn' for details. invoke-rc.d: initscript mysql, action "start" failed. + exit 1 dpkg: error processing package mariadb-server-10.0 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: mariadb-server-10.0 E: Sub-process /usr/bin/dpkg returned an error code (1)
On Sun, Mar 15, 2015 at 2:30 PM, Daniel Cialdella Converti <dcialdella@gmail.com <mailto:dcialdella@gmail.com>> wrote:
I will check it today and add more info. Thanks
On Sun, Mar 15, 2015 at 2:12 PM, John Leach <john@johnleach.co.uk <mailto:john@johnleach.co.uk>> wrote:
On Sat, 2015-03-14 at 20:48 +0200, Otto Kekäläinen wrote: > Hello Daniel B. and others, > > I decided to write to you via the mailing list so that we are > inclusive if somebody wants to join our effort to create a solid > passwordless (Debian/Ubuntu) packaging. >
it might be worth you noting the issue I found last month - mariadb and perconadb (and maybe mysql upstream, I'm unsure) use different names for the unix socket plugin, so switching between servers with the same data directory using this plugin does not work:
https://lists.launchpad.net/maria-developers/msg08177.html
I'm unsure if Debian uses different data directories for mariadb than /var/lib/mysql. The percona packages don't, and mariadb's own packages do not.
There are plenty of other things that make switching mysql versions difficult, but the default authentication stopping working seems like it's going to affect a lot of people!
John