Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP All
Known Affected Versions:
11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2
Fixed In:
12.1.0
Opened: May 26, 2015 Severity: 4-Minor
Stopping and starting the tmm causes bigd to restart with an 'emerg logger' error message. The restart is expected behavior, but the error-level message is not.
bigd restarts and a message is logged to the console similar to the following: emerg logger: Re-starting bigd. Traffic monitoring ceases until TMM restart is complete. For the failover offline, impact is limited as unit is sent offline.
On active unit run one of the following commands: -- bigstart restart tmm. -- bigstart stop tmm;bigstart start tmm. -- bigstart stop tmm;bigstart start. -- tmsh run sys failover offline.
None.
Restarting TMM or running failover offline command no longer causes bigd 'emerg logger' error message.