AWS EC2 Apache Load Balancer Issue - apache

We have 5 t2.medium instances on AWS, all the instances connect to MariaDB via RDS on a r4.xlarge instance.
The problem is that periodically the 5 instances suddenly stop working, Apache doesn't response anymore and we can't access via SSH.
We need to reboot all instances on the AWS Console to make them work again, the Load Balancer is an application lb, the server folder "/var/www" is on a EFS to share the project.
These are the images of the monitoring, we don't know why this happen so suddenly and how can we handle it.
The last issue was this morning the 5 instances stop working and the Load balancer to.
We share the monitoring of the last 12 hours.
Any advice?
Regards.

Related

Does EC2 Elastic Load Balancer remove the need for apache/nginx?

I am striving for a very simple cloud based architecture on Amazon AWS. I would like to have an app layer of several "elastic" EC2 instances where my application (and application servers) run, but I'm wondering what the load balancing will look like.
If I choose to use ELB, does it remove the need for Apache or Nginx?
No. All the loadbalancer does is just that, distributes load across instances. Whatever your stack is running on each instance will still need a nginx or apache or whatever service you want to respond back to the request routed through the load balancer.
I'm assuming you're running a web stack needing some type of server like nginx, apache, or java needing tomcat or something.
However, if you want AWS to take care of nginx and/or apache, look into running as a ElasticBeanstalk application: https://aws.amazon.com/elasticbeanstalk/

how to implement failover of apache httpd that is working as the loadbalancer for multiple tomcat instances

I am implementing almost 3 tomcat instances with the load balanced by apache httpd and mod_jk in on single machine. I also configured session affinity and session replication in the tomcat instances. So, even though, any one of the 3 tomcat instances goes down, there would be no worry.
But as I am balancing the load for 3 tomcat instances by a single apache httpd, if the apache httpd fails and if its service goes down, then it becomes again a single point of failure.
So, how to get rid of this problem? How can I do failover of the apache httpd which inturn works as the load balancer for multiple tomcats.
I have used cloud load balancers before (AWS). And they passed East US power failure. google

Weblogic load balancing and request re-routing to another server

I'm totally new to clustering and load balancing.
What I'm trying to do is "Deploy Application on a Cluster which contains 2 managed servers. Now, If one of the managed server goes down, request should be redirected to another server which is Up."
For Example:
I've 2 managed servers (M1:7021 and M2:7022)
And I've a Cluster C1 having M1 and M2.
And I've an Application App1 deployed on C1 and a Data Source deployed on C1.
Application App1 is working fine.
The way through which I'm accessing application is:
http://10.184.111.11:7021/App1/
AND
http://10.184.111.11:7022/App1/
Now, Suppose if M1(7021) goes down, and request is coming like
:7021/App1/
Then, it should be redirected to :7022/App1/
Any help is highly appreciated. Thanks!
I believe you will need a load balancer (or a software equivalent) to sit above the weblogic servers and direct traffic down to those servers.
The idea being that you access your application on http://loadBalancer.com/App and then the Load Balancer forwards your request onto either one of weblogic servers. Meanwhile in the background the load balancer is continually performing health checks on the two weblogic servers to see if they are running.
In the event that one of the weblogic servers go down, the load balancer will mark it as inactive and forward all traffic to the weblogic server still running. Once the failed weblogic server has come back online the load balancer will begin routing traffic back through it.
#Garreth Well, in fact WebLogic DOES provide an internal load balancer. You are supposed to use OHS or Apache for load balancing in production environments, but for development, httpclusterservlet works great.

Amazon EC2 ssh timeout

I am new to AWS services. I created an EC2 instance of Ubuntu and I was able to connect to it. I was able to run TeamCity and Rails server on the instance and things were fine. I created an image of the instance and now I can not ssh back.
Help is much appreciated. Thanks!
which country are you from? i know in china, the instances of ec2 cannot be connected unless you use a VPN tool.

Glassfish 3.1 loadbalancing setup

I am very new to server setup. I have a cluster with 2 instances in GF.
instance1:28081
instance2:28082
I am running my GF in Amazon Linux EC2 instance. What are the options to create a load balancer setup that directs traffic to these instances when I try to access my EC2 instance http 80 port?
1) Do I need to have a webserver to direct traffic to these instances?
2) Is there any options in Glass fish which can handle load balancing without a webserver on these instances? I couldn't find load balancing configuration on my admin console.
3) Is there a way to use Amazon Load balancing to distribute traffic to these cluster instances which resides in a single ec2 instance?
If some one can provide step by step instructions/link reference that would be helpful.
I did a nice write up on loadbalancing/failover and proxy options for GlassFish.
have a look: http://blog.eisele.net/2012/01/throwing-light-on-glassfish-webserver.html