Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP All
Known Affected Versions:
11.5.1, 11.5.1 HF1, 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.1 HF10, 11.5.1 HF11, 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, 11.5.10, 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.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
Fixed In:
12.0.0
Opened: Oct 20, 2014 Severity: 3-Major Related Article:
K16731
When the hostname (ie with TMSH) is new, some daemons continue to log with the old hostname until the BIG-IP system is restarted.
Logs from the same machine may contain a mix of old and new domain names.
The domain name must be changed without rebooting the box or restarting all daemons.
Restart the offending daemons or reboot the box.
The fix updates the core logging library to always get the hostname from a common location updated by mcpd/errdefd. Daemons using either POSIX/syslog or errdefs will quickly and automatically pick up hostname changes. If any daemon fails to pick up hostname changes after this fix, it will almost certainly be using its own ad-hoc logging system and will need to be updated to use errdefs.