old web_domain entries in multi-server webserver database

Discussion in 'General' started by nhybgtvfr, Aug 23, 2018.

  1. nhybgtvfr

    nhybgtvfr Well-Known Member HowtoForge Supporter

    running 3.13 ispconfig multi-server on ubuntu 16.04.
    we have multiple webservers. previously some sites have been moved between servers by changing the server_id In the master database and then re-syncing all services on the new hosting webserver, ensuring all the website files are correctly copied to the new server website folder, then resyncing the old webserver to remove the website from it.

    that all seems to be fine, the websites work ok on the new servers, on the old server, the vhost conf in /etc/apache2/sites-available Is removed, as is the symlink in sites-enabled. so no problems with any of that.

    we're now looking at migrating all our current servers, to new servers, running ubuntu 18.04, in a new location. and I've been testing the migration
    using the migration tool, from one of our smallest webservers.
    this has bought to light that all the information for any vhosts/subdomains/aliases that were previously moved by changing the server_id's and resyncing are still in that webservers local dbispconfig database. so the migration tool tries to migrate a site that is no longer on that server.

    shouldn't the information for any websites moved in this way have been removed from web_domain, ftp_user etc tables during a resync?

    am I ok to just delete any rows containing old moved sites/users etc from these tables on the webservers local dbispconfig database?
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    No, as resync just forces the system to write out the config on that server where the server_id points to. ISPConfig does not expect that such changes can happen which you made manually in the database, basically, you brought the database from a consistent state in an inconsistent state with that. by changing the server_id of a record manually in the DB, ISPConfig loses all information that this might exist on another server as well.

    Yes, that should be ok and is required in this case as ISPConfig can not clean this up.
  3. nhybgtvfr

    nhybgtvfr Well-Known Member HowtoForge Supporter

    ok. suspected that was the case. changing the server ids and resyncing seems to be the regular suggested method to move individual sites between webservers within the same ispconfig system. I've seen this method suggested multiple times in these forums. is there a better way to do this currently then?
    cool. thought it would be, but it's safer to double check first, still need these servers to work for a while yet. :)

    thanks Till.

Share This Page