Mysql server won't start after changing bind-address

Asked Jul 13 '21 at 16:38

Active Jul 13 '21 at 16:38

Viewed 672 times

I have two dropplets at digitalocean, one is for http server and another is for database.

In mysql config /etc/mysql/mysql.conf.d/mysqld.cnf I have set bind-address to digitalocean private ip and everithing was working without the errors.

After server was rebooted, mysql failed to start. After I change bind-address to 127.0.0.1 it was working again, but my php app could not connect to the database.

Just to be clear, this kind of set up was working fine atfer server reboot.

asked Jul 13 '21 at 16:38

sitemapxml

1

Are you sure the private IP was the same after reboot? – Tero Kilkanen Jul 13 '21 at 16:43
No, it was automatically changed to 127.0.0.1 – sitemapxml Jul 13 '21 at 17:01
So I have changed it again, mysql failed to start, change back to localhost and it is working, except I have no access to database. This was a bug in old mysql versions, but I use mysql 8.0.25 – sitemapxml Jul 13 '21 at 17:04
`127.0.0.1` is the localhost IP address and is not set by DHCP. Use `ip a` to find out the IP that your server picked up on reboot. – doneal24 Jul 13 '21 at 17:43
Or you can set the bind-address to `0.0.0.0` to listen on all IPv4 interfaces. – doneal24 Jul 13 '21 at 17:45
I tried, but whatever ip I set except `127.0.0.1` it throws an error. It seems as a bug. – sitemapxml Jul 13 '21 at 19:59

Mysql server won't start after changing bind-address

0 Answers0