Bug ID 1001541: TMM crash (SIGFPE) when starting on a VCMP guest

Last Modified: Jan 01, 2023

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS, vCMP(all modules)

Known Affected Versions:
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, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6

Fixed In:
14.1.0, 13.1.4, 12.1.6

Opened: Mar 11, 2021
Severity: 2-Critical

Symptoms

A log message in /var/log/tmm similar to the following: Assertion 'Hash type successfully set' failed.

Impact

Tmm may initially fail to start, log an SIGFPE, and then might or might not start normally afterwards.

Conditions

A vCMP guest running either: - v13.x release of 13.1.3.6 or later - v12.x release of 12.1.5.3 or later A vCMP hypervisor that is running - v13.x release of 13.1.3.4 or lower - v12.x release or 12.1.5.2 or lower - v11.x release Any vCMP guests running v14.x or later are not affected.

Workaround

Either: -- Upgrade the vCMP Hypervisor to the latest release. -- Upgrade the guest to v14.1.0 or later. It may also help to remove the cached libdag on the guest, and restart tmm by running the following commands on the guest: rm -f /var/run/libdag.so_* && bigstart restart tmm

Fix Information

None

Behavior Change