failed to install Roundcube

[yak983]

Hi, I have a problem updating Roundcube. The issue is as follows:


RoundCube 1.6.9 to 1.6.11 update is available.

Updating RoundCube
download_cached: using cached '/usr/local/directadmin/custombuild/cache/roundcubemail-1.6.11-complete.tar.gz' file
updating database user da_roundcube@localhost password
Checking for database schema updates...
Updating database schema (2018021600)... [FAILED]
ERROR: Error in DDL upgrade 2018021600: [1050] Table 'filestore' already exists
command_roundcube: failed to compile '/usr/local/directadmin/custombuild/cache/roundcubemail-1.6.11-complete.tar.gz' inside '/usr/local/directadmin/custombuild/tmp/tmp.hgUR8y9QTv.roundcubemail-1.6.11-complete.tar.gz'
failed to install Roundcube

Does anyone have any advice or suggestions?

 

[Richard G]

Just to be sure, you checked the /var/www/html and roundcube itself to verify nothing else has already updated Roundcube to 1.6.11?

 

[yak983]

Just to be sure, you checked the /var/www/html and roundcube itself to verify nothing else has already updated Roundcube to 1.6.11?

i have check and it's not upgraded

# grep 'RCMAIL_VERSION' /var/www/html/roundcube/program/include/iniset.php
define('RCMAIL_VERSION', '1.6.9');

I also verified the filestore table in the database — it exists but is completely empty (no rows).
If the installation process fails at that step, would it be safe to drop the filestore table and try the update again?

 

[Richard G]

would it be safe to drop the filestore table and try the update again?

I can't guarantee that this can be safe to drop. I would create a backup first anyway.
But since the table is empty at this moment as far a content goes, you won't loose anything in that specific table.
It most likely will get re-created anyway after it drops because it's announcing a duplicate.
But as said, backup first and try on your own risk.

Just to be sure, from a couple of years ago I found the contents of the filestore table of Roundcube on the net. I'm no database guru, but maybe you can use it to your benefit if rebuild is needed.

-- Table structure for table `filestore`

CREATE TABLE `filestore` (
 `file_id` int(10) UNSIGNED NOT NULL AUTO_INCREMENT,
 `user_id` int(10) UNSIGNED NOT NULL,
 `context` varchar(32) NOT NULL,
 `filename` varchar(128) NOT NULL,
 `mtime` int(10) NOT NULL,
 `data` longtext NOT NULL,
 PRIMARY KEY (`file_id`),
 CONSTRAINT `user_id_fk_filestore` FOREIGN KEY (`user_id`)
   REFERENCES `users` (`user_id`) ON DELETE CASCADE ON UPDATE CASCADE,
 UNIQUE `uniqueness` (`user_id`, `context`, `filename`)
) ROW_FORMAT=DYNAMIC ENGINE=INNODB CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;