Starting and stopping myARCH Cluster

Starting mySCILHS


myscilhs.sh start [service]


Once connected to the CHIP registry, this command will start the myARCH cluster on your machine. (Optionally, you can choose to start just an individual service by specifying it as an additional parameter.)
If a service container hasn't been created on the host yet (such as when starting the cluster for the first time), there will be a series of diagnostic messages that appear on the screen as the Docker images supporting each service container are downloaded from the CHIP registry. If the myARCH container service is being started for the first time, the myARCH truststore will also be created.


 
Preparing to create a service container by pulling down Docker images from the registry

Once completed the command prompt will return, notifying the user that all of the specified containers have been started. Each service container has its own startup process, so it may take several moments for everything to be ready for use.

First-time mySCILHS Startup

It may take several minutes for the myARCH cluster to startup fully when done for the first time. At the moment, the best way to ensure the cluster has started successfully is through monitoring the cluster's status and logs.


 Stopping mySCILHS

myscilhs.sh stop [service]

This stops the cluster/service.

 Restarting mySCILHS

myscilhs.sh restart [service]

This restarts the cluster/service. This command works on services that have already been initialized on the host.