System logs

Introduction

Each RCS component generates daily logs that help to analyze possible fault or error causes. File content analysis lets you follow RCS operations step by step to find the causes of any errors (i.e.: service started but immediately stopped).

Log analysis utility

The reasons that can lead to log analysis are provided below:

Component Analysis reason
Master Node

Check problems with RCS Console.

Collector

Check data reception from agents.

Carrier Checks data delivery to shards and the Master Node.
OCR module Check for any slowed indexing in exported content.
Translate module Check for any slowed content translation.
Network Controller

Check Network Injector or Anonymizer status.

Network Injector

Check completed operations.

Anonymizer

Check incoming data flow from agents.

Log file example

The log file name has the following syntax: component yyyy-mm-dd.log (i.e.: rcs-dbdb 2012-02-04.log)

RCS log files

Log files generate by components in full installation are provided below:

Component Folder
Master Node

Collector

Carrier
OCR module

Translate module
Network Controller

Network Injector

Anonymizer

WARNING: the lack of log files indicates incomplete installation.

Quick log display

BareTail, an application that lets you immediately view the content of several log files, is included in the RCS installation.

To run BareTail, enter:

> rcs-db-log

Log file content

Each record is identified by one of the following levels of severity:

Severity level Description
Fatal

RCS is not running and requires service (i.e.: no settings, no certificates).

Error

There is a component error but RCS can guarantee main service coverage (i.e.: Master Node not running).

Debug

It only appears if enabled upon support service indication, increases and provides more details on log records to resolve problems.

Info

information note.