Update from 3.1 to 3.2 left inconsistent database

Discussion in 'General' started by DVLS, Apr 12, 2023.

  1. DVLS

    DVLS New Member


    last weekend I updated from 3.1 to 3.2 following the tutorial "updating-ispconfig-3-1-to-ispconfig-3-2" in the forum.
    Everything seemed fine, however a couple of days later some small issues started to appear. For instance, I was unable to modify the options tab for a site (I was trying to add custom php code), the problem was a couple of "missing fields" in the database (they were related to the jailkit). Today, the mail server was rejecting connections, because of a missing database field (related to the quota). Both errors have been temporarily (?) fixed by creating the missing fields in the DB, manually (I copied the code from the incremental updates sql files).

    I must say the errors were really hard to spot, since it was difficult to relate the failures to missing fields in the database.

    Also, I am afraid that those 2 are not the only fields missing in the database. I am pretty sure some of the sql incremental updates were not applied during the update. I don't know why nor was any error message related to that.

    Is there any "automated" way to check which other updates to the ispconfig database are missing? or a somewhat "safe" way to re-apply the incremental sql updates without breaking the whole database?

    Thank you very much.
  2. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Run a forced ISPConfig update:
    ispconfig_update.sh --force
  3. DVLS

    DVLS New Member

    I had already tried a forced update but the missing fields were not created.

    Would it be ok to "manually" inject all the incremental update sql files into the database? I mean, if some of the changes in the sql files were already applied, will the process damage the database even more?

  4. till

    till Super Moderator Staff Member ISPConfig Developer

    That's ok. You will likely receive warnings while doing that, but this will not cause any issues. But to be sure, make a backup of the dbispconfig database with phpmyadmin before you start applying the patch files.
    ahrasis likes this.

Share This Page