Restart Orient Me pods after Internal Server Error

Created:
Author: Christoph Stoettner
Read in about 1 min · 72 words

Postboxes for newsletter

Photo by Timelab Pro | Unsplash

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
Add a comment
Error
There was an error sending your comment, please try again.
Thank you!
Your comment has been submitted and will be published once it has been approved.

Your email address will not be published. Required fields are marked with *

Suggested Reading
Card image cap

Last week I attended Social Connections 14 in Berlin, the event location had a great view and weather was great.

Created:
Last Update:
Read in about 1 min
Card image cap

Last week, I had three systems with issues displaying the Top Updates in the Orient Me. So I tried to find out which applications and containers are involved in generating the content for this view.

Created: Read in about 4 min
Card image cap

With HCL Connections 6.5 and later, we got the add-on HCL Connections Engagement Center (aka CEC, HCEC, ICEC or XCC) included in a normal HCL Connections deployment.

Created: Read in about 6 min