Event ID: 3299 is logged in application log after upgrade to SEP 12.1 RU6MP3
search cancel

Event ID: 3299 is logged in application log after upgrade to SEP 12.1 RU6MP3

book

Article ID: 164679

calendar_today

Updated On:

Products

Endpoint Protection

Issue/Introduction

Symantec Endpoint Protection Manager (SEPM) is upgraded from the previous version to RU6MP3, an error of event ID: 3299 is recorded in the application log when the web server is started up.

Log example:
Source: Apache Service
Event ID: 3299
Body: The Apache service named reported the following error: >>>
[Fri Jan 15 09: 33: 31.647060 2016] [so: warn] [pid 2884: tid 228] AH 0 1574: module Content_OutputFilterModule is already loaded, skipping

Cause

SEPM tries to load related modules as necessary at startup.

This event message means that skipping has been done to prevent double loading of already loaded modules.

It is considered that this event is likely to occur due to the fact that unnecessary settings are added at the time of version upgrade, and it is under investigation.

The same event also occurred after SEPM migration to 12.1 RU6 MP4 from pre-RU6 SEPM.

This event does not occur in the environment where SEPM 12.1 RU 6 MP3 or MP4 is fresh installed.

Resolution

Symantec is currently investigating this phenomenon and will update this document once we finish the investigation.

 

Workgroup:

Follow the steps below to avoid outputting this event by deleting duplicate settings from httpd.conf.

1. Back up httpd.conf under \ apache \ conf .

2. Stop SEPM and WEB service, and the services name as below:

Symantec Endpoint Protection Manager
Symantec Endpoint Protection Manager Web server

3. Open httpd.conf in a text editor and search with LoadModule Content_OutputFilterModule modules and put # in front of the second LoadModule Content_OutputFilterModule modules / mod_ContentOutputFilter.so.

[ Before Change]

#Content output filter for supporting content management(content storm)
LoadModule Content_OutputFilterModule modules/mod_ContentOutputFilter.so

  SetOutputFilter Content_HeaderOutputFilter

#Content output filter for supporting content management(content storm)
LoadModule Content_OutputFilterModule modules/mod_ContentOutputFilter.so

[After change]

#Content output filter for supporting content management(content storm)
LoadModule Content_OutputFilterModule modules/mod_ContentOutputFilter.so

  SetOutputFilter Content_HeaderOutputFilter

#Content output filter for supporting content management(content storm)
#LoadModule Content_OutputFilterModule modules/mod_ContentOutputFilter.so
 

4. Restart SEPM and WEB service.