Security Compliance

Serv-U logs incorrectly parsed by SEM

This article discusses how to resolve an issue when SEM can't parse Serv-U logs.

First published date

10/17/2018 3:18 PM

Last published date

5/7/2020 2:34 AM

Overview

This article describes how to resolve an issue when Security Event Manager (formerly Log & Event Manager) web console does not show any Serv-U connector logs, even though the connector is configured and started.

Product section

Security Event Manager

Cause

The issue is caused by either of the following:

There are spaces in log file name

- OR -

Incorrect date suffix format selected.

Resolution

The log path where SEM is supposed to read the logs is actually correct and it matched SEM log path location, but the format of the logs configured within Serv-U is not supported by SEM.

  1. Login to the Serv-U server and change the log format to match the SEM supported format as follows:

    How to enable log generation to a file
    1. Open the Serv-U Management Console.
    2. Navigate to Domain Activity, go to Settings.
    3. Check enable logging to file 
    4. Then browse the path location.
    5. Provide the name of the file you desired and make it .txt file extension.
        New File Name Interval: Monthly: yyyymmDD
        See example: Serv-U-log%Y%M%D.txt

     

  2. Conduct a test to verify SEM is to parsing the Serv-U logs.