Posts by fulltilt

    V-Box testing environment - i-MSCP 1.1.1 migration to i-MSCP 1.3.1
    i-MSCP 1.1.1
    Build: 20140216



    so far I had about 40 IMSCP server migrations, maybe I'm getting too old ...
    but it does not work anymore
    - new debian 8.5 Installation
    - installed latest IMSCP 1.3.1
    - imported complete MSQL dump
    - using original imscp.conf w/ new IP address from source server
    - edited tables, server_ips, plugins, config
    - original debian.cnf (from target installation) is in use without changing the password part


    IMSCP setup stucks at step 7 of 8 for about 1 hour ..
    Running Servers::sqld::mariadb preinstall tasks
    so there is no cancel button and I have to reboot the system, but I guess the TMP tables problem strikes back again after that



    has anyone successfully tested a migration from 1.1.x
    and is there a working migration guide?


    edit:
    it seems to be a problem with mysql root user .. I can not use the password from debian.cnf (basic installation before migration) because it is different after importing mySQL dump and on the other hand if I use mysql root password from mysql Dump in debian.cnf it is not accepted.

    Files

    V-Box testing environment - i-MSCP 1.1.1 migration to i-MSCP 1.3.1
    i-MSCP 1.1.1
    Build: 20140216


    setup fails because of roundcube TMP tables error ...

    Code
    1. [ERROR] main::setupUpdateDatabase: [ERROR] Database update 237 failed: SQLSTATE[42S01]: Base table or view already exists: 1050 Table '`ispcp`.`domain_traffic_tmp2`' already exists
    2. autoinstaller::Functions::install: An error occurred while performing installation steps


    also if I drop these tmp table/s and re-run setup it has been re-created ..

    OK, autoinstaller problem was solved by changing SQL_SERVER parameter:


    #SQL_SERVER = mysql_5.5
    SQL_SERVER = mariadb_10.0


    but my imscp.conf and old.conf from original system was still overwritten during the setup, instead of using ispcp as database name it was changed to imscp
    DATABASE_NAME = imscp

    yep, seems there is a problem w/ some old imscp.conf parameter too ...

    Code
    1. Configuration file `/etc/init.d/mysql', does not exist on system.Installing new config file as you requested.Configuration file `/etc/logcheck/ignore.d.paranoid/mysql-server-5_5', does not exist on system.Installing new config file as you requested.Configuration file `/etc/logcheck/ignore.d.server/mysql-server-5_5', does not exist on system.Installing new config file as you requested.Configuration file `/etc/logcheck/ignore.d.workstation/mysql-server-5_5', does not exist on system.Installing new config file as you requested.Configuration file `/etc/logrotate.d/mysql-server', does not exist on system.Installing new config file as you requested.Configuration file `/etc/mysql/conf.d/mysqld_safe_syslog.cnf', does not exist on system.Installing new config file as you requested.Configuration file `/etc/mysql/debian-start', does not exist on system.Installing new config file as you requested.Job for mysql.service failed. See 'systemctl status mysql.service' and 'journalctl -xn' for details.invoke-rc.d: initscript mysql, action "start" failed.dpkg: error processing package mysql-server-5.5 (--configure): subprocess installed post-installation script returned error exit status 1Processing triggers for systemd (215-17+deb8u5) ...Errors were encountered while processing: mysql-server-5.5E: Sub-process /usr/bin/dpkg returned an error code (1)


    Code
    1. autoinstaller::Functions::build: An error occurred while performing build steps
    2. root@host3:/usr/local/src/imscp-1.3.1# perl /var/www/imscp/engine/setup/imscp-reconfigure -d
    3. [WARN] iMSCP::Config::FETCH: Accessing non existing config value PHP_SERVER from the /etc/imscp/imscp.conf file (see file /var/www/imscp/engine/setup/../PerlLib/Servers/httpd/apache_fcgid/installer.pm at line 256)
    4. Servers::httpd::apache_fcgid::installer::_guessPhpVariables: Use of uninitialized value $imscpConfig{"PHP_SERVER"} in pattern match (m//) at /var/www/imscp/engine/setup/../PerlLib/Servers/httpd/apache_fcgid/installer.pm line 256, <$fh> line 186.
    5. [FATAL] Servers::httpd::apache_fcgid::installer::_guessPhpVariables: Could not guess value for the `PHP_VERSION' PHP configuration parameter. at /var/www/imscp/engine/setup/../PerlLib/Servers/httpd/apache_fcgid/installer.pm line 258, <$fh> line 186.

    thanks Nuxwin,


    steps to reproduce
    - new installation (debian 8.5) of IMSCP 1.3.1
    - imported my complete database dump and editing of tables server_ips & config (also plugins table)
    - copied and edited original imscp.conf (from old server) into 1.3 imscp.conf also imscp-db-keys & debian.cnf (password)


    should I remove any imscp.old.conf files?

    Hi Nuxwin,
    it is a server migration and upgrade from 1.1.1 to 1.3.1
    a prior imscp.conf is ignored and overwriten and a different database name other than imscp is not working ...
    so a custumer rebuild from an imported database was not possible.
    Migration only works w/ 1.3.0


    Regards

    some more details ...
    it seems the script database varibale is not in use or missing, because my database is named "ispcp" and the ispcp > roundcube database does not have a cache_shared table

    V-Box testing environment - i-MSCP 1.1.1 migration to i-MSCP 1.3.1


    i-MSCP 1.1.1
    Build: 20140216


    migration fails (manually & auto mode)


    Code
    1. [ERROR] Package::Webmail::Roundcube::Installer::_updateDatabase: ERROR: [1050] Table 'cache_shared' already exists (SQL Query: CREATE TABLE `cache_shared` (
    2. `cache_key` varchar(255) /*!40101 CHARACTER SET ascii COLLATE ascii_general_ci */ NOT NULL,
    3. `created` datetime NOT NULL DEFAULT '1000-01-01 00:00:00',
    4. `data` longtext NOT NULL,
    5. INDEX `created_index` (`created`),
    6. INDEX `cache_key_index` (`cache_key`)
    7. ) /*!40000 ENGINE=INNODB */ /*!40101 CHARACTER SET utf8 COLLATE utf8_general_ci */)Error 500: Error in DDL upgrade 2013052500: [1050] Table 'cache_shared' already exists

    also the passwords for services are no longer accepted with special character f.ex. + - #
    the imscp_user should have a secure password, because of his mysql privileges ...