[horde] Installation problem
Luis Felipe Marzagao
lfbm.andamentos at gmail.com
Fri Jan 17 13:25:15 UTC 2020
Em 17/01/2020 10:19, o1bigtenor escreveu:
> On Fri, Jan 17, 2020 at 2:28 AM Jan Schneider <jan at horde.org> wrote:
>>
>> Zitat von o1bigtenor <o1bigtenor at gmail.com>:
>>
>>> On Thu, Jan 16, 2020 at 9:32 AM Luis Felipe Marzagao
>>> <lfbm.andamentos at gmail.com> wrote:
>>>>
>>>> Em 16/01/2020 12:09, o1bigtenor escreveu:
>>>>> On Thu, Jan 16, 2020 at 8:52 AM Luis Felipe Marzagao
>>>>> <lfbm.andamentos at gmail.com> wrote:
>>>>>> Em 15/01/2020 20:40, o1bigtenor escreveu:
>>>>> snip
>>>>>>>>>>>> Working on installing horde groupwebmail on a debian
>>>> buster (10) where
>>>>>>>>>>>> apache 2.4.38, postgresql 11.5 and php 7.3.
>>>>>>>>>>>>
>>>>>>>>>>>> Chose to install using # apt install and the
>>>> installation completed easily.
>>>>>>>>>>>> It was in working through the configuration that a
>>>> roadblock occurred.
>>>>>>>>>>>> Quoting the terminal output:
>>>>>>>>>>>>
>>>>>>>>>>>> Creating and updating database tables...
>>>>>>>>>>>> Fatal Error:
>>>>>>>>>>>> SQLSTATE[42703]: Undefined column: 7 ERROR: column
>>>> "increment_by"
>>>>>>>>>>>> does not exist
>>>>>>>>>>>> LINE 1: ...q', (SELECT COALESCE(MAX("sentmail_id") + (SELECT
>>>>>>>>>>>> increment_...
>>>>>>>>>>>>
>>>> ^
>>>>>>>>>>>> In /usr/share/php/Horde/Db/Adapter/Pdo/Base.php on line 233
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> How do I resolve this?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Apparently your database was not correctly created. Try running
>>>>>>>>>>>> /usr/bin/horde-db-migrate from the command line.
>>>>> snip
>>>>>>>>>> If your db server is ok, then you had some problem when the
>>>> database was
>>>>>>>>>> created or you are missing horde dependencies, which could
>>>> be caused byBest regardsBest regards
> Bill
>
> Bill
>>>>>>>>>> a broken distro package install, or, as Jan has already mentioned,
>>>>>>>>>> "there are some patches for newer Postgresql versions on GitHub that
>>>>>>>>>> haven't been incorporated yet. Feedback on those is welcome."
>>>>>>>>> If you would be so kind as to point me to where I could find those
>>>>>>>>> patches . . . .
>>>>>>>> You could start here: https://github.com/horde/Db/commits/master
>>>>>>>>
>>>>>>> OK s o I can see the patch. When I'm reading the code (total noob to
>>>>>>> coding here)
>>>>>>> I can understand what the change is. What I have no clue how to
>>>> do (looked into
>>>>>>> both the use of the program 'patch' and a few write ups on doing a git
>>>>>>> patch but
>>>>>>> its not clear how I do this.
>>>>>>> Did some looking and have found the file on my system. Also
>>>> have the 'patch'
>>>>>>> available. Have not ever done this - - - - so - - - do I add the new
>>>>>>> lines into the
>>>>>>> file and remove the unwanted lines then save the new version?
>>>>>>> Would this 'apply' the patch?
>>>>>> It may be tricky to apply patches because you are not using a
>>>>>> development installation. But if you think you´ve found the correct
>>>>>> patch, and if there aren´t a lot of files involved in the commit, go
>>>>>> ahead and try to manually replace the entire file. Dirty hack but pretty
>>>>>> fast in order to make a quick test.
>>>>>>
>>>>> Greetings
>>>>>
>>>>> So I applied the patch (meaning that I added in the new lines indicated in
>>>>> green and removed the lines indicated in pink) and saved the file.
>>>>> Tried one more time to effect and install.
>>>>> Right back to where I started at :
>>>>>
>>>>> Fatal Error:
>>>>> SQLSTATE[42703]: Undefined column: 7 ERROR: column "increment_by"
>>>>> does not exist
>>>>> LINE 1: ...q', (SELECT COALESCE(MAX("sentmail_id") + (SELECT
>>>>> increment_...
>>>>> ^
>>>>> In /usr/share/php/Horde/Db/Adapter/Pdo/Base.php on line 233
>>>>>
>>>>> had been told earlier to try to use /usr/bin/horde-db-migrate
>>>> which gives:
>>>>> # /usr/bin/horde-db-migrate
>>>>> [ INFO ] Migrating DB up.
>>>>> [ INFO ] Current imp schema version: 1
>>>>> Migrating to ImpAutoIncrementSentmail (2)
>>>>> == 2 ImpAutoIncrementSentmail: migrating
>>>> ======================================
>>>>> -- changeColumn('imp_sentmail', 'sentmail_id', 'autoincrementKey')
>>>>> SQLSTATE[42703]: Undefined column: 7 ERROR: column "increment_by"
>>>>> does not exist
>>>>> LINE 1: ...q', (SELECT COALESCE(MAX("sentmail_id") + (SELECT increment_...
>>>>>
>>>>> and about a hundred more lines like the above.
>>>>> Searching on the horde website then led me to - - - - bug number :
>>>>>
>>>>> [#14878] Sequence reset incompatible with PostgreSQL 10+
>>>>>
>>>>> bug listed november 2018 with a comment in early 2019 and nothing further
>>>>>
>>>>> Seems to suggest that I'm not going to get an install.
>>>>>
>>>>> Oh well - - - - suggestions?????
>>>> You got horde-db-migrate to run, which is a good sign. But the error
>>>> appears to be still the same. At this point either you 1) set up a dev
>>>> install (https://www.horde.org/development/git) and try to fix the code
>>>> and submmit a fix; 2) file a bug report at https://bugs.horde.org/ or 3)
>>>> Try using MySQL
>>>>
>>> So - - - - trying option 3.
>>> Get to:
>>>
>>> . . .
>>> Writing main configuration file... done.
>>>
>>> Creating and updating database tables...
>>> Fatal Error:
>>> SQLSTATE[42S22]: Column not found: 1054 Unknown column
>>> 'object_category' in 'field list'
>>> In /usr/share/php/Horde/Db/Adapter/Pdo/Base.php on line 233
>>>
>>> I've tried running /usr/bin/horde-db-update where I got:
>>>
>>> # /usr/bin/horde-db-migrate
>>> [ INFO ] Migrating DB up.
>>> [ INFO ] Current imp schema version: 3
>>> [ INFO ] Ending imp schema version: 3
>>> [ INFO ] Current ingo schema version: 7
>>> [ INFO ] Ending ingo schema version: 7
>>> [ INFO ] Current kronolith schema version: 23
>>> [ INFO ] Ending kronolith schema version: 23
>>> [ INFO ] Current turba schema version: 9
>>> Migrating to TurbaUpgradeCategoriesToTags (10)
>>> == 10 TurbaUpgradeCategoriesToTags: migrating
>>> =================================
>>> == 10 TurbaUpgradeCategoriesToTags: Migrating contact categories to
>>> tags. =====
>>> -- select('SELECT object_uid, object_category, owner_id FROM turba_objects')
>>> -> 0.0000s
>>> SQLSTATE[42S22]: Column not found: 1054 Unknown column
>>> 'object_category' in 'field list'
>>> [ INFO ] Current nag schema version: 14
>>> [ INFO ] Ending nag schema version: 14
>>> [ INFO ] Current mnemo schema version: 8
>>> [ INFO ] Ending mnemo schema version: 8
>>> [ 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: 23
>>> [ INFO ] Ending Horde_ActiveSync schema version: 23
>>> [ 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: 3
>>> [ INFO ] Ending Horde_Perms schema version: 3
>>> [ 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_Service_Weather schema version: 2
>>> [ INFO ] Ending Horde_Service_Weather schema version: 2
>>> [ 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
>>>
>>> So I'm getting exactly the same error thrown as when I was trying to
>>> install on a postgresql instance but now on a mariadb instance - - - it
>>> would be quite funny if it weren't so frustrating.
>>>
>>> What do I do now?
>>> (Is there an upgrade/update for this 'turba' - - - - that's where the issue
>>> seems to be sitting?)
>> Probably something broke in the DB schema when earlier attempts to
>> installation failed. Try deleting all turba_* tables manually and
>> start the migration again. Unless you are coming from a Horde 3
>> version. Then you didn't have the default schema for Turba.
>>
> This is a first time install so I have no previous versions of anything.
>
> How would I delete all turba_* tables?
>
> Do I just dump the whole database and start over?
>
> Or to I remove and purge all files of all server related items (apache, php,
> postgresql, mariadb and anything else) and start by reinstalling from a clean
> system?
I think redoing horde and DB would be fine. Your problem does not seem
to be related with php, apache etc...
> TIA
More information about the horde
mailing list