Table 8.30. trepctl Command-line Options
|Will output full stack trace of the last error, if any. If no error, response will be empty.|
|Host name of the replicator|
|Port number of the replicator|
|Number of times to retry the connection|
|Name of the replicator service|
|Enable verbose messages for operations|
Global command-line options enable you to select specific hosts and services. If available, trepctl will read the active configuration to determining the host, service, and port information. If this is unavailable or inaccessible, the following rules are used to determine which host or service to operate upon:
If no host is specified, then trepctl defaults to the host on which the command is being executed.
If no service is specified:
To use the global options:
Specify the host for the operation. The replicator service must be running on the remote host for this operation to work.
Specify the base TCP/IP port used for administration. The default is
port 10000; port 10001 is also used. When using different ports,
port+1 is used, i.e. if port
4996 is specified, then port 4997 will be used as well. When multiple
replicators are installed on the same host, different numbers may be
The servicename to be used for the requested status or control operation. When multiple services have been configured, the servicename must be specified.
trepctl statusProcessing status command... Operation failed: You must specify a service name with the -service flag
Starting in 6.0.4, if multiple services are configured but not specified, then a list of available services is provided:
trepctl statusProcessing status command... Operation failed: You must specify a service name with the -service flag because there is more than one service available. The currently available status commands are: trepctl -service north status trepctl -service north_from_east status trepctl -service north_from_west status
Turns on verbose reporting of the individual operations. This includes connectivity to the replicator service and individual operation steps. This can be useful when diagnosing an issue and identifying the location of a particular problem, such as timeouts when access a remote replicator.
Retry the request operation the specified number of times. The default is 10.