This guide is intended to help install and configure Sophie. The reader should be familiar with Linux and Docker.

The instructions include setting up Data and Search nodes – in which case the TSDB and RDBMS services run on the Data node – this is the recommended initial setup.

To move the TSDB and RDBMS services to other nodes, please contact Loom support for advanced instructions.


From on-site support to central support, our team of experienced professionals provides the help and information you need to keep Sophie working for you. This team includes your Technical Representative, Account Manager, and Loom's staff of consultants and support specialists with expertise in your business area, and your hardware and software environment.

Thank you

Thank you for using Loom Systems Solution and this user’s guide. We value your comments and feedback. Mail your comments to the following address

System Requirements

Before installing, make sure the environment meets the software and hardware requirements as described in this topic.

Software Requirements 

The supported operating systems are CentOS / RHEL 7 versions 7.4 or 7.5.

Hardware Requirements 

The requirements are dependent on the volume/shape (average and burst) and characteristics of the data input, as well as retention requirements. To design for scale, refer to "Scaling and High-Availability", or consult Loom support.

Notes about virtualized environments

More often than not, the installation is done on VM rather than bare-metal servers. While this is perfectly fine, please make sure that the following is true:

  • CPU and RAM resources are *dedicated* and not shared with other VMs co-hosted on the same hardware
  • Use *locally attached* disks. Refrain from using SAN/NAS or any remotely mounted filesystem

Minimum requirements

The requirements listed below are minimum and recommended sizes for the different nodes.

The Data node should have:

  • 32 CPU Cores (recommended. Minimum is 8)
  • 32 GB RAM
  • 100 GB locally attached SSD for system, mounted under / (root) 
  • 100 GB locally attached SSD drive, mounted under /opt/Loom 

Search nodes should have:

  • 8 CPU Cores
  • 64 GB RAM
  • 100 GB locally attached SSD for system, mounted under / (root)
  • 500 GB locally attached SSD drive, mounted under /opt/Loom 

TSDB node and RDBMS node should have:

  • 8 CPU Cores
  • 8 GB RAM
  • 100 GB locally attached SSD for system, mounted under / (root)
  • 500 GB locally attached SSD drive, mounted under /opt/Loom 

Additional requirements:

  • The /var/lib/docker folder should have no less than 20GB of free space
  • The /tmp folder should have no less than 5GB of free space
  • There should be at least 50 GB available in the home directory for the user (/home/loomuser)

Supported Browsers

As per Release 7.2 of this installation guide, the Loom web application supports Google Chrome version 66 and newer, when viewed with a screen 19" or larger

Future upgrades always maintain support for browser versions no older than 6 months before the upgrade.

Creating the Cluster

After setting up the machines (nodes) that will run Sophie, and installing the supported operating-system, it’s time to setup inter-connectivity (SSH) between them.

Creating a user

First, make sure that on every node you created a user named loomuser, with sudoers (root) permissions.

Attaching and mounting the external disk

On every node, it is required to attach a secondary disk that will hold the created data. See the Hardware Requirements section for details about the recommended size of this disk.

Here are the steps to follow on every node:

  1. Attach the external disk
  2. Format the disk using ext4
  3. Mount it under /opt/Loom 
  4. Add the disk config to /etc/fstab (replace the ** with the device name):

/dev/sd**    /opt/Loom     defaults           ext4        0 2

Configuring the Operating System

Make sure Swap is disabled on the servers. To do this, you can run cat /proc/meminfo and make sure all swap related entries are 0.

Setting up inter-connectivity

On a server that has access to all of the nodes, create a new key by running:

ssh-keygen -f Loom_key -q -N ""

Copy the key created in the previous step to the node you designate to be the Data node:

scp Loom_key Loomuser@node1:/home/Loomuser/.ssh/id_rsa

Still from the same server, install the key on the nodes in the cluster:

for node in node1 node2 node3; do ssh-copy-id -i Loom_key -f Loomuser@$node; done

Setting up the Search Nodes

First, connect to every node that will function as a Search node and install Oracle JDK8.

Next, download the installation tarball:

wget <download-link>

(If the node does not have internet connection, download it to a machine that does and copy it to the node).

Extract and run the installation script:

tar xzvf search-node-install.tar.gz
cd search-node-install --silent

After installation is complete, you can check the status of every node by running:

Loom status

Run this command again as you add more nodes, to see the cluster form. It might take up to a few minutes for the nodes to recognize each other. 

Setting up the Data Node

Obtain and run the installation media 

In this step we'll create a standalone server running all the services. We will later reconfigure it to connect to the other nodes.

Download the installation package and copy it to the node designated as the Data node. Unpack it and run the deploy script:

cd ~/

wget -O sophie.tar.gz <download-link>

tar xzvf sophie.tar.gz

cd <extracted-folder>


You will be prompted to name the installation (the name you use here will be used in various places, such as notifications, monitoring alerts). It's recommended to enter the domain-name of the server (e.g. loom.acme.local).

You will then be prompted for a super-admin password.

Lastly, you will also be prompted for the IP addresses of the Search nodes.

Open the web application

Wait for Sophie to start (up to 3 minutes), then open Chrome and browse to the address of the node. You should see a certificate error:

Figure 3-7. Certificate warning

Click “show advanced”, then “Proceed...”.

To avoid this message, issue and install a certificate. Refer to the administration guide for details on how to do that.

Use Loom as the username and the super-admin password you used when deploying.


Network conflicts

By default, Sophie sets up an internal network which uses the address space for the different containers. If this address is in use, please open the following file for editing:


Look for a key named loom_network_subnet_range and change its value to a non-conflicting one.

Save the file, then run loom restart

Service Status and Logs

The following commands will help to triage a problem with the installation:

loom status - will print a list of all the containers and their current status

docker logs --since 5m -f <service_name> - will follow the logs of a specific service. See the list of the available services in the output of the docker ls command

Did this answer your question?