Update to 1.1.9 - main::setupUpdateDatabase - Database update 176 failed

zddr · May 26th 2014

While upgrading to 1.1.9 the installer fails with the error message seen in the screenshot I attached (main::setupUpdateDatabase: [ERROR] Database update failed: Database update 176
failed.).

The version I upgraded from was propably the following:
i-MSCP Git Master
Build: 20131121
Codename: Eagle

I'm not sure though. The upgrade was on Debian Wheezy.

gOOvER · May 26th 2014

Git Master?

zddr · May 26th 2014

Quote from gOOvER

Git Master?

I upgraded from Git-Master to 1.1.9 release, is that what you're asking?

gOOvER · May 26th 2014

We have since a long Time only Git Stable branch.. thats why i asked

zddr · May 26th 2014

Quote from gOOvER

We have since a long Time only Git Stable branch.. thats why i asked

Well, it's quite an old installation ;). I took another look and this is the version I updated from.
2013-11-21 - RELEASE i-MSCP 1.1.0-rc4.7

**Nuxwin** · May 26th 2014

@zddr

Hello ;

You have upgraded from a very old version. I'll check that issues in next minutes.

**Nuxwin** · May 26th 2014

Re;

Bug found:

In the downloaded archive, edit the gui/library/iMSCP/Update/Database.php file and change the r176() method by:

PHP

protected function r176()
{
return array(
// sql_database table update
$this->changeColumn('sql_database', 'domain_id', 'domain_id INT(10) UNSIGNED NOT NULL'),
$this->changeColumn(
'sql_database', 'sqld_name', 'sqld_name VARCHAR(64) CHARACTER SET utf8 COLLATE utf8_unicode_ci NOT NULL'
),
// sql_user table update
$this->changeColumn('sql_user', 'sqld_id', 'sqld_id INT(10) UNSIGNED NOT NULL'),
$this->changeColumn(
'sql_user', 'sqlu_name', 'sqlu_name VARCHAR(16) CHARACTER SET utf8 COLLATE utf8_unicode_ci NOT NULL'
),
$this->changeColumn(
'sql_user', 'sqlu_pass', 'sqlu_pass VARCHAR(64) CHARACTER SET utf8 COLLATE utf8_unicode_ci NOT NULL'
),
$this->addColumn(
'sql_user',
'sqlu_host',
'VARCHAR(255) CHARACTER SET utf8 COLLATE utf8_unicode_ci NOT NULL AFTER sqlu_name'
),
$this->addIndex('sql_user', 'sqlu_name', 'index', 'sqlu_name'),
$this->addIndex('sql_user', 'sqlu_host', 'index', 'sqlu_host')
);
}

Display More

Once it's done, run the installer again.

**Nuxwin** · May 26th 2014

Quote from gOOvER

We have since a long Time only Git Stable branch.. thats why i asked

Well, normally, master branch is pointing to the stable branch. I means, the stable branch is the default branch since some weeks. To resume, if you run

Shell-Script

# git clone https://github.com/i-MSCP/imscp.git

you'll be on the stable branch directly.

Shell-Script

nuxwin@dev:~/Bureau$ mkdir test
nuxwin@dev:~/Bureau$ cd test/
nuxwin@dev:~/Bureau/test$ git clone https://github.com/i-MSCP/imscp.git
Cloning into 'imscp'...
remote: Reusing existing pack: 148318, done.
remote: Counting objects: 788, done.
remote: Compressing objects: 100% (500/500), done.
remote: Total 149106 (delta 359), reused 0 (delta 0)
Receiving objects: 100% (149106/149106), 145.26 MiB | 536 KiB/s, done.
Resolving deltas: 100% (102429/102429), done.
nuxwin@dev:~/Bureau/test$ cd imscp/
nuxwin@dev:~/Bureau/test/imscp$ git status
# On branch stable
nothing to commit (working directory clean)
nuxwin@dev:~/Bureau/test/imscp$

Display More

zddr · May 26th 2014

Quote from Nuxwin

Re;

Bug found:

In the downloaded archive, edit the gui/library/iMSCP/Update/Database.php file and change the r176() method by:

PHP

...

Once it's done, run the installer again.

Display More

Thanks for your quick help, this time the installer got further. It's now stuck at the following error:

Code

[ERROR]
main::setupRebuildCustomerFiles:
[FATAL ERROR]
iMSCP::Debug::__ANON__: Can't locate iMSCP/Templator.pm in @INC (@INC contains:
/var/www/imscp/engine /var/www/imscp/engine/PerlLib
/var/www/imscp/engine/PerlVendor /etc/perl /usr/local/lib/perl/5.14.2
/usr/local/share/perl/5.14.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.14
/usr/share/perl/5.14 /usr/local/lib/site_perl .) at
/var/www/imscp/engine/Plugins/Mailgraph.pm line 620, <GEN2> line 1.
[ERROR]

Display More

**Nuxwin** · May 26th 2014

@zddr

Re;

It's not a bug from i-MSCP... You must disable the mailgraph plugin which is not compatible with that version of i-MSCP, run the installer again and after, update the mailgraph plugin to latest version (as available in our plugin store).

How to process

Connect to MySQL and run the following query:

SQL

# mysql -u root -p<password>
> use imscp;
> UPDATE plugin SET plugin_status = 'disabled';
> quit

Here I disable all plugins.

BTW: Next time, open a new thread because this is another problem.

Thanks

Update to 1.1.9 - main::setupUpdateDatabase - Database update 176 failed

Share

Daily visitors