View Issue Details

IDProjectCategoryView StatusLast Update
0003600SymmetricDSBugpublic2019-08-26 08:45
ReportercuztomiseAssigned Toelong 
Prioritynormal 
Status closedResolutionopen 
Product Version3.9.8 
Target VersionFixed in Version 
Summary0003600: symmetric ds unable to sync between servers
Descriptioni am trying to connect a database from ssl based master server to a non-ssl based slave server but i am unable to sync between them . data is routed from master server and there are logs in sym_outgoing_batch table but there are no logs in sym_incoming_table at slave end also i receive following error at slave end.

2018-06-13T05:58:59.197511Z 388 [Note] Aborted connection 388 to db: 'testdb' user: 'cuz' host: '10.10.12.2' (Got an error reading communication packets)
2018-06-13T05:58:59.201265Z 393 [Note] Aborted connection 393 to db: 'testdb' user: 'cuz' host: '10.10.12.2' (Got an error reading communication packets)
2018-06-13T05:58:59.201356Z 390 [Note] Aborted connection 390 to db: 'testdb' user: 'cuz' host: '10.10.12.2' (Got an error reading communication packets)
2018-06-13T05:58:59.201484Z 392 [Note] Aborted connection 392 to db: 'testdb' user: 'cuz' host: '10.10.12.2' (Got an error reading communication packets)
2018-06-13T05:58:59.201631Z 391 [Note] Aborted connection 391 to db: 'testdb' user: 'cuz' host: '10.10.12.2' (Got an error reading communication packets)

there are no errors in symmetric ds logs and i can see connection being established between master and slave server as initial table formation take place at both ends but there doesn't seems to be any data synchronization
TagsNo tags attached.

Activities

elong

2019-04-24 14:32

developer   ~0001436

It's a network communication error. In the slave database, look in sym_node for the row where node_id matches the master, and verify what sync_url is being used. You can put the same sync_url in a web browser to test it. Make sure you set it to "http" or "https" correctly. The ports for http and https are in the conf/symmetric-server.properties file.

admin

2019-08-26 08:45

administrator   ~0001579

Auto closing all issues waiting for feedback after 4 months. We don't have enough information to take any action.

Issue History

Date Modified Username Field Change
2018-06-13 02:19 cuztomise New Issue
2019-04-24 14:32 elong Assigned To => elong
2019-04-24 14:32 elong Status new => feedback
2019-04-24 14:32 elong Note Added: 0001436
2019-08-26 08:45 admin Note Added: 0001579
2019-08-26 08:45 admin Status feedback => closed