Last Modified: Oct 07, 2023
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
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, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1
Fixed In:
14.1.0, 13.1.0
Opened: Feb 02, 2017 Severity: 4-Minor Related Article:
K05304332
ulimit -c is set to 0 by default for login shells. This means that if a process crashes, and the process was started from an interactive session (e.g., via SSH or the console), it will not generate a core file. This behavior does not affect core system daemons such as TMM, MCPD, etc.
Processes run/started from an interactive session (e.g., via SSH or the console) that crash will not generate core files.
This occurs in the default configuration.
At a bash shell, set the core file limit for the current shell (and child processes) to "unlimited" by running the following command: ulimit -c unlimited
Processes that start from interactive sessions will now generate core files when they crash. The "bigstart" command ensures that the default core file limit is '0' for system services managed via sysvinit, even if restarted by an administrator.