Help - Senhasegura update from 3.33 to 4.0

PAM Core
1

Hello Senhasegura community.

I have an environment with 2 Senhasegura nodes and 1 arbiter. I want to perform the update for my Senhsegura instances, so that I have the latest version of the product.

I am following the official documentation guide on the update:
How to update Segura online
So, I took the snapshots, I removed my arbiter from the cluster, but here is what I am not sure about.

So, on my primary server once I executed the commands:
apt-get update
apt-get install orbit-cli
and then - orbit update

I ended up seeing this in my cli:

image
image949×492 8 KB

I checked the version afterwards and I saw this:

image
image340×241 2.7 KB

Is this a normal behavior? Should I proceed with my secondary server? If it’s not, what should I do? Can someone please help?

2

Hi Almaz,

you must running command orbit update up to 4 times and and every process must restart OS

Thanks,

3

Hello Almaz Akhmadullin,

The behavior you’re seeing is expected in certain scenarios. When the update process includes Debian kernel package updates, a specific message is displayed at the end of the update process. This message typically instructs you to:

  1. Restart the Segura® instance (as outlined in Step 7 of the official guide);
  2. After rebooting, run the orbit update command again (Step 6), if prompted or if the update wasn’t fully applied.

These steps are essential — skipping them may result in an incomplete update or lead to system instability.

In summary, yes — go ahead and restart your primary instance, then rerun the orbit update command. After confirming that the update completed successfully and the system is stable, you can proceed with updating your secondary node.

Feel free to reach out if you have any questions throughout the process!

Best regards.