5:51 a.m.
Hello
I was trying to set up a synchronization between my Nokia N900 phone and
owncloud (www.http://owncloud.org/). I followed instructions made by one of the
developpers of owncloud (http://tanghus.net/2012/01/syncing-your-n900-with-
owncloud/).
Syncing the contacts works suprisingly well, but I stucked by the initial slow
sync with the contacts. If I try to run the synchronization using:
$ syncevolution --sync slow owncloud-calendar
as described in the how-to I got following output :
#######################
[INFO] @default/contacts: inactive
[INFO @owncloud-calendar] @owncloud-calendar/addressbook: inactive
[INFO @owncloud-calendar] @owncloud-calendar/memo: inactive
[INFO @owncloud-calendar] @owncloud-calendar/todo: inactive
[INFO @owncloud-calendar] @owncloud-calendar/contacts: inactive
[INFO @owncloud-calendar] @owncloud-calendar/calendar: starting first time sync,
two-way
[INFO @owncloud-calendar] creating complete data backup before sync (enabled
with dumpData and needed for printChanges)
@owncloud-calendar data changes to be applied during synchronization:
*** @owncloud-calendar/calendar ***
no changes
[INFO] @default/calendar: starting first time sync, two-way
[ERROR] @default/calendar: error code from SyncEvolution fatal error (local,
status 10500): @default/calendar: not found: N900
[INFO] @default/calendar: first time sync done unsuccessfully
[ERROR] @default/calendar: fatal error (local, status 10500)
[INFO] creating complete data backup after sync (enabled with dumpData and
needed for printChanges)
Synchronization failed, see /home/user/.cache/syncevolution/owncloud_+calendar-
2012-03-11-19-46/syncevolution-log.html for details.
Changes applied during synchronization:
+---------------|-----------------------|-----------------------|-CON-+
| | @default | @owncloud-calendar | FLI |
| Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL | ERR | CTS |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| calendar | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| slow, 0 KB sent by client, 0 KB received |
| fatal error (local, status 10500) |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| start Sun Mar 11 19:46:50 2012, duration 0:08min |
| fatal error (local, status 10500) |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
First ERROR encountered: error code from SyncEvolution fatal error (local,
status 10500): @default/calendar: not found: N900
[ERROR @owncloud-calendar] parent has died unexpectedly
[INFO @owncloud-calendar] @owncloud-calendar/calendar: first time sync done
unsuccessfully
[ERROR @owncloud-calendar] @owncloud-calendar/calendar: aborted on behalf of
user (local, status 20017)
[INFO @owncloud-calendar] creating complete data backup after sync (enabled with
dumpData and needed for printChanges)
Synchronization failed, see
/home/user/.cache/syncevolution/target_+config@owncloud_+calendar-2012-03-11-19-
46-a/syncevolution-log.html for details.
Changes applied during synchronization:
+---------------|-----------------------|-----------------------|-CON-+
| | @owncloud-calendar | @default | FLI |
| Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL | ERR | CTS |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| calendar | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| slow, 0 KB sent by client, 0 KB received |
| item(s) in database backup: 0 before sync, 0 after it |
| aborted on behalf of user (local, status 20017) |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| start Sun Mar 11 19:46:53 2012, duration 0:06min |
| external transport failure (local, status 20043) |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
First ERROR encountered: parent has died unexpectedly
Data modified @owncloud-calendar during synchronization:
*** @owncloud-calendar/calendar ***
no changes
[ERROR @owncloud-calendar] writev(): Broken pipe
#######################
Here is my set up :
syncevolution --configure \
--template SyncEvolution \
backend=CalDAV \
--sync-property username=karlitos \
--sync-property password=****** \
--sync-property
syncURL=http://192.168.178.4/owncloud/apps/calendar/caldav.php/calendars/karlito
s/calendar \
--sync-property deviceId=n900 \
consumerReady=0 \
target-config@owncloud-calendar
syncevolution --configure \
--template "SyncEvolution Client" \
syncURL=local://@owncloud-calendar \
evolutionsource=N900 \
username= \
password= \
type=maemo-events \
consumerReady=1 \
owncloud-calendar calendar
I tried to use google to find out what is going worng, but without success.
Could anybody please give me some hints ? I have no idea where to start to find
the error.
Thanks in advance - K
1:04 p.m.
Den 11. mars 2012 19:51, skrev karlitos:
I was trying to set up a synchronization between my Nokia N900 phone
and
owncloud (www.http://owncloud.org/). I followed instructions made by one of the
developpers of owncloud (http://tanghus.net/2012/01/syncing-your-n900-with-
owncloud/).
Some of those config options are unnecessary. In particular, on the
N900, if you just want something that works, you'd usually be better off
using the defaults for "evolutionsource" instead of specifying it
explicitly (this goes for both contacts and calendar). It's also safe to
rely on the defaults for "type". And the "consumerReady" option
won't do
anything particularly useful on the N900 (unlike the other GUIs, the
N900 GUI doesn't look at it), but doesn't hurt of course.
It's possible that, depending on where you purchased your N900, that the
primary calendar is not called "N900". If you hadn't explicitly
specified evolutionsource, then SyncEvolution would have picked your
primary calendar by default no matter what it's called. If you do want
to specify the source explicitly (which you might if you have more than
one calendar you want to sync), you should be sure of what its name is.
Running "syncevolution" without arguments will provide a list.
If you please, could you post the output of "syncevolution" without
arguments here, for future reference, and so that we can be sure that's
the problem?
6:18 p.m.
Ove Kåven <ovek@...> writes:
Den 11. mars 2012 19:51, skrev karlitos:
> I was trying to set up a synchronization between my Nokia N900 phone and
> owncloud (www.http://owncloud.org/). I followed instructions made by one of
the
> developpers of owncloud
(http://tanghus.net/2012/01/syncing-your-n900-with-
> owncloud/).
Some of those config options are unnecessary. In particular, on the
N900, if you just want something that works, you'd usually be better off
using the defaults for "evolutionsource" instead of specifying it
explicitly (this goes for both contacts and calendar). It's also safe to
rely on the defaults for "type". And the "consumerReady" option
won't do
anything particularly useful on the N900 (unlike the other GUIs, the
N900 GUI doesn't look at it), but doesn't hurt of course.
It's possible that, depending on where you purchased your N900, that the
primary calendar is not called "N900". If you hadn't explicitly
specified evolutionsource, then SyncEvolution would have picked your
primary calendar by default no matter what it's called. If you do want
to specify the source explicitly (which you might if you have more than
one calendar you want to sync), you should be sure of what its name is.
Running "syncevolution" without arguments will provide a list.
If you please, could you post the output of "syncevolution" without
arguments here, for future reference, and so that we can be sure that's
the problem?
Thank youm thank you very much ! I just renamed the default calendar from
default to N900 and the sync just worked fine! Thats great.
Beside that, it would be very kind from you, if you could give me some hints how
to set up the sync properly. Especially if I want to set synchronization between
different calendars. I am just a bit confused by the many options and parameters
of syncevolution. But I guess the evolutionsource= options specifies the name of
the calendar on the N900 device, right ?
Here is the desired output:
CalDAV:
select database via relative URI (<path>)
CardDAV:
select database via relative URI (<path>)
Evolution Address Book = Evolution Contacts = evolution-contacts:
<<system>> (file:///home/user/.osso-abook/db) <default>
Maemo Calendar = maemo-events:
N900 (id:1) <default>
Privat (id:2)
cal_ti_smart_birthdays (id:3)
Work (id:4)
owncloud-calendar (id:5)
Maemo Tasks = maemo-tasks:
N900 (id:1) <default>
Privat (id:2)
cal_ti_smart_birthdays (id:3)
Work (id:4)
owncloud-calendar (id:5)
Maemo Notes = maemo-notes:
N900 (id:1) <default>
Privat (id:2)
cal_ti_smart_birthdays (id:3)
Work (id:4)
owncloud-calendar (id:5)
Show available sources:
syncevolution
Show information about configuration(s):
syncevolution --print-servers|--print-configs|--print-peers
Show information about a specific configuration:
syncevolution --print-config [--quiet] [--] <config> [main|<source> ...]
List sessions:
syncevolution --print-sessions [--quiet] [--] <config>
Show information about SyncEvolution:
syncevolution --help|-h|--version
Run a synchronization as configured:
syncevolution <config> [<source> ...]
Run a synchronization with properties changed just for this run:
syncevolution --run <options for run> [--] <config> [<source> ...]
Restore data from the automatic backups:
syncevolution --restore <session directory> --before|--after [--dry-run] [--]
<config> <source> ...
Create, update or remove a configuration:
syncevolution --configure <options> [--] <config> [<source> ...]
syncevolution --remove|--migrate <options> [--] <config>
List items:
syncevolution --print-items [--] <config> <source>
Export item(s):
syncevolution [--delimiter <string>] --export <dir>|<file>|- [--]
<config>
<source> [<luid> ...]
Add item(s):
syncevolution [--delimiter <string>|none] --import <dir>|<file>|- [--]
<config> <source>
Update item(s):
syncevolution --update <dir> [--] <config> <source>
syncevolution [--delimiter <string>|none] --update <file>|- [--]
<config>
<source> <luid> ...
Remove item(s):
syncevolution --delete-items [--] <config> <source> (<luid> ... |
'*')
Thank you again for your very help, greetings - K
9:43 p.m.
Den 12. mars 2012 08:18, skrev karlitos:
Ove Kåven <ovek@...> writes:
>
> Den 11. mars 2012 19:51, skrev karlitos:
>> I was trying to set up a synchronization between my Nokia N900 phone and
>> owncloud (www.http://owncloud.org/). I followed instructions made by one of
the
>> developpers of owncloud (http://tanghus.net/2012/01/syncing-your-n900-with-
>> owncloud/).
>
> Some of those config options are unnecessary. In particular, on the
> N900, if you just want something that works, you'd usually be better off
> using the defaults for "evolutionsource" instead of specifying it
> explicitly (this goes for both contacts and calendar). It's also safe to
> rely on the defaults for "type". And the "consumerReady" option
won't do
> anything particularly useful on the N900 (unlike the other GUIs, the
> N900 GUI doesn't look at it), but doesn't hurt of course.
>
> It's possible that, depending on where you purchased your N900, that the
> primary calendar is not called "N900". If you hadn't explicitly
> specified evolutionsource, then SyncEvolution would have picked your
> primary calendar by default no matter what it's called. If you do want
> to specify the source explicitly (which you might if you have more than
> one calendar you want to sync), you should be sure of what its name is.
> Running "syncevolution" without arguments will provide a list.
>
> If you please, could you post the output of "syncevolution" without
> arguments here, for future reference, and so that we can be sure that's
> the problem?
>
Thank youm thank you very much ! I just renamed the default calendar from
default to N900 and the sync just worked fine! Thats great.
Beside that, it would be very kind from you, if you could give me some hints how
to set up the sync properly. Especially if I want to set synchronization between
different calendars. I am just a bit confused by the many options and parameters
of syncevolution. But I guess the evolutionsource= options specifies the name of
the calendar on the N900 device, right ?
Here is the desired output:
Well, I was hoping you'd show this without going to the step of renaming
your calendars first. You could have just changed the SyncEvolution
configuration instead to use whatever calendar name you're using.
Maemo Calendar = maemo-events:
N900 (id:1) <default>
So am I to understand that this wasn't actually N900 before, but
something else?
11:26 p.m.
Den 12. mars 2012 11:43, skrev Ove Kåven:
> Beside that, it would be very kind from you, if you could give me
some hints how
> to set up the sync properly. Especially if I want to set synchronization between
> different calendars. I am just a bit confused by the many options and parameters
> of syncevolution. But I guess the evolutionsource= options specifies the name of
> the calendar on the N900 device, right ?
Forgot this. Yes, the evolutionsource lets you select a local calendar.
And the very last parameter in your configuration command for
"SyncEvolution Client" is a name for the particular source
configuration, you can use different names there (e.g. calendar2,
calendar3, etc) to configure multiple calendars. If you need to provide
different CalDAV URLs, you also need to add this parameter to the CalDAV
configuration command, so that the CalDAV URLs and local calendars can
be matched up.
I suppose you could also look at the instructions for syncing N900 with
Radicale, another type of CalDAV server:
http://syncevolution.org/wiki/synchronizing-radicale
(though on that page they don't seem to explain how to configure the
"SyncEvolution Client" side. They seem to assume that SyncEvolution will
use the source configuration name as the default evolutionsource when
it's not explicitly given. Not sure if that assumption is true.)
3:50 a.m.
Ove Kåven <ovek@...> writes:
Den 12. mars 2012 11:43, skrev Ove Kåven:
>> Beside that, it would be very kind from you, if you could give me some
hints how
>> to set up the sync properly. Especially if I want to set
synchronization
between
>> different calendars. I am just a bit confused by the many
options and
parameters
>> of syncevolution. But I guess the evolutionsource= options
specifies the
name of
>> the calendar on the N900 device, right ?
Forgot this. Yes, the evolutionsource lets you select a local calendar.
And the very last parameter in your configuration command for
"SyncEvolution Client" is a name for the particular source
configuration, you can use different names there (e.g. calendar2,
calendar3, etc) to configure multiple calendars. If you need to provide
different CalDAV URLs, you also need to add this parameter to the CalDAV
configuration command, so that the CalDAV URLs and local calendars can
be matched up.
I suppose you could also look at the instructions for syncing N900 with
Radicale, another type of CalDAV server:
http://syncevolution.org/wiki/synchronizing-radicale
(though on that page they don't seem to explain how to configure the
"SyncEvolution Client" side. They seem to assume that SyncEvolution will
use the source configuration name as the default evolutionsource when
it's not explicitly given. Not sure if that assumption is true.)
_______________________________________________
SyncEvolution mailing list
SyncEvolution <at> syncevolution.org
http://lists.syncevolution.org/listinfo/syncevolution
Hello
Sory for changing the calendar name instead of changing the sync-configuration.
I was just on the way to work and wanted to try
the sync fast
before leaving the house.
I read the wiki-article about the synchronization with radicale. Lot of things
are clearer now, but in some points I am still
confused a bit.
Should I use the --sync-property command or is it correct to use for example
username=**** like in the article ?
I am not quite sure how to set the syncURL in the first command propperly. In my
setup I used
syncURL=http://192.168.178.4/owncloud/apps/calendar/caldav.php/calendars/karlito
s/calendar , so for the first command (yncevolution --configure --template
webdav) I use the URL part before the username ?
Like
syncURL=http://192.168.178.4/owncloud/apps/calendar/caldav.php/calendars/ ???
At the end of the database URL - should there be a trailing / after the calendar
name ? The wiki article says yes, but in my
first config I
did not use it.
The deviceId and all the other propeties, used by me in the first config, are
they not needed ?
If I did understand it right, the config should looks like :
syncevolution --configure \
--template webdav \
username=karlitos \
password=*myPass* \
SyncURL=http://192.168.178.4/owncloud/apps/calendar/caldav.php/calendars/ \
target-config@owncloud
syncevolution --configure \
database=http://192.168.178.4/owncloud/apps/calendar/caldav.php/calendars/karlit
os/private \
backend=caldav \
evolutionsource=default \
target-config@owncloud private-cal
syncevolution --configure \
database=http://192.168.178.4/owncloud/apps/calendar/caldav.php/calendars/karlit
os/work \
backend=caldav \
evolutionsource=work \
target-config@owncloud work-cal
Thank you very much again for all your help. I am very excited about the working
sync.
Greetings - K
4:59 a.m.
Den 12. mars 2012 17:50, skrev karlitos:
Should I use the --sync-property command or is it correct to use for
example
username=**** like in the article ?
In SyncEvolution 1.2, the "--sync-property" part became unnecessary, but
for backwards compatibility reasons, it still works. It's up to you
whether to use it.
I am not quite sure how to set the syncURL in the first command
propperly. In my
setup I used
syncURL=http://192.168.178.4/owncloud/apps/calendar/caldav.php/calendars/karlito
s/calendar , so for the first command (yncevolution --configure --template
webdav) I use the URL part before the username ?
Like
syncURL=http://192.168.178.4/owncloud/apps/calendar/caldav.php/calendars/ ???
Maybe? Whatever your CalDAV server expects, if you're going to rely on
SyncEvolution's autodetection. If you're thinking of the radicale
instructions, it seems they're overriding it with the "database" option
anyway, so the autodetect probably won't be used anyway.
At the end of the database URL - should there be a trailing / after
the calendar
name ? The wiki article says yes, but in my
first config I
did not use it.
Use it. From what I understand, Radicale gets particularly upset if you
don't, but you should probably use it with all other CalDAV servers too.
The deviceId and all the other propeties, used by me in the first
config, are
they not needed ?
Ordinarily not. SyncEvolution has quite sane defaults, but your mileage
may vary. You can use them if you like.
syncevolution --configure \
database=http://192.168.178.4/owncloud/apps/calendar/caldav.php/calendars/karlit
os/private \
backend=caldav \
evolutionsource=default \
target-config@owncloud private-cal
The target-config is for configuring the remote database, so you cannot
use evolutionsource there. The evolutionsource should go into the local
configuration (i.e., the corresponding "SyncEvolution Client" stuff).
8:38 p.m.
Hello Ove,
thanks for helping Karel. I really appreciate not having to answer all
questions myself :-)
On Mon, 2012-03-12 at 13:26 +0100, Ove Kåven wrote:
I suppose you could also look at the instructions for syncing N900
with
Radicale, another type of CalDAV server:
http://syncevolution.org/wiki/synchronizing-radicale
(though on that page they don't seem to explain how to configure the
"SyncEvolution Client" side. They seem to assume that SyncEvolution will
use the source configuration name as the default evolutionsource when
it's not explicitly given. Not sure if that assumption is true.)
You are right, the client side setup is missing. The additional
calendars need to be configured there, too, because there is no such
implicit access to local databases based on the source name.
I've added instructions for the "radicale" sync config to the Wiki.
--
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.
9:21 a.m.
Hello Ove and Patrik
You are really very kind by helping me -)
I read through the most of the syncevolution-usage article in the syncevolution
wiki.
I can not say I did understand everything and I am still confused a lot.
So please check the following description and correct me one more time.
starting point
I would like to sync a personal CalDAV Calendar located under the URL
http
//192.168.178.4/owncloud/apps/calendar/caldav.php/calendars/karlitos/private
with a calendar on my N900 Phone named Privat and a work CalDav Calendar located
under
http //192.168.178.4/owncloud/apps/calendar/caldav.php/calendars/karlitos/work
with another calendar on N900 which has the name Work.
And this is my new setup
syncevolution --configure \
--template webdav \
username=karlitos \
password=****** \
SyncURL=http //192.168.178.4/owncloud/apps/calendar/caldav.php/calendars/ \
target-config@owncloud_new
syncevolution --configure \
database=http //192.168.178.4/owncloud/apps/calendar/caldav.php
/calendars/karlitos/private/ \
backend=caldav \
target-config@owncloud_new private-cal
syncevolution --configure \
database=http
//192.168.178.4/owncloud/apps/calendar/caldav.php/calendars/karlitos/work/ \
backend=caldav \
target-config@owncloud_new work-cal
syncevolution --configure \
--template SyncEvolution_Client \
sync=none \
syncURL=local //@owncloud_new \
username= \
password= \
owncloud_new
syncevolution --configure \
sync=two-way \
backend=calendar \
database= \
evolutionsource=Privat \
owncloud_new private-cal
syncevolution --configure \
sync=two-way \
backend=calendar \
database= \
evolutionsource=Work \
owncloud_new work-cal
Does it looks good or am I still missing something ?
Can not try it at this moment, so I just hope it is Ok.
Greetings - Karel
11:49 a.m.
Den 13. mars 2012 23:21, skrev karlitos:
syncevolution --configure \
--template SyncEvolution_Client \
sync=none \
syncURL=local //@owncloud_new \
I assume you mean to have colons in these URLs.
username= \
password= \
owncloud_new
syncevolution --configure \
sync=two-way \
backend=calendar \
database= \
evolutionsource=Privat \
owncloud_new private-cal
"evolutionsource" is a backwards-compatible alias for "database". You
can use either, but it's useless to specify both.
Otherwise it seems OK to me, I think.
6:39 a.m.
Hello
It works ! That is great, I am so happy. :-) And the most important thing is: I
am seeing through the config now (at least a little bit).
The two last thing I would like to ask are:
How to incorporate a contacts-sync into the configuration. Thomas Tanghus did in
the configuration described in his blog (http://tanghus.net/2012/01/syncing-your-
n900-with-owncloud/) a second config under the name owncloud-contacts. This way
it is necessary to start the sync two times (calendar and then contacts). I know
that I could use a bash script for example, but I would like to snyc everything
together infscript for example, but I would like to snyc everything script for
example, but I would like to snyc everything aking the con one command.
I thought about making the configuration as described in the blog under the same
name as I did the configuration for the calendar. Would this work ?
A secon thing is that I would like to send you (Patrick and Ove) a post card as
thanks for your excelent support (as described on the homepage). The adress of
Patrick is linked on the syncevolution page, so if i could have one from Ove
please ?
11:31 a.m.
Den 14. mars 2012 20:39, skrev karlitos:
I thought about making the configuration as described in the blog
under the same
name as I did the configuration for the calendar. Would this work ?
If they use the same configuration, they will share the deviceId,
syncURL, username, password, consumerReady and a few other settings (but
not things like backend, type, and database, which are source-specific).
Thus, like for the calendars, you should set the addressbook-specific
synchronization URL in the "database" property, not in the syncURL
itself. Otherwise, it's the same server, so it's supposed to work.
A secon thing is that I would like to send you (Patrick and Ove) a
post card as
thanks for your excelent support (as described on the homepage). The adress of
Patrick is linked on the syncevolution page, so if i could have one from Ove
please ?
I'm not really interested enough in a post card to give my address to a
stranger on the Internet just for that.
7:18 a.m.
I'm not really interested enough in a post card to give my
address to a
stranger on the Internet just for that.
I Understand. So let me just thank you again for the time you spend helping me
with the configuration. I try to use the information to extend the owncloud
documentation.
Cheers - Karel
3839
days inactive
3843
days old
syncevolution@synevolution.org
12 comments
3 participants
participants (3)
-
karlitos -
Ove Kåven -
Patrick Ohly