On Mi, 2011-08-24 at 00:54 -0700, Diane Trout wrote:
> Hi,
>
> My eventual goal is to try and get an N900 to synchronize with an ubuntu
> 11.04 desktop. The bluetooth path looks broken so I was trying to understand
> how to use the syncevo-http-server.
>
> On the N900 running "syncevolution ${server}" I get the error
>
> [DEBUG 00:00:04] SAN source calendar uri
> http://192.168.34.178:9000/syncevolution/calendar type text/x-vcalendar
> [DEBUG 00:00:04] SAN with overall sync mode 206
> [INFO 00:00:04] Server sending SAN
> [INFO 00:00:04] CurlTransport Failure: No URL set!
> [DEBUG 00:00:04] exception thrown at SyncContext.cpp:1854
> [ERROR 00:00:04] error code from SyncEvolution fatal error (local, status
> 10500): Server Alerted Sync init failed
> [DEBUG 00:00:04] Module_DeleteContext 'session'
That looks like you configured ${server} on the N900 as a "PeerIsClient"
config, where "syncevolution ${server}" attempts to contact a SyncML
client.
That's the wrong way around, the N900 is the SyncML client.
> Synchronization failed, see
> /home/user/.cache/syncevolution/myrada-2011-08-24-00-11/syncevolution-log.html
> for details.
>
> The part I think I'm not understanding is the relationship between the
> context and the peer.
>
> Does the context contains the configuration for the database you want to sync?
Correct.
> And then the peer describes the various "remote" devices you're tring to
> connect to. If so, what are the URLs in the peer supposed to be?
The SyncURL has to be the address of the server,
http://192.168.34.178:9000/syncevolution for a SyncEvolution HTTP server
running on machine 192.168.34.178, listening to port 9000 and started
with that URL.
The uri of the calendar source for the peer has to be "calendar" to
match the name on the server. Recent SyncEvolution releases use that
automtically for a local source called "calendar".
> Also any guesses what the CurlTransport failure is about?
The curl transport is not prepared to send a SAN message.
> in default/config.ini syncURL is set, in
> default/peers/${server}/sources/calendar/config.ini there's a url set.
> (I disabled the other databases while trying to understand whats going
> on).
The syncURL is peer-specific and thus needs to go into
default/peers/${server}/config.ini.
It seems that you created these config files from scratch. It is much
easier to use the command line
(http://syncevolution.org/documentation/getting-started):
syncevolution --configure --template SyncEvolution \
username=... password=... \
syncURL=http://192.168.34.178:9000/syncevolution \
${server}
This assumes that you are using 1.1.99.x, otherwise --sync-property must
be used.
Or use the UI that Ove has written.
--
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.
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
