Mysql/MariaDB, quirky restart after failure
Posted: 21. January 2019 17:07
hi
Have a quirky problem, occasionally after a server reboot(mandated monthly restart of the VM ) or once when we had a full disk issue the mysqld process starts but on port+1 i.e. 3307 instead of 3306. I've checked using netstat and lsof and nothing else appears to be holding 3306 so why is it falling back one port? I can't see anything in config that would suggest why this would happen?
I've got round for now that after restart I have a script that pulls the port # from the process and then updates my sites php config automatically but its a fudge and I'd rather work out why.
Thanks in advance!
Have a quirky problem, occasionally after a server reboot(mandated monthly restart of the VM ) or once when we had a full disk issue the mysqld process starts but on port+1 i.e. 3307 instead of 3306. I've checked using netstat and lsof and nothing else appears to be holding 3306 so why is it falling back one port? I can't see anything in config that would suggest why this would happen?
I've got round for now that after restart I have a script that pulls the port # from the process and then updates my sites php config automatically but its a fudge and I'd rather work out why.
Thanks in advance!