Last Modified: Oct 06, 2020
Affected Product:
See more info
BIG-IP TMOS
Known Affected Versions:
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, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9
Fixed In:
11.6.0
Opened: Feb 06, 2014
Severity: 2-Critical
Related AskF5 Article:
K51222549
TMM crashes at startup when reprovisioning.
TMM crashes on startup because it cannot obtain the memory allocated. In the specific case of provisioning failure, and depending on the modules being provisioned the system might post messages similar to the following: -- err mcpd[7608]: 01070066:3: Publication not found in mcpd for publisher Id WAMD_McpInvalidation_Publisher. -- err mprov:1265:: 'Reserving huge memory failed (desired amount: 6295 pages [12590 MiB], allocated: 4248 pages [ 8496 MiB].' -- err mprov:1265:: 'Resource reallocation could not be completed - A reboot is necessary for provisioning to complete.'
Although there are several potential causes for this issue, they are difficult to quantify. For example, when provisioning stops the tmm, subsequent processing that finishes the provisioning activity might restart some daemons.
Reboot the system.
Memory handling during reprovisioning has been improved, so that daemon restarts no longer cause TMM crashes.