Enabling Debug Logging

Procedure

1. Using a text editor such as vi, edit the following configuration files:

   WARNING Making incorrect changes to a configuration file can cause serious system errors. Back up tmsplx.xml and rsyslog.conf to restore your original settings. After modifying the rsyslog.conf file, restart the rsyslog service immediately before you continue.

   1. Edit tmsplx.xml to define the debug level for each debug parameter (UserDebugLevel and KernelDebugLevel).
   2. To assign the path and filename where ServerProtect will write debug logs, edit /etc/rsyslog.conf.
      See Configuring rsyslog for Linux
   • To direct all ServerProtect user debug logs to /path/splxUserDebug.log, include the following line in rsyslog.conf:
     local3.* /path/splxUserDebug.log
   • To direct ServerProtect kernel debug logs to /path/splxKernDebug.log, do the following:
     1. Open /etc/rsyslog.conf.
     2. For CentOS Linux and Red Hat Enterprise Linux, search for #$ModLoad imklog and delete the character # from the text.
     3. Add the following lines to the file:

        # this is for KHM debug log
        if $msg contains "SPLXMOD" and not($msg contains 
        "systemd-journal") then {
           action(type="omfile" 
        file="/path/splxKernDebug.log")
        }

2. Save and close the configuration file.
3. Restart rsyslog.
   service rsyslog restart

   Note To prevent Linux file operation errors, restart rsyslog before you restart the ServerProtect service.

4. Restart ServerProtect service:
   /etc/init.d/splx restart