So I just had the terrible to idea to try and switch from mysql to
mariadb (drop-in replacement, yeah sure...) and hit this bug.
After a couple of hours trying different things, I went back to mysql
5.7 and used the solution in #29. I think we should stop calling mariadb
a drop-in replacement, at
Sorry for the double-post, but I have to correct my previous statement. #29 did
not help.
What helped was logging in via the mysql console as debian-sys-maint and doing
the following:
use mysql;
update user set plugin='' where User='root';
\q
After restarting the service using "service mysql re
This happened to me after installing mariadb, deciding to go back to
mysqld and installing mysqld again. The fix by Markus (maier-m) (#29,
2015-04-30) solved the problem for me. Thank you very much! :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Well, I could help on the documentation part (although I have very
little experience with alternatives) but I think we should tackle this
issue somewhere else: we're currently implementing new config files and
the user sees an error message which does not guide him to the config
file immediately. N
** Summary changed:
- Cannot access mariadb after upgrading to Ubuntu 15.04: Plugin 'unix_socket'
is not loaded
+ Migration of custom configuration to my.cnf.migrated is not explicit enough
** Changed in: mariadb-10.0 (Ubuntu)
Status: Confirmed => Triaged
** Changed in: mariadb-10.0 (Ub
