• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Question ModSecurity: Failed to access DBM file "/var/asl/data/msa/ip": Permission denied

Richard18

Basic Pleskian
Plesk Onyx v17.8.11_build1708180301.19 os_Ubuntu 16.04

I've recently noticed the following in my modsec_audit.log:

Message: collection_store: Failed to access DBM file "/var/asl/data/msa/ip": Permission denied
Apache-Error: [file "apache2_util.c"] [line 273] [level 3] [client xxx.xxx.xxx.xxx] ModSecurity: collection_store: Failed to access DBM file "/var/asl/data/msa/ip": Permission denied [hostname "xxx"]

Is it something to worry about?

There is no /var/asl/data/msa/ip but there are two other ip files, /var/asl/data/msa/ip.dir and /var/asl/data/msa/ip.pag.
 
The permissions are incorrect and it was detected by our development team as a bug ( PPPM-6202 ).
The following article makes the reference for this issue - ModSecurity: Failed to access DBM file "/var/asl/data/msa/
You can change the permissions following the steps below:

# chown www-data.www-data /var/asl/data/msa
# chown www-data.www-data /var/asl/data/audit
# chown www-data.www-data /var/asl/data/suspicious
# chmod o-rx -R /var/asl/data/*
# chmod ug+rwx -R /var/asl/data/*

We also have an article that describes this issue - Errors in /var/log/modsec_audit.log: incorrect ModSecurity permissions
 
Back
Top