Apache may experience issues to load apache modules
configured . The error log will contain the information indicating the
issue. In such cases, make sure the .so file of the module is present
in the correct location and it is accessible. If the location is correct
check whether the module has any issues. You can check it using the
command “ldd”
A sample output would look like this
root@redhat003 [/usr/local/apache/modules]# ls./ httpd.exp ../ mod_hostinglimits.so* mod_security2.so
To check whether the module is configured correctly, you can evaluate it using ldd
root@redhat003 [/usr/local/apache/modules]# ldd mod_security2.so
linux-vdso.so.1 => (0x00007fff143fc000)
libpcre.so.0 => /opt/pcre/lib/libpcre.so.0 (0x00002b5d10fae000)
libxml2.so.2 => /opt/xml2/lib/libxml2.so.2 (0x00002b5d111ea000)
libz.so.1 => /lib64/libz.so.1 (0x00002b5d1153c000)
libm.so.6 => /lib64/libm.so.6 (0x00002b5d11750000)
liblua-5.1.3.so => /opt/lua/lib/liblua-5.1.3.so (0x00002b5d119d4000)
libc.so.6 => /lib64/libc.so.6 (0x00002b5d11bfd000)
libdl.so.2 => /lib64/libdl.so.2 (0x00002b5d11f54000)
/lib64/ld-linux-x86-64.so.2 (0x00000034e9400000)
Syntax Errors
Also the server restart may fail if any syntax errors are present. In such cases, check the syntax using the command
#httpd -t
Disk Space
#df -h
#df -hi
No comments:
Post a Comment