DragonFly, mysql, ipv6, and defaults

I am posting this so it can help someone else, someday.

I have a DragonFly-5.4 system.  I installed mysql56-server, and started it up.  By default, it listens on “*”, which meant it listens on a local socket and IPv6 ::1 – not 127.0.0.1.

2019-06-04 13:35:03 15833 [Note] IPv6 is available.
2019-06-04 13:35:03 15833 [Warning] Failed to reset IPV6_V6ONLY flag (error: 45). The server will listen to IPv6 addresses only.

I put bind_address=127.0.0.1 into my.cnf to get IPv4 loopback to work.   Local socket connections still worked either way.  I’m not using IPv6 on this machine, so this solution works in this situation.  I’m not sure my mysql decides to go only IPv6 based on a strange flag, but mysql is reliably unreliable.

3 Replies to “DragonFly, mysql, ipv6, and defaults”

  1. >> “Would that have fixed my problem?”

    Probably not since you’re most likely using MySQL for WordPress and WordPress doesn’t have an official port that works with Postgres.

    Though I do love me some Postgres.

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.