IBM DataPower Operations Dashboard v1.0.19.0

A newer version of this product documentation is available.

You are viewing an older version. View latest at IBM DPOD Documentation.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Removing non-DPOD Directories with a Prefix of /data

The following steps apply to all DPOD installations (All-in-One, cell manager and cell members).

Before applying the upgrade to 1.0.16.0, please make sure there are no non-DPOD directories that start with /data, such as /data-old, /datapower, /data_backup, etc. If such directories exist, please remove or rename them.

DPOD data directories start with /data and are optionally followed by a number, such as /data, /data2, /data33, etc.

Non-DPOD directories that start with /data will cause the upgrade to 1.0.16.0 to fail.

You may restore the directories after applying the fix.

Removing Unused Properties from the Retention Configuration File

The following steps apply to all DPOD installations (All-in-One, cell manager and cell members).

  1. Some installations might have unused properties in the retention configuration file, which may cause the upgrade to 1.0.16.0 to fail with the following error:

    File /app/hk_retention/MonTier-HK-ESRetention/conf/MonTierHousekeeping.conf contains placeholders
  2. Before applying the upgrade to 1.0.16.0, please execute the following commands:

    sed -i '/elasticsearch\.index\_set\.logical\-tran\-full\.max\_size\=.*/d' /app/hk_retention/MonTier-HK-ESRetention/conf/MonTierHousekeeping.conf
    sed -i '/elasticsearch\.index\_set\.iib\-log\-tran\.max\_size=.*/d' /app/hk_retention/MonTier-HK-ESRetention/conf/MonTierHousekeeping.conf
    sed -i '/elasticsearch\.index\_set\.iib\-stats\-tran\.max\_size=.*/d' /app/hk_retention/MonTier-HK-ESRetention/conf/MonTierHousekeeping.conf

Internal Alerts May Appear About the Reindex Manager

After the upgrade to 1.0.16.0 completes successfully, the following internal alert may appear once or twice:

A critical service is not working: Could not find the latest successful Reindex Manager execution

This is expected and does not indicate an issue with the upgrade.

However, if the internal alert is triggered continuously, please open a support case.

  • No labels