First report on updating

  • I have just one server to update critical problems, because there made to my local vserver and at home no e are immersed in and was ordered to find the server at my ran the update through over all customer was no longer available since I was at that time by ispCP Omega 1.0.7 was updated there is still the ispcp omega database available and the update he had with me ne new database with imscp thus created are data all not available anymore. book now understand how I get the old data ie logs and other data in the database again because not insert new imscp talk goes like this.




    I hope that you book now what you can do with it.




    see attachment

    Files

    my System :

    - Distribution: Debian | Release: 9.13 | Codename: wheezy
    - i-MSCP Version: i-MSCP 1.5.3| Build: 20181208 | Codename: Ennio Morricone
    - Plugins installed: ClamAV (v. 1.3.0), Mailgraph (v 1.1.1), OpenDKIM (v 2.0.0), SpamAssassin (v 2.0.1)
    - LetsEncrypt (v3.3.0), PhpSwitcher (v 5.0.5), RoundcubePlugins (v 2.0.2)YubiKeyAuth 1.1.0

    Edited once, last by Speddy ().


  • When i understand this correct, the old data from ispCP DB is not in the new i-MSCP DB. Correct??


    exactly right that's my problem and I can not book now simply insert the data from the simple to ispcp imscp that's not really easily.

    my System :

    - Distribution: Debian | Release: 9.13 | Codename: wheezy
    - i-MSCP Version: i-MSCP 1.5.3| Build: 20181208 | Codename: Ennio Morricone
    - Plugins installed: ClamAV (v. 1.3.0), Mailgraph (v 1.1.1), OpenDKIM (v 2.0.0), SpamAssassin (v 2.0.1)
    - LetsEncrypt (v3.3.0), PhpSwitcher (v 5.0.5), RoundcubePlugins (v 2.0.2)YubiKeyAuth 1.1.0

  • I do not know how he ended having both databases, but something was not performed as it should.
    You have 2 solutions:
    1. in /etc/imscp/imscp.conf and /etc/imscp/imscp.old.conf you set database name to ispcp and run setup.
    2. export database ispcp and import it to database imscp (clear all table before), the run setup.


  • I do not know how he ended having both databases, but something was not performed as it should.
    You have 2 solutions:
    1. in /etc/imscp/imscp.conf and /etc/imscp/imscp.old.conf you set database name to ispcp and run setup.
    2. export database ispcp and import it to database imscp (clear all table before), the run setup.



    ok I will try it soon because I need to book now to prepare for the work.

    my System :

    - Distribution: Debian | Release: 9.13 | Codename: wheezy
    - i-MSCP Version: i-MSCP 1.5.3| Build: 20181208 | Codename: Ennio Morricone
    - Plugins installed: ClamAV (v. 1.3.0), Mailgraph (v 1.1.1), OpenDKIM (v 2.0.0), SpamAssassin (v 2.0.1)
    - LetsEncrypt (v3.3.0), PhpSwitcher (v 5.0.5), RoundcubePlugins (v 2.0.2)YubiKeyAuth 1.1.0

  • badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

  • badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

  • #211 fixed in r5329 #210 fixed in r5331. God, this is too easy. More please :D:D:D Harder bugs, not typos :D:D:D

    Edited once, last by oldev01 ().

  • wait, i arrived, i will test with my openve server p^^, see you to 20 min p^^[hr]
    ISPCP 1.0.7 (copy of production server) upgrade to Trunk 5332 :


    i have only one errors at the end of setup script :


    Servers::mta::postfix::installer::buildAliasses: /etc/aliases.db: file size not a multiple of the pagesize


    and this error in mail.log
    Sep 28 18:01:42 vm3 postfix/trivial-rewrite[7082]: warning: database /etc/postfix/imscp/aliases.db is older than source file /etc/postfix/imscp/aliases
    Sep 28 18:01:42 vm3 postfix/trivial-rewrite[7082]: warning: database /etc/postfix/imscp/domains.db is older than source file /etc/postfix/imscp/domains
    Sep 28 18:01:42 vm3 postfix/trivial-rewrite[7082]: warning: database /etc/postfix/imscp/transport.db is older than source file /etc/postfix/imscp/transport

    Debian 6 with proxmox 2 - OpenVZ - KVM
    I-mscp 1.0.3.0 migrate from ispcp 1.0.7
    dovecot + zarafa + z-push + maia mail guard + apacheITK

    Edited once, last by krok ().


  • #211 fixed in r5329 #210 fixed in r5331. God, this is too easy. More please :D:D:D Harder bugs, not typos :D:D:D


    :P

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206