versions/X.Y.Z

Location of the Unravel binaries. This directory contains multiple versions of Unravel.

services

Location of all the generated scripts and configuration files for the services. Anything generated from templates is also located here.

logs

Location of log files. Refer to Log files.

run

Location of PID files and UNIX sockets.

tmp

Location of all the running services and configurations.

data

Location of all the data (data generated from Kafka, Zookeeper, MySQL, etc.) and configurations (entropy, unravel.properties, unravel.yaml etc.).

You can locate the following files in this directory:

unravel.properties

<Unravel installation directory>/data/conf/

This file contains all the Unravel properties.

unravel.yaml

>Unravel installation directory>/data/

This is the installer configuration file.

unravel.effective.yaml

<Unravel installation directory>/data/

This is the single source of truth (SSOT) when used for instantiating templates and configuration files.

conf_archives

<Unravel installation directory>/data

This contains the backup of all the services, configurations, and properties. In case you lose any changes, you can check this file.

base.yaml

/installer/conf/

Contains global entries and host defaults.

services/*.yaml

installer/conf/services/

Contains all the service definitions for each service template or service configuration.

/presets/*.yaml

installer/conf/presets/*.yaml

Contains default host definition which can be used as templates for user-defined initial configurations.

manager.log

All the commands that run through manager tool generate logs into this file. To diagnose thoroughly, run the manager commands with --debug.

The setup process is run due to some commands. These get logged in the setup.log file.

setup.log

When you are doing a first-time install, before the directory structure is created, this log file exists as /tmp/unravel-setup-YYYYMMDD-HHMMSS.log. This file exists in case the installation gets broken early in the process. As soon as the log directory is created, the logging location moves to Unravel installation directory/logs/setup.log and the contents of the /tmp/unravel-setup-YYYYMMDD-HHMMSS.log file is copied to setup.log.

2020-06-09 21:23:12 Sending logs to: /tmp/unravel-setup.log
2020-06-09 21:23:12 Prepare to install with: /home/unravel/edge.yaml
2020-06-09 21:23:14 Sending logs to: <Unravel installation directory>/logs/setup.log

monit.log

This log file is used to track the status of the services and restart in case the services get stopped due to any issues. Normally logs generated by the stop/start script go to their respective control.log file, but in some cases, you can find those logs here.

.control.log

Each of the unravel service has a stop/start script that logs to a control.logfile. For example, Postgres logs to pgsql.control.log. This log file provides information generated by the stop/start scripts and any information that is given out to standard out stream or standard error stream. Normal Postgres activities are logged into pgsql.log

2020-06-11 18:28:54 INFO *** Starting pgsql...
waiting for server to start....2020-06-11 11:28:54.773 PDT [36976] LOG:  listening on IPv4 address "0.0.0.0", port 4339
2020-06-11 11:28:54.773 PDT [36976] LOG:  listening on IPv6 address "::", port 4339
2020-06-11 11:28:54.773 PDT [36976] LOG:  listening on Unix socket "<Unravel installation directory>/run/.s.PGSQL.4339"
2020-06-11 11:28:54.860 PDT [36976] LOG:  redirecting log output to logging collector process
2020-06-11 11:28:54.860 PDT [36976] HINT:  Future log output will appear in directory "<Unravel installation directory>/logs".
 done
server started
2020-06-11 18:28:54 INFO *** Starting pgsql... Started
2020-06-11 18:30:07 INFO *** Stopping pgsql...
waiting for server to shut down.... done
server stopped
2020-06-11 18:30:08 INFO *** Stopping pgsql... Stopped