[gollem] gollem not working with groupware webmail 5.1.3

[Narendra Mehta]

Jan Schneider wrote, On 03/03/2014 4:10 AM:
>
> Zitat von Narendra Mehta <Narendra.Mehta at sce.carleton.ca>:
>
>> Jan Schneider wrote, On 24/02/2014 8:38 AM:
>>>
>>> Zitat von Narendra Mehta <Narendra.Mehta at sce.carleton.ca>:
>>>
>>>> Jan Schneider wrote, On 19/02/2014 8:24 AM:
>>>>>
>>>>> Zitat von Narendra Mehta <Narendra.Mehta at sce.carleton.ca>:
>>>>>
>>>>>> Horde Goupware Webmail 5.1.3 with Gollem =->FTP backend enabled,
>>>>>> clicking on File Manager brings back the gollem login screen.
>>>>>>
>>>>>> I have horde 3.3.13 with imp 4.3.11 and gollem 1.1.2 working for
>>>>>> several years with Gollem file manager configured with internal ftp
>>>>>> server.  No problem with this version.
>>>>>>
>>>>>> I dumped the Horde 3.3.13 database and imported it with a new name
>>>>>> horde5.  I used this database for Horde Groupware Webmail 5.1.3
>>>>>> install.  IMP works fine.  With ftp enabled in Gollem
>>>>>> backends.php, it
>>>>>> takes a long time to login to Horde/Imp.  After the user
>>>>>> authenticates
>>>>>> with imap, clicking on Other->File Manager, the user is shown the
>>>>>> login screen again with URL referring to the app=gollem.  In the old
>>>>>> version of Horde/Gollem, in the backends['ftp'] array, I had defined
>>>>>> 'name' => "SCE FTP server" and this was shown to the user instead of
>>>>>> "File Manager".  In Horde 5 install, this string is not shown.
>>>>>> Before
>>>>>> modifying backends.php directly, I had created backends.local.php
>>>>>> with
>>>>>> the following:
>>>>>>
>>>>>> <?php
>>>>>> $backends['ftp']['disabled'] = false;
>>>>>> $backends['ftp']['hordeauth'] = true;
>>>>>> $backends['ftp']['name'] = 'SCE FTP server';
>>>>>> $backends['ftp']['params']['hostspec'] = 'ftpserver';
>>>>>>
>>>>>> However, configuring Horde in DEBUG mode, the backends.local was
>>>>>> never
>>>>>> read so I modified backends.php directly
>>>>>
>>>>> backends.local is not a valid file name. You mentioned
>>>>> backends.local.php above, but I have no idea which one you are
>>>>> actually
>>>>> using.
>>>>>
>>>>
>>>>    Sorry, typo.  The file is backends.local.php.  In both
>>>> backends.php and backends.local.php, I have the same settings as
>>>> above.  I expected the "name" parameters string to at least show up in
>>>> the menu.  Even with backends.local.php removed (and restarting web
>>>> service), it the same behaviour.
>>>
>>> The backends are displayed in the menu after a successful authentication
>>> to Gollem. If your backend require authentication, then you will be
>>> authenticated to Gollem only after authenticating to at least one of the
>>> backends.
>>
>>
>>>
>>>>>> All files in gollem/config are read/write for the apache user. And
>>>>>> the
>>>>>> DEBUG log does show  that the file backends.php is read.  I also
>>>>>> generated conf.php for gollem though web interface.  Some relevant
>>>>>> lines from lof file.
>>>>>>
>>>>>> 2014-02-14T14:20:09-05:00 DEBUG: HORDE [gollem] Load config file
>>>>>> (conf.php; app: gollem) [pid 22568 on line 402 of
>>>>>> "/usr/share/pear/Horde.php"]
>>>>>>
>>>>>> 2014-02-14T14:20:09-05:00 DEBUG: HORDE [gollem] Load config file
>>>>>> (prefs.php; app: gollem) [pid 22568 on line 402 of
>>>>>> "/usr/share/pear/Horde.php"]
>>>>>>
>>>>>> 2014-02-14T14:20:09-05:00 DEBUG: HORDE [gollem] SQL  (0.0002s)
>>>>>>       SELECT pref_name, pref_value FROM horde_prefs WHERE pref_uid =
>>>>>> 'ntest' AND pref_scope = 'gollem' [pid 22568 on line 558 of
>>>>>> "/usr/share/pear/Horde/Db/Adapter/Base.php"]
>>>>>>
>>>>>> 2014-02-14T14:20:09-05:00 DEBUG: HORDE [gollem] Load config file
>>>>>> (backends.php; app: gollem) [pid 22568 on line 402 of
>>>>>> "/usr/share/pear/Horde.php"]
>>>>>>
>>>>>> Does gollem table need updating, since I exported from Horde 3 and
>>>>>> imported it into Horde 5?  I have not used permissions.
>>>>>
>>>>> I don't know, you have to check in the configuration screen if any
>>>>> tables need updating. I guess you talk about DB tables here.
>>>>
>>>>    The configuration screen shows SQL DB schema and Applications are
>>>> both ready for all components.  Since Horde 3 is still working on the
>>>> same machine with the same configuration, I thought different db
>>>> schema for Gollem may be the problem.  I even tried uninstalling
>>>> Gollem and re-installing it (with pear), no luck.  I also extracted
>>>> the gollem-3.0.1.tgz so see if there any upgrade script.
>>>
>>> Are you saying you are using the same database for both Horde 3 and
>>> Horde 5? This of course won't work and chances are that your table data
>>> is completely corrupted now, if you really did  this.
>>
>>     No!  I dumped the Horde 3 database  and reloaded it into Horde 5
>> with a different name, different user and different password.  The old
>> Horde 3 installation is still working (and Horde 5 installation,
>> except for Gollem).  If I wipe out Gollem database in Horde 5 and
>> re-install Gollem only, would it re-create the table?  Don't know what
>> else to try.
>
> You don't need to reinstall Gollem, just re-run the database migration.
> Either via horde-db-migrate, or via the adminstration interface.
>

	I have run the horde-db-migrate and it informed that all schemas were 
the current level.

>>>>    There is also a line "2014-02-14T14:22:47-05:00 NOTICE: HORDE User
>>>> is not authorized for gollem [pid 22564 on line 306 of
>>>> "/usr/share/pear/Horde/Registry.php"]" in the log file.  I have
>>>> searched for this string in the mailing list and Google, but none of
>>>> the suggested solutions work or in most cases the thread had never
>>>> been resolved.
>>>
>>> Well you aren't authenticated to Gollem, so this message makes perfect
>>> sense.
>>
>>
>>     I did not have to authenticate to Gollem in Horde 3, so I do not
>> understand what wrong with Horde 5 install.  In my Horde 3
>> configuration when a user clicks on File Manager, it gives the user
>> the FTP login screen and not the Gollem login screen as is done with
>> Horde 5 Groupware Webmail.
>
> If you have an FTP backend configured, then of course you need to
> authenticate. Unless you configured transparent authentication to that
> backend. See the 'hordeauth' configuration parameter.

The hordeauth is true.
% cat backends.local.php
<?php
$backends['ftp']['disabled'] = false;
$backends['ftp']['hordeauth'] = true;
$backends['ftp']['name'] = 'SCE ftp server';
$backends['ftp']['params']['hostspec'] = 'ftp-server';
$backends['smb']['disabled'] = false;
$backends['smb']['hordeauth'] = true;
$backends['smb']['params']['hostspec'] = 'deneb';

When ftp/smb is enabled, the login takes over a minute.  When ftp/smb is 
disabled, it takes about 10 seconds.  Just an observation.