Views:
Modify tmsplx.xml and syslog.conf to enable ServerProtect debug logging.

Procedure

  1. Using a text editor such as vi, edit the following configuration files:
    WARNING
    WARNING
    Making incorrect changes to a configuration file can cause serious system errors. Back up tmsplx.xml and syslog.conf to restore your original settings. After modifying the syslog.conf file, restart the syslog 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/syslog.conf.
      See Configuring syslog-ng for SUSE Linux for more information.
    • To direct all ServerProtect user debug logs to /path/splx.log, include the following line in syslog.conf:
      local3.* /path/splxUserDebug.log
    • To direct ServerProtect kernel debug logs to /path/splxKernDebug.log, include the following line in syslog.conf:
      kern.debug /path/splxKernDebug.log
  2. Save and close the configuration file.
  3. Query PID.
    ps -ef | grep syslogd (CentOS4 or CentOS5)
    ps -ef | grep syslog-ng (SLES11 or SLED11)
  4. Reload configuration.
    kill -HUP <syslogd PID> (CentOS4 or CentOS5)
    kill -HUP <syslog-ng PID> (SLES11 or SLED11)
    Note
    Note
    To prevent Linux file operation errors, restart syslog before you restart the ServerProtect service.
  5. Restart ServerProtect service:
    /etc/init.d/splx restart