[horde] Horde suddenly started half-working

[Louis-Philippe Allard]

  Quoting Michael J Rubinsky <mrubinsk at horde.org>:

> Quoting Louis-Philippe Allard <lp.allard.1 at gmail.com>:
>
>> Mike,  the horde-histories table has only one field called history_id
and
>> 7283 entries in it ... Im not a SQL Guru or anything like that, so
please
>> provide the proper SQL commands to provide what you need. The table
>> definitely exists..
>>
>> I can try to recreate the table but should I?
>
> Well, if that is truly the only field in that table, the table is
> useless. I would be more concerned about WHY it only contains that one
> column though...
>
> --
> mike
> The Horde Project
> http://www.horde.org
> https://www.facebook.com/hordeprojecthttps://www.twitter.com/hordeproject

Yes this is the only table...

I ran horde-db-migrate.  The output was:

[root at centos-productive]# horde-db-migrate
[  INFO  ] Migrating DB up.
[  INFO  ] Current imp schema version: 3
[  INFO  ] Ending imp schema version: 3
[  INFO  ] Current ingo schema version: 6
[  INFO  ] Ending ingo schema version: 6
[  INFO  ] Current kronolith schema version: 22
[  INFO  ] Ending kronolith schema version: 22
[  INFO  ] Current turba schema version: 11
[  INFO  ] Ending turba schema version: 11
[  INFO  ] Current nag schema version: 13
[  INFO  ] Ending nag schema version: 13
[  INFO  ] Current mnemo schema version: 7
[  INFO  ] Ending mnemo schema version: 7
[  INFO  ] Current trean schema version: 5
[  INFO  ] Ending trean schema version: 5
[  INFO  ] Current gollem schema version: 3
[  INFO  ] Ending gollem schema version: 3
[  INFO  ] Current content schema version: 2
[  INFO  ] Ending content schema version: 2
[  INFO  ] Current Horde_ActiveSync schema version: 21
[  INFO  ] Ending Horde_ActiveSync schema version: 21
[  INFO  ] Current Horde_Alarm schema version: 2
[  INFO  ] Ending Horde_Alarm schema version: 2
[  INFO  ] Current Horde_Auth schema version: 1
[  INFO  ] Ending Horde_Auth schema vaersion: 1
[  INFO  ] Current Horde_Cache schema version: 2
[  INFO  ] Ending Horde_Cache schema version: 2
[  INFO  ] Current Horde_Core schema version: 1
[  INFO  ] Ending Horde_Core schema version: 1
[  INFO  ] Current Horde_Dav schema version: 2
[  INFO  ] Ending Horde_Dav schema version: 2
[  INFO  ] Current Horde_Group schema version: 3
[  INFO  ] Ending Horde_Group schema version: 3
[  INFO  ] Current Horde_History schema version: 6
[  INFO  ] Ending Horde_History schema version: 6
[  INFO  ] Current Horde_Imap_Client schema version: 2
[  INFO  ] Ending Horde_Imap_Client schema version: 2
[  INFO  ] Current Horde_Lock schema version: 3
[  INFO  ] Ending Horde_Lock schema version: 3
[  INFO  ] Current Horde_Perms schema version: 2
[  INFO  ] Ending Horde_Perms schema version: 2
[  INFO  ] Current Horde_Prefs schema version: 3
[  INFO  ] Ending Horde_Prefs schema version: 3
[  INFO  ] Current Horde_Queue schema version: 1
[  INFO  ] Ending Horde_Queue schema version: 1
[  INFO  ] Current Horde_SessionHandler schema version: 2
[  INFO  ] Ending Horde_SessionHandler schema version: 2
[  INFO  ] Current Horde_SyncMl schema version: 1
[  INFO  ] Ending Horde_SyncMl schema version: 1
[  INFO  ] Current Horde_Token schema version: 1
[  INFO  ] Ending Horde_Token schema version: 1
[  INFO  ] Current Horde_Vfs schema version: 4
[  INFO  ] Ending Horde_Vfs schema version: 4

Table has NOT changed after this operation.  Is there a way to destroy the
table and recreate it fresh?  Obviously something is wrong....
-- 
Louis-Philippe Allard
lp.allard.1 at gmail.com
Sent from Horde Groupware - GNU/Linux