Troubleshooting ASAB Maestro¶

Apply changes from command line¶

There is ./gov.sh script in the /opt/site folder on each node. Use it to apply changes on any node.

This command applies changes in the model to the current node:

$ cd /opt/site
$ ./gov.sh up

Apply newest changes on a different node. (Replace <node_id> with the actual node ID.)

$ ./gov.sh up <node_id>

Interacting with the Docker or Podman manually¶

The ./gov.sh script also works exactly the same as a docker command but in the correct cluster setup. This includes the docker compose bit.

This is useful when ASAB Maestro components are not working as expected and their UI or API is not available.

Example:

$ cd /opt/site
$ ./gov.sh compose up -d
[+] Running 6/6
 ✔ Container asab-config-1          Started       0.1s
 ✔ Container asab-remote-control-1  Started       0.1s
 ✔ Container zookeeper-1            Started       0.1s
 ✔ Container zoonavigator-1         Started       0.1s
 ✔ Container asab-library-1         Started       0.1s
 ✔ Container asab-governator-1      Started       0.1s

$

Manual update to the recent ASAB Governator¶

If you need to manually update the asab-governator on the particular node, this is a proper procedure:

$ cd /opt/site
$ ./gov.sh image pull docker.teskalabs.com/asab/asab-governator:stable
$ ./gov.sh compose up -d asab-governator-1

Replace asab-governator-1 with a proper instance_id on the asab-governator on the given node. Use ./gov.sh ps -a to identify the instance_id.

Nginx can't bind to port 80¶

Nginx log

nginx: [emerg] bind() to 0.0.0.0:80 failed (13: Permission denied)

Solution

$ sudo sysctl -w net.ipv4.ip_unprivileged_port_start=80

Elasticsearch does not start due to virtual memory allocation¶

Solution

$ sudo sysctl vm.max_map_count=262144