Starting Apache HTTPD Failed Due to Cannot Open or No Such mod_bwlimited, mod_log_bytes or mod_bandwidth Files

For web hosting account using cPanel with WebHost Manager (WHM) and running on Apache web server, the following error messages or problems may be encoutering with the Apache HTTPD server has been messed up with, some shared library files such as mod_auth_passthrough.so, mod_bwlimited.so and mod_log_bytes.so located in libexec directory accidentally been deleted, the compilation of web server gone bad, or re-configuration of Apache http.conf not properly does:

Sep 30 07:06:14 web httpd: Syntax error on line 233 of /usr/local/apache/conf/httpd.conf:
Sep 30 07:06:15 web httpd: Cannot load /usr/local/apache/libexec/mod_bwlimited.so into server: /usr/local/apache/libexec/mod_bwlimited.so: cannot open shared object file: No such file or directory
Sep 30 07:06:15 web rc: Starting httpd: failed

Sep 30 07:47:48 web httpd: Syntax error on line 234 of /usr/local/apache/conf/httpd.conf:
Sep 30 07:47:48 web httpd: Cannot load /usr/local/apache/libexec/mod_log_bytes.so into server: /usr/local/apache/libexec/mod_log_bytes.so: cannot open shared object file: No such file or directory
Sep 30 07:47:48 web rc: Starting httpd: failed

Invalid command ‘BytesLog’, perhaps mis-spelled or defined by a module not included in the server configuration

The problem with this kind of symptom is most likely due to the cause that the mod_belimited.so, mod_log_bytes.so, or mod_bandwidth.so are deleted or corrupted. These 3 files are unique to cPanel-powered web hosting service and are used to control, monitor or restrict the bandwidth usage limit.

The resolution and solution to the error is to recompile and redeploy the missing or unable to find shared library modules. You can easily compile these cPanel modules for Apache by using the following commands:

cd /usr/local/cpanel/apache
/usr/local/apache/bin/apxs -iac mod_log_bytes.c
/usr/local/apache/bin/apxs -iac mod_bwlimited.c
/usr/local/apache/bin/apxs -iac mod_bandwidth.c

After compilation, the .so files will automatically copied to libexec directory for Apache HTTPD web server.

Share and contribute or get technical support and help at My Digital Life Forums.



6 Responses to “Starting Apache HTTPD Failed Due to Cannot Open or No Such mod_bwlimited, mod_log_bytes or mod_bandwidth Files”

  1. Mark
    May 2nd, 2007 11:15
    1

    This helped me a lot, thank you. :)

  2. A_HAPPY_CHAP
    June 7th, 2007 22:03
    2

    /usr/local/apache/bin/apxs -iac mod_log_bytes.c

    thankyou so much for this!!! you saved me an even bigger headache than the one I was already having.

  3. Jayson
    June 10th, 2007 14:24
    3

    Thanks, was having the same error with BytesLog. This helped alot.

  4. Zanella
    June 13th, 2007 05:49
    4

    Same error here, you’re a time saver my friend, thanks.

  5. Ez
    July 15th, 2007 00:03
    5

    Thanks! You were right on the money.. fixed my problem.

  6. EricMMartin.com » Blog Archive » Shared object error during cPanel Apache build
    October 24th, 2007 13:15
    6

    [...] a Google search, I found that I needed to run: cd /usr/local/cpanel/apache   /usr/local/apache/bin/apxs -iac [...]

Leave a Reply

You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Subscribe without commenting


Custom Search

New Articles

Incoming Search Terms for the Article

apache unable to open logs - mod_bwlimited - httpd failed - mod_log_bytes - Unable to open logs - apache cannot open shared object file: No such file or directory - defined by a module not included in the server configuration - httpd unable to open logs - apache2 Unable to open logs - starting httpd failed - Starting httpd: [FAILED] - Starting web server (apache2)... failed! - apache unable to open logs vista - Invalid command 'Header', perhaps misspelled or defined by a module not included in the server configuration - "Invalid command 'Header', perhaps misspelled or defined by a module not included in the server configuration" - Unable to open logs apache - httpd failed. The error was: Starting httpd: [FAILED] - Invalid command 'Header' - Invalid command \'BytesLog\', perhaps mis-spelled or defined by a module not included in the server configuration - Unable to open logs failed! - mod_bwlimited.so - "Starting web server (apache2)... failed!" - Invalid command 'Header' apache - mod_bwlimited.c - apache byteslog - Starting web server (apache2)... failed! - apache error unable to open logs - Invalid command 'Header', perhaps mis-spelled or defined by a module not included in the server configuration - apache "unable to open logs" - apache module not included in the server configuration - unable to open log apache - Unable to open logs + httpd - apache vista unable to open logs - Invalid command \'BytesLog\' - Unable to open logs - apache Invalid command 'Header' - httpd failed - cannot open shared object file: No such file or directory apache - Starting httpd: [FAILED] - apache download fails file - starting apache - Invalid command 'Header', perhaps mis spelled or defined by a module not included in the server configuration - Invalid command 'Header', perhaps misspelled or defined - httpd failed - mod_bwlimited apache - apache unable to open logs windows - Unable to open logs apache windows - Invalid command 'Header', perhaps misspelled or defined by a module not included in the server configuration - Unable to open logs apache - apache will not start unable to open logs -