View Issue Details

IDProjectCategoryView StatusLast Update
0003109SymmetricDSBugpublic2022-11-30 19:49
Reportermarc Assigned Toemiller  
Prioritylow 
Status closedResolutionfixed 
Product Version3.8.0 
Target Version3.14.3Fixed in Version3.14.3 
Summary0003109: File replication routing job fails with error message when channel is not a file sync channel - needs better error message
DescriptionHello,

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 ReproduceCreate 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 InformationContent 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'
Tagsfile sync

Relationships

has duplicate 0003607 closed file trigger error 
has duplicate 0003740 closed Error in log file could be improved in cases where file triggers are assigned to non-file-sync channels. 

Activities

lindom

2018-06-20 08:36

reporter   ~0001209

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.

hanes

2018-10-03 13:35

developer   ~0001249

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.

Related Changesets

SymmetricDS: 3.14 beda37c9

2022-11-08 18:07:44

evan-miller-jumpmind

Details Diff
0003109: Improved error message when file trigger is configured to use channel with file_sync_flag=0 Affected Issues
0003109
mod - symmetric-core/src/main/java/org/jumpmind/symmetric/route/FileSyncDataRouter.java Diff File

Issue History

Date Modified Username Field Change
2017-05-15 04:59 marc New Issue
2018-06-20 08:36 lindom Note Added: 0001209
2018-10-03 13:35 hanes Status new => feedback
2018-10-03 13:35 hanes Note Added: 0001249
2018-10-17 13:18 hanes Status feedback => confirmed
2018-10-17 13:18 hanes Target Version => 3.10.0
2018-10-17 13: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 13:18 hanes Target Version 3.10.0 =>
2018-10-17 15:51 hanes Relationship added has duplicate 0003607
2018-10-17 18:40 hanes Target Version => 3.10.0
2018-10-25 19:22 hanes Relationship added has duplicate 0003740
2018-12-05 19:58 hanes Priority normal => low
2019-03-14 12:39 admin Target Version 3.10.0 => 3.10.1
2019-04-23 13:46 elong Target Version 3.10.1 => 3.10.2
2019-04-24 15:08 elong Tag Attached: file sync
2019-05-08 12:51 admin Target Version 3.10.2 => 3.10.3
2019-06-24 17:45 elong Target Version 3.10.3 => 3.10.4
2019-08-09 19:41 elong Target Version 3.10.4 => 3.10.5
2019-10-31 14:59 admin Target Version 3.10.5 => 3.10.6
2019-11-14 19:47 elong Target Version 3.10.6 => 3.10.7
2019-12-09 15:25 admin Target Version 3.10.7 => 3.10.8
2020-01-02 14:40 admin Target Version 3.10.8 => 3.10.9
2020-01-22 19:03 elong Target Version 3.10.9 => 3.10.10
2020-02-14 13:46 elong Target Version 3.10.10 => 3.10.11
2020-03-16 20:14 admin Target Version 3.10.11 => 3.10.12
2020-05-26 12:28 elong Target Version 3.10.12 => 3.11.10
2020-06-24 20:14 elong Target Version 3.11.10 => 3.12.2
2020-07-20 13:06 elong Target Version 3.12.2 => 3.12.3
2020-08-31 19:47 elong Target Version 3.12.3 => 3.12.4
2020-09-23 15:32 admin Target Version 3.12.4 => 3.12.5
2020-11-09 13:45 admin Target Version 3.12.5 => 3.12.6
2021-01-08 20:42 admin Target Version 3.12.6 => 3.12.7
2021-02-25 13:01 admin Target Version 3.12.7 => 3.12.8
2021-03-30 19:13 admin Target Version 3.12.8 => 3.12.9
2021-04-28 14:41 admin Target Version 3.12.9 => 3.12.10
2021-05-28 11:54 admin Target Version 3.12.10 => 3.12.11
2021-07-13 12:43 admin Target Version 3.12.11 => 3.12.12
2021-11-03 12:11 elong Target Version 3.12.12 => 3.12.13
2021-12-11 17:11 admin Target Version 3.12.13 => 3.12.14
2021-12-20 13:55 admin Target Version 3.12.14 => 3.12.15
2022-01-13 13:34 elong Target Version 3.12.15 => 3.12.16
2022-04-08 17:41 elong Product Version 3.8.24 => 3.8.0
2022-04-08 17:41 elong Target Version 3.12.16 => 3.14.0
2022-07-25 16:23 elong Target Version 3.14.0 => 3.14.1
2022-08-24 18:56 elong Target Version 3.14.1 => 3.14.2
2022-10-03 14:42 elong Target Version 3.14.2 => 3.14.3
2022-11-07 13:06 elong Target Version 3.14.3 => 3.15.0
2022-11-08 18:09 emiller Assigned To => emiller
2022-11-08 18:09 emiller Status confirmed => resolved
2022-11-08 18:09 emiller Resolution open => fixed
2022-11-08 18:09 emiller Fixed in Version => 3.14.3
2022-11-08 18:09 emiller Target Version 3.15.0 => 3.14.3
2022-11-08 19:00 Changeset attached => SymmetricDS 3.14 beda37c9
2022-11-30 19:49 admin Status resolved => closed