Alex

Hi Eric, Thank you so much for help! Yes there were 5 duplicate entries in sym_data. I deleted all of them, and removed all files in ~/symmetric-server-3.8.31/tmp/diy_s001-000/outgoing/001. and then I stop/start SymmetricDS service, still got the same error. Is this the correct directory for staging file? actually all other subdir under ~/symmetric-server-3.8.31/tmp/outgoing are empty. 2019-12-12 02:10:48,846 ERROR [diy_s001-000] [FileSyncService] [qtp1050349584-18] Failed to extract file sync batch...

Thanks Eric, I do see 5 items in sym_data using this query: mysql> select * from sym_data where data_id in (select data_id from sym_data_event where batch_id = 334) and row_data like '%iPhone11_black%'; and delete them all: mysql> delete from sym_data where data_id in (505966, 505967, 505968, 505980, 505981); Query OK, 5 rows affected (0.00 sec) I also delete all entries in ~/symmetric-server-3.8.31/tmp/diy_s001-000/outgoing/001/. and then stop / start SymmetricDS service. Still see this error, this...

When I query the sym_outgoing_batch mysql> select * from sym_outgoing_batch where status <> 'OK'; all file sync outgoing batch are blocked, with the first one statue="ER" and remained "NE" | 334 | 001 | filesync | ER | -1 | 0 | 0 | 1 | 0 | 0 | 0 | 59 | 0 | 0 | 29 | 0 | 0 | 29 | 0 | 0 | 213 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | NULL | 0 | duplicate entry: 334/PROD_Apple_iPhone11_black_PC-TPU_t.png | 0 | 0 | serveradmin.diy-here.com | 2019-12-10 23:33:48 | 2019-12-10 22:35:01 | NULL | sym_file_snapshot...

My project has been using SymmetricDS v3.8.31 for more than 2 years, very stable, with two nodes, and file sync both directions(different file name patterns). Recently, without changing any config. I got the following error, only one direction master node to client node, and no file can be synced to client from master node. File from client node can be synced to master no problem. I stopped SymmetricDS service and manually cleaned these tables from both nodes and reboot both sides, doesn't help....

I noticed Symmetric might not support utf8mb4, so I changed everything back to utf8. my.cnf: [mysqld] datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock character-set-client-handshake = FALSE character-set-server=utf8 collation_server=utf8_unicode_ci log-error=/var/log/mysqld.log pid-file=/var/run/mysqld/mysqld.pid general_log_file=/var/log/mysql.log general_log=1 [client] socket=/var/lib/mysql/mysql.sock default-character-set=utf8 [mysql] default-character-set=utf8 mysql> SHOW VARIABLES WHERE...

I also modified ~/symmetric-server-3.8.31/engines/*.properties db.url=jdbc:mysql://localhost/diy_s001?tinyInt1isBit=false => db.url=jdbc:mysql://localhost/diy_s001?tinyInt1isBit=false&characterEncoding=utf8 Still no luck

Hi , I am using symmetricDS 3.8.31. mysql 5.7.18 on Centos 7. I found that utf8mb4 (or utf8, I tried also) can not be synced to remote server, for example, mysql> select * from product where id=32; | 32 | cases | 冒牌Apple | Iphone_X | 1 | 好 | {"name": "PROD_apple_iphonex2_v.jpg", "width": "1080", "height": "1440", "inner_width": "0", "inner_height": "0"} | NULL | 0 | 0 | 2018-03-13 10:00:41 | 2018-03-13 10:03:13 | in sender's sym_data, the Chinese character also been replaced by "??": | NULL | NULL...

Hi Max, I added "file.sync.enable=true" to engine files of both root and client sides, it works! Thank you so much!