How to solve MariaDB Plugin ‘unix_socket’ is not loaded problem after upgrade to Ubuntu 15.04

How to solve MariaDB Plugin ‘unix_socket’ is not loaded problem after upgrade to Ubuntu 15.04

——————-Apr 27, 2015 @ 10:45——————-


said this will cause a problem, which may enables everyone login with root with no password.

However, as I tried, access is denied when login without password.

So this should not be a problem.

After using the script, please try mysql -uroot, and if you can login into mysql with no password, restart mysql by /etc/init.d/mysql stop && /etc/init.d/mysql start. Try mysql -uroot again, if you can still login as root with no password, then you should undo the things by login into the mysql and update user set plugin=’unix-socket’ where User=’root’;flush privileges; exit then /etc/init.d/mysql stop && /etc/init.d/mysql start


or you can also change the same part of the script to do the same thing.

If there is really something wrong with the script (such as but not limited to causing security problems or unstable, etc.), please leave a comment under here.

——————-Apr 26, 2015 @ 21:22——————-

After upgrade to Ubuntu 15.04, MariaDB always saids “MariaDB Plugin ‘unix_socket’ is not loaded”

I suffered from this problem for hours, and finally I solved it.


Thanks for sergerod  & nerdtron
I had fixed my problem.
What I did is to combine their commands.
Do nerdron’s answer first.


Here is a script, and I think it is useful.

I tested the script, so it should work.

If the script doesn’t work, then do the things below manually.

And, if the script is not functional, please report to me by commenting.


Here’s what I did and saved my MariaDB.
Stop mysql:
1. /etc/init.d/mysql stop and killall -9 mysqld

Make sure no mysqld is exist.

Run mysql with skip grants to be able to login without any password
2. mysqld_safe –skip-grant-tables &

Login as root
3. mysql -u root

then is sergerod’s.

[mysql] use mysql;
[mysql] update user set plugin=” where User=’root’;
[mysql] flush privileges;
[mysql] \q or exit

and then:

/etc/init.d/mysql stop (or service mysql stop) and killall -9 mysqld (Using killall -9 will have a better effect, as @dwi said in the commenting area.)
and start the mysql thru
service mysql start or /etc/init.d/mysql restart

and it’s all done!

19 Replies to “How to solve MariaDB Plugin ‘unix_socket’ is not loaded problem after upgrade to Ubuntu 15.04”

  1. i m working on CentOS 7..
    when i start mariadb this error comes…… sudo systemctl start mariadb.service
    Job for mariadb.service failed. See ‘systemctl status mariadb.service’ and ‘journalctl -xn’ for details.

  2. I’m having this mysql/mariadb problem in my dev environment. I tried running your script, but I can’t get access to the mysql interface. I either get the ‘unix_socket’ is not loaded or if I add “plugin-load-add =” to my my.cnf I get the “Found option without preceding group”

    Even running “mysqld_safe –skip-grant-tables &” I have the same problem. Any thoughts?

    1. That’s weird. I tried this script on many servers and no error came out. Could you please give me some screenshots? thx!

  3. Hmmm… tried it again and got
    mysqld_safe –skip-grant-tables &
    to finally run and let me login as root.

    Looks like your process fixed my problem. Thanks!

  4. I know this if off topic but I’m looking into starting my
    own weblog and was wondering what all is needed to get set
    up? I’m assuming having a blog like yours would cost a pretty
    penny? I’m not very internet smart so I’m not 100% sure.

    Any suggestions or advice would be greatly
    appreciated. Thank you

    1. Hi!
      Sorry for the late reply.

      You need to have a web server and a domain to start up your own web blog. You need to buy a web server online, then register a domain. After that, you need to do some configurations (MySQL, nginx/apache, etc) on your website in order to let your site work properly.

  5. Once more, in contrast to propriety net serving techniques, everyone can see what php is made from.
    Some individuals will argue that this makes php less secure as a result of everyone is aware of what php specific exploits

  6. it’s better if last 2 killall using “-9” option

    killall -9 mysqld mysqld_safe

    I did that because I have plenty “InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.” errors

Leave a Reply

Your email address will not be published. Required fields are marked *