Posted by R-H on February 24, 2010 at 1:23am
Hello,
I tried to follow the install instructions and got stuck with this step
bzr branch lp:~pantheon-developers/projectmercury/bcfg2 /var/lib/bcfg2• First, I'm told Permission denied (publickey)
• If I generate a key with ssh-keygen and share that with Launchpad, then I'm told
bzr: ERROR: Not a branch: "bzr+ssh://bazaar.launchpad.net/~pantheon-developers/projectmercury/bcfg2/".
If anyone knows what's going on I would appreciate it.
Thanks
Comments
Bad Branch Path
It seems like the branch
bzr branch lp:~pantheon-developers/projectmercury/bcfg2 /var/lib/bcfg2is incorrect or out-dated.Anyone know what the correct branch is?
Thanks
I ran into this too .. the
I ran into this too .. the instructions are wrong.
...look around on bazaar http://bazaar.launchpad.net/~pantheon-developers/projectmercury/trunk/files
its in the trunk dir
~pantheon-developers/projectmercury/trunk/bcfg2
so the instructions should be to run this instead
bzr branch lp:~pantheon-developers/projectmercury/trunk/bcfg2 /var/lib/bcfg2
Please report back if you get the bcfg2 stuff to work .. ive failed every time so far, but im going to test it again soon I think.
Updated instructions posted
The instructions were incorrect - they've now been updated: http://groups.drupal.org/node/50408
Please let me know if there's anything in the instructions that aren't clear or are not working.
Thanks!
Greg
--
Greg Coit
Systems Administrator
http://www.chapterthree.com
Problem configuring the BCFG2 Server
Had a problem configuring the bcfg2 server. My EC2 instance freezes after
/etc/init.d/bcfg2-server start; tail -f /var/log/syslogI wasn't 100% sure about configuring the groups.xml file. Since I'm using a Ubuntu 9.04 jaunty Server, AMI (ami-0d729464) that is 32 bit on AWS and I want Mercury and BCFG2, I figured the default setting was correct.
<Group profile='true' public='true' default='true' name='mercury-ubuntu-jaunty-32'><Group name='ubuntu-jaunty'/>
<Group name='i386'/>
<Group name='amazon-web-services'/>
<Group name='mercury'/>
<Group name='bcfg2'/>
</Group>
My clients.xml file matches that
<Clients version="3.0"><Client profile="mercury-ubuntu-jaunty-32" pingable="Y" pingtime="0" name="ip-10-251-43-207.ec2.internal"/>
</Clients>
I figure that this is probably all good.
You can see the errors here: http://dpaste.com/165756/
Any thoughts?
More info
So, I tried to start up the BCFG2 server again and it appears to be running???
root@ip-10-251-43-207:/# /etc/init.d/bcfg2-server startStarting Configuration Management Server: * bcfg2-server
Any thoughts about what happened? How can I check if it is configured properly?
Thanks
Nothing's hanging
NyRy,
/etc/init.d/bcfg2-server start; tail -f /var/log/syslog is 2 commands:
/etc/init.d/bcfg2-server start
and
tail -f /var/log/syslog
the ";" tells your terminal to run the second command when the first command returns. In this case, bcfg2-server, being a service, returns immediately (even before it's done starting up). We then monitor the start up process using the tail command since bcfg2-server logs to syslog (the -f flag means follow and output appended data as the file grows).
The message "Feb 27 21:19:21 ip-10-251-43-207 bcfg2-server[6205]: serve_forever() [start]" is your indication that the server is ready. But you're still viewing /var/log/syslog using tail - so just control-c that and you're ready to run the next command: bcfg2-vq
Oh, and if you are installing on an Ubunty Jaunty 32-bit server on AWS, then the groups.xml files is already set up for you.
Hope this helps,
Greg
--
Greg Coit
Systems Administrator
http://www.chapterthree.com
Few more issues
Hey,
Was able to get Mercury installed with BCFG2 using the wiki instructions. I do have a few status message warnings now in Pressflow.
Site is unable to connect to Solr
• Host: localhost
• Port: 8180
• Path: /solr
Permissions errors
• sites/default should be non-writable
• sites/default/settings.php should be non-writable
I was able to change the permissions, but thought you might like to know.
I've corrected the permissions errors, not sure why that happened. Did anyone else have this?
Not sure what I need to do to get the server to see Solr.
I've also updated the wiki. Might be helpful if someone takes a look.
Re: Few more issues
NyRy,
Not sure whey you're site's unable to see solr - settings are correct. Is tomcat running on that server?
The permission errors occur because the sites/default and sites/default/settings.php have to be writable when you install pressflow, but it's safest to remove write acess after pressflow is installed. Pressflow should have told you during the install to remove write access once it was safe to do so.
Hope this helps,
Greg
--
Greg Coit
Systems Administrator
http://www.chapterthree.com
re: solr errors
NyRy,
I just had a thought. In solr section of the instructions:
wget http://people.apache.org/builds/lucene/solr/nightly/solr-
date +%Y-%m-%d.tgztar xvzf solr-
date +%Y-%m-%d.tgzsolr won't install if http://people.apache.org/builds/lucene/solr/nightly/solr-
date +%Y-%m-%d.tgz doesn't exists - ie: if, say, http://people.apache.org/builds/lucene/solr/nightly/solr-2010-03-01.tgz hasn't been built yet.Do you have a /var/solr? if not, re-run the following commands (making sure the first 2 run - if not then go to http://people.apache.org/builds/lucene/solr/nightly/ and get the latest nightly build):
wget http://people.apache.org/builds/lucene/solr/nightly/solr-
date +%Y-%m-%d.tgztar xvzf solr-
date +%Y-%m-%d.tgzmv apache-solr-1.5-dev/example/solr /var/
mv apache-solr-1.5-dev/dist/apache-solr-1.5-dev.war /var/solr/solr.war
chown -R tomcat6:root /var/solr/
drush dl --destination=/var/www/sites/all/modules apachesolr
svn checkout -r22 http://solr-php-client.googlecode.com/svn/trunk/ /var/www/sites/all/modules/apachesolr/SolrPhpClient
mv /var/www/sites/all/modules/apachesolr/schema.xml /var/solr/conf/
mv /var/www/sites/all/modules/apachesolr/solrconfig.xml /var/solr/conf/
Hope this helps,
Greg
--
Greg Coit
Systems Administrator
http://www.chapterthree.com