ArcLink remote merging tool (one-way synchronization)
sync_arc is a tool that merges inventory from different arclink sources into your SeisComP3 database by following a list of nodes (master table) provided by the webdc.eu portal (or another source as configured on the configuration file). This tool is today used inside the EIDA (European Integrated Data Archives) network to keep its nodes synchronized (the inventory and routing parts).
Warning
Running seiscomp update-config (or using the GUI scconfig) to update the system configuration will erase from your database the last one-way synchronized inventory and routing. It will be necessary to run the sync_arc again to restore the missing entries of the inventory and routing after each update.
sync_arc inherits global options.
Type: string
Indicates a folder to store/retrieve the RAW inventory files when the options --keep-raw/--load-raw are in use Default is ./.
Type: int
Indicate the number of Inventory and Routing files that the pool folder should contain. If set to 0 the pool folder is never cleaned, if this variable contains a number larger than zero the sync_arc program will make sure that the pool folder contains only "poolKeep" set of files (inventory/routing) for each node. Default is 0.
Type: string
Location of the webservice responsible for generating the master table. The complete address used is: #masterTableAddress#/table?group=#arclinkGroup# Default is http://webdc.eu/arclink.
Type: string
The arclink network group name that we want to merge to. This will be used to query the server pointed by the 'masterTableAddress' for the master table as indicated. Default is eida.
show help message.
show version information
Use alternative configuration file. When this option is used the loading of all stages is disabled. Only the given configuration file is parsed and used. To use another name for the configuration create a symbolic link of the application or copy it, eg scautopick -> scautopick2.
Load given plugins.
Run as daemon. This means the application will fork itself and doesn't need to be started with &.
Enable/disable self-shutdown because a master module shutdown. This only works when messaging is enabled and the master module sends a shutdown message (enabled with --start-stop-msg for the master module).
Sets the name of the master-module used for auto-shutdown. This is the application name of the module actually started. If symlinks are used then it is the name of the symlinked application.
Sets the name of the master-username of the messaging used for auto-shutdown. If "shutdown-master-module" is given as well this parameter is ignored.
Verbosity level [0..4]. 0:quiet, 1:error, 2:warning, 3:info, 4:debug
Increase verbosity level (may be repeated, eg. -vv)
Quiet mode: no logging output
Limits the logging to a certain component. This option can be given more than once.
Use syslog logging back end. The output usually goes to /var/lib/messages.
Path to lock file.
Send log output to stdout.
Debug mode: --verbosity=4 --console
Use alternative log file.
Overrides configuration parameter connection.username.
Overrides configuration parameter connection.server.
Overrides configuration parameter connection.timeout.
Overrides configuration parameter connection.primaryGroup.
A group to subscribe to. This option can be given more than once.
Overrides configuration parameter connection.encoding.
Sets sending of a start- and a stop message.
List all supported database drivers.
The database connection string, format: service://user:pwd@host/database. "service" is the name of the database driver which can be queried with "--db-driver-list".
The configmodule to use.
Load the inventory database from a given XML file.
Do not use the database at all
Check my own inventory against the Master Table (the list of nodes affected can be controlled by the --nodes/--exclude options)
Check the sanity of the inventory loaded on this node finding possible overlaps with the Master Table.
Remove the conflicting elements loaded on my host pointed out by the sanity command.
Performs a merging (one-direction synchronization) of inventory and routing based on the content of the Master Table (the list of nodes affected can be controlled by the --nodes/--exclude options).
Remove (undo the merge) inventory/routing information that was merged (the list of nodes affected can be controlled by the --nodes/--exclude options).
Erase my inventory/routing entries restoring the local seiscomp3 database to an empty state (use with caution).
Fetch and list the Master Table content.
Comma separated list of nodes to remove, merge, check.
Comma separated list of nodes to exclude from remove, merge, check.
keep a copy of the Inventory and Routing tables merged.
keep a copy of the RAW Inventory and Routing tables fetched.
load a copy of the RAW Inventory/Routing information from disk. It expects a date value in the following format YYYY-MM-DD.
Perform everything that should be done but don't write changes to the database.
Force merging against MYSELF.