Need help?

Our experts have had an average response time of 13.52 minutes in October 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

ModSecurity failed to open the audit log file – How to fix

by | Mar 3, 2021

Wondering how to fix the error ‘ModSecurity failed to open the audit log file’? Here is how we fix it.

Generally, this error can occur due to various reasons that include missing log files or due to improper permissions set for the log files.

Here at Bobcares, we have seen several such ModSecurity errors as part of our Server Management Services for web hosts, cPanel users, and online service providers.

Today we will take a look at the causes for this error and see how to fix it.


How we fix the error ‘ModSecurity failed to open the audit log file’

Now let’s take a look at how our Support Engineers fix this error.


1. Missing log files

Recently, one of our customers came across an error message while running the SSH terminal. The Apache wasn’t starting. Here is the error message he received.

AH00526: Syntax error on line 12 of /etc/apache2/conf.d/modsec2.conf:
ModSecurity: Failed to open the audit log file: /etc/apache2/logs/modsec_audit.log

This error here clearly says that the log files are missing.

Sometimes, customers might delete the log files unknowingly from /etc/apache2/logs/ or /usr/local/apache/logs. So this error can occur.

So, we manually create the log files. Here is the command for it.

touch /etc/apache2/logs/error_log
touch /etc/apache2/logs/modsec_audit.log

After that, we ensure that the permissions are set properly. For that, we run the below commands.

chmod 0644 /etc/apache2/logs/error_log
chmod 0600 /etc/apache2/logs/modsec_audit.log

The modsec log files are assigned 0600 permissions by default, whereas the error_log is assigned 0644 permissions by default.

This resolved the error message.


2. SecAuditLogType

SecAuditLogType configures the type of audit logging mechanism to be used. This has 2 possible values, they are:

  • Serial – all audit log entries saves in the main audit logging file.
  • Concurrent – audit log entries saves in separate files, one for each transaction.

So, we suggest our customers set the value of SecAuditLogType is to Serial. Else, if Concurrent is set then we suggest creating the directory for saving concurrent logs.

[Need any further assistance in fixing ModSecurity errors? – We are here to help you.]



In short, this error ‘ModSecurity failed to open the audit log file’ can occur due to missing log files or due to improper permissions. Today, we saw how our Support Engineers resolve this error.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *


Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.