Class 'Horde' not found in lib/Horde/SessionHandler/memcache.php on line 232

With memcache enabled syncml is failing, the error message i

Sun, 19 Jul 2009 11:32:54 +0000

With memcache enabled syncml is failing, the error message is found in the client_11.wbxml file: "Fatal error: Class 'Horde' not found in /usr/share/horde/lib/Horde/SessionHandler/memcache.php on line 232
" Without memcache sync is fine.

Changes have been made in CVS for this ticket: http://cvs.h

Mon, 20 Jul 2009 15:42:28 +0000

Changes have been made in CVS for this ticket: http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Backend/Horde.php?rt=horde&r1=1.8.2.17&r2=1.8.2.18&ty=u

Should be fixed now.

Mon, 20 Jul 2009 15:42:58 +0000

Should be fixed now.

no luck, applied the patch by hand... grep -1 ^require_

Mon, 20 Jul 2009 16:50:52 +0000

no luck, applied the patch by hand... grep -1 ^require_once /usr/share/horde/lib/SyncML/Backend/Horde.php require_once 'Horde.php'; require_once 'Horde/Auth.php'; still get the same error message.

That doesn't make any sense to me, since Horde's session han

Mon, 20 Jul 2009 17:05:49 +0000

That doesn't make any sense to me, since Horde's session handler is only instantiated if using the Horde backend of the SyncML server. Try logging a debug_backtrace() output in that line of memcache.php so that we can see from where it's called.

I can let you have more of the backtrace over email, but the

Tue, 21 Jul 2009 09:20:06 +0000

I can let you have more of the backtrace over email, but there's auth and other data in there, however this is probably what you need... Array [0] => Array ( [file] => /usr/share/horde/lib/Horde/SessionHandler.php [line] => 257 [function] => _write [class] => SessionHandler_memcache [object] => SessionHandler_memcache Object ( [_memcache] => Horde_Memcache Object ( [_memcache] => Memcache Object ( [connection] => Resource id #31

No, it's not sufficient, we need a more complete backtrace.

Mon, 03 Aug 2009 15:21:18 +0000

No, it's not sufficient, we need a more complete backtrace.

what's the resolution?

Tue, 18 Aug 2009 13:42:21 +0000

what's the resolution?

The solution is: works for us. And you didn't provide the re

Tue, 18 Aug 2009 13:49:13 +0000

The solution is: works for us. And you didn't provide the requested information to help us fixing anything we don't see.

> The solution is: works for us. And you didn't provide the

Tue, 18 Aug 2009 14:01:47 +0000

> The solution is: works for us. And you didn't provide the requested > information to help us fixing anything we don't see. sorry, I've been away till Sunday and catching up. After the quoted backtrace it went to session data, I can give you this, or is there a better way of capturing a fuller backtrace?

Just paste the complete backtrace. Yours was cut off.

Tue, 18 Aug 2009 14:19:15 +0000

Just paste the complete backtrace. Yours was cut off.

have supplied full backtrace in a direct email. If you need

Tue, 18 Aug 2009 14:35:38 +0000

have supplied full backtrace in a direct email. If you need more info let me know.

Please try putting a "session_write_close();" at the end of

Tue, 18 Aug 2009 16:27:28 +0000

Please try putting a "session_write_close();" at the end of the close() method in SyncML/Backend.php.

no errors, looks good!

Tue, 18 Aug 2009 16:39:50 +0000

no errors, looks good!

Changes have been made in CVS for this ticket: http://cvs.h

Tue, 18 Aug 2009 16:47:09 +0000

Changes have been made in CVS for this ticket: http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Backend.php?rt=horde&r1=1.8.2.17&r2=1.8.2.18&ty=u

That was a tough one, but now I know more about the PHP engi

Tue, 18 Aug 2009 16:49:42 +0000

That was a tough one, but now I know more about the PHP engine. :) Thanks for testing!