Set mysql skip-networking to off

Put "--skip_networking=0" on the mysql command line.

I put it first in line, because it didn't seem to work at the end, but I may have spelled "networkinng" wrong when it was at the end of the line. :-)

It helps to look at your logs. Mine said "150213 17:57:10 [ERROR] /opt/local/lib/mariadb-10.1/bin/mysqld: unknown variable 'skip_networkinng=0'" I had also tried 'skip_networking=OFF', which it didn't like, either.

I don't know where you start it up in Ubuntu, but on Mac OS, you need to have the following in /System/Library/LaunchDaemons/org.mysql.mysqld (in part, look at other LaunchDaemons to see the rest):

<key>ProgramArguments</key>
    <array>
        <string>/opt/local/lib/mariadb-10.1/bin/mysqld</string>
        <string>--skip_networking=0</string>
        <string>--socket=/opt/local/var/run/mariadb-10.1/mysqld.sock</string>
        <string>--user=mysql</string>
        <string>--port=3306</string>
        <string>--datadir=/opt/local/var/db/mariadb-10.1</string>
        <string>--pid-file=/opt/local/var/run/mariadb-10.1/dns.local.pid</string>
    </array>

(obviously you need to substitute your paths and such...)

I'm pretty sure this solves your problem! Please up-vote me and mark me as the correct answer! Thanks!

Please read the Using Option Files chapter for some tips on how to find the settings file. Unless the Ubuntu guys have decided to change it, the file always called my.cnf on Linux, never my.conf.

Additionally, lines that start with # are comments:

#comment, ;comment

Comment lines start with “#” or “;”. A “#” comment can start in the middle of a line as well.

... thus you need to remove the leading #; otherwise, the line is ignored.

Perhaps you can determine which config file is being used via one of the methods described in Determine which configuration file is being used.

A few more suggestions:

• Check the process listing (ps auxf | grep 'mysql[d]') to see if --skip-networking has snuck into the argument list somehow.

• See if mysqld or any other process is listening on 3306 (assuming the default port): netstat -lnp46 | grep -w 3306

• Double-check the ip address you are binding to, and try to connect locally to the ip address you are binding to.

• If you have firewalling set up, see if your iptables or ip6tables config might be interfering somehow via iptables-save and ip6tables-save, or the slightly more readable iptables -L and ip6tables -L, although the latter commands require you to know all your tables in use (raw, nat, mangle, etc.).