Bug ID 554134: Evrouted crash if 2nd instance evrouted started.

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP TMOS(all modules)

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, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 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: Oct 23, 2015

Severity: 2-Critical

Symptoms

If evrouted is already running and a new instance is started, the new instance will exit uncleanly and leave a core dump.

Impact

evrouted dumps core instead of exiting cleanly.

Conditions

This is only possible if evrouted exited uncleanly and therefore failed to clean up its PID file.

Workaround

None

Fix Information

evrouted is a daemon related to the iCall feature. If it was already running and a new instance is started, then the new instance would exit uncleanly and leave a core dump. This has been fixed, and the second evrouted instance will now exit cleanly (without dumping core).

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips