- 4 minutes to read
- Print
- DarkLight
- PDF
Update senhasegura
- 4 minutes to read
- Print
- DarkLight
- PDF
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.
Never update senhasegura without taking a snapshot in your hypervisor and creating a backup using Orbit CLI.
Taking a snapshot
Snapshots should only be taken when senhasegura instances are off to ensure you can revert to a previous version if needed.
Always update instances in the reverse clustering order. Start by updating the last node in the cluster and move on until you update the Primary node last. Don't forget to take a snapshot of all senhasegura instances, running each instance separately. For each instance, shut it down, take a snapshot, and reboot this instance before moving on to the next.
- You can shut down a senhasegura instance using the following command:
sudo orbit shutdown
- When the instance is completely off, take the snapshot in the hypervisor.
- 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.
- Use our official mirror to update senhasegura to the latest version.
- 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.Shell
sudo apt-get update sudo apt-get install orbit-cli sudo orbit upgrade
DangerDo not run the "apt-get upgrade" command.If you have done it accidentally, run "orbit upgrade" to correct any potential problems.
- Reboot the instance to make sure all services are now using the updated interface. Shell
sudo orbit shutdown --reboot
- 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:
- Download the update package to a separate device:Shell
wget https://repo:[email protected]/buster-se-update.sh
- Create a folder for the update files inside the /var/update directory using the following command:Shell
sudo install -d update -g mt4adm -o mt4adm
- Upload the file downloaded in step 1 to senhasegura's server (via scp, fir example): Shell
scp -P 59022 <update_file_name> mt4adm@<IP>:/var/update
- Move the update file to /var/tmp/update:
- Add a "#" comment to every line in 'resolv.conf' to prevent it from trying to connect to the internet during the update:
sudo vim /etc/resolv.conf
- Next, give the user permission to run the update file:
sudo chmod +x <update_file_name>
- In our example, we named the update file 'buster-se-update-3.20.sh', so our command would read:
- Run the package using the following command:
sudo bash <update_file_name>
- Type Y to agree with the EULA terms.
- After running the update file, go back to 'resolve.conf' and remove the '#' comment from all previously modified lines.
- Reboot the device:
sudo orbit shutdown --reboot
- After the reboot is complete, run the following command and type Y to confirm:
sudo orbit application init
- The application has now been successfully updated. If you want to check the current version, run the following command:
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. 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 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.