Troubleshooting

This topic describes how to troubleshoot issues with the BMC Defender SyslogDefender product.

SyslogDefender is not receiving messages

After configuring the SyslogDefender program, the most likely reason for failing to receive messages is that a firewall has blocked the listener port.

The system administrator should verify that the Windows Advanced Firewall is configured and that no network-based firewall is blocking messages.

Troubleshooting tools

The following tools can help you troubleshoot issues with SyslogDefender.

Testing Listener or Output

To test any Listener or Output, the operator can click the Test option on the top-level window. This sends a test message. For Listener type configuration items, the message is sent to the listener in the appropriate format. For Output type configuration items, the message is sent in the format of the configured output. After sending a test message, the message might appear in the BMC Defender Server (depending on the configuration of the listener or output.).

Reviewing the Process Log

To troubleshoot issues with SyslogDefender, click the Process Log link at the top of the window and view the detailed statistics associated with the running process. This log file is updated at rates specified in the Advanced window of the system.

Running in Foreground mode

Finally, under extraordinary situations, it might be useful to run the SyslogDefender program in Foreground mode at the BMC Defender Server platform to view any special errors.

To run SyslogDefender in Foreground mode, first stop the SyslogDefender background process, and then launch SyslogDefender in an administrative prompt (at the BMC Defender Server) within the installationDirectory\SyslogDefender folder as follows:

When running at a command prompt, messages and error indications are displayed to standard output. Additionally, the s option displays running statistics and the q command executes an orderly shutdown of the program.