The new forum

[Peter Anderson]

Can someone check the address of the new forum, just to make it easy for folks to get there?  Here's the one I have:

http://ec2-204-236-213-121.compute-1.amazonaws.com/index.php


Not sure it's right.

Pete

[Dave Webb]

http://ec2-204-236-213-121.compute-1.amazonaws.com/index.php

Yes thats right Pete

Dave

[ronnydw]

Anybody knows what happened with this forum ? Cannot be found anymore since today:
no response from server ec2-204-236-213-121.compute-1.amazonaws.com

[Peter Cawthron]

Hello All,

We are now on: ec2-107-20-111-208.compute-1.amazonaws.com

Something odd going on here so any advice would be appreciated:

I got up this morning to find the server could not be accessed. Ping didn't work although it usually does, so things like SSH obviously didn't work either.

I rebooted the server - no change. I stopped and the server - no change. I've been out for a couple of hours and now the server has a new name/IP address as above.

We are running a 'micro' EC2 server instance. I know that if I temporarily switch to a larger 'standard' instance - to install MySQL for example - then I get a new name/IP address, and then yet another one when I switch back to the free 'micro' instance. But I haven't done that since installation on Sunday.

Regards,

Peter

--
You received this message because you are subscribed to the Google Groups "talibpython" group.
To post to this group, send email to talib...@googlegroups.com.
 
 

[Peter Cawthron]

...stopped and started...

[Jose Guedez]

Hi Peter,

To avoid this issue you need to allocate and assign a AWS "Elastic IP" to the server instance, you do this on the AWS console. That essentially assigns a fixed IP address to the server. The idea is that you can dynamically assign it to other server instances, but for the current purposes it's ok assigning it permanently.

If you don't assign a Elastic IP, everytime you stop and start the server a new IP will be assigned automatically (you cannot get a previous address back)

You can find more details here: http://www.newvem.com/elastic-ip-how-to-allocate-new-elastic-ip/

Let me know if you have any questions.

[Peter Cawthron]

Thanks, Jose.

Can you or anyone else advise here, please?

AmazonEC2,CreateSnapshot,EBS:SnapshotUsage,,12/02/12 00:00:00,12/03/12 00:00:00,42908597352

AmazonEC2,CreateVolume,EBS:VolumeUsage,,12/03/12 00:00:00,12/04/12 00:00:00,206158430208

I read those numbers as 42Gb and 20Gb. But the instance is 8Gb as is the snapshot:

P.

[Jose Guedez]

Hi Peter,

Where did those numbers come from? Without more information I would think that those are not "storage" numbers but "IO usage" (i.e. data transfer). See the following link for an example (https://forums.aws.amazon.com/thread.jspa?threadID=41971)

I think you mentioned spinning up and down several types of instances in an earlier post. The charges might be due to the creation/deletion of EBS volumes and reading the snapshots - when you are creating the new servers.

JG

[Ronny De Winter]

fyi forum is unreachable again

Ronny De Winter
http://www.linkedin.com/in/ronnydewinter
http://www.5consulting.com

[Dave Webb]

Thanks Ronny

Peter is working on setting a nonelastic IP so it doesn't keep changing on us.- the joys of technology :)

Will advise.

Dave

[Peter Cawthron]

Hi Jose,

This is from the EC2 billing summary for this month, see attached. I'm getting billed about $0.12 a day at present but I'm not sure why. Is the snapshot chargeable? Will the Elastic IP be chargeable? This is all new to me.

P.

[Jose Guedez]

Hi Peter,

Were you creating new instances/volumes over those days, EBS:VolumeUsage shows up under the operation "CreateVolume", that should only happen when you create a new EBS volume (i.e. a new virtual "hard drive").

I have a EC2 micro instance on the free tier, it's been running for almost a year now with no issues. A couple of time I've gotten charges for a couple of cents, but only when I've run some cpu intensive calculations. I would think that for this forum you should be well within the free usage limits.

My advice would be to monitor the usage over a couple of days of the same instance running (no new instances, upgrades, etc.), the "create volume" charge should go away.

JG

P.S. I am assuming you did not activate some auto-snapshot feature (although the snapshots are incremental, they only store the changes)