Start/Shutdown (AEN 4.1.2)#

Overview

Anaconda Enterprise Notebooks has 3 main components: Server, Gateway, and Compute-Launcher

Each component must be started and shutdown independently because they may be running on separate boxes. The process is basically the same for each component but the path to the correct commands will vary.

All the instructions below assume that the 3 components are installed in the following locations:

  • Server -> /opt/wakari/wakari-server/
  • Gateway -> /opt/wakari/wakari-gateway/
  • Compute-Launcher -> /opt/wakari/wakari-compute/

Supervisor Process

Anaconda Enterprise Notebooks uses a process control system called Supervisor to run the Anaconda Enterprise Notebooks services. Supervisor is run by the AEN Service Account user, usually “wakari” or “aen_admin”.

The Supervisor daemon process is called supervisord. The Supervisor daemon runs in the background and should rarely need to be restarted itself.

To verify the Supervisor processes are running, execute each of these on the appropriate nodes:

service wakari-server status
service wakari-gateway status
service wakari-compute status

The services can be restarted with:

service wakari-server restart
service wakari-gateway restart
service wakari-compute restart

Start Procedure

Services should start automatically both when they are first installed and then at any point where the system is restarted. If it is necessary to manually start the services, this can be achieved by executing the appropriate command below on the node running that service:

service wakari-server start
service wakari-gateway start
service wakari-compute start

It is possible to check the service status with:

service wakari-server status
service wakari-gateway status
service wakari-compute status

Shutdown Procedure

Services can be stopped using the following commands:

service wakari-server stop
service wakari-gateway stop
service wakari-compute stop

Anaconda Enterprise Notebooks Compute Nodes may have running processes as well. These are not automatically stopped, but can be stopped by executing:

sudo /opt/wakari/wakari-compute/bin/wk-compute-apps kill-all