Breadcrumbs

Troubleshooting Kubernetes

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.

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 Analyzer for possible causes.

container error status is shown in the service list.

A problem with the container occurred.

This error is related to problems in your model. Check the service logs in the Log Analyzer for possible causes.

crash loop back off status is shown in the service list.

The container is repeatedly crashing and being restarted.

This error is related to problems in your model. Check the service logs in the Log Analyzer for possible causes.

disk space error status is shown in the service list.

Not enough disk space available.

Please contact the PAS support team for help.

high restart count status is shown in the service list.

The container was restarted unusually often.

This error is related to problems in your model. Check the service logs in the Log Analyzer for possible causes.

image pull error status is shown in the service list.

The container image could not be downloaded.

Please contact the PAS support team for help.

init container crash status is shown in the service list.

The initialization container has crashed.

Please contact the PAS support team for help.

init image pull error status is shown in the service list.

The init container image could not be downloaded.

Please contact the PAS support team for help.

insufficient resources status is shown in the service list.

Not enough resources available for the container.

Please contact the PAS support team for help.

liveness probe failure status is shown in the service list.

The liveness check failed.

The service is no longer functioning properly. Check your model and the service logs in the Log Analyzer for errors.

network error status is shown in the service list.

A problem with the network communication occurred.

Please contact the PAS support team for help.

out of memory status is shown in the service list.

Container was terminated because it needed more memory than allocated.

Go to the Resource Monitor to check the resources for this service.Expert AdviceFor xUML services, you can increase the resources in the service configuration. Enable Expert Mode to do so.Depending on your setup, refer to Docker: Adapting the Configuration of Containerized xUML ServicesKubernetes: Adapting the Configuration of Containerized xUML Services

pod creation failure status is shown in the service list.

The pod could not be created properly.

Please contact the PAS support team for help.

pod termination failure status is shown in the service list.

The pod could not be terminated properly.

Please contact the PAS support team for help.

readiness probe failure status is shown in the service list.

The readiness check has failed.

The service is no longer functioning properly. Check your model and the service logs in the Log Analyzer for errors.

SELinux error status is shown in the service list.

A problem with security policies occurred.

Please contact the PAS support team for help.

SELinux permission denied status is shown in the service list.

Access denied by security policies.

Please contact the PAS support team for help.

Service does not start and you get the following error messages:

Can not connect: 1045 "Access denied for user '...'@'...' (using password: NO)"

Initializing addon "PState_AddOn" failed, reason "Failed to connect sql database "StateDB" for state engine."

The SQL alias is named StateDB but the user is not configured.

Configure a user for the SQL alias StateDB.

SQL Adapter Reference

Service does not start and you get the following error message:

Initializing addon "PState_AddOn" failed, reason "Connection StateDB is not available"

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.

  • You have not selected a database option.

  • You have selected database options :local:, :memory: or :volatile:. They all behave the same in Kubernetes environments.

Select database option StateDB.

Getting Started with Persistent State Databases

volume attach error status is shown in the service list.

The volume could not be attached.

Check the settings of your connected volumes for erroneous or outdated entries, e.g. password, path etc. Refer to Connecting External Volumes for more information.

Connecting External Volumes

volume failure status is shown in the service list.

A problem with the requested volume occurred.

volume mount error status is shown in the service list.

An error occured while mounting the volume.

Related Content

📘

Related Documentation: