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
Comments
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.
Success!
Your comment has been posted successfully.

Comments

Loading comments...

Leave a Comment

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

Suggested Reading
Card image cap

For HCL Connections 8 CR9, it is mandatory to update MongoDB to version 7. During my first migrations, I encountered some issues and would like to provide workarounds and additional troubleshooting tips to help others with this process.

Created:
Last Update:
Read in about 5 min
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

I haven’t touched the Connections scripts for a long time, but I recently made some minor updates to fix compatibility issues with newer versions and added small scripts to speed up configuration. I also got the documentation script running from the menu.

Created:
Last Update:
Read in about 2 min