Bug ID 525464: Restarting TMM or running failover offline command causes causes bigd 'emerg logger' error message.

Last Modified: Jan 01, 2023

Bug Tracker

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

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, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4

Fixed In:
12.1.0

Opened: May 28, 2015
Severity: 4-Minor

Symptoms

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.

Impact

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.

Conditions

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.

Workaround

None.

Fix Information

Restarting TMM or running failover offline command no longer causes bigd 'emerg logger' error message.

Behavior Change