Compatibility problem between upgraded master and fresh installed web server
I have a multi server installation that I recently upgraded to 3.2
A few days later I added a new web server. Installed directly in version 3.2
I noticed initially that the cron jobs on the new server were not running at all.
The problem was that the web_domain table was not populated with the sites for that server. If fact it was completely empty.
After enabling the debug mode for the new server I noticed the following in the logs.
13.11.2020-11:31 - WARNING - Falsche Anfrage / Wrong QuerySQL-Query = REPLACE INTO
web_domain ..... -> 1054 (Unknown column 'fastcgi_php_version' in 'field list')
The column existed in the master database. I added the column manually and now everything works perfectly.
Note that existing slave web servers that were upgraded to version 3.2 worked perfectly since the column existed in their database.
The expected behaviour I suppose is that both installations (upgraded from previous version and fresh installation) should be compatible and work, since no customizations existed in any of them. The column should either be created in the new database (for backwards compatibility maybe) or it should be taken out from the master database during the upgrade process if no longer needed. If for any reason you don't want to remove the column from the master database, then you could just ignore it during the sync process.
More importantly, I believe that this kind of problem should be reported in the System-log area as ERROR without the need to enable debugging.
Server OS: ubuntu
Server OS version: 20.04.1 LTS ISPConfig version: 3.2