Hi, here is the scenario: server1 -> master server with web and database server2 -> slave with mail server server3 -> new master server (server1 replacement). I bought the "migration toolkit" and run to copy data from server1 to server 3 (after I configured it and installed ispconfig). On server 2 I launched ispconfig_update.sh --force and reconfigured master (in my ispconfig "config.inc.php" I have now server3). My new master (server3) can't communicate with server2. If I make a change on server3 to a mailbox, doesn't trigger the update (the red dot). If I make a change instead on website on server 3, it trigger the update. Any suggestion? Thank you, Marco.
This most likely means that server2 is not able to connect to mysql on server. Check /etc/hosts file on server2 and server 3, they must contain the correct hostnames and IP addresses from server2 and 3. Then rerun the ispconfig update on server2 and let it configure permissions in master database again.
In my /etc/hosts I have already set the ip and hostname. On slave when I launch: /usr/local/ispconfig/server/server.sh I get "finished server.php." with no error. I don't understand why on new master server the update don't trigger the red dot with number. Is it linked to server2 or it's something due to master settings?
Take a look into the dbispconfig database on the new master server, which is the highest datalog_id in sys_datalog table? And which number is in the field 'updated' for server 2 in the table 'server'.
So I updated the server table id with the same of sys_datalog table. Now It trigger the update (red dot) but it's stuck. No entries for server2 in ispconfig log.
