Each RCS component generates daily logs that help to analyze possible fault or error causes. Analyzing file content lets you review RCS operations step by step and understand any error cause (i.e.: service starts but immediately stops, service started but with incorrect deploy.htm page redirect).
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. |
OCR module | Check for any slow image conversions into text. |
Network Controller |
In the event of doubts on Network Injector or Anonymizer status. |
Network Injector |
Check completed operations. |
Anonymizer |
Check incoming data flow from agents. |
The log file name has the following syntax: <component> yyyy-mm-dd.log (i.e.: rcs-dbdb 2012-02-04.log)
Log files generate by components in full installation are provided below:
Component | Folder |
---|---|
Master Node |
C:\RCS\DB\log |
Collector |
C:\RCS\Collector\log |
OCR module |
C:\RCS\DB\log |
Network Controller |
C:\RCS\Collector\log |
Network Injector |
/rcsnia/log |
Anonymizer |
/var/log |
WARNING: the lack of log files indicates incomplete installation.
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
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 |
(only appears if enabled upon support service indication, increases and provides more details on log records to resolve problems). |
Info |
information note. |
RCS8.2 | User's and Installation Guide | © COPYRIGHT 2012