Code: root@ns3:~# ispconfig_update.sh --force -------------------------------------------------------------------------------- _____ ___________ _____ __ _ |_ _/ ___| ___ \ / __ \ / _(_) | | \ `--.| |_/ / | / \/ ___ _ __ | |_ _ __ _ | | `--. \ __/ | | / _ \| '_ \| _| |/ _` | _| |_/\__/ / | | \__/\ (_) | | | | | | | (_| | \___/\____/\_| \____/\___/|_| |_|_| |_|\__, | __/ | |___/ -------------------------------------------------------------------------------- >> Update Please choose the update method. For production systems select 'stable'. WARNING: The update from GIT is only for development systems and may break your current setup. Do not use the GIT version on servers that host any live websites! Note: On Multiserver systems, enable maintenance mode and update your master server first. Then update all slave servers, and disable maintenance mode when all servers are updated. Select update method (stable,nightly,git-develop) [stable]: Downloading ISPConfig update. Unpacking ISPConfig update. -------------------------------------------------------------------------------- _____ ___________ _____ __ _ ____ |_ _/ ___| ___ \ / __ \ / _(_) /__ \ | | \ `--.| |_/ / | / \/ ___ _ __ | |_ _ __ _ _/ / | | `--. \ __/ | | / _ \| '_ \| _| |/ _` | |_ | _| |_/\__/ / | | \__/\ (_) | | | | | | | (_| | ___\ \ \___/\____/\_| \____/\___/|_| |_|_| |_|\__, | \____/ __/ | |___/ -------------------------------------------------------------------------------- >> Update Operating System: Debian 10.0 (Buster) or compatible This application will update ISPConfig 3 on your server. Shall the script create a ISPConfig backup in /var/backup/ now? (yes,no) [yes]: Creating backup of "/usr/local/ispconfig" directory... Creating backup of "/etc" directory... MySQL master server hostname [pswwwnz1.primesoft.co.nz]: MySQL master server port [3306]: MySQL master server root username [root]: MySQL master server root password []: abcdefg MySQL master server database name [dbispconfig]: Checking ISPConfig database .. OK Starting incremental database update. Loading SQL patch file: /tmp/update_runner.sh.iklEf4xZHa/install/sql/incremental/upd_dev_collection.sql Reconfigure Permissions in master database? (yes,no) [no]: yes Service 'web_server' has been detected (currently disabled) do you want to enable and configure it? (yes,no) [no]: WARNING: If ISPConfig-Interface (Webfrontend) is installed on this Server we will configure the Web Server anyways but will not enable it in ISPConfig. Service 'db_server' has been detected (currently disabled) do you want to enable and configure it? (yes,no) [no]: Reconfigure Services? (yes,no,selected) [yes]: Configuring BIND Configuring Bastille Firewall Configuring Database Updating ISPConfig Do you want to create SSL certs for your server? (y,n) [y]: n Reconfigure Crontab? (yes,no) [yes]: Updating Crontab Restarting services ... Update finished. root@ns3:~#
No, it looks OK. Did you grant the root MySQL user for this server all rights on the master? How did you install the system?
It was installed in 2012 and has been upgraded ever since, but as I recall granting all rights to each slave root user was part of it and I have no issues logging in as root to the master and doing anything, it is the ispcsrv11 user that seems to have the wrong permissions, not capable of doing an insert. I'll manually grant the user more permissions but I was hoping that reconfigure permissions option would work in the upgrade.
Yes, that should work through the update script, and it does work here. I have not seen any other reports about it either.
Yes I am pretty certain that it relates to the move to a different subnet and a unique quirk of how that network is formed by my isp. I will consult with them. I may have to have this dns server back in the original subnet but that doesn’t provide the resilience of being in a seperate datacentre
I suspect that in that case there is no root@newip user. See https://www.howtoforge.com/tutorial...-the-remote-mysql-users-for-our-slave-servers
Ok, for anyone who accidentally stumbled across this thread. The reason the above didn't work was because of a masquearade rule in my router which was made inappropriate by my reconfiguration of location of ispconfig servers. For the very rare reference to anyone else not being able to identify why server update setting seem stuck with no obvious clues coming from debug, well perhaps look to your router. Thanks for the help guys.
