3:54 a.m.
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'
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? 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?
Also any guesses what the CurlTransport failure is about?
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).
Thanks
Diane
4:54 a.m.
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.
2:14 a.m.
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.
Got it, correcting the peerIsClient fixed it.
This assumes that you are using 1.1.99.x, otherwise --sync-property
must
be used.
Ah, sync-property is optional with 1.1.99?
Thank you for your help.
Diane
3:54 a.m.
On Mi, 2011-08-24 at 23:14 -0700, Diane Trout wrote:
> This assumes that you are using 1.1.99.x, otherwise
--sync-property must
> be used.
Ah, sync-property is optional with 1.1.99?
Yes. Because the property names are unique, the command line now
automatically determines whether a foo=bar assignment is a sync or
source property assignment.
--
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:04 a.m.
New subject: [SyncEvolution] N900 Bluetooth (was: Re: trying to understand syncevolution config)
On Mi, 2011-08-24 at 00:54 -0700, Diane Trout wrote:
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.
Have you tried the latest hint about updating openobex on the N900? See:
https://bugs.meego.com/show_bug.cgi?id=4835#c19
Now that I think about it, if the problem really is the message size,
perhaps there is an easier workaround. On the desktop side, when
configuring the N900 in SyncEvolution, set the maxMsgSize to something
small, for example maxMsgSize=8192.
Run with loglevel=5 and you will get *.wbxml files dumped into the
session directory (the one which contains the -log.html file, mentioned
at the end of each failed sync). Those *.wbxml files should be smaller
than 8192 bytes.
--
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.
3:15 a.m.
New subject: [SyncEvolution] N900 Bluetooth (was: Re: trying to understand syncevolution config)
Have you tried the latest hint about updating openobex on the N900?
See:
https://bugs.meego.com/show_bug.cgi?id=4835#c19
haven't tried that, will try when more awake.
Now that I think about it, if the problem really is the message size,
perhaps there is an easier workaround. On the desktop side, when
configuring the N900 in SyncEvolution, set the maxMsgSize to something
small, for example maxMsgSize=8192.
Run with loglevel=5 and you will get *.wbxml files dumped into the
session directory (the one which contains the -log.html file, mentioned
at the end of each failed sync). Those *.wbxml files should be smaller
than 8192 bytes.
Ok I did try that and it didn't work for me. Nor did I did I get wbxml files.
Tail of my log is below:
To configure to connect via bluetooth I did the following:
syncevolution --configure --template Nokia_N900 --sync-property
syncURL=obex-bt://AD:DR:RE:SS:00:00 ${newpeer}
And then edited default/peers/${newpeer} and changed loglevel to "loglevel = 5"
I did also verify that the bluetooth connection worked by using the ubuntu bluetooth menu
to browse files on my phone. And just to be thorough I tried it with the bluetooth file
browser mounted and unmounted, but in both cases the tail, after loading backend
libraries, was the same.
Diane
--- log of "syncevolution ${newpeer}
[2011-08-26 00:02:40.609] starting SAN 12 auth 1B2M2Y8AsgTpgAmY7PhCfg== nonce
SyncEvolution session 1 server PC Suite
[2011-08-26 00:02:40.610] SAN source addressbook uri Contacts type 7 mode 206
[2011-08-26 00:02:40.610] SAN source calendar+todo uri Calendar type 6 mode 206
[2011-08-26 00:02:40.610] SAN source memo uri Notes type 3 mode 206
[2011-08-26 00:02:40.679] Connecting Bluetooth device with address AD:DR:RE:SS:00:00 and
channel 25
[2011-08-26 00:02:40.707] OBEX progress
[2011-08-26 00:02:40.754] Cancel disconncting process
[2011-08-26 00:02:40.754] Server Alerted Sync init with SANFormat 12 failed, trying with
legacy format
[2011-08-26 00:02:40.754] starting SAN 11 auth 1B2M2Y8AsgTpgAmY7PhCfg== nonce
SyncEvolution session 1 server PC Suite
[2011-08-26 00:02:40.754] SAN source addressbook uri Contacts type text/x-vcard
[2011-08-26 00:02:40.755] SAN source calendar+todo uri Calendar type text/x-vcalendar
[2011-08-26 00:02:40.755] SAN source memo uri Notes type text/plain
[2011-08-26 00:02:40.755] SAN with overall sync mode 206
[2011-08-26 00:02:40.779] Connecting Bluetooth device with address AD:DR:RE:SS:00:00 and
channel 25
[2011-08-26 00:02:40.791] OBEX progress
[2011-08-26 00:02:40.816] Cancel disconncting process
[2011-08-26 00:02:40.817] TransportException thrown at ObexTransportAgent.cpp:374
[2011-08-26 00:02:40.818] ObexTransprotAgent: Underlying transport error
[2011-08-26 00:02:40.819] ##### enginemodulebase (LNK): Disconnect
4 a.m.
New subject: [SyncEvolution] N900 Bluetooth (was: Re: trying to understand syncevolution config)
On Fr, 2011-08-26 at 00:15 -0700, Diane Trout wrote:
> Now that I think about it, if the problem really is the message
size,
> perhaps there is an easier workaround. On the desktop side, when
> configuring the N900 in SyncEvolution, set the maxMsgSize to something
> small, for example maxMsgSize=8192.
>
> Run with loglevel=5 and you will get *.wbxml files dumped into the
> session directory (the one which contains the -log.html file, mentioned
> at the end of each failed sync). Those *.wbxml files should be smaller
> than 8192 bytes.
Ok I did try that and it didn't work for me. Nor did I did I get wbxml files.
Tail of my log is below:
[...]
It fails too early, before the SyncML session with its wbxml messages
even starts.
Therefore setting the maximum message size can't have an effect. I also
wonder whether the message size really is the root cause, because the
initial SAN message is fairly small already.
--
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.
3474
days inactive
3476
days old
syncevolution@synevolution.org
6 comments
2 participants
participants (2)
-
Diane Trout -
Patrick Ohly