OxTrust - Out of memory error

By: Pawel Walus named 21 Mar 2024 at 8:54 a.m. CDT

5 Responses
Pawel Walus gravatar
Hello, We have just observed that from time to time oxtrust is being killed due to OOM. The related version of image is 4.5.1-1. Please investigate. pod describe: ``` oxtrust: ... Last State: Terminated Reason: OOMKilled Exit Code: 137 Ready: True Restart Count: 2 Limits: cpu: 2500m memory: 1000Mi Requests: cpu: 125m memory: 1000Mi ```
Gluu 4.5 Docker 20.1
pending

Answers

By Aliaksandr Samuseu staff 21 Mar 2024 at 8:56 a.m. CDT

Copy
Aliaksandr Samuseu gravatar
Hi, Pawel. Do you employ Cache Refresh in your setup? If so, how many user entries (roughly) do you have in the system?

By Pawel Walus named 21 Mar 2024 at 10:46 a.m. CDT

Copy
Pawel Walus gravatar
we don't integrate other AD databases, so there should not be cache refresh. as for user entries - we don’t have live customers, so users are around 10

By Aliaksandr Samuseu staff 22 Mar 2024 at 4:37 a.m. CDT

Copy
Aliaksandr Samuseu gravatar
I see.. How often does this happen? Also, what platform is it? EKS, GCS, some private cloud? If possible, we would like to see logs from oxTrust pod from the time the crash will happen next time.

By Pawel Walus named 25 Mar 2024 at 3:30 a.m. CDT

Copy
Pawel Walus gravatar
We're on EKS, the issue is happening once every a couple of days. I'm attaching the logs
oxtrust_1.log

By Pawel Walus named 27 Mar 2024 at 5:17 a.m. CDT

Copy
Pawel Walus gravatar
We'll attempt the upgrade of components to 4.5.3, will return here if the issue persists afterwards.

Post an answer