BlueMind Major Version Update: Upgrade from v4 to v5
BlueMind's major version change requires special attention to a number of points in addition to validating the prerequisites for any Updating BlueMind.
Check the points of vigilance
BlueMind Version
In order to upgrade to BlueMind 5, version 4 must be installed and updated to the latest available version.
System
Disk space
In view of PostgreSQL's upgrade from version 14 to 16, the /var/lib/postgresql partition must have an occupancy rate of less than 50%.
Similarly, if archiving is in place, check the quick spool size and make sure you have at least 50% free space.
Network
The KeyDB port must be authorized.
For further information, see: BlueMind Ports
Hardware
Hardware requirements have changed between BlueMind 4 and BlueMind 5. It is strongly recommended to consult Hardware sizing to adjust the server configuration.
Specific setup
CAS configuration
In BlueMind 5, CAS configuration is carried out per domain, rather than for the entire server as in v4. The server's CAS configuration is therefore not migrated.
OpenID configuration
In the case of a remote authentication service, ensure that it is properly configured and that you have a URL accessible from the BM server.
For further information, see :
- Setting up SSO with an external OpenID authentication server
- Configuring an OpenID client for BlueMind with a third-party Keycloak
Installation with Edge server
In the case of an installation with an Edge server not managed by BlueMind, correct its Nginx configuration.
Post-upgrade problems
See known problems at the end of the page:
Start eligibility test
This Eligibility Test must not be completed before updating BlueMind from v4 to v5.
A check-upgrade-v5 eligibility test has been added to CLI Admin Client to avoid any loss of data and ensure a smooth and secure upgrade to v5.
This test checks these 5 major points:
- Checking custom settings
- Checking hotupgrades
- Checking elasticsearch cluster status
- Checking cyrus replication
- Cyrus email checks
Run and validate the test
- Run the test by executing the following command:
bm-cli setup check-upgrade-5 --force-delete-many-orphans
Depending on sizing, the chek-upgrade-5 command can take over an hour. It is recommended to run in a screen or tmux session.
Testing and subsequent maintenance operations can be resource-intensive. It is therefore recommended to perform them during long periods of low activity, for example at the end of the day.
Repair commands are then proposed, according to the failures identified. The command list follows as follows (example):
Recommended repair commands to run:
bm-cli hotupgrade start --no-delay --scheduled
bm-cli index coherency --all --run-consolidate --workers=1 all
bm-cli maintenance repair --ops replication.parentUid 1518B471-729C-4C99-AEC0-86D4D87DCB12@734ea413.internal
bm-cli maintenance repair --ops replication.parentUid,message_bodies B9584543-273B-43F0-A450-09FCB38526A6@734ea413.internal
- Start a new verification once the recommended repairs are completed. This allows you to refresh the list of errors and potentially track those that have not been reported or repaired.
Transmitting results
We strongly recommend that you send our Support team the results of successive executions of these test commands via the creation of a ticket.
Update subscription
Upgrading BlueMind to a major version change requires a change in the addresses of the software periods. The subscription file must therefore be updated in order to be able to carry out the version change.
Purge trash
During data transfer, emails contained in the double bottom of the trash and drafts marked for deletion (old versions of drafts) are not migrated.
To free up disk space, we recommend purging these emails before the upgrade (this is a Cyrus server-specific process, no longer used in version 5) with the following command:
cyr_expire -X 0
Run BlueMind Update
Once the prerequisites and eligibility test have been validated:
- Follow the process of Updating BlueMind
⚠️ Support
In case of difficulty, create an issue ticket containing the following information:
- the contents of
/var/log/in tgz or zip format. If too large, provide at least these logs:
/var/log/bm/core.log/var/log/bm/imap.log/var/log/bm-webserver/webserver.log/var/log/bm-webserver/setup.log/var/log/bm-keycloak/keycloak.log/var/log/postgresql/postgresql-??-main.log- the return of these commands:
bm-cli node status
bmctl status
nproc
free -m
df -h;
uptime
- Clean up v4 backups
⚠️ Once the update is complete, we recommend that you purge your BlueMind 4 backups.
BlueMind 5 backs up e-mails using a new method in
/var/backups/bluemind/sds-spool. The first backup includes all e-mails, which can trigger a disk saturation alert if the available space is < 50%.V4 backups are no longer compatible. Removing them saves space.
Run post-update operations
Automatic BlueMind operations
Background operations are performed after the update. They have been designed to run without impacting the service in production.
Some features are unlocked over time following these post-ugrade operations. These include advanced e-mail sorting and message conversation settings.
To check the progress of post-upgrade operations, run the command :
bm-cli hotupgrade progress --details --filterSuccess
If these operations fail, a banner appears in the administration console, informing administrators. In this case, create a ticket (or update the one concerning the eligibility test - see above) on our ticket tracking tool.
Nginx configuration
If the Nginx configuration for a domain has been customized, copy the /etc/nginx/bm-local.d/<domain>.conf file to /etc/nginx/bm-local.d/<xxxxxtechnical_domain>/ and update the configuration there.
Known problems
Resolved issues
Signature display in composer
The signature is not visible in the composer, but is present in the e-mail received by the recipient.
↳ corrected in versions 5.2.7 and 5.3.1
Ref. BM-22080
Remaining cyrus data after migration from v4 to v5
Some data remain in the cyrus spool after upgrading to v5. These are e-mails that have been marked 'Expunged' by cyrus, and which we are not including in the upgrade. These files are located in the following directories:
/var/spool/cyrus/data//var/spool/cyrus/meta/This is not normally a large volume of mail.
↳ corrected in version 5.3.2
Ref. BM-21846
Draft saving error
On some installations, BlueMind webmail (mailApp) users' drafts are not saved and the e-mail cannot be sent. The problem does not systematically affect all drafts. ⇒ Bypass: refresh the page with the ctrl+F5 command, which disables the nginx websocket.
↳ corrected in versions 5.2.9 and 5.3.1
Ref. BM-22000
Problems awaiting correction
Mail icon in contact list
From the contact application, the e-mail shortcut in the contact list links to the old webmail interface:
Let's Encrypt activation
On some installations it is no longer possible to accept the Let's Encrypt terms and conditions after upgrading to version 5. ⇒ Bypass: use the following bm-cli command:```bash bm-cli certificate manage-lets-encrypt
*Ref. [BM-21613](https://forge.bluemind.net/jira/browse/BM-21613)*
#### Opening mailto links
If the old webmail interface has been removed, users who do not have the "Access to new webmail" role will not be able to display the *mailto* link configuration option in the BlueMind options.
⇒ **Bypass:** give this role to users.
<Pourinfo></Pourinfo> :
- <LiensMailto></LiensMailto>
- <Roles></Roles>
*Ref. [BM-21735](https://forge.bluemind.net/jira/browse/BM-21735)*
#### BlueMind videoconferencing access button
The button for quickly launching a videoconference has disappeared from the old bluemind banner.
:bulb: This problem only concerns the black banner, which only appears if the user uses the old webmail to read his mail.
*Ref. [BM-21977](https://forge.bluemind.net/jira/browse/BM-21977)*
#### Folder sorting error in old webmail
Sorting by sender in old webmail generates a server error if the current folder is too large. Once the server error has occurred, e-mails in the user's folder will no longer be retrieved.
⇒ **Bypass:** use the application's sorting parameters (instead of clicking at the top of the column) to re-sort by date.
*Ref. [BM-22019](https://forge.bluemind.net/jira/browse/BM-22019)*
#### Disappearance of shared mailboxes
https://forge.bluemind.net/jira/browse/BM-22058
Users subscribing to shared mailboxes and using Bluemind's old webmail may find themselves lost on the new one: their shared mailboxes are no longer displayed in the banner on the left of their screen.
If they are still subscribed to these mailboxes, they will have to go through their own settings to subscribe to the various mailboxes shared with them.
Although this is not a bug, given the impact on the sometimes confused users concerned, we plan to automatically subscribe each user to the shared mailboxes shared with them during the upgrade.
#### Non-terminal filters
The mail filters created since the old preferences were obligatorily terminal: once a filter had been applied to an email, no other filter was applied.
With the new webmail and preferences, you can now choose whether a filter is terminal or not.
When upgrading from BlueMind 4 to BlueMind 5, this option is not activated by the filter recovery, so all filters are non-terminal and can lead to confusing sorting for users.
*Ref. [BM-22085](https://forge.bluemind.net/jira/browse/BM-22085)*
<More></More>
<Moredoc></Moredoc>
- <Support></Support>
- <Logs></Logs>
- <Dimensionnement></Dimensionnement>
<Moreblog></Moreblog>
- [Bye Bye Cyrus IMAP](https://blog.bluemind.net/fr/bye-bye-cyrus-imap/)