[horde] Horde 3.2.2 SQL SessionHandler Error

Andrew Morgan morgan at orst.edu
Wed Oct 1 19:10:16 UTC 2008


On Wed, 1 Oct 2008, Michael M Slusarz wrote:

> Quoting Andrew Morgan <morgan at orst.edu>:
>
>> On Wed, 1 Oct 2008, Laura McCord wrote:
>> 
>>> I upgraded our horde installation last Thursday and everything has been 
>>> going great until last night. All of a sudden we started receiving the 
>>> following error in the logs:
>>> 
>>> Sep 30 23:00:21 HORDE [error] [horde] Could not connect to database for 
>>> SQL SessionHandler. [pid 31393 on line 157 of 
>>> "/srv/www/htdocs/horde/lib/Horde/SessionHandler.php"]
>>> 
>>> Then, we received the messages following the above:
>>> 
>>> Sep 30 23:00:26 HORDE [error] [imp] DB Error: connect failed: 
>>> [nativecode=Host 'webmail.university.edu' is blocked because of many 
>>> connection errors; unblock with 'mysqladmin flush-hosts'] ** 
>>> mysql(mysql)://horde:PASSWORD at tcp+ipaddress:3306/horde?persistent=&charset=iso-8859-1&splitread=&table=horde_prefs&driverconfig=horde&umask=63 
>>> [pid 31369 on line 1 38 of 
>>> "/srv/www/htdocs/horde/lib/Horde/Prefs/sql.php"]
>>> 
>>> Does anyone know what may have sprung this or have some insight on where I 
>>> should look to investigate?
>> 
>> I had this happen when I hit the max-connections limit in MySQL after 
>> upgrading to the latest Horde.  Since we've upgraded, we are using more 
>> apache processes.  I'm not sure why, but it's no big deal for us. However, 
>> I didn't have the max-connections limit tuned to match the MaxClients 
>> settings on our apache servers.
>> 
>> After fixing the MaxClients settings, I ran the suggested command 
>> "mysqladmin flush-hosts" and all was well.  I think MySQL was just 
>> protecting itself against too many failed logins.
>
> Is this an upgrade from 3.2?  Or earlier?  The only changes between 
> 3.2->3.2.2 re: sessionhandling code is this:
> http://cvs.horde.org/diff.php/framework/SessionHandler/SessionHandler/mysql.php?r1=1.16.12.19&r2=1.16.12.20
>
> So I doubt the sessionhandling code is the issue.

I upgraded from Horde 3.1.7 to 3.3rc1.

 	Andy


More information about the horde mailing list