View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003109 | SymmetricDS | Bug | public | 2017-05-15 00:59 | 2020-02-14 08:46 |
| Reporter | marc | Assigned To | |||
| Priority | low | ||||
| Status | confirmed | Resolution | open | ||
| Product Version | 3.8.24 | ||||
| Target Version | 3.10.11 | Fixed in Version | |||
| Summary | 0003109: File replication routing job fails with error message when channel is not a file sync channel - needs better error message | ||||
| Description | Hello, I have configured file sync to setup master master replication of a folder using symmetricds but I'm getting stuck. I can confirm the records in the sym_file_snapshot table on the master have been created by the tracker job, with correct data in trigger_id and router_id fields, but then routing fails with the following log output FileSyncDataRouter - Could not find a trigger router with a trigger_id of null and a router_id of null. The file snapshot will not be routed Not so sure if this is a bug or if I missed something in the config but couldn't find what is wrong. | ||||
| Steps To Reproduce | Create a /dockercom folder on source and target Insert symmetric conf : insert into sym_file_trigger (trigger_id,channel_id,base_dir,recurse,last_update_time,create_time) values('dockercom','dockercom', '/dockercom', 0, current_timestamp,current_timestamp); insert into sym_file_trigger (trigger_id,channel_id,base_dir,recurse,last_update_time,create_time) values('dockercom_slave','dockercom', '/dockercom', 0, current_timestamp,current_timestamp); insert into sym_router (router_id,source_node_group_id,target_node_group_id,router_type,create_time,last_update_time) values('master_2_store_dockercom', 'master', 'store', 'default',current_timestamp, current_timestamp); insert into sym_router (router_id,source_node_group_id,target_node_group_id,router_type,create_time,last_update_time) values('store_2_master_dockercom', 'store', 'master', 'default',current_timestamp, current_timestamp); insert into sym_file_trigger_router (trigger_id,router_id,last_update_time,create_time) values('dockercom','master_2_store_dockercom', current_timestamp, current_timestamp); insert into sym_file_trigger_router (trigger_id,router_id,last_update_time,create_time) values('dockercom_slave','store_2_master_dockercom', current_timestamp, current_timestamp); Add some text files to the master /dockercom folder Look at the master log | ||||
| Additional Information | Content of the snapshot table trigger_id, router_id, relative_dir, file_name, channel_id, reload_channel_id, last_event_type, crc32_checksum, file_size, file_modified_time, last_update_time, last_update_by, create_time 'dockercom', 'master_2_store_dockercom', '.', '.env', 'dockercom', 'filesync_reload', 'C', '3454198307', '47', '1494749769000', '2017-05-14 08:20:00', NULL, '2017-05-14 08:20:00' 'dockercom', 'master_2_store_dockercom', '.', 'docker-compose.run.yml', 'dockercom', 'filesync_reload', 'C', '1664581753', '2404', '1494749769000', '2017-05-14 08:20:00', NULL, '2017-05-14 08:20:00' 'dockercom', 'master_2_store_dockercom', '.', 'run_client_docker.sh', 'dockercom', 'filesync_reload', 'C', '1667299467', '2021', '1494749769000', '2017-05-14 08:20:00', NULL, '2017-05-14 08:20:00' 'dockercom', 'master_2_store_dockercom', '.', 'upgrade_latest', 'dockercom', 'filesync_reload', 'C', '0', '0', '1494746198000', '2017-05-14 08:20:00', NULL, '2017-05-14 08:20:00' | ||||
| Tags | file sync | ||||
|
|
marc: have you sollution this problem?I face the same problem of you. I don't know whether it's a bug or a config error. if you have the sollution,please send a email to me ,thank you ! my email is lindom@foxmail.com. |
|
|
I was able to recreate the issue. It's one of configuration (although SymmetricDS could probably do a better job of explaining the error in the logs). You have your channel for the file sync set to be "dockercom", but I'm guessing you dont have the file_sync_flag set to "1" on that channel (which indicates to SymmetricDS that it's a channel for file sync.) I can get the same error you describe above. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-05-15 00:59 | marc | New Issue | |
| 2018-06-20 04:36 | lindom | Note Added: 0001209 | |
| 2018-10-03 09:35 | hanes | Status | new => feedback |
| 2018-10-03 09:35 | hanes | Note Added: 0001249 | |
| 2018-10-17 09:18 | hanes | Status | feedback => confirmed |
| 2018-10-17 09:18 | hanes | Target Version | => 3.10.0 |
| 2018-10-17 09:18 | hanes | Summary | File replication routing job fails with error message => File replication routing job fails with error message when channel is not a file sync channel - needs better error message |
| 2018-10-17 09:18 | hanes | Target Version | 3.10.0 => |
| 2018-10-17 11:51 | hanes | Relationship added | has duplicate 0003607 |
| 2018-10-17 14:40 | hanes | Target Version | => 3.10.0 |
| 2018-10-25 15:22 | hanes | Relationship added | has duplicate 0003740 |
| 2018-12-05 14:58 | hanes | Priority | normal => low |
| 2019-03-14 08:39 | admin | Target Version | 3.10.0 => 3.10.1 |
| 2019-04-23 09:46 | elong | Target Version | 3.10.1 => 3.10.2 |
| 2019-04-24 11:08 | elong | Tag Attached: file sync | |
| 2019-05-08 08:51 | admin | Target Version | 3.10.2 => 3.10.3 |
| 2019-06-24 13:45 | elong | Target Version | 3.10.3 => 3.10.4 |
| 2019-08-09 15:41 | elong | Target Version | 3.10.4 => 3.10.5 |
| 2019-10-31 10:59 | admin | Target Version | 3.10.5 => 3.10.6 |
| 2019-11-14 14:47 | elong | Target Version | 3.10.6 => 3.10.7 |
| 2019-12-09 10:25 | admin | Target Version | 3.10.7 => 3.10.8 |
| 2020-01-02 09:40 | admin | Target Version | 3.10.8 => 3.10.9 |
| 2020-01-22 14:03 | elong | Target Version | 3.10.9 => 3.10.10 |
| 2020-02-14 08:46 | elong | Target Version | 3.10.10 => 3.10.11 |