[Tickets #8671] Nag::listAlarms fails when called from the scritps/alarms.php cron job

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/8671
------------------------------------------------------------------------------
  Ticket             | 8671
  Created By         | Valentin.Vidic at CARNet.hr
  Summary            | Nag::listAlarms fails when called from the
                     | scritps/alarms.php cron job
  Queue              | Nag
  Version            | 2.3.3
  Type               | Bug
  State              | Unconfirmed
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Valentin.Vidic at CARNet.hr (2009-11-02 10:49) wrote:

The cron job that should trigger scheduled alarms constantly fails  
with this error:

Nov 02 16:32:32 HORDE [error] [nag] The Tasks backend is not currently  
available: DB Error: connect failed [pid 19885 on line 228 of  
"/srv/webmail/www/lib/Horde/Alarm.php"]

It seems the problem is in the call to Nag::listAlarms. This function  
creates a new database connection for each storage instance and after  
a few hundred users database returns the error 'Too many connections'.  
Perhaps a single database connection could be used or old connections  
can be closed?