# [Bug] New CalDAV has deleted all my appointments on the server

I tried adding a CalDAV account this morning after upgrading to 1.0.7.16 yesterday. I use owncloud and used the same credentials I had previously used for SyncEvolution. At first it didn't seem to work until I hit 'sync' a number of times. Then, all of a sudden, the calendar showed the new 'Default calendar' which contained my appointments. Some time later (perhaps an hour) my appointments vanished again. I tried to sync a few times to no effect. After checking directly in owncloud I was shocked to see all my appointments gone/deleted. These were not my business appointments but only the private ones, but it's annoying nonetheless :/

Is there a possiblity to debug the CalDAV stuff to see what has gone wrong and to avoid such a situation in future?

Edit: I was able to restore the data by a syncevolution backup (in .cache/syncevolution). Is there something similar for the integrated CalDAV sync? If not, there probably should be :)

Edit2: Now all my appointments are doubled, 'experimental' alright :D

edit retag close delete

Sorry to say, this bug still exists. It has happened to me three times now. Twice it happened in conjunction with a reboot or forced shutdown, once without any sudden irregularities (all events were just gone!). I am using Baikal 0.4.6.

( 2017-09-12 22:44:02 +0300 )edit

Sort by » oldest newest most voted

You can see warning and critical level debug for buteo in the output of journalctl, or by restarting msyncd in a shell (after doing 'system --user stop msyncd.service first). Lower levels of debug currently need to be enabled by recompilation.

Which CalDAV server do you use? I'd like to test with it. It sounds like either A) These events were not listed in the server REPORT response on a subsequent sync, and thus deleted locally, and then these changes were wrongly propagated to the server on the next sync, or B) The events were deleted locally somehow and then these changes were propagated to the server on the next sync.

more

I'm using a self-hosted owncloud. Before creating an account for you I shall investigate some more. Currently I cannot preclude that SyncEvolution deleted everything. Yet, the double appointments and the failiure to sync appointments created on the device to the server are definetly no SyncEvolution glitches (as I keep it disabled since)

( 2014-06-11 11:41:12 +0300 )edit
1

If you don't mind recompiling, then rebuilding https://github.com/nemomobile/buteo-sync-plugin-caldav with DEFINES += BUTEO_ENABLE_DEBUG in the src.pro should give you the full logs. We'll fix this to allow enabling of non-critical debug logs at runtime in a later release.

The "Sync" pulley menu currently does not work for caldav accounts; this has been fixed for the next release, so they need to be synced automatically at the moment. The double appointments I am not sure about -- this needs further investigation.

( 2014-06-12 02:29:22 +0300 )edit

Quick notice: I didn't do any debugging yet as, since the first problem, the sync seems to work somehow. I didn't have any other deleted appointments and even the transfer of appointments created on the Jolla to the server works sometimes ;)

( 2014-06-17 00:32:44 +0300 )edit
1

Update: After the latest update (Tahkalampi, 1.0.8...) sync to the server works more reliably. Will report more in future as I also updated owncloud on the server.

( 2014-07-14 23:09:27 +0300 )edit

@blam: Thanks for your debugging tips! But as I tried system --user stop msyncd.service, I only got -bash: system: command not found. (tried as nemo and devel-su at a 1.0.8.21 (Tahkalampi) jolla phone)

ps axu does list a /usr/bin/msyncd.

Can you give me a little further hint, please?

( 2014-11-17 22:51:10 +0300 )edit