Handling Workload Errors
On PAS systems running with Kubernetes, various error states can be displayed in the service list. If you see a red error label, you need to take action to resolve the workload error.
On this page we have compiled an overview on the error states, its meanings and possible solutions.
Error Status | Description | Possible Solution |
|---|---|---|
container back off | The container is restarting with delay due to repeated failures. | This error is related to problems in your model. Check the service logs in the Log Analzyer for possible causes. |
container error | A problem with the container occurred. | This error is related to problems in your model. Check the service logs in the Log Analzyer for possible causes. |
crash loop back off | The container is repeatedly crashing and being restarted. | This error is related to problems in your model. Check the service logs in the Log Analzyer for possible causes. |
disk space error | Not enough disk space available. | Please contact the PAS support team for help. |
high restart count | The container was restarted unusually often. | This error is related to problems in your model. Check the service logs in the Log Analzyer for possible causes. |
image pull error | The container image could not be downloaded. | Please contact the PAS support team for help. |
init container crash | The initialization container has crashed. | Please contact the PAS support team for help. |
init image pull error | The init container image could not be downloaded. | Please contact the PAS support team for help. |
insufficient resources | Not enough resources available for the container. | Please contact the PAS support team for help. |
liveness probe failure | The liveness check failed. | The service is no longer functioning properly. Check your model and the service logs in the Log Analzyer for errors. |
network error | A problem with the network communication occurred. | Please contact the PAS support team for help. |
out of memory | Container was terminated because it needed more memory than allocated. | Go to the Resource Monitor to check the resources for this service. Expert Advice For xUML services, you can increase the resources in the service configuration. Enable Expert Mode to do so. |
pod creation failure | The pod could not be created properly. | Please contact the PAS support team for help. |
pod termination failure | The pod could not be terminated properly. | Please contact the PAS support team for help. |
readiness probe failure | The readiness check has failed. | The service is no longer functioning properly. Check your model and the service logs in the Log Analzyer for errors. |
SELinux error | A problem with security policies occurred. | Please contact the PAS support team for help. |
SELinux permission denied | Access denied by security policies. | Please contact the PAS support team for help. |
volume attach error | The volume could not be attached. | Check the settings of your connected volumes for erroneous or outdated entries, e.g. password, path etc. Refer toConnecting External Volumes for more information. |
volume failure | A problem with the requested volume occurred. | |
volume mount error | An error occured while mounting the volume. |
