Kolab 404 errors when syncing with DavDroid 0.8.0


  • So how can we detect the events that cause the error? And how can we assure that in the future no such events will be created?

    Am 19. Juni 2015 16:41:01 MESZ, schrieb Jeroen van Meeuwen notifications@github.com:

    As a result of some troubleshooting, we’ve found that SabreDAV attempts
    to examine the object tree for a VEVENT UID property that is (in the
    form of) a URI. This is very likely the cause, because removing the
    offending events brings the matter to resolution.

    I propose this issue is closed.


    Reply to this email directly or view it on GitHub:
    https://github.com/bitfireAT/davdroid/issues/542#issuecomment-113533797


  • I was recently made aware of this problem happening on DAVdroid 0.6.x. It started 5 days ago on a friend’s phone - same error that can be seen in the screenshots (though I can’t obtain the log files so far). The server in question is running Horde 5.2.1, which to my knowledge also utilizes SabreDAV. So this is definitely looking like a SabreDAV issue, but I don’t think it is necessarily related to DAVdroid 0.8 then. (Of course, the issue also happens once I upgraded to 0.8, and didn’t go away).

    @greve, can you downgrade to a 0.6.x version of DAVdroid and see if the problem still persists?


  • Afaict it’s already clear that changes in DavDroid 0.8+ trigger this behavior.

    On 20 June 2015 10:45:42 CEST, Natanji notifications@github.com wrote:

    I was recently made aware of this problem happening on DAVdroid 0.6.x.
    It started 5 days ago on a friend’s phone - same error that can be seen
    in the screenshots (though I can’t obtain the log files so far). The
    server in question is running Horde 5.2.1, which to my knowledge also
    utilizes SabreDAV. So this is definitely looking like a SabreDAV issue,
    but I don’t think it is necessarily related to DAVdroid 0.8 then. (Of
    course, the issue also happens once I upgraded to 0.8, and didn’t go
    away).

    @greve, can you downgrade to a 0.6.x version of DAVdroid and see if the
    problem still persists?


    Reply to this email directly or view it on GitHub:
    https://github.com/bitfireAT/davdroid/issues/542#issuecomment-113731821


  • Then why does it happen in earlier versions as well?

    Am 20. Juni 2015 15:35:44 MESZ, schrieb Markus Unterwaditzer notifications@github.com:

    Afaict it’s already clear that changes in DavDroid 0.8+ trigger this
    behavior.

    On 20 June 2015 10:45:42 CEST, Natanji notifications@github.com
    wrote:

    I was recently made aware of this problem happening on DAVdroid 0.6.x.
    It started 5 days ago on a friend’s phone - same error that can be
    seen
    in the screenshots (though I can’t obtain the log files so far). The
    server in question is running Horde 5.2.1, which to my knowledge also
    utilizes SabreDAV. So this is definitely looking like a SabreDAV
    issue,
    but I don’t think it is necessarily related to DAVdroid 0.8 then. (Of
    course, the issue also happens once I upgraded to 0.8, and didn’t go
    away).

    @greve, can you downgrade to a 0.6.x version of DAVdroid and see if
    the
    problem still persists?


    Reply to this email directly or view it on GitHub:
    https://github.com/bitfireAT/davdroid/issues/542#issuecomment-113731821


    Reply to this email directly or view it on GitHub:
    https://github.com/bitfireAT/davdroid/issues/542#issuecomment-113769669


    Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.


  • Hmm, you seem to be the first one to report this issue on an older version (as far as I can see), maybe it’s a slightly different issue?

    On 20 June 2015 15:44:12 CEST, Natanji notifications@github.com wrote:

    Then why does it happen in earlier versions as well?

    Am 20. Juni 2015 15:35:44 MESZ, schrieb Markus Unterwaditzer
    notifications@github.com:

    Afaict it’s already clear that changes in DavDroid 0.8+ trigger this
    behavior.

    On 20 June 2015 10:45:42 CEST, Natanji notifications@github.com
    wrote:

    I was recently made aware of this problem happening on DAVdroid
    0.6.x.

    It started 5 days ago on a friend’s phone - same error that can be
    seen
    in the screenshots (though I can’t obtain the log files so far). The
    server in question is running Horde 5.2.1, which to my knowledge also
    utilizes SabreDAV. So this is definitely looking like a SabreDAV
    issue,
    but I don’t think it is necessarily related to DAVdroid 0.8 then. (Of
    course, the issue also happens once I upgraded to 0.8, and didn’t go
    away).

    @greve, can you downgrade to a 0.6.x version of DAVdroid and see if
    the
    problem still persists?


    Reply to this email directly or view it on GitHub:
    https://github.com/bitfireAT/davdroid/issues/542#issuecomment-113731821


    Reply to this email directly or view it on GitHub:
    https://github.com/bitfireAT/davdroid/issues/542#issuecomment-113769669


  • It should not be surprising that most people use an up to date version 😉 I mean, you could be right, but that is exact why I’m asking others that have this problem to check if this happens with old versions too. Doesn’t take much time, since the error is 100% reproducible on every sync.

    Am 20. Juni 2015 15:47:09 MESZ, schrieb Markus Unterwaditzer notifications@github.com:

    Hmm, you seem to be the first one to report this issue on an older
    version (as far as I can see), maybe it’s a slightly different issue?

    On 20 June 2015 15:44:12 CEST, Natanji notifications@github.com
    wrote:

    Then why does it happen in earlier versions as well?

    Am 20. Juni 2015 15:35:44 MESZ, schrieb Markus Unterwaditzer
    notifications@github.com:

    Afaict it’s already clear that changes in DavDroid 0.8+ trigger this
    behavior.

    On 20 June 2015 10:45:42 CEST, Natanji notifications@github.com
    wrote:

    I was recently made aware of this problem happening on DAVdroid
    0.6.x.

    It started 5 days ago on a friend’s phone - same error that can be
    seen
    in the screenshots (though I can’t obtain the log files so far). The
    server in question is running Horde 5.2.1, which to my knowledge
    also

    utilizes SabreDAV. So this is definitely looking like a SabreDAV
    issue,
    but I don’t think it is necessarily related to DAVdroid 0.8 then.
    (Of

    course, the issue also happens once I upgraded to 0.8, and didn’t go
    away).

    @greve, can you downgrade to a 0.6.x version of DAVdroid and see if
    the
    problem still persists?


    Reply to this email directly or view it on GitHub:
    https://github.com/bitfireAT/davdroid/issues/542#issuecomment-113731821


    Reply to this email directly or view it on GitHub:
    https://github.com/bitfireAT/davdroid/issues/542#issuecomment-113769669


    Reply to this email directly or view it on GitHub:
    https://github.com/bitfireAT/davdroid/issues/542#issuecomment-113770078


    Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.


  • I can confirm that this issue is caused by events that have a URL as UID. Removing these events (e.g. the ones imported from Xing) restores the ability to sync the calendar without errors.


  • The issue has been nailed down to be the filter as specified by DAVDroid on REPORT, causing iRony to not encode individual event’s UID properties as properly as on a non-filter REPORT payload and/or non-REPORT requests.

    The upstream ticket is for iRony, the *DAV protocol access abstraction to Kolab backed by SabreDAV.

    You can find the ticket here: https://git.kolab.org/T474 – note that the description of the ticket changes over time as progress is made on discovering, resolving and wanting to make sure it stays resolved in the future.

    You will find that this ticket mentions two commits (one for current stable 0.3, and one for next stable 0.4/master), that appear to resolve this issue. This means this issue will be fixed for Kolab Enterprise 13, Kolab Enterprise 14, Kolab 3.4 and Kolab Development, as soon as we get our packages passed Quality Assurance and out the door.

  • developer

    Cool, thanks!

  • admin

    Great, thanks for the update and for finding that out!

Similar topics