Cloudera Docs

Known Issues in Platform

This document lists the known issues in the Cloudera Runtime 7.1.9 SP1 CHF16 Platform. Review this content to understand how these issues impact functionality and to find the necessary workarounds.

Known issues identified in Cloudera Runtime 7.1.9 SP1 CHF 16

CDPD-95213: Service startup failure due to strict Log4j 2.25 property validation

After you upgrade to Cloudera Runtime 7.1.9 SP1 CHF16 or higher (and Cloudera Manager 7.13.1.710 or higher), services might fail to start with the following exception: ConfigurationException: No type attribute provided for component logger

This issue arises from a regression in Log4j 2.25.x (introduced to resolve CVE-2025-68161). Unlike previous versions that ignored configuration mismatches, Log4j 2.25 strictly validates all property prefixes.

If your configuration includes a logger or appender but lacks a corresponding type definition for that entry, the system throws a fatal exception. While Cloudera has automated a fix for the default Hive service, any other service—or any service utilizing custom loggers through a safety valve remains vulnerable to this breaking change.

You must manually align the loggers or appenders list with their definitions:

  1. In Cloudera Manager, navigate to the affected or failing service (for example, Hive, HBase, Kafka).

  2. Navigate to the affected service Configuration tab and search for the relevant log4j_safety_valve (for example, Hive Service Advanced Configuration Snippet (Safety Valve) for log4j2.properties).

  3. Locate and review the loggers or appenders property.

  4. Add the missing logger or appender entry to the loggers or appenders list to fix the mismatch.

  5. Alternatively, remove the mismatched definition entirely.

  6. Save the changes and restart the affected service.