answered
2016-01-02 21:48:12 +0200
Answer at "dabaer":
Yes, logging is available via journalctl (start dev mode, ssh to Jolla, become god as devel-su, just invoke journalctl, refine with grep etc)
Yes, logging is in /home/nemo/.cache/msyncd/sync/logs
Moreover here is a different way to trace the CardCalDAV failure ... :
https://together.jolla.com/question/116918/caldavcarddav-in-saimaa-20010/?sort=votes&page=1
I doubt it helps much but it's a start.
Well ... what is the port?!?
Some sources say:
.
8843 for posteo CardDAV
.
8443 for posteo CalDav; reasonable since it works ;-)
Rem: My Calendar ONLY works if I omit the path to server!! I have to leave it empty with my posteo.de:8843 server.
.
Did anyone get CardDAV working in 2.0.0.10 or later ?!?
Some other uncertainty:
When I create a CardDAV account WITHOUT CalDAV it does create an entry in /home/nemo/.cache/mysyncd/sync anyways. With the same port, intended or not.
One is caldav-sync-13.xml and the other is carddav.Contacts-13.xml.
But why both?
Oh my dear, it is really experimental ...
.
Jan 02 20:55:24 Jolla carddav-client[1643]: [W] Syncer::cardDavError:284 - CardDAV sync finished with error: 0 purging state data for account: 13
Jan 02 20:55:24 Jolla carddav-client[1643]: [C] CardDavClient::syncFinished:142 - CardDAV sync failed: 401 ""
means what???
. I think posteo is running a Sabre Server or so. Now ...
It would help much to understand which side of the process failed ... the remote or the Jolla? What is wrong ?
Hints much appreciated!!
/d
Posteo wrote to me the Ports are as follows:
Der Port für den Kalenderabgleich ist: 8443
Der Port für den Adressbuchabgleich: 8843
This is a quote from Posteo Support 15 Jan 2016. .
I asked them for help (my CardDav does not work while my CalDav works fine. They have some employee around with a Jolla :-)
Unfortunately Posteo Support does not have log files about the connect. So I still do not know what side fails to connect using DardDAV.
Any hints welcome.
Viele Gruesse
dietmar ( 2016-01-22 07:15:20 +0200 )edit