I've been running mercury for a year on a small amazon instance. Performance wasnt great so I decided today to move it to a large instance, which is quite a step up.
I started with a fresh Ubuntu 10.04 and installed Apache, Varnish, Memcache, etc. I moved my database over and pointed the IP at the new instance. The site shows up and Varnish is working, but no matter what url I goto it shows me the main page of my website.
I cant log into the site as it only shows me the front page, but using the command line I can see that memcache seems to be causing trouble. Its showing "Memcache::connect(): Can't connect to 127.0.0.1:11217, Connection refused"
I have added the needed code to php.ini. I think I tracked the error down to the fact that in the original mercury the init.d script started 9 instances of memcache, so I copied the init.d script to the new server and also the corasponding /etc/memcached_*.conf files.
I noticed though, that on the old server when I bring memcache up using init.d it loads fine, but on the new server it says "memcache is already running" when it starts to load more than one instance.
Does anyone know how I can fix this?
Comments
Well it seems like Mercury
Well it seems like Mercury doesnt have the thunder it did about a year ago. It's really too bad. This place used to be alive and full of excitement. Guess its time to move back to vanilla Drupal
Did you try spinning up one
Did you try spinning up one of the pre-configured ami's?
I use a customized mercury 1.0 since its a solid start.
pantheon-amis-us-east/mercury-pressflow-drupal-64-1.0.manifest.xml
Search for Mercury in the Amazon EC2 management console, in the launch instance area.... By starting here your tweaks and configurations begin from a fully functioning instance.... its a nice shortcut IMO.
My customized 1.0 (large instance) has been running for well over a year now flawlessly, I added aegir and other goodies to fit my use.
Once you spin up an instance you should be able to move the database & webroot to external volumes (hd's) then do apt-get updates etc and finally bring in your old content.
well .. let me take that back
well .. let me take that back .. you probably shouldn't use the 1.0 since its ubuntu 9.04 and is no longer supported by ubuntu, just follow the best practices guides and setup your own from scratch using the latest Long Term Support version of ubuntu or whatever linux you'd like.
I tried doing this same thing
I tried doing this same thing awhile back. It was a huge headache. I agree. You shouldn't use the 1.0. It is best to start from scratch or use an amazon alternative.