14

Apache2 mod_proxy: backend servers log frontend server as source of all requests

view full story
linux-howto

http://serverfault.com – I have five servers running Ubuntu (LAMP). One of them (called Server1) receves all incomming requests from the internet, and uses VirtualHosts and mod_proxy to deliver the correct request to the correct server on the LAN. My problem is that in all the logs on my backend servers, all requests are logged as incomming from Server1's IP. Why is this, and how do I fix it? (HowTos)

dayu's picture
Submitted by dayu on 05/18/2012 – Made popular on 05/18/2012

Stories similar to Apache2 mod_proxy: backend servers log frontend server as source of all requests

I basically have the same problem as mentioned in this thread -- I would like to temporarily suspend all requests to all servers of a certain backend, so that I can upgrade the backend and the database it uses. Since this is a live system, I would like to queue up requests, and send them to the backend servers once they've been upgraded.

I hope this isn't too headache-inducing.

Two servers, server1 (Windows Server 2003, IP 192.168.100.25) and server2 (Windows Server 2008, IP 192.168.100.22).

server2 is the DHCP server and a DNS server.

I'm not sure if this is the right location, but this is fairly urgent. I have completely removed all traces of mod_proxy and the other mod_proxy mods, although the Apache server continues to allow proxy requests. I have restarted numerous times, and have shut down until I can find an answer.

I am using the heartbeat configuration on two of my servers as it is recommended The only difference is I am sending requests using ab command.

# ab -n 10000 -r http://"hostname"

initially requests goes to server 1 without ny prob bt once its heartbeat service is stopped, requests are lost and it takes about 4 min for the requests to be accepted by server 2.

meanwhile logs of ab command in verb

Efficient High-Available LoadBalanced Cluster On CentOS 5.3 (Direct Routing Method)

Possible Duplicate: FTP reverse proxying based on hostname/domain

I have 3 servers which all have FTP on the same port. They are all at the same ip address behind the same router. The router cannot port forward based on the domain requested, only the port.

Pound sits in front of HAProxy (on the same box) to perform SSL off-load. Requests are passed to 127.0.0.1:80 where HAProxy then balances the requests across backend servers for a hosted ASP .NET web app.

A user is getting HTTP error 500 (Internal Server Error) returned to their browser this morning and I can see it is comming from Pound.

I've a webapp deployed on tomcat server A, which is dependent on a couple of wars deployed on a different tomcat server B.

I have a Django app running under Apache2 and mod_wsgi and, unfortunately, lots of requests trying to use the server as a proxy.