Error malloc_consolidate(): invalid chunk while initializing ODBC policy store with Native Drivers on starting the SiteMinder Policy Server container

Products

• SITEMINDER

Issue/Introduction

SiteMinder in containers has been successfully deployed and it has been correctly configured to point to an ODBC Policy Store using native drivers. The Database has been correctly populated with the policy store schema and the relevant entries in the tables created

However, on starting the Admin policy server container, the following errors are obtained in the log (shown for MySQL ODBC)

[*][16:43:58][POLICY_SERVER_CONTAINER] - Running smconfigtool for Policy Store DSN Creation
  Configuring admin ODBC DSN of type:POLICY_STORE
    [<policy_store_name>]
    Driver=<Path_to_odbc_native_lib>/libmaodbc.so
    Description= Connector ODBC MariaDB for MySQL
    SERVER=<server_ip>
    PORT=3306
    Database=<policy_store_name>
    DMEnvAttr=SQL_ATTR_UNIXODBC_ENVATTR={MARIADB_PLUGIN_DIR=<Path_to_odbc_native_lib>/plugin}
    OPTION=2
malloc_consolidate(): invalid chunk size
<SiteMinder_home>/bin/smconfigtool.sh: line 251:   194 Aborted                 $java -classpath $cp com.ca.sm.smconfigtool.ConfigSmOdbcStore $STORE_TYPE $CREATEONLYDSN $SERVER_PORT "$STORE_DSN" "$STORE_USER" "$STORE_USER_PASSWORD" "$SERVER_NAME" "$DATABASE_NAME" DB_MYSQL null true $ROLE $CONNECTION_CHECK
[*][16:44:00] - ConfigSmOdbcStore failed
[*][16:44:00][POLICY_SERVER_CONTAINER] - Error ODBC configuration failed for policy store, exiting in 60 sec

And the policy server cannot complete correct startup and initialization

Using LDAP policy store works seamlessly.

Environment

SiteMinder versions 12.8.8 and 12.9 in Containers

Cause

This may be caused by the Dynatrace Agent deployed in containers.

Whenever Dynatrace is installed in containers, Dynatrace-Operator automatically injects a Dynatrace Agent container into the pods. It looks like this container may be interfering with operation of the policy server container

Resolution

Remove the Dynatrace Agent container to prevent it from interacting with the Policy Server container

If Dynatrace must be involved due to business requirements please contact Dynatrace Support for finding a way to eliminate its fingerprint on the Policy server container