Tag Info

New answers tagged

0

most likely that item is updated not that often and values are not included in one hour graph (default period). try to increase the displayed period.


1

Monitor it like any other server (Nagios, opennms etc). The output of top etc. will be specific to your container, rather than the hypervisor. As for the second part of your question; that is personal preference. I would not personally set up alerting based off CPU load, as it does not definitively indicate a problem.


1

I am copying some sentences from http://httpd.apache.org/docs/current/misc/perf-tuning.html : The single biggest hardware issue affecting webserver performance is RAM. A webserver should never ever have to swap, as swapping increases the latency of each request beyond a point that users consider "fast enough". This causes users to hit stop and reload, ...


0

You just need to change this line: "SecurityGroups" : [ {"Ref" : "WebServerSecurityGroup"} ], to this: "SecurityGroupIds" : [ {"Ref" : "WebServerSecurityGroup"} ], Per the Cloudformation documentation on the topic, the SecurityGroups attribute is only valid for EC2 security groups. You're using VPC, so you need to use SecurityGroupIds.


0

When you delete any EBS snapshot, if there's a later snapshot for the same volume, every block in the first snapshot that wasn't included in the later snapshot (because it didn't change) is logically rolled forward (in a sense) into the later snapshot, so the later snapshot is still perfectly valid when any or all earlier snapshots are deleted. ...


1

Instead of AutoScaling based on CPU try Server Load. AWS AutoScaling can operate on any CloudWatch metric, and you can write your own custom CloudWatch metrics. More Information on how AutoScaling works: http://docs.aws.amazon.com/AutoScaling/latest/DeveloperGuide/as-scale-based-on-demand.html Creating a custom metric ...


0

You can set that command in /etc/rc.local. Modify rc.local in your image, so that it consists of something along these lines: #!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just ...


-2

We had same problem, below command I use for getting internal IP of ELB "LAMP-Prod" aws ec2 describe-network-interfaces --filters "Name=description,Values=ELB LAMP-Prod" |grep -wE 'Description|PrivateIpAddress'


1

The Private IP is not accessible from outside the AWS network and is only useful when you have a cluster of EC2 instances for communication between them with-in your security group. You could assign a Elastic IP to the instance or use a Dynamic DNS Solution.


1

You have to use a Dynamic DNS solution for this. You could use a DNS provider or configure your own Dynamic DNS server (there are a lot of tutorials for this). There are also scripts for using Route53 for this.


1

Also make sure Route table of VPC is set to enable IP address outside the VPC (0.0.0.0/0) to flow from the subnet to the Internet gateway. Navigate to VPC > Route Tables ; Route tab. Check Destination is 'mapped' to Target Internet Gateway Id (apart from local).


1

You should create your CSR using your own domain name for the Common Name. If you're planning to run your website on https://www.example.com, use www.example.com for the Common Name. (ie, include the www). Otherwise, folks will have to access your website by visiting: https://ec2-xx-xxx-xx-xxx.compute-1.amazonaws.com Which is probably not what you want. ...


0

The error message: IOError: failed to write data generally indicates that the HTTP client communicating with your web site is dropping the connection. One would normally only see it if you are using mod_wsgi embedded mode. It is usually a transient issue and should not be a permanent issue. If it is a permanent issue and your site is no longer accepting ...


0

Check to see if there's a local firewall running on the host that would block such things as ICMP and other traffic. Is UFW, IPTables or something else contributing to this issue?


1

Here are some options you have: Startup logs: There is a possibility to check the systems status by looking into the startup logs. If some process crashes during startup, it can cause the system to become unreachable. Elastic IP: Did you give the instance an external IP? VPC: If your instance is in another zone, it can be that the subnet of that zone does ...


0

The solution I use for blocking realtime bad activity IP's coming out of AWS and others is this... In my CSF Firewall in the config for LFD Blocklists I use a list found here - http://myip.ms/browse/blacklist/Blacklist_IP_Blacklist_IP_Addresses_Live_Database_Real-time Download Blacklist for CSF Firewall ยป ...


1

Looking at the Hortonworks Sandbox installation requirements, this runs inside a virtual machine - you can choose the virtual machine to run it on from VMWare, Hyper-V and VirtualBox. Which means the answer from Michael Hampton is correct - this isn't going to work on your Amazon instance. The good news is that from the looks of it you can run this from most ...


4

Your Amazon EC2 instance is itself a virtual machine, and there is no "BIOS" in the way you mean. And Amazon doesn't support any form of accelerated nested virtualization. This means, among other things, that you cannot use VirtualBox inside an EC2 instance to run 64-bit guests. (You could in theory run 32-bit guests unaccelerated, but it would be painfully ...


0

You need to look in /var/log/apache2/error_log (or wherever your apache error log is configured to go) It will tell you in there what the actual problem is. A problem which arises over time, and is solved by an apache and/or mysql restart could be something memory/resource related. I guess memory is the most obvious, but that's speculation.


0

Presumming you are talking about the ssh host key (and not keys for user accounts). I suppose it depends on how the installation was performed. Most Linux systems will generate new ssh host keys when sshd is initially started. Interesting in that I thought these keys were in a specific file and not contained in any log file. Perhaps the ssh package was ...


0

The Ubuntu HVM AMIs are out now, it is ami-0307d674 and they are marked as free tier.


0

Closing this because it was 3 years ago and I don't remember the final solution.


0

From the logs above you are connecting to an Ubuntu machine: debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3p1 Debian-3ubuntu7 Therefore the default username for that box will be ubuntu, not ec2-user which is only for Amazon Linux.


0

Amazon let you create alarms for 1 minute period even if you do not have detailed monitoring enabled but there is no data for 4 minutes. If you see the CloudWatch console, your alarm should be in Insufficient state for 4 minutes and change into OK every 5th minute. So you will be all good if you just change period to 5 minutes or maybe enable detailed ...


0

I have figured out how to solve my problem. The answer by Andrew Lusk pointed me to the right direction. However, my current environment makes me prefer a GUI option versus the command line one. But, he is incorrect in stating that GUI console option doesn't exist for creating a new AMI from an EBS snapshot. I have researched a little bit more and found that ...


1

It sounds like you want to make a new AMI from an EBS snapshot. The console doesn't let you do this; you should use the command line tools. http://docs.aws.amazon.com/AWSEC2/latest/CommandLineReference/ApiReference-cmd-RegisterImage.html You want 'ec2-register -s snap-XXXXXXXX'.


1

Just create a new securitygroup with 5432 as inbound TCP connection and replace current security group on your RDS instance with the newly created one.


1

Is that something you would recommend? Sure, if it makes sense for your situation. what are the pros and cons? You could save money by hosting multiple websites on one server. One server also acts as a single point of failure. You'll also lose the ability to scale the websites independently. Can you recommend the best approach to configure AWS to ...


0

Try changing the nfs in the mount command to nfs4. NFS v3 and earlier depend on many daemons and port mappings in order to work correctly. NFSv4 just needs the nfsd and port 2049/tcp. About the *, just substitute it with the ip address of the client instances. If you have more than 1, just add them like: /mount/point ip1(options1) ip2(options2) ...


0

Your netstat -tulpn | grep :80 command clearly shows that you have a service already listening on port 80 : tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN - tcp 0 0 :::80 :::* LISTEN - Identify this service by running : sudo netstat -anp | grep :80 ...


0

I found CentOS 5 HVM AMI in one of AWS regions and converted my image using method similar to http://www.nixhat.com/2014/01/migrate-aws-pv-to-hvm-instance, i.e. by cloning my "/" to HVM AMI.


0

If your VPC EC2 instances are in private subnets, then to access EC2-Classic, your VPC will need a NAT. Give your NAT an elastic IP address so it's a constant public IP address. Then in your RDS security group, allow access only for that Elastic IP address. If your VPC EC2 instances are in public subnets, then you could give each of them elastic IP ...


6

You want to setup NTP. See: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-time.html Extra content here.


3

I just became aware of this question, so I thought I'd chime in. I'm an engineer with Chef who has looked into this issue. The accepted answer on this is the correct way you can get around this issue. Note that following the accepted answer will also allow you to reconfigures and keep the setting the same, since that is an issue in another one of the ...


1

If you can't telnet to port 9000 on the master from the slaves(and the error is connection timed out), then it's most likely a firewall issue. Check that the ec2 instances are in the same ec2 security group, and that there's no iptables firewall rules active blocking the connections(you can check this by running iptables -vnxL).


1

Assuming you're running Apache 2, your /etc/apache2/ directory should have a sites-available directory inside of it. This is where you want to configure your sites. You'll create a file for each of your sites that looks something like this: NameVirtualHost *:80 <VirtualHost *:80> ServerName xxx.com ServerAlias www.xxx.com ServerAdmin my ...


2

Are us-east-1a, us-east-1b, and us-east-1d considered one or three availability zone? Three AZs within one region. Say I have two instances within us-east-1a, one has a mongodb server, the other has a nodejs app. Do I need to add permissions for port 27017 (mongodb) to the security group for the app server to connect to the mongo server? ...


0

Can you please paste your backup.conf and slave.conf files? Also, you should check these two articles: http://www.trk7.com/blog/keepalived-instance-not-entering-failed-state/ or http://comments.gmane.org/gmane.linux.keepalived.devel/4102 ?


3

As recommended in sysadmin1138's answer, these kind of situations are why VPCs were added to Amazon Web Services: so you can have a private intranet between EC2 instances. In my opinion, that's part one of the solution: put your database server in a VPC with your application server and only allow access to the database server from the internal ...


2

include(../scripts/connect.php) Your script is using a relative directory. These are linked to the current working directory. When cron is running your CWD is almost certainly not what you think it is. Either set the CWD in your cron script, or update your PHP code to use use a path relative to themselves. Something like ...


6

Using a VPC will solve a lot of your problems, as private IP addresses will be static there. Amazon is strongly encouraging people to move to VPC for reasons like this. Once you have one, your two systems should be able to talk over the AWS-internal network. To answer your question about exposure along the aws-public <---> aws-public route, it is ...


1

it's likely that your server has been compromised, so do your due diligence to check this out. start a packet capture so you can determine the nature of the traffic. If you determine that the server was compromised, you may be able to work with AWS support to get the charges reversed.


1

It turns out ufw disable doesn't actually turn iptables rules off. I had this line in my iptables: REJECT all -- anywhere anywhere reject-with icmp-host-prohibited and this prevented the appended ACCEPT lines to be ignored. I added the iptables -I INPUT -i eth0 -p tcp -m tcp --dport 3306 -j ACCEPT line with -I instead of -A ...


1

You don't have permission to create this directory. You have many possibilities to solve that, but anyways you need to get root access (either by the sudo bash or by the su commands, or by ssh-ing into them with root. You need the root password for all of them.) The best were to create the directory for your project in /var/www/html with the mkdir ...


3

You can use sudo command or sudo su for root access in Amazon ssh. Try sudo mkdir prestashoptest or use sudo su followed by the password for ec2-user and perform the simply mkdir


0

After adding the --subnet attribute with the default subnetid of that region and adding --server-connect-attribute public_ip_address, its possible to create instances with eip assigned. knife ec2 server create -N test-eip -I ami-e7b8c0d7 --security-group-id sg-685a00d -f m3.medium --region us-west-2 --ssh-user ubuntu -S testKey -i key.pem --associate-eip ...


4

Ping uses the ICMP protocol, not TCP. Routing tables are not involved in intra-subnet communication, unless you meant security groups.


0

The problem seemed to be generating from the path name of the EC2 key pair in the ssh command of step 10. My key pair was on desktop. So earlier, I tried executing the ssh command from the HOME$ prompt and mentioned the pathname of key pair file in the ssh command of step 10 of the instructions as '/desktop/key-pair-filename.pem', and it dint work. But ...


1

If you're using micro or small instances, mysql database running websites can can put a pretty big load on your VMs memory which will end up constantly crashing your mysql server. Consider using RDS which might be more expensive or at least ec2 t2.medium to save money and still run fine. For IPs, you'd have to allocate your instance elastic IP which will ...


0

Following @Osterjour suggestion, I asked Amazon to restore my default VPC and then created the instance from the AMI



Top 50 recent answers are included