Apache 2.4 proxy_balancer and lbmethod_byrequest

apache-2.2apache-2.4

I'm trying to build my Apache server with static modules. But run into some problems with the proxy_balancer module. I get an error:

[ssl:info] [pid 11863] AH01876: mod_ssl/2.4.10 compiled against Server: Apache/2.4.10, Library: OpenSSL/1.0.1i
[proxy:crit] [pid 11868] AH02432: Cannot find LB Method: byrequests
[proxy_balancer:emerg] [pid 11868] (22)Invalid argument: AH01183: Cannot share balancer
[:emerg] [pid 11868] AH00020: Configuration Failed, exiting

When I look at the loaded modules using bin/apachectl -M there are no mod_lbmethod module there.

I've tryied to load the module by adding these lines to the configuration script --enable-lbmethod-byrequest and --with-lbmethod=byrequest but it does not show up in the modules list nor in the included folder.

Someone experienced this problem before and got a solution to it?

Best Answer

This can be resolved by enabling the module mod_lbmethod_byrequests, like so:

$ sudo a2enmod lbmethod_byrequests

This wasn't required in Apache 2.2.22, but is required by Apache 2.4

Related Solutions

Httpd – Error Start Apache “php value”

I recently ran into this exact problem using Plesk 9.5 on CentOS.

I cannot say for sure whether it was caused by an update to Plesk, or not. The customer doesn't think any changes were made recently, but Apache failed to start with this error.

After an assesment of the system to ensure it wasn't due to a breach, I did some troubleshooting and determined that mod_php had been removed from the Apache config. After checking Plesk settings, every vhost on the box was using FastCGI and SuExec.

When using FastCGI and SuExec, you cannot change PHP directives in php.conf (FastCGI) and .htaccess (SuExec).

The customer had originally commented out the offending lines, but this broke session support for everything. The only way I was able to resolve it was to manually add mod_php back to httpd.conf.

Add the following line to the section with the other LoadModule's. Make sure the path (../modules/) matches the rest of the modules in there. Chances are good that it already exists on your system and was simply removed from the config during the update.

bash# vi /etc/httpd/conf/httpd.conf
LoadModule php5_module ../modules/libphp5.so

bash# apachectl restart

This caught me off guard, and I cannot say for sure it is the upgrade that caused the issue or whether this is the best fix. I am open for comment, but highly advise against commenting out the php directives in /etc/httpd/conf.d/php.conf as it will break stuff.

Freebsd – How to get access to Icinga on Apache 2.4

The apache24 package on FreeBSD does not ship with the mod_dir. Check if it is present in /usr/local/libexec/apache24, and if not, install apache24 from ports. Add LoadModule dir_module libexec/apache24/mod_dir.so to your httpd.conf.

Best Answer

Related Solutions

Httpd – Error Start Apache “php value”

Freebsd – How to get access to Icinga on Apache 2.4

Related Topic