| Summary | reminders.php don't send notification with many calendars |
| Queue | Kronolith |
| Queue Version | 2.1.5 |
| Type | Bug |
| State | Duplicate |
| Priority | 2. Medium |
| Owners | |
| Requester | michael.menge (at) zdv (dot) uni-tuebingen (dot) de |
| Created | 04/11/2007 (6784 days ago) |
| Due | |
| Updated | 04/16/2007 (6779 days ago) |
| Assigned | |
| Resolved | 04/16/2007 (6779 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
users don't use the notifications some don't use the calendar at all and have
only the default calendar.
Why not select the events with notification from all calendars and ceck the
permissons only for those? This may not be a solution for all DataTree
Problems,
but could solve this subproblem.
State ⇒ Duplicate
duplicate of
bug 3046. When that's fixed, this will be, and untilDataTree is taken out of the picture for shares and permissions, this
will still be an issue - the threshold might change, but not the
underlying problem.
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ reminders.php don't send notification with many calendars
Queue ⇒ Kronolith
thescript did not send out
any mails.
Setting the loglevel to debug and adding some more debug statements
showed, that
the script could not find any calendars to monitor
kronolith-h3-2.1.5/lib/Scheduler/kronolith.php line 62
the function call
$this->_calendars = $shares->listAllShares();
in line 59 causes a ugly SQL query which takes very long.
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 (647, 49077, 5295, 15892, 72276, 55905, 58293, 561,
7103, 63809, 904, 49693, ...
13961, 9801) [on line 993 of
"/PATHTOHORDE/horde-3.1.3/lib/Horde/DataTree/sql.php"]
the ... stand for ~14000 more numbers, which is aboute the number of
users we have in horde. The reminders.php takes about 8 minutes to
run. Most of oure users don't use the calendar or the reminders
We had the Problem with horde-3.1.3 and kronolith-h3-2.1.2
and with horde-3.1.4 and kronolith-h3-2.1.5