[horde] Class definition of Horde_Cache_emcache not found - Revisted
Michael Rubinsky
mrubinsk at horde.org
Mon Aug 3 17:09:27 UTC 2009
Quoting d.hill at yournetplus.com:
> Quoting Michael Rubinsky <mrubinsk at horde.org>:
>
>>
>> Quoting d.hill at yournetplus.com:
>>
>>> Quoting d.hill at yournetplus.com:
>>>
>>>> Quoting Michael Rubinsky <mrubinsk at horde.org>:
>>>>
>>>>> Quoting d.hill at yournetplus.com:
>>>>>
>>>>>>
>>>>>> As I stated, I was looking in the Horde log file and do not
>>>>>> know what I should be looking for.
>>>>>
>>>>> Do you have the log level turned up enough to see debug messages?
>>>>
>>>> I apologize for my ignorance. Now that I have Horde logging
>>>> everything, what am I looking for? I'm sorry I'm not fluent with
>>>> PHP.
>>>
>>> Never mind. I found the log lines:
>>>
>>> Aug 03 12:21:08 HORDE [debug] [horde] emcache [pid 85246 on line
>>> 174 of "/usr/local/www/apache22/data/horde/lib/Horde/Cache.php"]
>>> Aug 03 12:21:08 HORDE [debug] [horde] emcache [pid 85246 on line
>>> 184 of "/usr/local/www/apache22/data/horde/lib/Horde/Cache.php"]
>>> Aug 03 12:21:08 HORDE [debug] [horde] emcache [pid 85246 on line
>>> 193 of "/usr/local/www/apache22/data/horde/lib/Horde/Cache.php"]
>>>
>>> The three log lines I've found to be repeated three times all
>>> within the same hour.
>>>
>>> There should be four lines being logged. I'm not sure why the
>>> first one is not being logged. It should be the first thing
>>> executed within the fuction:
>>
>>
>> It sounds to me like you have a badly broken PHP.
>
> I would accept that as an answer to the issue. However, I am finding
> it hard to believe when there are several other PHP applications
> running without issue.
>
> When you say broken, it what particular area(s) are you talking about?
I have no idea. I'm not familiar with PHP internals. But when a
statement doesn't execute, when it clearly should, and when the value
of a parameter is changed between the time it is passed to a function
and the time it gets to the function, it's broken. Unless you can
trace your code to the exact point in Horde's code that the value of
$driver is changed from 'memcache' to 'emcache', I have to assume it's
something broken in PHP.
Thanks,
mike
--
The Horde Project (www.horde.org)
mrubinsk at horde.org
"Time just hates me. That's why it made me an adult." - Josh Joplin
More information about the horde
mailing list