OK, I've seen. I leave memcache for the moment and wait for new release.



Thanks



Dom

Duplicate of Ticket #7181.

Mar 25 14:20:37 testDom HORDE[2826]: [imp] tracedom Unserialization 
failed. [pid 2826 on line 80 of 
"/var/www/perso/horde-webmail-1.2.2/lib/Horde/IMAP/Cache.php"]



It says unserialization failed. Seems that message caching/jss/css are 
not working over memcache?.. There is not much logging either in horde 
or memcache to see where and why it's not working.

I'm just (for the moment) staying over memcached sessions through php



I switched to filesystem for css and jss cache.

I have  difficulties to use memcache.



I see request in the memcache server, kronolith is OK, but imp or dimp failed





Fatal error: Cannot use object of type PEAR_Error as array in 
/var/www/perso/horde-webmail-1.2.2/lib/Horde/IMAP/Cache.php on line 80



What I noticed is that I am obliged to get rid of those cache in order to run.



#$conf['msgcache']['use_compress'] = false;

#$conf['msgcache']['preview_size'] = 1000;

#$conf['msgcache']['lifetime'] = 86400;

#$conf['msgcache']['use_msgcache'] = true;

#$conf['mlistcache']['lifetime'] = 86400;

#$conf['mlistcache']['use_mlistcache'] = true;



#$conf['server']['cachejsparams']['lifetime'] = 86400;

#$conf['server']['cachejs'] = 'horde_cache';

#$conf['server']['cachecssparams']['lifetime'] = 86400;

#$conf['server']['cachecss'] = 'horde_cache';



So what is better, now memcache or message caching? Is it designed to 
get it working?



Nothing written in debug logs, nor in memcache server.



Dom