The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, admin@xxxx and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
In the error log:
[Mon Nov 23 16:10:05 2009] [notice] Child 7528: Exit event signaled. Child process is ending.
[Mon Nov 23 16:10:05 2009] [notice] Apache/2.2.14 (Win32) configured -- resuming normal operations
[Mon Nov 23 16:10:05 2009] [notice] Server built: Sep 28 2009 22:41:08
[Mon Nov 23 16:10:05 2009] [notice] Parent: Created child process 6468
[Mon Nov 23 16:10:06 2009] [notice] Child 6468: Child process is running
[Mon Nov 23 16:10:06 2009] [notice] Child 7528: Released the start mutex
[Mon Nov 23 16:10:06 2009] [notice] Child 6468: Acquired the start mutex.
[Mon Nov 23 16:10:06 2009] [notice] Child 6468: Starting 64 worker threads.
[Mon Nov 23 16:10:06 2009] [notice] Child 6468: Starting thread to listen on port 8005.
[Mon Nov 23 16:10:06 2009] [notice] Child 6468: Starting thread to listen on port 8003.
[Mon Nov 23 16:10:06 2009] [notice] Child 6468: Starting thread to listen on port 8001.
[Mon Nov 23 16:10:06 2009] [notice] Child 6468: Starting thread to listen on port 8004.
[Mon Nov 23 16:10:06 2009] [notice] Child 6468: Starting thread to listen on port 8002.
[Mon Nov 23 16:10:06 2009] [notice] Child 6468: Starting thread to listen on port 80.
[Mon Nov 23 16:10:07 2009] [notice] Child 7528: All worker threads have exited.
[Mon Nov 23 16:10:07 2009] [notice] Child 7528: Child process is exiting
[Mon Nov 23 16:10:10 2009] [warn] proxy: No protocol handler was valid for the URL /. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
[Mon Nov 23 16:10:11 2009] [warn] proxy: No protocol handler was valid for the URL /. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
[Mon Nov 23 16:10:11 2009] [warn] proxy: No protocol handler was valid for the URL /. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
[Mon Nov 23 16:10:11 2009] [warn] proxy: No protocol handler was valid for the URL /. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
I suspect you should be specifying things as follows:On Mon, 2009-11-23 at 15:57 +0200, Onur Ağın wrote:
> Hi,
>
>
> I am trying to define several load balancers each working on different
> ports on same apache http server.
> For example, calling the apache http server on 8001 should load
> balance on servers a and b, while calls made to port 8002 should be
> forwarded to c and d.
> How can I achieve this?
>
>
> Thanks...
>
>
>
>
>
>
> <Proxy http://127.0.0.1:8001/ >
> BalancerMember http://10.x.x.x:5101
> BalancerMember http://10.x.x.x:5102
> </Proxy>
>
>
> ProxyPass ????
>
>
> <Proxy http://127.0.0.1:8002/ >
>
>
> BalancerMember http://10.x.x.x:5103
> BalancerMember http://10.x.x.x:5104
> </Proxy>
>
>
>
>
> ProxyPass ???
<Proxy balancer://127.0.0.1:8001>
<Proxy balancer://127.0.0.1:8002>
<VirtualHost 0.0.0.0:8001>
ProxyPass / balancer://127.0.0.1:8001/
</VirtualHost>
<VirtualHost 0.0.0.0:8002>
ProxyPass / balancer://127.0.0.1:8002/
</VirtualHost>
Mark.
--
Mark Watts BSc RHCE MBCS
Senior Systems Engineer, Managed Services Manpower
www.QinetiQ.com
QinetiQ - Delivering customer-focused solutions
GPG Key: http://www.linux-corner.info/mwatts.gpg