Update senhasegura

Why should you keep your application up-to-date?

• Security
• Protects your system from more cyberattacks.
• Other benefits
• Includes changes in response to customer feedback. 
• Improves existing functions.
• Improves system performance, and prevents your application from becoming slow and obsolete.
• Enhances usability.
• Fixes known bugs.

Check out our latest Changelog to learn about new features and fixes, security enhancements, and improved usability.

Requirements

• If you choose an Online update, please ensure your firewall rules allow communication with senhasegura repositories.
• Set the correct server time.
• Take a snapshot before the update.

Taking a snapshot

Snapshots should only be taken when senhasegura instances are off to ensure you can revert to a previous version if needed.

1. You can shut down a senhasegura instance using the following command:

   sudo orbit shutdown

2. When the instance is completely off, take the snapshot in the hypervisor.
3. Next, reboot your senhasegura instance and update the application.

   
   

Online update

To update senhasegura online, you will have to access senhasegura's repository.

Update the platform using our official mirror so that this instance receives the most up-to-date version of senhasegura.

1. Use our official mirror to update senhasegura to the latest version.
2. Use the command sequence below to update the package list, Orbit binary, and platform. The log output is often long and can take a few minutes to print in your terminal.
   ShellShell

   sudo apt-get update
   
   sudo apt-get install orbit-cli
   
   sudo orbit upgrade

   Danger

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

   If you have done it accidentally, run "orbit upgrade" to correct any potential problems.

   
   
3. Reboot the instance to make sure all services are now using the updated interface.
   ShellShell

   sudo orbit shutdown --reboot

   
   
4. After the reboot is complete, the system will be available through the web interface again.

   
   

Offline update

If your vault is not connected to the internet, you can follow these steps to update your application offline:

1. Download the update package to a separate device:
   ShellShell

   wget https://repo:[email protected]/buster-se-update.sh

2. Create a folder for the update files inside the /var/update  directory using the following command:
   ShellShell

   sudo install -d update -g mt4adm -o mt4adm

3. Upload the file downloaded in step 1 to senhasegura's server (via scp, fir example):
   ShellShell

   scp -P 59022 <update_file_name>  mt4adm@<IP>:/var/update

4. Move the update file to /var/tmp/update:
5. Add a "#" comment to every line in 'resolv.conf' to prevent it from trying to connect to the internet during the update:ShellShell

   sudo vim /etc/resolv.conf

6. Next, give the user permission to run the update file:ShellShell

   sudo chmod +x <update_file_name>

7. In our example, we named the update file 'buster-se-update-3.20.sh', so our command would read:
8.  Run the package using the following command:
   ShellShell

   sudo bash <update_file_name>

9. Type Y to agree with the EULA terms.
10. After running the update file, go back to 'resolve.conf' and remove the '#' comment from all previously modified lines.
11. Reboot the device:ShellShell

    sudo orbit shutdown --reboot

12.  After the reboot is complete, run the following command and type Y to confirm:
    ShellShell

    sudo orbit application init

    
13. The application has now been successfully updated. If you want to check the current version, run the following command: lShell

    sudo orbit version

    

Updating a cluster

Before updating a cluster, make sure that it meets the following requirements:

• All instances in the cluster are configured properly.
• Firewall rules allow the use of Port 443 to connect to senhasegura's repository. 
• If you change settings, reboot all instances to apply the latest configuration.

If your cluster satisfies all the requirements above, perform these steps to update it:

1. Go to Orbit Config Manager ➝ Replication ➝ Status and check the status of each node. All nodes must be ON and synced.
2. Pause the password automation in Settings ➝ Execution processes. Turn the following items OFF:

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

3. Take snapshots of each instance. Remember to take snapshots in reverse order, from the last node to the first.

4. Run the following command to update the cluster's primary member:

sudo apt-get update

sudo apt install orbit-cli

5. Next, update senhasegura:

Shell
sudo orbit update

6. Check the current version to ensure that senhasegura has been updated successfully. Make sure all instances have the same version after the update.

sudo orbit version

7. Once the update is complete, reboot the device:

sudo orbit shutdown --reboot

8. Repeat steps 4 to 7 to update the following instances.

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

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

10. Finally, go back to Orbit Config Manager ➝ Replication ➝ Status, and check the status of each node to confirm that they are ON and synced.