During an upgrade from EEP 6.x to EEP 7.0.0 or EEP 7.0.1, some monitoring components do not get
updated because of an error in the fourth digit of the package version. This page provides a
workaround for the issue.
About this task
The issue (known issue ES-77 or FLUD-55) is fixed in EEP 7.1.0 and later.This issue can occur during
manual upgrades or upgrades performed using the Installer. The affected components
can include any or all of the following:
- Elasticsearch
- Fluentd
- Grafana
- Kibana
Follow these steps to identify, remove, and reinstall the packages that were
not upgraded:
Procedure
-
After upgrading, use one of the following commands to check the package
versions of the installed monitoring components:
| OS |
Command |
| RHEL/CentOS |
yum list installed |
| SLES |
zypper packages --installed-only |
| Ubuntu |
apt list --installed |
-
Identify the packages that were not upgraded. The following table shows the
desired versions for each package for EEPs 7.0.0 and 7.0.1. For more version
information, see Component Versions for Released Ecosystem Packs.
| Package |
Desired Version |
| EEP
7.0.0 |
EEP
7.0.1 |
mapr-elasticsearch |
6.8.8.0 |
6.8.8.0 |
mapr-fluentd |
1.10.3.0 |
1.10.3.0 |
mapr-grafana |
6.7.4.0 |
6.7.4.0 |
mapr-kibana |
6.8.8.0 |
6.8.8.0 |
-
Before removing the packages that were not upgraded:
-
Ensure that you have backed up any configuration files and indexes as
described in Pre-Upgrade Steps for Monitoring. For
Elasticsearch in particular, you must back up the default location for
Elasticsearch index data unless you specified a non-default location
using the
-ESDB parameter with
configure.sh during installation.
-
Export or make backup copies of any custom dashboards you configured
for Grafana or Kibana.
-
Manually uninstall the packages that were not upgraded by using one of the
following commands. For example, to uninstall the Elasticsearch package:
- RHEL/CentOS:
- SLES:
- Ubuntu:
-
Install the desired packages for EEP
7.0.0 or EEP 7.0.1 using one of
the following methods: