[horde] Bad log level META

[Michael J Rubinsky]

Quoting Simon B <simon.buongiorno at gmail.com>:

> On 20 February 2017 at 19:53, Michael J Rubinsky <mrubinsk at horde.org> wrote:
>>
>> Quoting Simon B <simon.buongiorno at gmail.com>:
>>
>>> On 20 February 2017 at 17:50, Michael J Rubinsky <mrubinsk at horde.org>
>>> wrote:
>>>>
>>>>
>>>> Quoting Simon B <simon.buongiorno at gmail.com>:
>>>>
>>>>> On 20 February 2017 at 16:58, Michael J Rubinsky <mrubinsk at horde.org>
>>>>> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> Quoting Simon B <simon.buongiorno at gmail.com>:
>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>> Since updating via git yesterday AM, ActiveSync has stopped working
>>>>>>> (i.e. IMP is working fine).
>>>>>>>
>>>>>>> Attempting to to go to .../admin/activesync.php in the browser (to
>>>>>>> clear the devices as my first troubleshooting step), give this error:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> A fatal error has occurred
>>>>>>>
>>>>>>> Bad log level META
>>>>>>>
>>>>>>
>>>>>> Are you 100% sure you are up to date with git master? There were a few
>>>>>> BC
>>>>>> related fixes I committed after the main push that introduced these
>>>>>> changes.
>>>>>
>>>>>
>>>>>
>>>>> Hi Mike
>>>>>
>>>>> I ran it again this morning before sending the mail.  I even restarted
>>>>> Apache after changing the logging requirement to false..
>>>>
>>>>
>>>>
>>>>
>>>> I found and fixed an issue that would cause this when logging is turned
>>>> off,
>>>> or when the path is not writeable. Still not sure what would have caused
>>>> this when logging was configured properly, or when viewing the admin
>>>> page.
>>>>
>>>> Anyway, let me know if this gets you closer...
>>>
>>>
>>> Git says it is up to date, but no change in behaviour.
>>
>>
>> Is this just a "normal" git master checkout? I can't reproduce any of this.
>>
>> Try putting:
>>
>> Horde::debug($this->_logger);
>>
>> on line 121 of Horde_ActiveSync_SyncCache (before the // @todo line) and
>> navigate to the activesync admin page again. This will output the contents
>> of _logger in your {tmp directory}/horde_debug.txt.
>
> Done and sent off-list.

Well, this is not correct:

2017-02-21T12:17:33+00:00 DEBUG: Variable information:
object(Horde_Core_Log_Logger)#76 (3) {
   ["_levels":"Horde_Log_Logger":private]=>  <----------------- Not correct.
   array(8) {
     [0]=>
     string(5) "EMERG"
     [1]=>
     string(5) "ALERT"
     [2]=>
     string(4) "CRIT"
     [3]=>
     string(3) "ERR"
     [4]=>
     string(4) "WARN"
     [5]=>
     string(6) "NOTICE"
     [6]=>
     string(4) "INFO"
     [7]=>
     string(5) "DEBUG"
   }

The visibility of that member should be "protected", and not  
"private". This was changed in Horde_Log along with the commits that  
modified the logging. Are you SURE you have a pristine git *master*  
checkout and your system isn't including any FRAMEWORK_5_2 libraries?

See  
https://github.com/horde/horde/commit/f78145d405576ce30fabcbbc87e28952225a8ba5


-- 
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3282 bytes
Desc: S/MIME Signature
URL: <https://lists.horde.org/archives/horde/attachments/20170221/b0621c7f/attachment.bin>