Creating syslog-ng OSE core files

When syslog-ng OSE crashes for some reason, it can create a core file that contains important troubleshooting information.

To enable core files, complete the following procedure:

Steps

Core files are produced only if the maximum core file size ulimit is set to a high value in the init script of syslog-ng. Add the following line to the init script of syslog-ng:
```
 ulimit -c unlimited
```
Verify that syslog-ng OSE has permissions to write the directory it is started from, for example, /opt/syslog-ng/sbin/.
If syslog-ng OSE crashes, it will create a core file in the directory syslog-ng OSE was started from.
To test that syslog-ng OSE can create a core file, you can create a crash manually. For this, determine the PID of syslog-ng OSE (for example, using the ps -All | grep syslog-ng command), then issue the following command: kill -ABRT <syslog-ng pid>

This should create a core file in the current working directory.