Versions Compared

Old Version 14

changes.mady.by.user Tzanetos Balitsaris

Saved on

compared with

New Version 15

changes.mady.by.user Tzanetos Balitsaris

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Squirro offers a number of ways to debug what is happening in the system. Each service maintains its log file, which helps with finding the source of an error. Additionally systemd  helps by automatically restarting services that fail completely. A few basic operating system commands are also explained here, which can be used to find out if the base system is running smoothly.

Table of Contents

Table of Contents
outlinetrue
excludeTable of Contents

Log files

All log files can be found in the /var/log directory. The following table shows the relevant log files and their usage.

Log File

Service

OS

Additional Notes

/var/log/squirro/SERVICE_NAME/SERVICE_NAME.log

Squirro services

All

Detailed log file about each service.

/var/log/squirro/SERVICE_NAME/stdout.log

Squirro services

All

Messages sent to the standard output stream of the service and not logged in the main service log file.

/var/log/squirro/SERVICE_NAME/stderr.log

Squirro services

All

Messages sent to the standard error stream of the service (typically error messages) and not logged in the main service log file. Might contain useful information when a service is unable to boot up.

/var/log/squirro/SERVICE_NAME/nginx-access.log

Nginx (Squirro services)

All

Every request to the web services is recorded in this log file in a line-by-line format.

/var/log/squirro/SERVICE_NAME/nginx-error.log

Nginx (Squirro services)

All

Records errors on the HTTP level. When a service is stopped, errors may show up here indicating that the service is not reachable.

/var/log/squirro/update-cluster-node.log

/var/log/squirro/update-storage-node.log

-

All

Update log for Squirro Cluster/Storage node.

/var/log/messages

-

All

General system log. Serious system failures will be recorded here.

/var/log/elasticsearch/ES_CLUSTER_NAME*.log




Elasticsearch

All

ES_CLUSTER_NAME.log: Records cluster information and major failures.

ES_CLUSTER_NAME__index_indexing_slowlog.log: contains the logs about the indexing performed by the system

ES_CLUSTER_NAME__index_search_slowlog.log: contains the logs about the queries asked to the system 

/var/log/redis/*.log

Redis

All


/var/log/mysqld.log

MySQL

RHEL/CentOS 6


/var/log/mariadb/mariadb.log

MariaDB

RHEL/CentOS 7


/var/log/cron

Cron



/var/log/monit/monit.log

Monit

RHEL/CentOS 6

Records service state changes and actions.

/var/log/secure

/var/log/audit/audit.log

System

RHEL/CentOS 6/7

Used to debug connection issues

Additionally the /var/lib/squirro/ directory contains the following log files:

Log File

Service

OS

Additional Notes

/var/lib/squirro/datasource/job_logs/*.log

datasource (sqdatasourced)

All

Contains rotated log files for the created data sources. Any logs during the initial phase of creating the source and loading data into the system (dataloader logs; before transforming them in the pipeline; for these the ingester logs are relevant) will be found here.

/var/log/squirro/machinelearning/job_logs/*.log

machinelearning (sqmachinelearningd)

All

Contains log files for the machinelearning jobs that run on the server. Each machinelearning job uses its own log file and any output during its execution is logged there (for example, output during the training of a model).

The log level can be changed for each service. Such changes can be made within :

Code Block
languagebash
/etc/squirro/SERVICE_NAME.ini

For any of the services, the following can be added to the.ini files to adjust the log level.

Code Block
languagebash
[logger_root]
level = INFO

...

Such a feature is available as a plugin from within the Server space as can be seen below.Image Removed

...

System commands

The Squirro services are standard Unix daemons. Standard Linux utilities can be used to debug any issues that may arise.

...