SymmetricDS: Could not find trigger router sym_file_snapshot - symmetricds

I'm doing 3-tier file synchronization. Let say the tier is Corp - Store - Device. I'm also doing it like 3-tier database synchronization. I create trigger, router, and trigger_router for Corp - Store and Store - Device.
But appeared error TriggerRouterService - Could not find triger router [sym_file_snapshot] in list [sym_file_snapshot].
After I found out, the error is the Corp node wants to connect to Device node. What's wrong here? Is my approach wrong?
Update:
Corp node wants to send initial load to Device node directly.

Check sym_node_security and look at initial_load_enabled is set or not.

Seems like sym_router routes files from Corp to Device directly. Create two sym_routers:
first one to route files from Corp's corp_directory to Store's store_directory
second one to route file from Store's store_directory to Device's device_directory

Related

ReactJS - first entry point

I am trying to work out if a visitor is entering / first page they visit is site.com/life
As we need a change a few things like:
CSS
Audio Playing in Background
etc etc.
I am wondering is their a function that allows us to work out if a path was the first entry point for that visitor?
I was thinking we could check to see if their is a back history but not sure if this would work?
Any advice would be great.
If your app is using react-router, you can access the history object and see where the oldest entry is.

Retrieving the route parameter in Next 9 when loading a page directly?

I'm trying the get the route parameter in Next 9 and all the examples in the docs make sense and work. Here https://nextjs.org/learn/basics/clean-urls-with-dynamic-routing/dynamic-routing and here https://nextjs.org/docs#imperatively
My problem is that these examples are all in the context of navigating to a page from a link, I would like to load the page directly from the url.
If I go to localhost:3000/meeting/123 it loads the index page, not teh page nested in the meetings folder.
The query parameter shows the 'asPath' key with eth value 'meeting/123' so its all working but it doesn't actually use the code at pages/meeting/[meetingId].js
How do I load a dynamic route directly from the url?
For anyone else reading this, this works absolutely fine, false alarm, I just forgot to remove my customer server setup that I had for this previously. To do this prior to next 9 you had to set up a custom server and startup using the server. I set everything up for version 9 but was still starting up in teh custom server. Leaving this up here in case anyone else makes teh same mistake.

Issue in setting up inbound calling with FreePBX in docker with a DID number?

I have a DDI number +8XXXXXXXXXXXXXX from sip.ippi.fr and I tried setting it directly on zoiper phone and when I made a call from my mobile number it worked. I want to set this inside freePBX.
So, I set up a trunk with all the sip.ippi.fr details and I created a inbound route with "+8XXXXXXXXXXXXXX" (and once with the +) "8XXXXXXXXXXXXXX" as my DID number and set the destination as an extension. I have given the context as "from-trunk" in the trunk.
Now, when I try to call this DID number over the phone, I just get an reply that the number is not available. I checked the CDR reports, there is nothing updated there. So the call does not reach the server at all.
I am using asterisk 13 with freepbx setup on docker. Is there any configuration that I am missing ?
You need to register to your provider directly as you did with zoiper. Try to register your asterisk to the sip.ippi.fr so that provider can route the calls to your freepbx, then you can distribute the call whatever you like.

Apache Camel Copying Files from multiple source folders to multiple destination folders

I am new to camel and we are building an EDI engine and our requirement is to read the files from multiple folders then second step is to parse the message type and the receiver id and based on that the messages need to be routed to different folders.
The source, message type, receiver id and destination cannot be hardcoded in camel instead it should be read from the database and the routes need to be built dynamically.
Please let me know what should be the strategy that we need to follow.
Thanks,
Jayadeep
As I understand from your comments, you can read from multiple folders by adding routes dynamically but are facing issue when trying to decide on where to send the messages as the destination , headers etc is being read from database.
Here's how I would do it.
Get the file --> Enrich it with database call and get the receiever id etc --> Use Xpath and get the receiver id etc and set them in propertyor header --> Use XSLT and remove the values that you enriched for database call so now you have the original message ---> Now use router and look at properties/headers to decide the <camel:to> path

Torrent file protocol - custom field

I am wondering if there is any available field in the .torrent files that could be used for some custom functionality in someone's implementation of a torrent client? For example, one might want to encode an URL to the file owner's website, someone else - some custom message to be displayed when opening the files, etc. Is something like this feasible in the current implementation of .torrent files?
Yes. .torrent files are just bencoded dictionaries and can hold arbitrary key-value pairs.
The main consideration when adding a custom field is to determine whether it should go into the root of the .torrent or inside the info dictionary.
If it goes into the root, it will not affect the info hash (which is the unique identifier of the torrent), and it will also not be available when downloading magnet links.
If it goes into the info dictionary, it is sort of locked down to the info-hash, in the sense that the info-hash depends on it. It will be transferred as part of the metadata when downloading magnet links and it cannot be changed (without changing the info-hash and thus creating a separate swarm).
So, if it's something you want 3rd parties should be able to change after the torrent was created, it should go in the root, if you want it to be entered once when the torrent is created and never change, it should go in the info dict.

Resources