Last Modified: Apr 10, 2019
See more info
Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199
Opened: Feb 22, 2018
Related AskF5 Article: K74714343
The bigd daemon may core due to excessive memory consumption caused by a slow memory leak that occurs when creating or updating an LTM node or pool member. This memory leak occurs much more quickly when using FQDN nodes/pool members with the 'autopopulate' feature enabled.
The bigd daemon may core due to excessive memory consumption.
The bigd memory leak occurs slowly with non-FQDN nodes/pool members, but much more quickly when using FQDN nodes/pool members with the 'autopopulate' feature enabled. An additional leak occurs each time an FQDN name is resolved for an FQDN node or pool member. The rate of the leak in this case is determined by the number of FQDN nodes/pool members configured with the 'autopopulate' feature enabled, and the FQDN name resolution interval (determined by the 'interval' setting of the 'fqdn' configuration for the FQDN node).
It is possible to work around this issue by one of the following methods: 1. Configure a longer 'interval' value in the 'fqdn' configuration for configured FQDN nodes. 2. Configure FQDN nodes/pool members without the 'autopopulate' setting enabled. 3. Restart the bigd daemon before memory consumption becomes excessive. (Note that this may interrupt traffic to configured pool members.)
The bigd daemon no longer leaks memory when configuring an LTM node or pool member, particularly when using FQDN nodes/pool members with 'autopopulate' enabled.