Kolab-3. DB error

[Carpenter, Troy]

On 2015-02-03 12:17 pm, Carpenter, Troy wrote:
> On 2015-02-01 4:22 pm, Daniel Hoffend wrote:
>> The kolab_cache_contact table belongs to the roundcube database.
>> 
>> Usually you shouldn't need to apply those patches manually. This
>> is usually done by the upgrade script that gets executed during
>> an installation or package upgrade.
>> 
>> Btw. Your error messages is about the cache_messages table and
>> not the kolab_cache_contact table. It looks like the database
>> structure of your default roundcube installation is out-of-date.
>> 
>> Maybe you would like to execute a command like this:
>> 
>>     /usr/share/roundcubemail/bin/updatedb.sh \
>>         --dir /usr/share/doc/roundcubemail/SQL/ \
>>         --package roundcube
>> 
>> But keep in mind: Usually this should have happend during the
>> yum/apt-get upgrade command unless you've patched or installed
>> roundcube yourself.
> 
> 
> Sidetrack, but since it's related to DB errors, I thought I would ask.
> 
> I have been getting a DB error every time I update Roundcube or any
> other components.  So I tried the command above (with a slight
> modification listed below) and here are the results:
> 
> [root at mail etc]# /usr/share/roundcubemail/bin/updatedb.sh --dir
> /usr/share/doc/roundcubemail-1.1/SQL/ --package roundcube
> Updating database schema (2013052500)... [FAILED]
> ERROR: Error in DDL upgrade 2013052500: [1050] Table 'cache_shared'
> already exists
> 
> I see the first error all the time.  There are subsequent schemas in
> that SQL directory, but I'm guessing they are not applied since I'm
> getting the error.  How do I troubleshoot and fix this problem?

Ok, when you finally send an email about something (like this), you 
usually try something to correct it afterwards.  So I disabled the 
2013052500 schema, ran again and got a duplicate column ('expires') 
error for schema 2013061000.  I disabled that one and 2014042900 applied 
and said it was OK.  Don't know why the schema got out of sync, but I'm 
guessing

Now I need to go back to the 2013061000 and see if all those changes 
have already been applied.

-- 
Troy Carpenter
troy at carpenter dot cx