An integration restarts in a loop

The row’s figure gives the numbers in a few words, such as 6 restarts in 40 min, out of memory.

What it means#

The integration’s Java process keeps stopping and its agent keeps starting it again. While it restarts, its routes run only for moments at a time.

What raises it#

The agent reports the deployment as crashed after its process exits and is restarted again and again. The figure counts the restarts since the run began, and adds out of memory when the process ran out of Java heap. The detail gives the agent and what it last reported.

What to check#

Read the last log lines before each exit:

$ weikio logs <project>/<integration> --env <environment> --since 1h --level warn

See each copy’s restarts and last exit:

$ weikio describe deployment <project>/<integration> --env <environment>

List every deployment of the environment that is crashing:

$ weikio get fleet --env <environment> --state crashed

How to fix it#

The log usually gives the cause: a variable or secret the route needs and doesn’t get, an endpoint that fails at start, or a class missing from the dependencies. Fix it in the integration’s files or values and publish a new version, or roll back. When the figure says out of memory, give the process more heap with -Xmx in the integration’s jvm.options in integration.yaml, or for every deployment of an environment:

$ weikio env set <environment> --launch-jvm-option -Xmx1g