How did you ever setup your servers before the OS upgrades?? Within MySQL/MariaDB on your master server you need a user with root previleges (can be called root) that can connect from your slave server. And of course tcp port 3306 needs to be open on your master server. Only when that user can connect from the slave server to mysql on the master server you can continue with updating ISPConfig on the slave server and use that user during the setup. Otherwise it's useless to try. A mysql user has nothing to do with ssh. For SSH you use a normal linux user.
Did you even follow the manual tutorial when you setup multi server like this? The part you need to add access for mysql for all other servers to the master. Find that and do that, thereafter test the mysql connection from the slave to the master again.
You did not use the command I posted. You added an additional space before the "p". You used "- p" while I said to use "-p".
yes. i read a long long time ago. but error is now, after update. So: 1. Yes, i have separate [email protected] account on master database 2. Yes, i have separate [email protected] acount on master database 3. This account have grant all priveliges 4. I can connect from ns2 to master database by mysql -u root -h hosting1.mydomain.net -p 5. When i try to install ispconfig update scripts i have this error Checking ISPConfig database .. mysqlcheck: Got error: 2002: Can't connect to server on 'localhost' (115) when trying to connect OK ERROR 2002 (HY000): Can't connect to server on 'localhost' (115) Unable to call mysql command line with credentials from mysql_clientdb.conf 6. I can loginy in to mysql on ns2 to local database using mysql -u root -h localhost -p 7. But i can't login in to mysql on ns2 to local database using mysql -u root -h 127.0.0.1 -p
Ok, so your remote connect error is fixed now and this is a new error. As the error you posted before is a different error. Your problem is that you removed mariaDB during update and that#s causing the issue snow and the details in /usr/local/ispconfig/server/lib/mysql_clientdb.conf are still not correct and that#s why the updater fails. And that#s what you must fix. Check yozúr mariaDB to ensure that you did not disable networking and take care that you have a mysql root user that allows connections from 127.0.0.1 and not just localhost.
When you ping localhost on ns2, what ip you get? Should be 127.0.0.1, but my guess is it's not. Check your /etc/hosts file. On the other hand, it doesn't harm if you create a 2nd user root which may connect from 127.0.0.1 in ns2's mysql. After you checked/fixed your hosts file and/or created 2nd root user in mysql try to run the script again.
ok. after reboot slave vm i can run update script and that works. How can i check is everything is ok (dns zone) on slave vm?
Just remembered something about mysql. Connecting to localhost connects directly to the socket in /var/run and connecting to 127.0.0.1 uses a tcp connection. That could explain the error about 127.0.0.1 before. For testing your dns go to dnschecker.org If you have dnssev active you can also use dnsviz.net
