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 enter rcs-db-license

Master Node status check

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

Command

In folder enter rcs-db-evidence-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.

What to check

In folder check log rcs-worker*.log logs

Check agent status via Collector

Make sure agents are routinely communicating their status to RCS via Network Controller 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 enter rcs-collector-status

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 any other synchronizations to check whether 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. If the value is high, this means that Master Node is not running or is not connected. Check Master Node service status.

The number of logs will decrease as soon as the connection is resumed.

Network Injector start check

Network Injector logs are normally saved in folder .

To learn more

To view logs see "System logs".