Well, I got a lot further this time, but still had an abort. I followed the instructions in the new readme file at:
https://github.com/pantheon-systems/mercury
Everything seemed to be going along fine until the script tried to upgrade the distribution. Here's the last few lines before abort:
[pantheon@localhost] Executing task 'initialize'
[localhost] run: mkdir /etc/pantheon
[localhost] run: curl http://pki.getpantheon.com | sudo tee /usr/share/ca-certificates/pantheon.crt
[localhost] run: echo "pantheon.crt" | sudo tee -a /etc/ca-certificates.conf
[localhost] run: sudo update-ca-certificates
[localhost] run: ln -s /usr/local/bin/fab /usr/bin/fab
[localhost] run: cp apt.pantheon.list /etc/apt/sources.list.d/pantheon.list
[localhost] run: cp apt.php.pin /etc/apt/preferences.d/php
[localhost] run: cp apt.openssh.pin /etc/apt/preferences.d/openssh
[localhost] run: apt-key add apt.ppakeys.txt
[localhost] run: echo 'APT::Install-Recommends "0";' >> /etc/apt/apt.conf
[localhost] run: apt-get -y update
[localhost] run: apt-get -y dist-upgradeFatal error: local() encountered an error (return code 100) while executing 'apt-get -y dist-upgrade'
Note that I'm installing to a standalone test server with Lucid and 1.2 gigs of memory.
Comments
Superuser?
It looks like several of these script commands omit sudo, which might cause them to fail. Should I be logged in as root before running setup.py?
I think you might want to
I think you might want to stay away from the so-called 1.2 as it's not really 1.2, it's running HEAD, and thats like trying to hit a moving target.
http://groups.drupal.org/node/113284#comment-362744
I know I was trying and just went back to 1.1
Yeah I've performed many
Yeah I've performed many successful 1.2 / TRUNK based builds but sometimes you have to dig into the code yourself and at this stage nobody is available to help for the most part - especially if you are at a relative beginner stage (e.g. yes of course you should be running from a fresh install of lucid and as root).
1.1 is recommended unless you can do 95% of your own support on the ever changing 1.2 branch and it works well.
IRC has been pretty good for
IRC has been pretty good for support though.
re: IRC has been pretty good for
pantheon on freenode.org is where the pantheon developers hangout. We're often idle, but are happy to help out if we're around.
Best to ask your questions and stick around for one of us to read it.
Greg
--
Greg Coit
Systems Administrator
http://www.chapterthree.com
Yes
setup.py assumes you are already root
https://pantheon.io | http://www.chapterthree.com | https://www.outlandishjosh.com
Tried that
I reinstalled a fresh copy of Lucid on my test server and reran setup.py after using "sudo -i" just to be sure I was seen as root the whole time.
I still error out every time at "apt-get -y dist-upgrade" the error says that dist-upgrade needs --force-yes as a parameter, so I manually ran it with --force-yes and the upgrade completed. I then tried commenting out the scripts that had run up to that point in setup.py and reran it. I got to the fab initialize stage and ran that manually, but then had problems after that. (I've forgotten what they were now)
Long story short, I gave up and went straight to Linode and installed my slice with the Mercury stackscript. Unfortunately, that failed as well. My server will not boot successfully. I'm starting to feel like an absolute moron. :-(
Are the necessary scripts and other uploads for prior Mercury versions still in place? Should the old Linode stackscript still work??
I'm at a loss now and really getting behind schedule on my launch! Any advice welcome!
Have you given 1.1 a go?
Have you given 1.1 a go? Install instructions are excellent, if somewhat lengthier. As a complete newbie to everything, |'_'| I had that running on Rackspace first time. I must find a better vertical smiley...
I second that. If you are
I second that. If you are getting behind on your project, are you sure you really want to be running 1.2 (bleeding edge)? There are plenty of us running 1.1 just fine.
Symetrik Design
Drupal Consulting
http://www.symetrkdesign.com
Gave up on 1.2 and went with 1.1
I got all excited because everything seemed to be going according to plan on my Linode slice, that is, until I accessed Hudson. It came up the first time and I ran Mercury init, but since then, I'm unable to access the Hudson console.
Am I just totally incompetent, or are there other problems? :-(
I have 1.1 on linode going
I have 1.1 on linode going just fine. Installed about a week or so ago. Should be fine.
re: Tried that
I suspect that the new install of Lucid included PHP 5.3. Since many Drupal modules still don't play well with PHP 5.3, Pantheon uses 5.2. If 5.3 is already installed, apt requires a --force-yes if the -y flag is being used and a downgrade is asked for.
Best to start with an install of Lucid that doesn't have PHP 5.3 installed.
Hope this helps,
Greg
--
Greg Coit
Systems Administrator
http://www.chapterthree.com
--force-yes issue
Not php 5.3 - it is downgrading the openssh server. No idea why!
Aruna
--force-yes issue
same on my server (which lucid do you use @Greg)