I have heard people say "oh that server is off the load balancer so you can run that expensive script on it".
What implications does a server off the load balancer have? Fundamental to answering this, I understand load balancing, but I don't know what the dynamics of a system with 5 servers (4 on the load balancer) has.
Thanks
We are using aws load-balancer. There is one machine which is behind the load balancer. So for this reason we have configured apache2.conf such that %h are replaced by %{X-Forwarded-For}i in our file.
But something wired is happening. We can't see any ip of the client in the logs section.
But when we change back from %{X-Forwarded-For}i to %h all client ip's are visible in the log section.
I am going to host few servers (MS-Windows) listening on certain port to which my clients would connect. I will have to have a load balancer to distribute connections amongst these servers. I have gathered knowledge about load balancer's and have learned few things. But I am not sure if my understanding is correct. Hence, sharing it here so that someone experienced can please verify the same?
When ever I try to load test a site that is load balanced on EC2 I get the following message:
ab -n 20 -c 20 http://www.somesite.com/
Benchmarking www.somesite.com (be patient)...Send request failed!
apr_socket_recv: Connection reset by peer (54)
Any sites that are hosted on EC2 without the load balancer can be load tested successfully, so I figure it's not related to the security group I have
If I set up a load balancer on aws that terminates ssl at the load balancer, then the requests being sent to the application server is in plain text. That has definite security implications. How do folks mitigate this implication in practice?
If alternatively, I set up https traffic between load balancer and the application servers also, what are the performance implications?
I generally understand the problems that a load balancer poses for Kerberos. In fact, Microsoft's KB article outright states that it's not possible. However, this article - also on an MS site - suggests that there are possible workarounds.
Has anyone configured a system to use Kerberos and a load balancer? Did you need to use a Forefront server?
We have a aws load balancer. The load balancer uses the TCP connections 443 to encrypt the data.
Since the load balancer encrypts the IP of the client, in our apache log file we can see only the IP of the load balancer rather then the client. Even though we have used %{X-Forwarded-For}i in our log format.
Is there any way to handle this issue?
When I try to use curl (or wget, lynx, etc) to connect from a server on our local network to our website, which is on a local server behind a CoyotePoint load balancer, curl fails. Ping does not have this problem.
When I curl directly to any of the servers behind that load balancer (from and to the same local network), I also have no problem.
I have a basic ASP.NET application that sits behind an F5 load-balancer.
Incoming SSL requests (over HTTPS) terminate at the load-balancer and all internal communication between the load-balancer and my application servers is unsecure (over HTTP).
When a unsecure request comes in, my app is able to use Response.Redirect("https://...") to redirect a secure URL with no problems.
Email this page
