Bug ID 684782: APM eam process may be in restart loop with a core file generated each time when log level was changed from LOGLEVEL_DEBUG3 to LOGLEVEL_ERROR.

Last Modified: Mar 21, 2019

Bug Tracker

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

Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3,,,,, 11.6.4, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 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.4, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,

Fixed In:

Opened: Sep 21, 2017
Severity: 2-Critical
Related AskF5 Article:


APM eam process might go into a restart loop, with a core file generated at each restart, when log level is changed from LOGLEVEL_DEBUG3 to LOGLEVEL_ERROR.


eam restart loop, with a core file generated each time it restarts.


Change log level from LOGLEVEL_DEBUG3 to LOGLEVEL_ERROR (which you might do to implement the workaround in K82304591: OAM ASDK log files may grow to consume excessive disk space, https://support.f5.com/csp/article/K82304591).


Delete any unwanted accessgate from APM. For every accessgate configured on the APM, you must also configure and enable a corresponding accessgate on the OAM server.

Fix Information

The EAM module now processes logging level changes correctly.

Behavior Change