Restart Orient Me pods after Internal Server Error

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

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

Christoph Stoettner

I work at Vegard IT GmbH as a senior consultant with a focus on collaboration software, Kubernetes, security and automation. I mainly deal with HCL Connections, WebSphere Application Server, Kubernetes, Ansible, Terraform and Linux.

Sometimes my daily work results in technical talks and blog articles, which you can follow here more or less regularly. You can find the presentations in the main menu under public speaking .

I created a list of tools I use regularly, most of which have been released under an open source license.

In my spare time I read a lot, test all kinds of technical software and gadgets and try to follow about 200 RSS feeds.
Here you can find a collection of them.

This is my private blog, all opinions are my own.

           

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

Social Connections 14 in Berlin

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

Migrate MongoDB in HCL Connections Component Pack 8

The official documentation, “Migrating data from MongoDB 3 to 5”, wants to dump the MongoDB databases in 3.6 and then restore this data into the newly deployed MongoDB 5.

One issue with this process is that we can’t run the two MongoDB versions in parallel on Kubernetes because the provided helm charts and container for MongoDB 3.6 stop running after Kubernetes 1.21. On the other side, the helm chart providing MongoDB 5 can’t be installed on those old Kubernetes versions. So the process to update is:

Migration process

  1. Dump databases in MongoDB 3.6 (version delivered with Connections 7)
  2. Update Kubernetes to 1.25 or 1.27
  3. Restore MongoDB databases to version 5.0
Created:
Last Update: Read in about 6 min
Card image cap

Show table borders during editing in Tiny Editors

After updating HCL Connections to 8CR3 and Tiny Editors to 4.9.2.24 the lines of tables are no longer visible during editing.

Here is the edit form with Tiny Editors 4.8.2.0:

Created: Read in about 2 min