2:28 p.m.
Hello Tino,
I tested the packages and my local CalDav/CardDav sync fails with Debian
Wheezy. The original Wheezy packages work fine.
The logfile and the stdout are attached.
Cheers,
Sebastian Heinlein
2:43 p.m.
On Thu, 2012-10-25 at 15:28 +0200, Sebastian Heinlein wrote:
Hello Tino,
I tested the packages and my local CalDav/CardDav sync fails with Debian
Wheezy. The original Wheezy packages work fine.
The logfile and the stdout are attached.
| [WARNING] libecal: Cannot get cal from factory: Timeout was reached
| [ERROR] Error allocating calendar
That looks very much like a mismatch or problem between libecal and
evolution-data-server. Which versions of these are installed?
I assume accessing the local calendar data fails the same way?
syncevolution --print-items @dpool calendar
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
4:30 p.m.
Am Donnerstag, den 25.10.2012, 15:43 +0200 schrieb Patrick Ohly:
On Thu, 2012-10-25 at 15:28 +0200, Sebastian Heinlein wrote:
> Hello Tino,
>
> I tested the packages and my local CalDav/CardDav sync fails with Debian
> Wheezy. The original Wheezy packages work fine.
>
> The logfile and the stdout are attached.
| [WARNING] libecal: Cannot get cal from factory: Timeout was reached
| [ERROR] Error allocating calendar
That looks very much like a mismatch or problem between libecal and
evolution-data-server. Which versions of these are installed?
I assume accessing the local calendar data fails the same way?
syncevolution --print-items @dpool calendar
The calendar was empty. I created an event and now it works.
But I get another problem: syncevolution complains about missing rights
to sync my addressbook. But this has worked before. I get the same error
with other accounts to. The server is davical 1.1.1.
Cheers,
Sebastian
4:50 p.m.
On Thu, 2012-10-25 at 17:30 +0200, Sebastian Heinlein wrote:
Am Donnerstag, den 25.10.2012, 15:43 +0200 schrieb Patrick Ohly:
> On Thu, 2012-10-25 at 15:28 +0200, Sebastian Heinlein wrote:
> > Hello Tino,
> >
> > I tested the packages and my local CalDav/CardDav sync fails with Debian
> > Wheezy. The original Wheezy packages work fine.
> >
> > The logfile and the stdout are attached.
>
> | [WARNING] libecal: Cannot get cal from factory: Timeout was reached
> | [ERROR] Error allocating calendar
>
> That looks very much like a mismatch or problem between libecal and
> evolution-data-server. Which versions of these are installed?
>
> I assume accessing the local calendar data fails the same way?
>
> syncevolution --print-items @dpool calendar
The calendar was empty. I created an event and now it works.
But I get another problem: syncevolution complains about missing rights
to sync my addressbook.
This is a side effect of the earlier failed sync. Please try
"--refresh-from-remote/local/slow webdav@dpool addressbook".
Use -remote when the CardDAV side has all your data, -local when the
local side is up-to-date, -slow if both have changes.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
7:59 a.m.
On Thu, Oct 25, 2012 at 17:30:19 +0200, Sebastian Heinlein wrote:
[...]
~$ syncevolution webdav@dpool addressbook
[INFO] @dpool/calendar: inactive
[INFO] @dpool/memo: inactive
[INFO] @dpool/todo: inactive
[INFO @webdav-dpool] target side of local sync ready
[INFO @webdav-dpool] @webdav-dpool/calendar: inactive
[INFO @webdav-dpool] @webdav-dpool/memo: inactive
[INFO @webdav-dpool] @webdav-dpool/todo: inactive
[INFO @webdav-dpool] @webdav-dpool/addressbook: resuming normal sync, two-way (peer is
server)
[INFO] @dpool/addressbook: resuming normal sync, two-way (peer is client)
[INFO] creating complete data backup of source addressbook before sync (enabled with
dumpData and needed for printChanges)
@dpool data changes to be applied during synchronization:
*** @dpool/addressbook ***
no changes
[INFO] @dpool/addressbook: started
[INFO] @dpool/addressbook: sent 1
[INFO @webdav-dpool] @webdav-dpool/addressbook: started
[INFO] @dpool/addressbook: resumed normal sync done unsuccessfully
[ERROR] operation not allowed (remote, status 405)
[INFO] creating complete data backup after sync (enabled with dumpData and needed for
printChanges)
Synchronization failed, see
/home/renate/.cache/syncevolution/webdav(a)dpool-2012-10-25-17-20/syncevolution-log.html for
details.
Hi Sebastian,
did you get it working with the hints from Patrick?
Regards,
Tino
5:16 a.m.
Am Freitag, den 26.10.2012, 08:59 +0200 schrieb tino.keitel
+syncevolution(a)tikei.de:
On Thu, Oct 25, 2012 at 17:30:19 +0200, Sebastian Heinlein wrote:
[...]
> ~$ syncevolution webdav@dpool addressbook
> [INFO] @dpool/calendar: inactive
> [INFO] @dpool/memo: inactive
> [INFO] @dpool/todo: inactive
> [INFO @webdav-dpool] target side of local sync ready
> [INFO @webdav-dpool] @webdav-dpool/calendar: inactive
> [INFO @webdav-dpool] @webdav-dpool/memo: inactive
> [INFO @webdav-dpool] @webdav-dpool/todo: inactive
> [INFO @webdav-dpool] @webdav-dpool/addressbook: resuming normal sync, two-way (peer
is server)
> [INFO] @dpool/addressbook: resuming normal sync, two-way (peer is client)
> [INFO] creating complete data backup of source addressbook before sync (enabled with
dumpData and needed for printChanges)
> @dpool data changes to be applied during synchronization:
> *** @dpool/addressbook ***
> no changes
>
> [INFO] @dpool/addressbook: started
> [INFO] @dpool/addressbook: sent 1
> [INFO @webdav-dpool] @webdav-dpool/addressbook: started
> [INFO] @dpool/addressbook: resumed normal sync done unsuccessfully
> [ERROR] operation not allowed (remote, status 405)
> [INFO] creating complete data backup after sync (enabled with dumpData and needed
for printChanges)
>
> Synchronization failed, see
/home/renate/.cache/syncevolution/webdav(a)dpool-2012-10-25-17-20/syncevolution-log.html for
details.
Hi Sebastian,
did you get it working with the hints from Patrick?
Regards,
Tino
It worked nicely until yesterday with Patricks help (we also had some
off list messages). But now I see a lot of duplicates in my addressbook.
(I use a Davical server, 2 Ubuntu Precise Laptops, a Debian testing
system and an Android phone - but the later only in one way sync from
the server mode).
Perhaps I will find some time to look at the logs which of the systems
caused the duplicates.
By the way do you know a tool to remove duplicated entries in a save
way? Going through 170 contacts is a quite boring and time consuming
task.
Cheers,
Sebastian
7:22 a.m.
On Mon, Oct 29, 2012 at 06:16:12 +0100, Sebastian Heinlein wrote:
[...]
By the way do you know a tool to remove duplicated entries in a save
way? Going through 170 contacts is a quite boring and time consuming
task.
How does Davical store the data? I use syncevolution with file storage
on the server side, and duplicates can be detected using grep on the
files.
Regards,
Tino
4:35 p.m.
Am Donnerstag, den 25.10.2012, 15:43 +0200 schrieb Patrick Ohly:
On Thu, 2012-10-25 at 15:28 +0200, Sebastian Heinlein wrote:
> Hello Tino,
>
> I tested the packages and my local CalDav/CardDav sync fails with Debian
> Wheezy. The original Wheezy packages work fine.
>
> The logfile and the stdout are attached.
| [WARNING] libecal: Cannot get cal from factory: Timeout was reached
| [ERROR] Error allocating calendar
That looks very much like a mismatch or problem between libecal and
evolution-data-server. Which versions of these are installed?
libecal is 3.4.3-1 and e-d-s is 3.4.3-1, too. There haven't been any
updates to both of them for weeks.
I assume accessing the local calendar data fails the same way?
syncevolution --print-items @dpool calendar
The calendar was empty. It seems that this was the problem, see other
mail.
Cheers,
Sebastian
4:51 p.m.
On Thu, 2012-10-25 at 17:35 +0200, Sebastian Heinlein wrote:
Am Donnerstag, den 25.10.2012, 15:43 +0200 schrieb Patrick Ohly:
> On Thu, 2012-10-25 at 15:28 +0200, Sebastian Heinlein wrote:
> > Hello Tino,
> >
> > I tested the packages and my local CalDav/CardDav sync fails with Debian
> > Wheezy. The original Wheezy packages work fine.
> >
> > The logfile and the stdout are attached.
>
> | [WARNING] libecal: Cannot get cal from factory: Timeout was reached
> | [ERROR] Error allocating calendar
>
> That looks very much like a mismatch or problem between libecal and
> evolution-data-server. Which versions of these are installed?
libecal is 3.4.3-1 and e-d-s is 3.4.3-1, too. There haven't been any
updates to both of them for weeks.
> I assume accessing the local calendar data fails the same way?
>
> syncevolution --print-items @dpool calendar
The calendar was empty. It seems that this was the problem, see other
mail.
That doesn't explain the failure. Looks like a bug in EDS to me. The
"Cannot get cal from factory" error message came from it.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
3488
days inactive
3492
days old
syncevolution@synevolution.org
8 comments
3 participants
participants (3)
-
Patrick Ohly -
Sebastian Heinlein -
tino.keitel+syncevolution＠tikei.de