Troubleshooting
You can find here guidance for resolving issues that may arise during the setup or use of your app. We offer solutions for fixing problems to ensure smooth app and database operation.
Containers Restarting
A container restart may indicate memory overuse, abnormal CPU usage, or unexpected application termination.
Investigate your app's memory and CPU usage via Grafana dashboards, accessible from the App Env page header in the Metrics dropdown, can also help in this process.
Common Exit Errors
Exit Error Code 137 - Immediate termination (SIGKILL)
Out-of-memory errors are the most common root cause for this error. If this occurs, inspect the "App Envs" Grafana dashboard for this app environment. If memory usage approaches or exceeds limits, increase your zClouds and apply the changes.
Verify changes by checking the "App Envs" Grafana dashboard to monitor memory usage and confirm container restarts have ceased.
All Errors
The table below helps diagnose application errors by explaining what certain error codes imply.
| Code | Name | What it means |
|---|---|---|
| 0 | Purposely stopped | Used by developers to indicate that the container was automatically stopped |
| 1 | Application error | Container was stopped due to application error or incorrect reference in the image spec |
| 125 | Container failed to run error | The docker run command did not execute successfully |
| 126 | Command invoke error | A command specified in the image specification could not be invoked |
| 127 | File or directory not found | File or directory specified in the image specification was not found |
| 128 | Invalid argument used on exit | Exit was triggered with an invalid exit code (valid codes are integers between 0-255) |
| 134 | Abnormal termination (SIGABRT) | The container aborted itself using the abort() function. |
| 137 | Immediate termination (SIGKILL) | Container was immediately terminated by the operating system via SIGKILL signal. It may also be related to Out Of Memory (OOM) condition |
| 139 | Segmentation fault (SIGSEGV) | Container attempted to access memory that was not assigned to it and was terminated |
| 143 | Graceful termination (SIGTERM) | Container received warning that it was about to be terminated, then terminated |
| 255 | Exit Status Out Of Range | Container exited, returning an exit code outside the acceptable range, meaning the cause of the error is not known |