Ticket #465 (new defect)

Opened 7 years ago

Last modified 6 years ago

syncml doesn't syncwith 3 nokia phones

Reported by: maxponzoni Owned by: dgollub
Priority: normal Milestone:
Component: Plugin: syncml Version: 0.22
Severity: blocker Keywords:
Cc:

Description (last modified by felixmoeller) (diff)

Hi My name is Max Ponzoni and i can't undestand why my nokias (9300, N70 and 6600) cant syncronize with my evolution-mail-and-all-other program.

My system is a dual Pentium with 2 G RAM and kubuntu edgy.

KBluetoothd recognize all the phones. I can push a file from my presonal to each phone, eg using konqueror : bluetooth:/ show me all phones and i can navigate into him very well.

I send to you my configuration (for the N70 only)

ponzoni@lele:~/logOS$ msynctool --showgroup N70
Groupname: N70
Member 1: evo2-sync
        Configuration : <?xml version="1.0"?>
<config>
  <address_path>default</address_path>
  <calendar_path>default</calendar_path>
  <tasks_path>default</tasks_path>
</config>

Member 2: syncml-obex-client
        Configuration : <?xml version="1.0"?>
<config>
       <bluetooth_address>00:15:A0:7D:18:35</bluetooth_address>
       <bluetooth_channel>11</bluetooth_channel>
       <interface>0</interface>
       <identifier>Pc Suite</identifier>
       <version>1</version>
       <wbxml>1</wbxml>
       <username></username>
       <password></password>
       <type>2</type>
       <usestringtable>1</usestringtable>
       <onlyreplace>0</onlyreplace>
       <recvLimit>10000</recvLimit>
       <maxObjSize>0</maxObjSize>
       <contact_db>Rubrica</contact_db>
</config>

Note that: 1) Rubrica is the Italian name of Contacts 2) no user and no password are set in the phone in syncronization profile

when i launch the sync i obtain the following response:

#msynctool --sync N70
Synchronizing group "N70"
The previous synchronization was unclean. Slow-syncing
Member 1 of type evo2-sync just connected
Member 2 of type syncml-obex-client had an error while connecting: Request not successfull: 80
Member 1 of type evo2-sync just disconnected
All clients have disconnected
The sync failed: Unable to connect one of the members
Error while synchronizing: Unable to connect one of the members

googling and searching i find (at : http://geektalk.andreat.de/2006/11/how-to-syncronize-nokia-n70-palm.html ) an extended command:

# msynctool --sync N70 --filter-objtype note --filter-objtype event --conflict 1 --slow-sync todo
Synchronizing group "N70" [slow sync]
The previous synchronization was unclean. Slow-syncing
Member 1 of type evo2-sync just connected
Member 2 of type syncml-obex-client had an error while connecting: Request not successfull: 80
Member 1 of type evo2-sync just disconnected
All clients have disconnected
The sync failed: Unable to connect one of the members
Error while synchronizing: Unable to connect one of the members

So i try with tracing (as described in GUIDE TO TRACING on your site)

#export OSYNC_TRACE=/home/ponzoni/logOS
#export OSYNC_PRIVACY=1
#msynctool --sync N70 --filter-objtype note --filter-objtype event --conflict 1 --slow-sync todo
Synchronizing group "N70" [slow sync]
The previous synchronization was unclean. Slow-syncing
Member 1 of type evo2-sync just connected
Member 2 of type syncml-obex-client had an error while connecting: Request not successfull: 80
Member 1 of type evo2-sync just disconnected
All clients have disconnected
The sync failed: Unable to connect one of the members
Error while synchronizing: Unable to connect one of the members

and the logs produces :

#grep ERROR *
Thread3081782960-4995.log:[1174291014.358611]           <--- ERROR --- _manager_event: Request not successfull: 80
Thread3081836736-4989.log:[1174291014.361678]   <--- ERROR --- osengine_sync_and_block: Unable to connect one of the members

can you help me ?

Change History

comment:1 follow-up: ↓ 2 Changed 7 years ago by felixmoeller

does this still happen several "Request not successfull: 80" were fixed since your report.

comment:2 in reply to: ↑ 1 Changed 6 years ago by mikedlr

  • Version changed from 0.21 to 0.22

Replying to felixmoeller:

does this still happen several "Request not successfull: 80" were fixed since your report.

I get the same error message with msynctool-0.22-0 and an Nokia N70; I have SYNCML_TRACE logs but am not sure what private data they might contain so I'd rather not post them here; I can email them though if useful. As far as I can tell the interesting bit is this:

[1199881821.865160] Target application/vnd.syncml+wbxml [1199881822.149885] >>>>>>> _smlObexEvent(0x9bebe58, 0x9bedc80, 0, 3, 2, 80) [1199881822.149954] Request Done [1199881822.150008] >>>>>>> smlTransportReceiveEvent(0x9beb560, (nil), 2, (nil), 0x9be94f0) [1199881822.150059] >>>>>>> _smlManagerDataHandler(0x9beb560, (nil), 2, (nil), 0x9be94f0, 0x9bec080) [1199881822.150113] >>>>>>> _smlManagerSendEvent(0x9bec080, 2, (nil), (nil), (nil), 0x9be3fb0) [1199881822.150165] <<<<<<< _smlManagerSendEvent [1199881822.150212] <--- ERROR --- _smlManagerDataHandler: Request not successfull: 80 [1199881822.150259] <<<<<<< smlTransportReceiveEvent: 0 [1199881822.150306] <--- ERROR --- _smlObexEvent: Request not successfull: 80

comment:3 Changed 6 years ago by mikedlr

Again with better formatting.. Sorry.

[1199881821.865064]                     >>>>>>>  smlTransportObexClientSend(0x9be8028, (nil), 0x9beda58, (nil))
[1199881821.865112]                             Adding connection id -1022384746
[1199881821.865160]                             Target application/vnd.syncml+wbxml
[1199881822.149885]                             >>>>>>>  _smlObexEvent(0x9bebe58, 0x9bedc80, 0, 3, 2, 80)
[1199881822.149954]                                     Request Done
[1199881822.150008]                                     >>>>>>>  smlTransportReceiveEvent(0x9beb560, (nil), 2, (nil), 0x9be94f0)
[1199881822.150059]                                             >>>>>>>  _smlManagerDataHandler(0x9beb560, (nil), 2, (nil), 0x9be94f0, 0x9bec080)
[1199881822.150113]                                                     >>>>>>>  _smlManagerSendEvent(0x9bec080, 2, (nil), (nil), (nil), 0x9be3fb0)
[1199881822.150165]                                                     <<<<<<<  _smlManagerSendEvent
[1199881822.150212]                                             <--- ERROR --- _smlManagerDataHandler: Request not successfull: 80
[1199881822.150259]                                     <<<<<<<  smlTransportReceiveEvent: 0
[1199881822.150306]                             <--- ERROR --- _smlObexEvent: Request not successfull: 80
[1199881822.150357]                     <--- ERROR --- smlTransportObexClientSend: Unable to send put request. Bailing out

comment:4 Changed 6 years ago by felixmoeller

  • Owner changed from abauer to dgollub
  • Component changed from Plugin: syncml-client to Plugin: syncml

Just learned from Daniel that syncml-client is the one based on sync4j.

comment:5 Changed 6 years ago by felixmoeller

  • Description modified (diff)
Note: See TracTickets for help on using tickets.