Package: php-horde-webmail
Version: 5.2.11-1
I had to fresh reinstall horde on Debian testing.
It was installed several months ago on the same machine and it was
working, it passed through a series of updates and I just had to update
the DB schema of some components.
Now with the same package version that were previously working fine and
coming from a series of upgrades I can't get a fresh install working.
I did
1) createuser -E -P horde
2) createdb -O horde horde "Horde DB"
3) webmail-install
it creates and populate a bunch of tables then it fail when it tries to
recreate imp_schema_info.
Duplicate table: 7 ERROR: relation "imp_schema_info" already exists
Still connecting to horde with the browser somehow works... I keep
generating conf.php files for the various application (horde included).
Statuses change to "Application is ready."
The SQL Shell works and it is able to connect to my DB but still all
columns in "Database" says "DB access is not configured".
log out, log in again it tries once more to create imp_schema_info table.
Dropped the DB, run horde-db-migrate. It successfully build the DB with
no error this time but again, when I log into horde it tries again to
create imp_schema_info table.
After I log in and refresh the page in it doesn't try to recreate tables
(getMigrator get called just on login) but still I can't get it work
properly.
I still see "DB access is not configured", in "portal" it says User ivan
is not authorized for Mail (Host: gloom.home.webthatworks.it).
And I get:
SQLSTATE[42703]: Undefined column: 7 ERROR: column "event_timezone" does
not exist LINE 1: ...endees, event_title, event_recurcount, event_url,
event_time... ^
So possibly this indicates that there is not just a problem of horde
trying to create multiple times tables, but some table get created with
a different schema than the one expected by the rest of the program.
imp_schema_info is not the only table that horde tries to create
multiple times. If I drop it from pgsql there is another one that
produce the same error, if I drop those 2, there is another one that
cause the error, so apparently it is trying to recreate twice the whole
schema.
Up to my understanding at every login it feels it has to update the
schema no matter what in getMigrator().
thanks
--
Ivan Sergio Borgonovo
http://www.webthatworks.it
