[kronolith] issue with automatic synckronization from clients

Gerard Breiner gerard.breiner at ias.u-psud.fr
Fri Jan 31 10:12:39 UTC 2014


Le 20 janv. 2014 à 17:11, Gerard Breiner <gerard.breiner at ias.u-psud.fr> a écrit :

> 
> Le 16 janv. 2014 à 12:24, Gerard Breiner <gerard.breiner at ias.u-psud.fr> a écrit :
> 
>> Thanks Jan for the hint…. 
>> Simon :  What you suggest is the first thing I did. I asked to the friend Mister Google but I didn't find anything that could be related with this problem even though there is many  
>> possible case at the error "user is not authorize". 
>> Moreover permissions I set up in the new server are identical that the ones of  the old server for which I never had this issue.
>> There is only a few user whose subscriptions to kronolith calendar  from thunderbird  genere these messages.
>> For these users the problem stopped immediately if they delete  their subscription to kronolith in thunderbird but start again as soon as they subscribe again.
>> However the users are not impacted by this issue, all works very fine for them but not for me obviously. 
>> 
>> Best regards.
>> 
>> Gérard Breiner
>> Le 15 janv. 2014 à 15:18, Simon B <simon.buongiorno at gmail.com> a écrit :
>> 
>>> On 15 Jan 2014 14:47, "Jan Schneider" <jan at horde.org> wrote:
>>>> 
>>>> 
>>>> Zitat von Gerard Breiner <gerard.breiner at ias.u-psud.fr>:
>>>> 
>>>> 
>>>>> Hello,
>>>>> 
>>>>> I've recently updated horde. So actually we use horde 5.1.5 and
>>> kronolith 4.1.4. All works very fine except that horde.log is polluted with
>>> messages :
>>>>> EMERG: HORDE [horde] User is not authorized  [pid 7706 on line 1547 of
>>> « /www/horde5/pear/php/Horde/Registry.php « ]
>>>>> It appears that this issue are linked with subscriptions at kronolith
>>> agendas from thunderbird.
>>>>> 
>>>>> In order to trace this issue, I added two lines in Registry.php ($file
>>> and $tt) as below.
>>>>> 
>>>>> 
>>>>> if ($checkPerms) {
>>>>>          if ($this->getAuth() && !$this->checkExistingAuth()) {
>>>>>              $file = '/www/horde5/pear/php/Horde/debug-backtrace.txt';
>>>>>              $tt = Horde::debug($GLOBALS['registry']->getAuth(),
>>> $file);
>>>>>              throw new Horde_Exception_PushApp('User is not
>>> authorized'.$tt, self::AUTH_FAILURE, $app);
>>>>>          }
>>>>> 
>>>>> "tail -300 debug-backtrace.txt" give the output below.
>>>>> 
>>>>> 2014-01-14T14:37:40+01:00 DEBUG: Variable information:
>>>>> string(8) "scaminad"
>>>>> 
>>>>> Backtrace:
>>>>> 1. Horde_Rpc_Webdav->getResponse() /www/horde5/rpc.php:156
>>>>> 2. Sabre\DAV\Server->exec() /www/horde5/pear/php/Horde/Rpc/Webdav.php:67
>>>>> 3. Sabre\DAV\Server->invokeMethod()
>>> /www/horde5/pear/php/Sabre/DAV/Server.php:214
>>>>> 4. Sabre\DAV\Server->broadcastEvent()
>>> /www/horde5/pear/php/Sabre/DAV/Server.php:455
>>>>> 5. call_user_func_array() /www/horde5/pear/php/Sabre/DAV/Server.php:433
>>>>> 6. Sabre\DAVACL\Plugin->beforeMethod()
>>>>> 7. Sabre\DAV\ObjectTree->nodeExists()
>>> /www/horde5/pear/php/Sabre/DAVACL/Plugin.php:701
>>>>> 8. Sabre\DAV\ObjectTree->getNodeForPath()
>>> /www/horde5/pear/php/Sabre/DAV/ObjectTree.php:96
>>>>> 9. Sabre\DAV\Collection->getChild()
>>> /www/horde5/pear/php/Sabre/DAV/ObjectTree.php:64
>>>>> 10. Horde_Dav_RootCollection->getChildren()
>>> /www/horde5/pear/php/Sabre/DAV/Collection.php:33
>>>>> 11. Horde_Registry->hasMethod()
>>> /www/horde5/pear/php/Horde/Dav/RootCollection.php:85
>>>>> 12. Horde_Registry_Api->methods()
>>> /www/horde5/pear/php/Horde/Registry.php:1077
>>>>> 13. Ingo_Api->disabled() /www/horde5/pear/php/Horde/Registry/Api.php:86
>>>>> 14. Horde_Registry->pushApp() /www/horde5/ingo/lib/Api.php:37
>>>>> 15. Horde::debug() /www/horde5/pear/php/Horde/Registry.php:1548
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> Do you have an idea of what could  cause  this issue ?  Any hints would
>>> be great help.
>>>>> 
>>>>> Many thanks in advance.
>>>>> 
>>>>> Gérard Breiner
>>>> 
>>>> 
>>>> Obviously checkExistingAuth() fails.
>>> 
>>> As I recall this is usually a permissions problem and reported often on the
>>> list.  Check the archives.
>>> 
>>> Simon
>>> -- 
>>> kronolith mailing list
>>> Frequently Asked Questions: http://wiki.horde.org/FAQ
>>> To unsubscribe, mail: kronolith-unsubscribe at lists.horde.org
>> 
>> -- 
>> kronolith mailing list
>> Frequently Asked Questions: http://wiki.horde.org/FAQ
>> To unsubscribe, mail: kronolith-unsubscribe at lists.horde.or
> 
> Hum… it seems that tis issue is not related to kronolith but  to horde… isn’t it ?
> I have many many "user is not authorized »   in horde.log and this time  Horde_Debug give :
> 
> 2014-01-20T16:18:44+01:00 DEBUG: Variable information:
> string(8) "jsolerpu"
> 
> Backtrace:
> 1. IMP_Application->exceptionHandler()
> 2. Horde_ErrorHandler::fatal() /www/horde5/imp/lib/Application.php:586
> 3. Horde_Registry->clearAuth() /www/horde5/pear/php/Horde/ErrorHandler.php:64
> 4. Horde_Registry->callAppMethod() /www/horde5/pear/php/Horde/Registry.php:2101
> 5. Horde_Registry->pushApp() /www/horde5/pear/php/Horde/Registry.php:1210
> 6. Horde::debug() /www/horde5/pear/php/Horde/Registry.php:1548
> 
> Thanks for help….
> 
> Best regards.
> 
> Gérard-- 
> kronolith mailing list
> Frequently Asked Questions: http://wiki.horde.org/FAQ
> To unsubscribe, mail: kronolith-unsubscribe at lists.horde.org

Hello,

I managed to reproduce this issue with my own account… It appears that theses error messages (User is not authorized) are logged when the users configure his client Thunderbird/Lightning or Calendar (apple) for an automatic synchronization. With a manual synchronization, all works very fine… 
I have never encountered this issue with horde 5.1.1 kronolith 4.1.0. Actually it is horde 5.1.5 and kronolith 4.1.4
It sounds like a bug with horde/kronolith ?  Do I have to  create a ticket ?

Many thanks in advance.

Best regards.





-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1885 bytes
Desc: not available
URL: <http://lists.horde.org/archives/kronolith/attachments/20140131/ba7849b0/attachment.bin>


More information about the kronolith mailing list