You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MODSEC-278: When using ModSecurity with a per-user request handling module such as MPM-ITK or mod_ruid2, geoiplookup will not be able to lock the proc mutex and thus fail to do the lookup:
Message: Geo Lookup: Failed to lock proc mutex: Permission denied
Vhosts/directories that do not have a specific user assigned, but rather the 'global' httpd user, do not get this error message.
The text was updated successfully, but these errors were encountered:
lb06: FYI: A workaround is possible using libapache2-mod-geoip. This module populates the ENV variables with GEO* data. You can then perform GEO lookups using SecRule ENV:GEOIP_* rather than with GEO:*.
MODSEC-278: When using ModSecurity with a per-user request handling module such as MPM-ITK or mod_ruid2, geoiplookup will not be able to lock the proc mutex and thus fail to do the lookup:
Message: Geo Lookup: Failed to lock proc mutex: Permission denied
Vhosts/directories that do not have a specific user assigned, but rather the 'global' httpd user, do not get this error message.
The text was updated successfully, but these errors were encountered: