Horde seems to have cached deleted contacts... how can I clear them?

Alexander Haensch alexander.haensch at ipc.uni-tuebingen.de
Tue Jan 24 14:42:05 CET 2012


Hi Greg,
you are welcome. I feel, that the webmail responds much better with the
recreated horde.db.
We should file a bug, to minimize the hassle for new users.

greets,
Alexander

On 01/24/2012 02:33 PM, Greg Conway wrote:
> Hi Alexander,
>
> Many thanks for your assistance. I recreated all the missing Horde databases
> last night, and following that my cached Horde contacts have gone, along
> with all the errors in the log files.
>
> Well, most of them! :)
>
> Thanks again,
>
> Greg.
>
> -----Original Message-----
> From: kolab-users-bounces at kolab.org [mailto:kolab-users-bounces at kolab.org]
> On Behalf Of Alexander Haensch
> Sent: 23 January 2012 08:42
> To: kolab-users at kolab.org; Greg Conway
> Subject: Re: Horde seems to have cached deleted contacts... how can I clear
> them?
>
>
> Hi Greg,
> We had the same error here. Finally i recreated the horde.db with the sql
> script in :
>
> /kolab/var/kolab/www/client/scripts/sql/create.sql
>
> The errors are gone now and it feels a little bit faster now. Everything
> seems to work.
>
>
> Alexander
>
>
> On 01/23/2012 12:50 AM, Greg Conway wrote:
>> Hi Alexander,
>>
>> To answer your first point last... yes there is an error (or rather, 
>> lots of
>> errors!) in the horde.log file -
>>
>> Jan 22 23:21:35 HORDE [error] [turba] DB Error: no such table: 1 ** 
>> SELECT * FROM horde_histories WHERE object_uid = 
>>
> 'turba:user at domain.com:20120119145629.13264mqjjnlzq4nh at k3p0.site.domain.com'
>> [nativecode=sqlite_query() [<a
>> href='function.sqlite-query'>function.sqlite-query</a>]: no such table:
>> horde_histories] [pid 27439 on line 247 of 
>> "/kolab/lib/php/Horde/History.php"]
>>
>> So I spent a while working out that we're using SQlite (not MySQL) 
>> here, and then how to interrogate the tables. And this is the 
>> interesting part -
>>
>> On this (2.3.4) kolab server I have only these tables inside horde.db 
>> -
>>
>> horde_alarms          horde_syncml_anchors
>> horde_perms           horde_syncml_map
>>
>> Whereas on my other (2.2.4) kolab server I have all these tables -
>>
>> horde_alarms               ingo_shares
>> horde_cache                ingo_shares_groups
>> horde_datatree             ingo_shares_users
>> horde_datatree_attributes  ingo_spam
>> horde_groups               ingo_vacations
>> horde_groups_members       kronolith_events
>> horde_histories            kronolith_shares
>> horde_histories_seq        kronolith_shares_groups
>> horde_locks                kronolith_shares_users
>> horde_perms                kronolith_storage
>> horde_prefs                mnemo_memos
>> horde_sessionhandler       mnemo_shares
>> horde_signups              mnemo_shares_groups
>> horde_syncml_anchors       mnemo_shares_users
>> horde_syncml_map           nag_shares
>> horde_tokens               nag_shares_groups
>> horde_users                nag_shares_users
>> horde_vfs                  nag_tasks
>> imp_sentmail               turba_objects
>> ingo_forwards              turba_shares
>> ingo_lists                 turba_shares_groups
>> ingo_rules                 turba_shares_users
>>
>> So I guess I'm missing a stack of tables! Could somebody else with a 
>> 2.3.4 server please just confirm that I am missing all these tables, 
>> and it's not just that the later version only needs a few tables?
>>
>> Presuming I am, can I just run all the horde SQL scripts within 
>> /kolab/var/kolab/www/client/scripts/sql to recreate any missing 
>> tables? Will this affect any existing data or cause any problems?
>>
>> And how exactly do I do that?! I presume something like this...
>>
>> /kolab/bin/sqlite /kolab/var/kolab/webclient_data/storage/horde.db < 
>> script.sql
>>
>> ...or is there a master script for Horde somewhere that would run all 
>> the required scripts and put everything in the right place. Presumably 
>> the installer would have run such a script initially... is there in 
>> fact an install log file somewhere that I could examine to see what 
>> went wrong initially?
>>
>> Anyway, thanks for the help in getting me this far, and thanks also 
>> for the info on caching, but I'm hoping if I solve the missing tables 
>> error then everything will come right after that!
>>
>> Regards,
>>
>> Greg.
>>
>>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>


-- 
Dipl. Chem. Alexander Haensch
AG Weimar
Institute of Theoretical and Physical Chemistry
Eberhard Karls University Tübingen
Auf der Morgenstelle 15
72076 Tuebingen
Germany
Tel: +49(0) 7071 2978768
Fax: +49(0) 7071 295960




More information about the users mailing list