Update senhasegura
  • 3 minutes to read
  • Dark
  • PDF

Update senhasegura

  • Dark
  • PDF

Importance of updates

  • Security
    • The environment is more protected against cyberattacks.
  • Benefits
    • Improvements suggested by customers.
    • Improvements to existing functions.
    • System performance improvement to prevent slowness and staleness.
    • Usability improvement.
    • Bug fixes.

Check the Changelog often for fixes, new features, and security and usability improvements.


  • Appropriate firewall rules to allow access to senhasegura repositories if you choose an Online update
  • Set the correct server time.
  • Take a snapshot before the update.

Before executing the senhasegura update, always run a snapshot in your hypervisor and perform a backup using Orbit CLI.

Take a snapshot

Take the snapshots with the senhasegura instances turned off to ensure that the reversal is possible.

Snapshot with Cluster
In senhasegura clusters, start from the last node and end at the master. Always run a snapshot of all senhasegura instances, but run each instance separately. Power off one instance at a time, take the snapshot, power back on, and validate before proceeding to the next instance.
  1. Turn off the senhasegura instance using the command:
    sudo orbit shutdown
  2. After the instance is shut down, proceed with running the hypervisor snapshot.
  3. When the snapshot is complete, activate the senhasegura instance again and update the application.

Online update

To update senhasegura online, remember to access the senhasegura repository.

  1. Update the platform using our official mirror so that this instance receives the most up-to-date version of senhasegura.
  2. The command sequence below updates the package list, Orbit binary, and platform. The terminal will display a long log output, which can take a few minutes.
    sudo apt-get update
    sudo apt-get install orbit-cli
    sudo orbit upgrade

    Do not run the "apt-get upgrade" command.

    In case of execution, use "orbit upgrade" to correct any problems generated.

  3. Restart the instance to ensure all services use this configured interface.
    sudo orbit shutdown --reboot
  4. Wait for the instance to finish rebooting, and the system will be available to be accessed through the web interface.

Offline update

If the vault does not have internet access, perform the following steps to perform the offline upgrade:

  1. On another station, download the update package:
    wget https://repo:[email protected]/buster-se-update.sh
  2. Create the updated folder inside the /var/update directory using the following command:
    sudo install -d update -g mt4adm -o mt4adm
  3. Upload the downloaded file to the senhasegura server (for example, via scp):
    scp -P 59022 <update_file_name>  [email protected]<IP>:/var/update
  4. Transfer the update file to the /var/tmp/update:
  5. After downloading, comment out all lines of the 'resolv.conf' file using "#" so that the update does not connect to the internet and try to update to an online version:
    sudo vim /etc/resolv.conf
  6. After commenting out the 'resolve.conf' file, give the downloaded file execute permissions using the command below:
    sudo chmod +x <update_file_name>
  7. In this example, the file name is 'buster-se-update-3.20.sh'.
  8.  Run the package using the following command:
    sudo bash <update_file_name>
  9. Confirm EULA terms for enforcement. 
  10. After execution, return to the 'resolve.conf' file and remove the '#' from all previously modified lines.
  11. Reboot the machine with the following command:
    sudo orbit shutdown --reboot
  12. After rebooting, run the following command and confirm:
    sudo orbit application init
  13. The application has been updated. To validate the version, use the command below:
    sudo orbit version

Cluster update

To perform the cluster upgrade process, ensure the requirements below:

  • All instances within the cluster are properly configured.
  • Port 443 released on the Firewall for the senhasegura repository.
  • After definitions, reboot all instances to update the information.

With the requirements fulfilled, you can start the action:

1. Go to Orbit Config Manager ➝ Replication ➝ Status and check the status of all clusters. They must be active and synchronized.
2. Turn off the password changer robot in the Settings ➝ Execution processes menu. Items that need to be OFF are:

  • Expired password
  • Expired operation cancellation
  • Operation executor
  • Operation executor: Retry

3. Take snapshots of all instances. Do not forget to carry out the process in reverse order, starting from the last member to the first.

4. Run the command to start updating the primary member:

sudo apt-get update

sudo apt install orbit-cli

5. Next, write the command to update senhasegura:

sudo orbit update

6. Check if it has been updated to the desired version using the command below and ensure that all instances are at the same version.

sudo orbit version

7. Once the update is complete, restart the machine:

sudo orbit shutdown --reboot

8. Repeat the process with the other instances.


When updating senhasegura in a cluster, do not make the members standalone. Update them individually, starting with the primary member and moving on to the other members.

E.g. "Update Member 1, when finished, Update Member 2, when finished, update Member 3".

Failure to follow these steps during the upgrade could break the cluster.

9. Return to Settings ➝ Execution processes menu and switch the items below to ON:

  • Expired password
  • Expired operation cancellation
  • Operation executor
  • Operation executor: Retry

10. Again, go to Orbit Config Manager ➝ Replication ➝ Status, and check the status of each cluster to confirm that they are up and in sync.

Was this article helpful?

What's Next