[horde] Successful install, cannot login (Fatal error) Suspect outdated database schemas - How to upgrade from CLI?

[Jan Schneider]

Zitat von Louis-Philippe Allard <lp.allard.1 at gmail.com>:

> Hello!
>
> I have a "horde-db-migrate" in /usr/bin/horde-db-migrate  which I already
> ran.  Apparently all of my schemas were already up to date.   What else
> could explain this problem?
>
> Output of horde-db-migrate
>
> [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 version: 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
>
>
> Error when trying to login:
>
> A fatal error has occurred
> QUERY FAILED: Unknown column 'object_uid' in 'where clause' SELECT * FROM
> horde_histories WHERE object_uid = 'lp.allard.1 at gmail.com@logins.failed'
> Details have been logged for the administrator.
>
>
> On Mon, Sep 1, 2014 at 3:21 AM, Patrick De Zordo <patrick at spamreducer.eu>
> wrote:
>
>> To bring the DB up-to-date you have to issue:
>>
>> "horde/horde/bin/horde-db-migrate"
>>
>> Cheers!
>>
>> ---------------------------------------------------------------------
>> Mit freundlichen Grüßen / Distinti saluti / Kind regards
>> De Zordo Patrick
>> patrick at spamreducer.eu
>>
>> > -----Ursprüngliche Nachricht-----
>> > Von: horde [mailto:horde-bounces at lists.horde.org] Im Auftrag von Louis-
>> > Philippe Allard
>> > Gesendet: Sonntag, 31. August 2014 23:42
>> > An: horde at lists.horde.org
>> > Betreff: [horde] Successful install, cannot login (Fatal error) Suspect
>> outdated
>> > database schemas - How to upgrade from CLI?
>> >
>> > Hello
>> >
>> > So I just rebuilt a CentOS 6.5 virtual server and installed Horde
>> following
>> > the instructions available on the horde/Install webpage.
>> >
>> > All went well.  Then I configured the general settings in
>> > horde/config/confi.php and imp/config/backends.php to use Gmail as the
>> > login backend.
>> >
>> > I can access Horde's login page but I cannot login.  Whatever
>> credentials I
>> > try, I immediately get a white page saying
>> >
>> > A fatal error has occurredQUERY FAILED: Unknown column 'object_uid' in
>> > 'where clause' DELETE FROM horde_histories WHERE object_uid IN
>> > ('lp.allard.1 at gmail.com@logins.failed')Details have been logged for the
>> > administrator.
>> >
>> >
>> > Reading this message I suspect my horde database is out of date and needs
>> > updating.  As a matter of fact, the last time I used horde was about 4
>> > months ago (cant remember the exact horde release I was running back then
>> > but definitekly not the current one.
>> >
>> >
>> > Its worth mentioning that I am reusing an existing DB (mysqli) from my
>> > previous install.
>> >
>> >
>> > How do I update the DB schemas from the command line?  SInce I cannot
>> > login
>> > as admin, I cannot upgrade the DB schemas from the horde interface..
>> >
>> >
>> > Any insight is appreciated!
>> >
>> >
>> > Thanks!
>> > --
>> > Horde mailing list
>> > Frequently Asked Questions: http://horde.org/faq/
>> > To unsubscribe, mail: horde-unsubscribe at lists.horde.org
>>
>> --
>> Horde mailing list
>> Frequently Asked Questions: http://horde.org/faq/
>> To unsubscribe, mail: horde-unsubscribe at lists.horde.org
>>
>>

How *does* the horde_histories table look like?

-- 
Jan Schneider
The Horde Project
http://www.horde.org/
https://www.facebook.com/hordeproject