
Originally Posted by
rbob523
So - and please bear with me as I'm sure I'm going to sound like a bumbling fool here - is the looping at the language select screen pretty much an indication that the database is corrupted beyond repair, etc.? Or, is there something that can be done before simply considering the database dead?
Not the entire database, merely the session table. That is why I cringe whenever people use the fullhordereset and update-horde scripts, because it's overkill. The easiest option is to drop and restore the horde session table:
Code:
mysql
mysql> use horde;
mysql> drop table horde_sessionhandler;
mysql> CREATE TABLE horde_sessionhandler (
session_id VARCHAR(32) NOT NULL,
session_lastmodified INT NOT NULL,
session_data LONGBLOB,
PRIMARY KEY (session_id)
) ENGINE = InnoDB;

Originally Posted by
rbob523
Also, having the same problem with multiple clients on our reseller server - which makes me think that it's a server-wide issue. Do multiple clients share the same Horde database, or does each client have their own?
There is one database for the entire server.