Last Modified: Sep 13, 2023
Known Affected Versions:
11.6.2 HF1, 11.2.0, 11.2.1, 11.3.0, 11.4.0
11.6.0, 11.5.1 HF6
Opened: Feb 21, 2014 Severity: 3-Major Related Article:
Related Article: K15255
There is a race condition on secondary blade in which the bigd service sometimes does not get built-in monitors.
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: 01060129:3: Template /Common/postgresql is not initialized. -- err bigd: 01060129:3: Per-invocation log rate exceeded; throttling.
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.
Manually restart bigd on the affected blade.
An issue has been corrected that potentially caused blade failures on secondary blades in a VIPRION chassis to have subsequent issues executing health monitors.