Configuration changes required on protocol nodes to collect core dump data

To collect core dumps for debugging programs in provided packages, these system configuration changes need to be made on all protocol nodes in the cluster.

Install the abrt-cli RPM if not already installed. For example, run rpm -qa | grep abrt-cli to check if it is already installed, or yum install abrt-cli to install the RPM.
Set OpenGPGCheck=no in the /etc/abrt/abrt-action-save-package-data.conf file.
Set MaxCrashReportsSize = 0 in the /etc/abrt/abrt.conf file.
Start (or restart) the abort daemon (for example, run systemctl start abrtd to start the abort daemon after a new install, or systemctl restart abrtd if the daemon was already running and the values in steps 2 and 3 were changed).

For additional details, see the Documentation about ABRT-specific configuration.

Additional setup steps applicable for NFS

A core dump might not be generated for code areas where the CES NFS process has changed credentials. To avoid this, do the following steps:

Insert the following entry into the /etc/sysctl.conf file:
```
fs.suid_dumpable = 2
```
Issue the following command to refresh with the new configuration:
```
sysctl -p
```
Verify that /proc/sys/fs/suid_dumpable is correctly set:
```
cat /proc/sys/fs/suid_dumpable
```
Note: The system displays the following output if it is correctly set:
```
2
```