...
nex-cli will be used to determine app name and retrieving its status
nex-cli domains | grep myfrontend.maestrano.io
will output something similar to this:
...
+----------------+--------+--------------------+------+---------+------------------+------+-------+------------+-----------------+------------------+
| App Details |
+----------------+--------+--------------------+------+---------+------------------+------+-------+------------+-----------------+------------------+
| NAME | STATUS | IMAGE | SSL | STORAGE | PREFERRED REGION | SIZE | NODES | OWNER | DESCRIPTION | TAGS |
+----------------+--------+--------------------+------+---------+------------------+------+-------+------------+-----------------+------------------+
| persevering-dolphin-5 | active | maestrano/web-ruby | true | false | ap-southeast-1 | 4 | 0/12 | u:alachaumtartempion | My Testcool publishingfrontend | development,ruby |
+----------------+--------+--------------------+------+---------+------------------+------+-------+------------+-----------------+------------------+
...
First thing we want to do is to restart the service , unless you can allow to keep it down longer, to avoid erasing clues on why it went down.
...
In case there is nothing to see here, or we erased the useful logs by restarting the nodes, we will have to check in cubes logs directly.
For each cubes (listed in nex-cli apps:info command) we can run
nex-cli cubes:events --tail 200 d2a2d9d9-ef8b-41ea-9e45-3cc911254a80
...