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.

This entry was posted on Wednesday, February 14th, 2007 at 2:35 am and is filed under Webmaster Resources. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

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

  1. 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 [...]

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

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

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

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

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

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

  5. 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.

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

    This helped me a lot, thank you. :)

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 to comments feature has been disabled. To receive notification of latest comments posted, subscribe to My Digital Life Comments RSS feed or register to receive new comments in daily email digest.
« Free Download: Preview Handler Association Editor to Group Same Type of File with Different Extensions
Trend Micro PC-cillin Internet Security 2007 Beta for Windows Vista Free Download »

New Articles

Incoming Search Terms for the Article

starting httpd failed - mod_bwlimited - cannot access org.apache.http.message.AbstractHttpMessage - defined by a module not included in the server configuration - cannot open shared object file apache - apache cannot open shared object file no such file or directory - mod_bwlimited configuration - Apache php libgds.so: cannot open shared object file - apache2 mod_bandwidth install - download mod_log_bytes.c - Apache2 mod_bwlimited downloads - mod_bwlimited.so - mod_auth_passthrough on cpanel - request operation has failed - Apache cannot open shared object file: No such file or directory - apache cannot open shared object file - Invalid command 'Header', perhaps misspelled or defined by a module not included in the server configuration - starting httpd fail - apache cannot open shared object file: - Apache module mod_auth_passthrough - Starting httpd: [FAILED] - windows apache 2.2 mysql extension requested operation failed - apache wont load after vista update - apache : cannot open shared object file: - apache2.2 the required operation is failed - Apache 2.2 windows vista the requested operation has failed - apache tomocat cannot open shared object file: Permission denied - starting web server: apache2 failed - "request operation has failed" error when restarting apache - apache the requsted operation has failed - apache the request operation is failed - cpanel httpd failed - debian apache2 symfony .htaccess: Invalid command 'Header' - httpd failed in cpanel - httpd failed on cpanel - httpd failed to restart + solution - httpd failed - Invalid command 'BytesLog', perhaps misspelled or defined by a module not included in the server configuration - Starting httpd: [FAILED] - the request operation failed in apache 2.2 - apache conf directory requested operation failed - Cannot open source file: '.\lib\Fmusic.c': No such file or directory - apache "windows 7" php "requested operation failed" - Invalid command 'Header', perhaps mis-spelled 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 failed! - mod_auth_passthrough - apache the request operation failed - cpanel problem by httpd failed - apache mod_bwlimited - mod_bwlimited error -