Restart Orient Me pods after Internal Server Error ·

After rebooting the Kubernetes server for HCL Connections Componentpack, I sometimes see that Orient Me is not working and just shows:

{"error":{"statusCode":500,"message":"Internal Server Error"}}

I think one of the liveness checks could be improved, but for now the following commands restart just the necessary amount of pods to get Orient Me back running.

kubectl rollout restart statefulset redis-server
sleep 45
kubectl rollout restart deployment redis-sentinel
sleep 90
kubectl rollout restart deployment orient-web-client

Author

Christoph Stoettner

I work at Vegard IT GmbH as a senior consultant, focusing on collaboration software, Kubernetes, security, and automation. I primarily work with HCL Connections, WebSphere Application Server, Kubernetes, Ansible, Terraform, and Linux. My daily work occasionally leads to technical talks and blog articles, which I share here more or less regularly.

Related