lbmethod_heartbeat:notice - No slotmem from mod_heartmonitor --error after installing apache2.4.2 [closed]

Question

On starting the webserver the error_log shows

[Wed May 16 03:48:53.027372 2012] [lbmethod_heartbeat:notice] [pid 1114:tid 3075385024] AH02282: No slotmem from mod_heartmonitor
[Wed May 16 03:48:53.028312 2012] [mpm_event:notice] [pid 1114:tid 3075385024] AH00489: Apache/2.4.2 (Unix) configured -- resuming normal operations
[Wed May 16 03:48:53.028351 2012] [core:notice] [pid 1114:tid 3075385024] AH00094: Command line: '/usr/local/apache2/bin/httpd'

apache configuration:

# ./configure --prefix=/usr/local/apache2 --enable-mods-shared=all --enable-deflate --enable-proxy --enable-proxy-balancer --enable-proxy-http --with-included-apr

I am getting Forbidden You don't have permission to access / on this server error

This is the error generated in error_log

[Wed May 16 03:49:20.116317 2012] [authz_core:error] [pid 5015:tid 2946440000] [client 127.0.0.1:59386] AH01630: client denied by server configuration: /home/gowtham/webSites/ferry/

is this error because of lbmethod_heartbeat:notice ??

or there is a permissions misconfiguration on DocumentRoot directory?? but the directive's configuration is taken from a working webserver, so I think there r no mistakes in block. N i even tried giving

chown -R [apache_user:apache:group] /home/Necktwi/webSites/ferry 

and /home/Necktwi got chmod -R 766

thanq

Answer 1

These messages are unrelated. It is common to encounter the "AH02282: No slotmem from mod_heartmonitor" message (which is not actually an error) but still have a functioning server.

Usually, you can suppress that message by commenting out the heartbeat load-balancer method module from httpd.conf (unless, of course, you are actually using it). It has been suggested that this be disabled in the default configuration, but evidently it is not yet.

#LoadModule lbmethod_heartbeat_module modules/mod_lbmethod_heartbeat.so

It is possible that there is a problem with one of the authentication or authorization modules which is causing the server to deny requests. You might try disabling the modules beginning with "auth" in httpd.conf as well as any restrictions that you have in your configuration.