Security Compliance

Configure Apache Error log connector in SEM

This article briefly describes steps to configure and troubleshoot Apache Error log connectors in SEM.

First published date

11/5/2018 10:05 PM

Last published date

8/1/2023 1:33 AM

Overview

This article describes steps to configure and troubleshoot the Apache Error log connector in SolarWinds Security Event Manager (formerly Log & Event Manager).

Product section

Security Event Manager

Resolution

Configure the connector

  1. Install SEM agent on the Server running Apache Web server and ensure the Agent service is running.

  2. Get the absolute path for the Apache error_log file (the file name can be different for Debian/Redhat Distros).

  3. On the SEM web console toolbar, navigate to Manage > Nodes.
    - OR-
    In the HTML5 console, click the Nodes tab.
  4. Configure the Apache Error Connector on the Agent node, and then set the path with the exact. For example: /var/log/httpd/error_log on CentOS7.x and /var/log/apache2/error_log on Debian.
  5. Save the changes and start the connectors as shown below.

    Flash console

    HTML5 console

     

Note: The connector works for any Linux or Windows-based Apache Web server installation, as long as the correct path is configured and has permissions to read the error_log file by the user account running the SWSEM-agent service.

Troubleshooting

The connector is configured, but Apache Error logs are not appearing in SEM web console.

  • Make sure the connector is referring to the correct file name and the path is the absolute path for error_log.

  • Make sure the connector is not out of date. If necessary, apply the latest connector update either manually or automatically via the SEM web console.

  • Check permissions on the error_log file and make sure the user running SEM agent service has read access to the file.

  • In some cases, deleting and re-adding works.