Logs

Overview

SENSR and its utilities produce a significant amount of logs that can be used for debugging issues. This section describes where to find those logs.

SENSR

SENSR logs can be found in the directory /opt/seoulrobotics/logs. They are classified into 2 categories:

• Algo node logs, a dedicated directory will be created for each algo node used on the site
• Master node logs.

At each Runtime selection, a new folder named after the runtime timestamp will be created in each of the folders.

Master node logs

The Master node logs contain information on the master node's status and its connection to the algo nodes. The Master node logs are of 3 categories:

• [I] Information: These are routine updates and can be disregarded.
• [W] Warning: While these messages might point towards system failure, they are not necessarily a cause for concern. However, they might be worth a look.
• [E] Error: These are critical messages demanding your attention. They are typically triggered by events that could affect the system's stability badly.

Algo node logs

The Algo node logs contain information relative to the data processing and detection. The logs are also divided into 3 categories:

• [I] Information: These messages are for informational purposes and can be overlooked.
• [W] Warning: These messages could potentially signify system failure but aren't immediately critical. They might still warrant a check.
• [E] Error: These are important alerts and require your prompt attention. They are typically brought on by events that could jeopardize the system's stability.

SR Launcher logs

The SR launcher produces logs that can be used to debug installation or cluster issues. The logs are located in the directory /opt/seoulrobotics/sr-launcher/logs.

Kubernetes statuses

If the system does not run properly, you can use the following command kubectl get pods. This command will provide information on which pods are running properly and which are not. If running a single algo node, after clicking Start Algo Nodes in project mode. you should be seeing something similar to this:

NAME                                  READY   STATUS    RESTARTS   AGE
roscore-pldzc                         1/1     Running   0          24s
controller-6fddf855d6-c566l           1/1     Running   0          24s
master-0-54bbcf8cdf-lp8jg             1/1     Running   0          24s
algo-node-algo0001-687f69949d-4wzjd   1/1     Running   0          6s

If the statuses are not consistent with the template, please contact support@seoulrobotics.org for further assistance.