[Tickets #9937] Re: when caching is enabled for a server in backends exception is logged
bugs at horde.org
bugs at horde.org
Fri Jul 15 13:59:48 UTC 2011
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/9937
------------------------------------------------------------------------------
Ticket | 9937
Updated By | jives at gmx.at
Summary | when caching is enabled for a server in backends
| exception is logged
Queue | Horde Framework Packages
Version | Git master
Type | Bug
State | Not A Bug
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------
jives at gmx.at (2011-07-15 13:59) wrote:
> Try to use pdo_mysql instead of mysqli.
That leads to the same JSON data reply, but with a different error at the end:
Fatal error: Uncaught exception 'Horde_Db_Exception' with message
'QUERY FAILED:
INSERT INTO horde_cache (cache_id, cache_timestamp, cache_expiration,
cache_data) VALUES ('', 1310737654, 1311342454, '')' in
/usr/share/pear/Horde/Db/Adapter/Mysql.php:258
Stack trace:
#0 /usr/share/pear/Horde/Db/Adapter/Mysql.php(281):
Horde_Db_Adapter_Mysql->execute('INSERT INTO hor...', Array, NULL)
#1 /usr/share/pear/Horde/Cache/Storage/Sql.php(160):
Horde_Db_Adapter_Mysql->insert('INSERT INTO hor...', Array)
#2 /usr/share/pear/Horde/Cache.php(131):
Horde_Cache_Storage_Sql->set('horde_imap_clie...',
'?a:50:{i:1840;a...', 604800)
#3 /usr/share/pear/Horde/Imap/Client/Cache.php(166):
Horde_Cache->set('horde_imap_clie...', 'a:50:{i:1840;a:...', 604800)
#4 [internal function]: Horde_Imap_Client_Cache->__destruct()
#5 {main}
Next exception 'Horde_Cache_Exception' with message 'QUERY FAILED:
INSERT INTO horde_cache (cache_id, cache_timestamp, cache_expiration,
cache_data) VALUES ('', 1310737654, 1311342454, '')' in
/usr/share/pear/Horde/Ca in
/usr/share/pear/Horde/Cache/Storage/Sql.php on line 162
The table schemas are up to date according to the Horde configuration
UI, but the problem is maybe somewhere else anyway, because if i run
the exact same query manually, it succeeds.
More information about the bugs
mailing list