[Need support]: Getting CrashLoopBackOff on hlm-backend node

[shinojnmp]

Describe the problem

unable to instantiate the hlm-backend using helm chart. getting error CrashLoopBackOff

pod description:

Name: hlm-backend-64b996c4db-cqzkg
Namespace: default
Priority: 0
Service Account: default
Node: aks-agcsnode1-38038755-vmss000006/10.224.0.5
Start Time: Mon, 25 Sep 2023 18:01:03 +0530
Labels: component=hlm-backend
pod-template-hash=64b996c4db
Annotations: cni.projectcalico.org/containerID: 42b85de1db482ed0b6990528c062171a05ebe28ffd48038aee26e4d08a53f5eb
cni.projectcalico.org/podIP: 10.244.1.7/32
cni.projectcalico.org/podIPs: 10.244.1.7/32
Status: Running
IP: 10.244.1.7
IPs:
IP: 10.244.1.7
Controlled By: ReplicaSet/hlm-backend-64b996c4db
Containers:
hlm-backend:
Container ID: containerd://ae33f923e51cfb19099b3756ee00862dcb7aaef59dacbb914651d402acfef5e1
Image: healenium/hlm-backend:3.4.0
Image ID: docker.io/healenium/hlm-backend@sha256:c8bad0103c6e7ebcab529439775b573e399ad0ca9a532c03f52e7ebf2ff72f22
Port: 7878/TCP
Host Port: 0/TCP
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 1
Started: Mon, 25 Sep 2023 18:04:51 +0530
Finished: Mon, 25 Sep 2023 18:05:01 +0530
Ready: False
Restart Count: 5
Limits:
cpu: 1
memory: 2Gi
Requests:
cpu: 200m
memory: 1Gi
Environment:
SPRING_POSTGRES_DB: healenium
SPRING_POSTGRES_SCHEMA: healenium
SPRING_POSTGRES_USER: healenium_user
SPRING_POSTGRES_PASSWORD: YDk2nmNs4s9aCP6K
SPRING_POSTGRES_DB_HOST: db-postgresql.default.svc.cluster.local
KEY_SELECTOR_URL: false
COLLECT_METRICS: true
HLM_LOG_LEVEL: info
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-mpwbm (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
kube-api-access-mpwbm:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional:
DownwardAPI: true
QoS Class: Burstable
Node-Selectors:
Tolerations: node.kubernetes.io/memory-pressure:NoSchedule op=Exists
node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message

---

Normal Scheduled 5m29s default-scheduler Successfully assigned default/hlm-backend-64b996c4db-cqzkg to aks-agcsnode1-38038755-vmss000006
Normal Pulled 3m12s (x5 over 5m28s) kubelet Container image "healenium/hlm-backend:3.4.0" already present on machine
Normal Created 3m12s (x5 over 5m28s) kubelet Created container hlm-backend
Normal Started 3m12s (x5 over 5m28s) kubelet Started container hlm-backend
Warning BackOff 21s (x19 over 5m2s) kubelet Back-off restarting failed container hlm-backend in pod hlm-backend-64b996c4db-cqzkg_default(494776c9-e570-47af-877a-899b0e594dcd)

Healenium Web version

3.4.4

Healenium Backend version

3.4.0 ( healenium/hlm-backend:3.4.0)

Selenium version

4.10.0

Platform

JAVA

Properties file

recovery-tries = 1
score-cap = .6
heal-enabled = true
hlm.server.url = http://localhost:7878
hlm.imitator.url = http://localhost:8000

Logs appeared during using Healenium

healenium standalone installation with the same configuration is working fine, 
Now trying to run the services on Kubernetes (AKS) where hlm-backend is throwing error.
postgress & imitator service are up and running

Installation type: using hlm chart

Additional context

No response