Errors may occur while working in Scheer PAS. The overview of error messages allows you to identify possible causes and possible solutions. It also refers to documentation pages that contain further details.
Overview of Errors and Problems on Kubernetes Setups
|
Problem / Error Message |
Possible Reason |
Solution |
Further Information |
|---|---|---|---|
|
container back off status is shown in the service list. |
We don't have a way to export this macro.
|
We don't have a way to export this macro.
|
|
|
container error status is shown in the service list. |
We don't have a way to export this macro.
|
We don't have a way to export this macro.
|
|
|
crash loop back off status is shown in the service list. |
We don't have a way to export this macro.
|
We don't have a way to export this macro.
|
|
|
disk space error status is shown in the service list. |
We don't have a way to export this macro.
|
We don't have a way to export this macro.
|
|
|
high restart count status is shown in the service list. |
We don't have a way to export this macro.
|
We don't have a way to export this macro.
|
|
|
image pull error status is shown in the service list. |
We don't have a way to export this macro.
|
We don't have a way to export this macro.
|
|
|
init container crash status is shown in the service list. |
We don't have a way to export this macro.
|
We don't have a way to export this macro.
|
|
|
init image pull error status is shown in the service list. |
We don't have a way to export this macro.
|
We don't have a way to export this macro.
|
|
|
insufficient resources status is shown in the service list. |
We don't have a way to export this macro.
|
We don't have a way to export this macro.
|
|
|
liveness probe failure status is shown in the service list. |
We don't have a way to export this macro.
|
We don't have a way to export this macro.
|
|
|
network error status is shown in the service list. |
We don't have a way to export this macro.
|
We don't have a way to export this macro.
|
|
|
out of memory status is shown in the service list. |
We don't have a way to export this macro.
|
We don't have a way to export this macro.
|
|
|
pod creation failure status is shown in the service list. |
We don't have a way to export this macro.
|
We don't have a way to export this macro.
|
|
|
pod termination failure status is shown in the service list. |
We don't have a way to export this macro.
|
We don't have a way to export this macro.
|
|
|
readiness probe failure status is shown in the service list. |
We don't have a way to export this macro.
|
We don't have a way to export this macro.
|
|
|
SELinux error status is shown in the service list. |
We don't have a way to export this macro.
|
We don't have a way to export this macro.
|
|
|
SELinux permission denied status is shown in the service list. |
We don't have a way to export this macro.
|
We don't have a way to export this macro.
|
|
|
Service does not start and you get the following error messages:
|
The SQL alias is named StateDB but the user is not configured. |
Configure a user for the SQL alias StateDB. |
|
|
Service does not start and you get the following error message:
|
The SQL alias is not named StateDB. |
Your alias has the wrong name and must be renamed to StateDB. |
|
|
SQLite Persistent state data is lost with every service restart or update in Kubernetes environments. |
|
Select database option StateDB. |
|
|
volume attach error status is shown in the service list. |
We don't have a way to export this macro.
|
We don't have a way to export this macro.
|
|
|
volume failure status is shown in the service list. |
We don't have a way to export this macro.
|
||
|
volume mount error status is shown in the service list. |
We don't have a way to export this macro.
|