You are here: Risoluzione dei problemi > Procedure di verifica stato componenti

Component status check procedure

Introduction

Typical procedures on how to check hardware and software status are provided below.

Installed license check

Check all licenses installed in RCS, including updates.

Command

In folder C:\RCS\DB\bin enter rcs-db-license

Master Node status check

Make sure Master Node is routinely communicating data to databases via Worker services.

Command

In folder C:\RCS\DB\bin enter rcs-db-queue.

Result: an example is provided below .

What to check

If the logs and size values begin to significantly increase, this may be due to Worker service that is not running. Check status on each Worker service.

Checking Worker service status

Make sure that Worker service is correctly running to decode and save data in databases.

Command

In folder C:\RCS\DB\bin enter rcs-db-queue.

Check agent status via Collector

Make sure agents are routinely communicating their status to RCS and that they are sending their data to Collector. Agent data may be lost in the event of a persistent Collector fault.

Command

In folder C:\RCS\Collector\bin enter rcs-collector-queue

Result: the Collector status report appears

What to check

The Last sync time must be as recent as possible, compatible with the set synchronization methods for each agent: a recent Last sync time indicates that agents correctly communication with Collector. If Last sync time is not recent, wait for other synchronizations to see if it is updated. Alternatively, check Collector logs to see whether there are synchronization attempts: in this case inform support service.

The logs value must be minimum since it is the data saved by the Collector awaiting to be sent to Master Node via the Carrier. If the value is high, this means that Master Node is not running or is not connected or the Carrier malfunctioned. Check Master Node status and Carrier logs.

If the problem is the connection with Master Node, the number of logs will decrease as soon as the connection is restored.

Network Injector start check

Network Injector logs are normally saved in folder /var/log/syslog.

Check system components

Check system component status and view front end and back end component topology.

Command

In folder C:\RCS\DB\bin enter rcs-db-status Use the following command to view the correct syntax and description of all options:

> rcs-db-status --help

Support service file creation

Create a .zip file with all the information required for technical support.

Command

In folderC:\RCS\DB\bin or C:\RCS\Collector\bin enter rcs-db-diagnostic or rcs-collector-diagnostic respectively. Use the following command to view the correct syntax and description of all options:

> rcs-db-diagnostic --help

> rcs-collector-diagnostic --help

For example, the --hide-addresses option lets you delete all references to IP addresses or domain names in files.

To learn more

To view logs see "System logs"

RCS9.4 | User's Guide | © COPYRIGHT 2014