Upgrade#
This section lists known issues that may affect Carbonio during or after the upgrade process. Most of them may arise when upgrading from old releases.
Known Issues (Current Release)#
This is a list of known issues that impact Carbonio during or after the upgrade to 25.3.0.
During the Carbonio upgrade procedure, you will be asked whether or not to update the janus configuration file:
Configuration file '/etc/janus/janus.jcfg'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** janus.jcfg (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/janus/janus.jcfg ...
As shown in the snippet above, you need to install the new configuration file by pressing Y (or I); after the upgrade is complete and before rebooting the Node, check that the file contains the Carbonio VideoServer public IP address, for example:
nat_1_1_mapping = "93.184.216.34"
During the Carbonio upgrade procedure, you will be asked whether or not to update the mongoose configuration file:
Configuration file '/etc/carbonio/message-dispatcher/mongooseim.toml'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** janus.jcfg (Y/I/N/O/D/Z) [default=N] ? N
As shown in the snippet above, you need to keep the existing configuration file N (or O).
In some occasions, e-mails shown in the Carbonio webmail are not
displayed correctly or are not shown at all. This is generally due to
the OWASP HTML Sanitiser, which must be disabled. To do so, log in to the
Node featuring the Mailstore & Provisioning Role and execute the
following command as the zextras user
zextras$ zmlocalconfig -e zimbra_use_owasp_html_sanitizer=false
Once done, restart the service
As the zextras user execute
zextras$ zmcontrol restart
As the zextras user execute
zextras$ zmcontrol restart
As the zextras user execute
zextras$ zmcontrol restart
As the root user execute
# systemctl restart carbonio-appserver.target
Known Issues (Older Releases)#
During or after the upgrade from an older version, you may encounter one or more of the following issues that require a manual intervention.
New GPG Key of Grafana in Ubuntu 22.04
Monitoring: a new configuration file for carbonio-prometheus package must be installed
Initialise domains for Delegated Administrators
Some accounts are not migrated during upgrade
PostgreSQL Upgrade fails
A missing library causes a RHEL Netcat Issue
Domain Initialisation fails with an error
Older version included a package that has been replaced, but it can cause conflicts during upgrades
You might be asked to keep or replace the Janus and Mongoose configuration files
E-mails’ body are not displayed or their rendering is wrong, due to the value a variable
If you migrate from Ubuntu 20.04 to 22.04 and use Monitoring Role’s Grafana, you need to update the location on which its GPG key is stored to prevent warning during upgrades. Log in to the Node on which the Carbonio Monitoring Role is installed and execute the following commands.
-
Remove existent repository
# add-apt-repository -r "deb https://packages.grafana.com/oss/deb stable main"
-
Retrieve GPG key
# wget -q -O - https://packages.grafana.com/gpg.key | \ gpg --dearmor | sudo tee /usr/share/keyrings/grafana.gpg > \ /dev/null
-
Add repository
# echo "deb [signed-by=/usr/share/keyrings/grafana.gpg] \ https://packages.grafana.com/oss/deb stable main" | sudo tee -a \ /etc/apt/sources.list.d/grafana.list
While upgrading the carbonio-prometheus package, you will be
prompted with the following text:
Configuration file '/etc/carbonio/carbonio-prometheus/prometheus.yml'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
You must replace the existing file with the new one, therefore answer Y or I.
In this release, you need to initialise again the domain(s) for Delegation: for each domain that has active Delegations, in the Carbonio Admin Panel go to and click the INIT DOMAIN button.
If the Global Administrator receives an e-mail notification about some
accounts not migrated to use the new backupEnabled attribute, run
the following commands as the zextras user to fix the issue.
First, stop the backup migration service
zextras$ carbonio backup dostopservice migrate-backup-enabled-setting
Then, start the service again to trigger the migration
zextras$ carbonio backup dostartservice migrate-backup-enabled-setting
During the upgrade of PostgreSQL, an error might be raised in case the existent databases have been created with older version of libc:
2024-03-19 12:28:14.209 UTC [909825] HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE activesync REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
2024-03-19 12:28:19.669 UTC [909915] WARNING: database "abq" has a collation version mismatch
In case you find in the log some messages similar to the one shown above, you need to recreate the collation and indexes of the databases using the following commands.
First, become the postgres user
# su - postgres
Then issue these two commands
$ psql -d abq -c "REINDEX DATABASE abq"
$ psql -d abq -c "ALTER DATABASE abq REFRESH COLLATION VERSION;"
These commands should probably be given for each of the databases, so you can copy & paste all the following commands:
psql -d abq -c "REINDEX DATABASE abq"
psql -d abq -c "ALTER DATABASE abq REFRESH COLLATION VERSION;"
psql -d powerstore -c "REINDEX DATABASE powerstore"
psql -d powerstore -c "ALTER DATABASE powerstore REFRESH COLLATION VERSION;"
psql -d activesync -c "REINDEX DATABASE activesync"
psql -d activesync -c "ALTER DATABASE activesync REFRESH COLLATION VERSION;"
psql -d auth -c "REINDEX DATABASE auth"
psql -d auth -c "ALTER DATABASE auth REFRESH COLLATION VERSION;"
psql -d "carbonio-docs-connector-db" -c "REINDEX DATABASE \"carbonio-docs-connector-db\""
psql -d "carbonio-docs-connector-db" -c "ALTER DATABASE \"carbonio-docs-connector-db\" REFRESH COLLATION VERSION;"
psql -d "carbonio-files-db" -c "REINDEX DATABASE \"carbonio-files-db\""
psql -d "carbonio-files-db" -c "ALTER DATABASE \"carbonio-files-db\" REFRESH COLLATION VERSION;"
psql -d "carbonio-tasks-db" -c "REINDEX DATABASE \"carbonio-tasks-db\""
psql -d "carbonio-tasks-db" -c "ALTER DATABASE \"carbonio-tasks-db\" REFRESH COLLATION VERSION;"
psql -d carbonio_adm -c "REINDEX DATABASE carbonio_adm"
psql -d carbonio_adm -c "ALTER DATABASE carbonio_adm REFRESH COLLATION VERSION;"
psql -d core -c "REINDEX DATABASE core"
psql -d core -c "ALTER DATABASE core REFRESH COLLATION VERSION;"
psql -d ha -c "REINDEX DATABASE ha"
psql -d ha -c "ALTER DATABASE ha REFRESH COLLATION VERSION;"
psql -d postgres -c "REINDEX DATABASE postgres"
psql -d postgres -c "ALTER DATABASE postgres REFRESH COLLATION VERSION;"
psql -d template0 -c "REINDEX DATABASE template0"
psql -d template0 -c "ALTER DATABASE template0 REFRESH COLLATION VERSION;"
psql -d template1 -c "REINDEX DATABASE template1"
psql -d template1 -c "ALTER DATABASE template1 REFRESH COLLATION VERSION;"
In systems which feature RHEL 8 or RHEL 9, you might find in
journalctl’s log an error about a missing library for netcat:
May 02 09:20:02 demo.example.com systemd[1]: Started Session 3 of User zextras.
May 02 09:20:02 demo.example.com bash[3910]: netcat: error while loading shared libraries: libbsd.so.0: cannot open shared object file: No such file or directory
May 02 09:20:02 demo.example.com systemd[1]: Started Session 4 of User zextras.
May 02 09:20:02 demo.example.com bash[3912]: netcat: error while loading shared libraries: libbsd.so.0: cannot open shared object file: No such file or directory
The solution is to install the libbsd package:
# dnf install libbsd
After performing the INIT DOMAIN operation (required for creating delegated administrators), the following error may occur.
zextras@:~$ carbonio admin initDomainForDelegation local.loc
Unknown Exception com.zextras.lib.http.HTTPClientException:
<soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">soap:Header<context
xmlns="urn:zimbra"/></soap:Header>soap:Bodysoap:Fault<faultcode>soap:Client</faultcode><faultstring>
no such distribution list:
__monitoring_admins@local.loc</faultstring><detail> <Error
xmlns="urn:zimbra"><Code>account.NO_SUCH_DISTRIBUTION_LIST</Code><Trace>qtp2021053848-1571:1721660801727:f88a830e260d85fa</Trace></Error></detail></soap:Fault></soap:Body></soap:Envelope>
The workaround is to manually generate the empty ACL groups BEFORE initializing the domain. This can be done with the following commands:
zextras$ carbonio prov cdl __monitoring_admins@local.loc zimbraIsAdminGroup TRUE
zextras$ carbonio prov cdl __helpdesk_admins@local.loc zimbraIsAdminGroup TRUE
zextras$ carbonio prov cdl __groups_admins@local.loc zimbraIsAdminGroup TRUE
zextras$ carbonio prov cdl __users_admins@local.loc zimbraIsAdminGroup TRUE
zextras$ carbonio prov cdl __delegated_admins@local.loc zimbraIsAdminGroup TRUE
zextras$ carbonio prov cdl __domain_admins@local.loc zimbraIsAdminGroup TRUE
After executing the suggested commands, you can then carry out the INIT DOMAIN operation, from either the Carbonio Admin Panel or the CLI.
If you upgrade from a release older than 24.5.0, you may run
into a conflict between the installed package config-generator
and the new service-discover-template package on both RHEL and
Ubuntu. To fix this conflict, before upgrading, you need to remove
the existing package and install the new one. You can do this with
the following commands
# apt install service-discover-template
# rpm -e --nodeps config-generator
Right after the command completes, proceed with the upgrade.
During the Carbonio upgrade procedure, you will be asked whether or not to update the janus configuration file:
Configuration file '/etc/janus/janus.jcfg'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** janus.jcfg (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/janus/janus.jcfg ...
As shown in the snippet above, you need to install the new configuration file by pressing Y (or I); after the upgrade is complete and before rebooting the Node, check that the file contains the Carbonio VideoServer public IP address, for example:
nat_1_1_mapping = "93.184.216.34"
During the Carbonio upgrade procedure, you will be asked whether or not to update the mongoose configuration file:
Configuration file '/etc/carbonio/message-dispatcher/mongooseim.toml'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** janus.jcfg (Y/I/N/O/D/Z) [default=N] ? N
As shown in the snippet above, you need to keep the existing configuration file N (or O).
In some occasions, e-mails shown in the Carbonio webmail are not
displayed correctly or are not shown at all. This is generally due to
the OWASP HTML Sanitiser, which must be disabled. To do so, log in to the
Node featuring the Mailstore & Provisioning Role and execute the
following command as the zextras user
zextras$ zmlocalconfig -e zimbra_use_owasp_html_sanitizer=false
Once done, restart the service
As the zextras user execute
zextras$ zmcontrol restart
As the zextras user execute
zextras$ zmcontrol restart
As the zextras user execute
zextras$ zmcontrol restart
As the root user execute
# systemctl restart carbonio-appserver.target