Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP GTM
Known Affected Versions:
11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2
Fixed In:
12.1.0, 11.6.5.3
Opened: Dec 17, 2014 Severity: 4-Minor
Excessive 'hash grow: malloc failed' messages in the ltm log: err tmm10[31888]: hash grow: malloc failed. The message indicates that the cache has reached a point where it needs to be resized because memory allocation failed.
Log filled with 'hash grow: malloc failed' log messages. Although the failure of the allocation can occur during normal operation, the number of messages is excessive, as it does not provide any useful information after the first failure.
The messages are visible when viewing the ltm log during low memory conditions, perhaps due to memory leaks or high memory usage.
To filter out hash grow: malloc failed errors from the log, set dnscacheresolver.loglevel to critical or emerg. For example, to set log level to critical, run the following command: tmsh modify sys db dnscacheresolver.loglevel value critical. This records only critical errors to the log.
The DNS cache hash table memory expansion warning message 'hash grow: malloc failed' now occur four times a minute instead of excessive number of times during the failed memory allocation events, so the log is no longer filled with excessive numbers of messages.