Summary | Since Horde 3.1 Update Turba Addressbook is unusable slow |
Queue | Horde Framework Packages |
Queue Version | FRAMEWORK_3 |
Type | Bug |
State | Not A Bug |
Priority | 1. Low |
Owners | |
Requester | horde (at) mailinator (dot) com |
Created | 03/20/2006 (7064 days ago) |
Due | |
Updated | 04/19/2006 (7034 days ago) |
Assigned | 04/15/2006 (7038 days ago) |
Resolved | 04/17/2006 (7036 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
because it was working before even with all backends enabled in
sources.php - don't get me wrong it isn't problem that i have to
comment out sth more now.
auth o. ssl/tls (that it wasn't answered before - or I just couldn't
find anwer anywhere). I see that most of the questions are answered,
and many of them by developers (especially by Jan Schneider).
*is* free - telling us we should be paid for us is nice, but doesn't
give you license to tell us how to spend our time as if we *were*
paid for it.
documentation files.
all. There are some basic things which are not documentated and it
don't help, because Horde day by day is bigger and more complicated
piece of soft (now it's quite hard to find some answers in source code).
Ok, I think that it's good time to EOT - it's bad place for similar
discussions.
ps. sorry if it still sounds negative ...
about that should be placed somewhere in documentation. I think that
is (or surely will be) one of the biggest Horde problems - no good,
up to date documentation.
how do you expect us to feel about spending more time on documentation
when you say things like this, and right in turba/docs/INSTALL, we have:
" You must configure ``sources.php`` to list your data sources (both SQL and
LDAP if necessary). This configuration file contains a large number of
**examples**. Please remove or comment out those examples that **you don't
need**."
If looking in a docs/ directory in the tarball isn't intuitive, maybe
the "Documentation" link at http://horde.org/turba/, which leads you
to http://www.horde.org/turba/docs/?f=INSTALL.html, is better?
overwhelming) majority of questions on all 30+ Horde mailing lists are
answered, and answered quickly. Some things slip through the cracks,
some things people don't know. Telling us that nothing gets answered
just tells us our efforts aren't helping anything, so we may as well
spend our time somewhere else. Like you said, all of this *is* free -
telling us we should be paid for us is nice, but doesn't give you
license to tell us how to spend our time as if we *were* paid for it.
Especially with such negativity and missing basic documentation files.l
about that should be placed somewhere in documentation. I think that
is (or surely will be) one of the biggest Horde problems - no good,
up to date documentation.
designed to work out of the box for every situation. It is expected
that the admin should review/edit/delete appropriate entries.
about that should be placed somewhere in documentation. I think that
is (or surely will be) one of the biggest Horde problems - no good, up
to date documentation.
I don't ask for any howtos or sth, but there should be at least some
manual, where I can read about all available options and features of
some module. As an example you can see my mail to imp maillist:
http://lists.horde.org/archives/imp/Week-of-Mon-20060417/044990.html -
there are only questions without answers in maillist archive... how
should we know if (for example) it is possible to set smtp auth over
ssl/tls in imp? Second question... where can I find information about
that which option deprecated user_change_from in new horde/imp
version? I don't know... maybe there is everything in some
documentation and I just can't find it (maybe somewhere in cvs?). Ok,
enough complaining - all in all horde developers do great work and
they should be paid for it (for example horde not completely free for
commercial use), anyway huge thanks to them.
Sorry for my English, it's 2.45AM here.
KOLAB) and that seems to have taken care of the problem. The only
other question I have is whether or not this should still be
considered a bug since the sources.php module should have prevented
Turba from searching through the aforementioned directory services
which were set to disabled in the configuration file.
IIRC and the KOLAB stuff probably even earlier.
2) The LDAP checks for the existence of the LDAP extension.
3) The entries in sources.php.dist are *example* entries only and not
designed to work out of the box for every situation. It is expected
that the admin should review/edit/delete appropriate entries.
Thanks,
Mike
Victor
I've made the suggested changes (commenting out LDAP, IMSP, and KOLAB)
and that seems to have taken care of the problem. The only other
question I have is whether or not this should still be considered a
bug since the sources.php module should have prevented Turba from
searching through the aforementioned directory services which were set
to disabled in the configuration file.
Thanx!
Victor
Priority ⇒ 1. Low
State ⇒ Not A Bug
New Attachment: sources[1].php
With LDAP/IMSP/Kolab based drivers commented out, performance is back
to expectations, but sidebar disappears. (Left sitting on portal
screen for 10+ minutes with no appearance of sidebar.
Removed prefs based SQL driver and Public LDAP servers with no change.
I have attached my sources.php file in it's current state as well.
New Attachment: sources.php
everything in /horde/turba/config/sources.php without sql
configuration. I attached my sources.php file.
(+imp,turba,nag,ingo,passwd +new horde database in mysql) once again
(I had some other problems with that installation...), and there is
still the same problem with long logging to horde. Here is my
horde.log (while I'm trying to log in):
http://slwkk.alternatywa.net/horde1.log
and second, while I'm trying to send an email:
http://slwkk.alternatywa.net/horde2.log
Why there are "?" in sql queries instead of some values, for example:
SELECT datatree_id, datatree_parents FROM horde_datatree WHERE
datatree_name = ? AND group_uid = ? ORDER BY datatree_id;
I have to reconfigure many things now, after fresh install, maybe sth
will change...
Apr 15 12:14:43 HORDE [debug] [turba] SQL Query by
DataTree_sql::getAttributes(): SELECT datatree_id, attribute_name AS
name, attribute_key AS "key", attribute_value AS value FROM
horde_datatree_attributes WHERE datatree_id IN (145) [on line 989 of
"/usr/share/horde/lib/Horde/DataTree/sql.php"]
Apr 15 12:17:52 HORDE [debug] [turba] SQL Query by
DataTree_sql::_buildParentIds(): SELECT datatree_id, datatree_parents
FROM horde_datatree WHERE datatree_name = ? AND group_uid = ? ORDER BY
datatree_id [on line 261 of
"/usr/share/horde/lib/Horde/DataTree/sql.php"]
TOP shows minimal CPU activity, with the Mysql and Apache processes
barely (if at all) registering
State ⇒ Feedback
Since update from 3.0.9 to 3.1 the Turba addressbook is incredibly
slow. From debug horde.log:
the log files with the long delay:
Apr 15 00:53:44 HORDE [debug] [turba] SQL Query by
DataTree_sql::getAttributes(): SELECT datatree_id, attribute_name AS
name, attribute_key AS "key", attribute_value AS value FROM
horde_datatree_attributes WHERE datatree_id IN (145) [on line 989 of
"/usr/share/horde/lib/Horde/DataTree/sql.php"]
Apr 15 00:56:54 HORDE [debug] [turba] SQL Query by
DataTree_sql::_buildParentIds(): SELECT datatree_id, datatree_parents
FROM horde_datatree WHERE datatree_name = ? AND group_uid = ? ORDER BY
datatree_id [on line 261 of
"/usr/share/horde/lib/Horde/DataTree/sql.php"]
If I disable Turba and it's portal block, speed returns to normal.
Configured modules:
Gollem: H3 (1.0.2)
Horde: 3.1.1
Imp: H3 (4.1.1)
Ingo: H3 (1.1)
Kronolith: H3 (2.1.1)
Mnemo: H3 (2.1)
Nag: H3 (2.1)
Passwd: H3 (3.0)
Turba: H3 (2.1)
working, and it seems to be. It just takes a very long time between
clicks to display the required screen. One thing I did notice was that
it seemed to take a little longer with every successive click. Only
the Turba related links are affected, meaning, once I'm in Horde and I
click on any link on the side or top menu that doesn't require Turba
to report some kind of information the page updates normally. If for
example IMP has Turba linked in it's menu, IMP will take a long time
to display, but if I remove the link IMP displays normally.
On the same system I have an older version of Horde (2.13), IMP
(2.21), and Turba (1.12), in a separate folder of course, and that
combination is working fine. My latest configuration has the
following versions:
Horde 3.1.1
IMP 4.1.1
Turba 2.1
MIMP 1.0-RC1
RedHat Linux Enterprise Edition Version 3
MySQL 5.0.19
PHP 4.4.2
Thanx!
Victor
Linux instead of FreeBSD.
FreeBSD 6.0
horde-3.1
turba-2.1
php4-cgi-4.4.2_1
I have no time to debug it at the moment... I had to deactive turba
because logging to horde took about 2 minutes.
Linux instead of FreeBSD.
Priority ⇒ 3. High
State ⇒ Unconfirmed
Queue ⇒ Horde Framework Packages
Summary ⇒ Since Horde 3.1 Update Turba Addressbook is unusable slow
Type ⇒ Bug
Since update from 3.0.9 to 3.1 the Turba addressbook is incredibly
slow. From debug horde.log:
Mar 17 10:08:10 HORDE [debug] [turba] SQL Query by
DataTree_sql::getAttributes(): SELECT attribute_name AS name,
attribute_key AS "key", attribute_value AS value FROM
horde_datatree_attributes WHERE datatree_id = 1 [on line 1011 of
"/usr/local/www/horde/lib/Horde/DataTree/sql.php"]
Mar 17 10:09:26 HORDE [debug] [turba] SQL Query by
DataTree_sql::_buildParentIds(): SELECT datatree_id, datatree_parents
FROM horde_datatree WHERE datatree_name = ? AND group_uid = ? ORDER BY
datatree_id [on line 261 of
"/usr/local/www/horde/lib/Horde/DataTree/sql.php"]
Thanks.
Horde 3.1
Turba 2.1
imp 4.1
Freebsd 5.4
MySQL 4.0
PHP 5.1.1