Bug ID 449798: Race condition on secondary blade where bigd service sometimes does not get built-in monitors

Last Modified: Feb 13, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5

Fixed In:
11.6.0, 11.5.1 HF6

Opened: Feb 21, 2014
Severity: 3-Major
Related AskF5 Article:
K15255

Symptoms

There is a race condition on secondary blade in which the bigd service sometimes does not get built-in monitors.

Impact

Causes some nodes/pool members to not be monitored, while others may be monitored by multiple bigd processes in the cluster. The system posts messages similar to the following in LTM and logs: -- err bigd[9433]: 01060129:3: Template /Common/postgresql is not initialized. -- err bigd[9433]: 01060129:3: Per-invocation log rate exceeded; throttling.

Conditions

Intermittently, when a failure on a VIPRION blade in a clustered system causes mcpd to restart, the bigd service does not receive configuration information for built-in monitors, causing the service to log failures and misidentify which monitors it should be running.

Workaround

Manually restart bigd on the affected blade.

Fix Information

An issue has been corrected that potentially caused blade failures on secondary blades in a VIPRION chassis to have subsequent issues executing health monitors.

Behavior Change