Symptoms
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.
Impact
eam restart loop, with a core file generated each time it restarts.
Conditions
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).
Workaround
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.
