docs: recommend more helper commands for deploy timeout
This commit is contained in:
parent
ba9abcb0d7
commit
66d5453248
|
@ -486,17 +486,21 @@ func WaitOnService(ctx context.Context, cl *dockerclient.Client, serviceID, appN
|
|||
return err
|
||||
case <-time.After(timeout):
|
||||
return fmt.Errorf(fmt.Sprintf(`
|
||||
%s has still not converged (%s second timeout reached)
|
||||
%s has not converged (%s second timeout reached).
|
||||
|
||||
This does not necessarily mean your deployment has failed, it may just be that
|
||||
the app is taking longer to deploy based on your server resources or network
|
||||
latency. Please run the following the inspect the logs of your deployed app:
|
||||
latency.
|
||||
|
||||
You can track latest deployment status with:
|
||||
|
||||
abra app ps --watch %s
|
||||
|
||||
And inspect the logs with:
|
||||
|
||||
abra app logs %s
|
||||
|
||||
If a service is failing to even start (run "abra app ps %s" to see what
|
||||
services are running) there could be a few things. The follow command will
|
||||
try to smoke those out for you:
|
||||
If a service is failing to even start, try smoke out the error with:
|
||||
|
||||
abra app errors --watch %s
|
||||
|
||||
|
|
Loading…
Reference in New Issue