Amazon Web Services (S3, EC2)

I need to reinstall Mercury but I fortunately had migrated mysql to an ebs volume. How would I reconnect to the mysql from Mercury?

Drupal is also telling me that APC is capable of displaying upload progress, but it's not enable.

I added apc.rfc1867 = 1 at the end of the following files, but that didn't seem to fix the problem:

./etc/php5/apache2/php.ini
./etc/php5/cli/php.ini

Is it possible to enable Upload Progress through APC?

DRUPAL STATUS REPORT MESSAGE

Upload Progress Not enabled

Can someone please provide some instruction for how to move the db to an ebs?

Assuming:

1. Create an EBS
2. Move db from usr/share/mysql to ebs
3. Update location in settings.php

Anything else?

Thanks!

Hello,

AWS shut down my instance's mail sending abilities after they noticed that my instance was sending too many emails. I spoke with their support team and they confirmed that to avoid possible spam my instance was stopped from emailing. Does anyone have any ideas what could be causing that? I haven't shared my password key with anyone. It's stored locally on my computer. Outside of the Mercury AMI nothing else was installed. My mail.log file has a bunch of activity. Here's some for log entries:

I'm having a problem with sites/default/files.

I have permissions set to 775.

If I recall I copied this directory from my previous server using the Mac Finder.

Any ideas what's going on?

Hello,

I've managed to authenticate. My first missteps were not understanding that ports 80 and 22 had to be open. I get the concept but for a non-sysadmin I assumed the EC2 defaults for Security Groups would be set to work automatically. I did finally manage to get to root using Terminal though once these ports were open.

Since I prefer a GUI I'm now trying to get past having to use Terminal on the Mac, but I can't really find a Mac SSH client that works with EC2's private keys. They all want me to authenticate with a username/pw.

Mercury 0.71-Beta has been released with small bugfixes (see https://bugs.launchpad.net/projectmercury for details).

AMI IDs are:

US 32-bit: ami-bd7c9fd4 - chapter3-storage/PANTHEON-pressflow-mercury-0.71-Beta.manifest.xml
US 64-bit: ami-b17c9fd8 - chapter3-storage/PANTHEON-pressflow-mercury64-0.71-Beta.manifest.xml
EU 32-bit: ami-8f2c07fb - chapter3-storage-europe/PANTHEON-pressflow-mercury-0.71-Beta.manifest.xml
EU 64-bit: ami-73230807 - chapter3-storage-europe/PANTHEON-pressflow-mercury64-0.71-Beta.manifest.xml

Once you've followed the steps outlined for installing your site on Mercury you'll then want to take your site to the next level using Elastic Block Store. This is going to keep your MySQL database(s) persistent should your server instance crash. Also make it easy to replicate data for testing etc.

There's a good generic Amazon doc page on this here.

Step 1 - Collect the necessary data

Note the following:

<

ul>

My name is Greg Coit, sysadmin for Chapter 3 and I've been helping with Mercury development and testing.

We wanted a get a quick idea of how hard we could push mercury under more "real world" circumstances, so I combined siege and ab to generate a broad spectrum of hits. ab (short for apache benchmark and part of the apache2-utils package) allows you to generate a very large number of hits on one url, while siege (a perl script which comes in a self-titled debian/ubuntu package) lets you spread the hits across many urls, most of which won't be cached. This mixed-load is a much more nuanced and accurate way of looking at performance than peak throughput on a single url.