Versions Compared

Old Version 3

changes.mady.by.user Serhii

Saved on

compared with

New Version 4

changes.mady.by.user Anastasiia Kovalinas

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel
borderColor#FFBABA
bgColor#FFBABA
borderWidth2px
borderStylesolid

Important!

Please use these tools only if you have a clear understanding of what you are doing. Misuse of the tools may cause an improper functioning of the system.

...

Panel
borderColor#ffffb3
bgColor#ffffb3
borderWidth2px

(warning)   Attention

To free our clients from confusion while trying to indicate a path to VCS system, we introduce the <VCS_PATH> variable that differs depending on VCS version:

  • <VCS_PATH> before version 3.13.0 is “/usr/local/vcs”
  • <VCS_PATH> after version 3.13.0 is “/opt/jerasoft/vcs”

The example is as follows:
To restart RADIUS Server, you need to execute <VCS_PATH>/bin/service bbradiusd restart, which will look like /usr/local/vcs/bin/service bbradiusd restart for clients with VCS version 3.12.0 and lower or /opt/jerasoft/vcs/bin/service bbradiusd restart for VCS version 3.13.0 and higher.


Requirements Checker

The tool is aimed to check minimal requirements and security recommendations at your server before and after installation. 

...

The tool should be run under root permissions without any arguments. When the tool is run, it will perform a list of checks and show results for each of them. Use it:

...

OptionDescription
--path=<path>
Specify the VCS location. Only if different from <VCS_PATH>
--user=<user>
Specify user the VCS runs under. Only if different from "vcs".

...

The tool is used to manage clusterclusters. It allows to init the cluster, add and promote slave to master, etc. 

...

The command is run on the Master and used for:

  • first time initialisationinitialization of the cluster;
  • addition of the new slave node to the cluster;
  • addition of the old master to work as slave after failover.

...

  • configuration of the Master to ship replication logs (init-master)
  • configuration of the Master to accept connections from the Slave (init-master-access)
  • configuration of the Slave to receive replication logs (init-slave)
  • show status of the cluster (status).

Each of this these commands may be performed separately if you know exactly what you need.

...

The command is used for failover. After you fix old Master, you may add it as new Slave using "init" command.

...

Slave: Sync Files

The command is run on the Slave and used to synchronise files synchronize files from the Master. The command is mostly used in crontab for auto-sync.

Code Block
titleBash
<VCS_PATH>/bin/cluster sync-files

During initialisation of initialization of the cluster tool adds this command to the crontab (/etc/cron.d/vcs-cluster) at the Slave node. 

Cluster Status

The command may be run on any node and used to get status of the cluster. 

...

When command is run on the Master, it shows type of the node and attached Slaves , that are up to date:

Code Block
[ NOTICE ] Cluster Status
  ifconfig  | grep 'inet addr:'| grep -v '127.0.0.1' | cut -d: -f2 | awk '{ print $1}'

Master (master ip): ACTIVE 
    Redundancy (slave ip): ACTIVE

When command is run on the Slave, it shows type of the node and synchronisation delaysynchronization delay.

Code Block
[ NOTICE ] Cluster Status
  ifconfig  | grep 'inet addr:'| grep -v '127.0.0.1' | cut -d: -f2 | awk '{ print $1}'

Master (master ip): NOT AVAILABLE | Activity delay: -00:00:58.393423
    Redundancy (slave ip): ACTIVE

...

Code Block
the row: Master (master ip): NOT AVAILABLE 

It's a normal behaviourbehavior. Instead, please pay attention to Activity delay parameter − it shows large values if replication is broken and servers are not in sync. 

In case when the Slave is not in synchronisation synchronization (NOT-in-sync) with the Master, you need to re-initialiseinitialize.