Start
This asctl method instantiates the Orchestrator processes: manager, engine monitor, workers, and mongrels.
Method name | Start |
Command |
|
Details | Instantiates orchestrator processes. |
Inputs | None. |
Outputs | STDOUT to show that Orchestrator processes have been stopped. |
# asctl orchestrator:start
starting...
started...
nohup: redirecting stderr to stdout
Orchestrator Status:
-> Orchestrator Manager running with pid: 26783
-> Orchestrator Engine running with pid: 26797
-> Mongrel serving orchestrator on port 3000 is running with pid: 26802
-> Mongrel serving orchestrator on port 3001 is running with pid: 26804
-> Mongrel serving orchestrator on port 3002 is running with pid: 26806
-> Orchestrator Monitor running with pid: 26800
-> Asynchronous Worker Process 0 is running with pid: 26813
-> Asynchronous Worker Process 1 is running with pid: 26815
-> Synchronous Worker Process 2 is running with pid: 26817
-> Synchronous Worker Process 3 is running with pid: 26819
-> Synchronous Worker Process 4 is running with pid: 26821
-> Synchronous Worker Process 5 is running with pid: 26811
Note: When you initially run asctl orchestrator:start, you may see, instead of the
above Orchestrator Status, Orchestrator Engine running with pid, a different
status:
Orchestrator Engine NOT running
This displays if Orchestrator
is still completing the installation process. To confirm that Orchestrator processes are
running, wait a minute, and then run the following
command:asctl orchestrator:status
This will provide an updated status.
See Status for more information.