AMI issue with mercury-pressflow-drupal-lucid-64-1.1-Beta2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
DEPRECATED Pantheon |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I fired up AMI ID ami-554aa33c today on a large instance, which is mercury-
ubuntu@
+ [ -e /etc/mercury/incep ]
+
+ cd /var/www/
+ bzr merge --force
+ exec
Merging from remembered parent location http://
bzr: ERROR: exceptions.
*** Bazaar has encountered an internal error. This probably indicates a
bug in Bazaar. You can help us fix it by filing a bug report at
https:/
attaching the crash file
and including a description of the problem.
The crash file is plain text and you can inspect or edit it to remove
private information.
+ cd /var/lib/bcfg2
+ bzr merge --force
Merging from remembered parent location http://
bzr: ERROR: Branches have no common ancestor, and no merge base revision was specified.
+ /etc/init.
Stopping Configuration Management Server: * bcfg2-server
Starting Configuration Management Server: * bcfg2-server
+ netstat -atn
+ grep :6789
+ [ -z ]
+ sleep 5
+ netstat -atn
+ grep :6789
+ [ -z tcp 0 0 0.0.0.0:6789 0.0.0.0:* LISTEN ]
+ echo 1 minute: BCFG2 is loading packages and config files
1 minute: BCFG2 is loading packages and config files
+ sleep 60
+ bcfg2-admin xcmd Packages.Refresh
+ bcfg2 -vqe
Server failure: The read operation timed out
Failed to download probes from bcfg2
The read operation timed out
+ /etc/init.d/varnish stop
* Stopping HTTP accelerator
...fail!
+ ls /etc/mercury/
+ bash /etc/mercury/
mv: cannot move `/var/log/mysql' to `/mnt/mysql/log': No such file or directory
ln: creating symbolic link `/var/log/
mv: cannot move `/var/lib/mysql' to `/mnt/mysql/lib': No such file or directory
ln: creating symbolic link `/var/lib/
mv: cannot move `/var/lib/varnish' to `/mnt/varnish/lib': No such file or directory
ln: creating symbolic link `/var/lib/
chown: cannot access `/mnt/varnish/
chmod: cannot access `/etc/init.
+ bash /etc/mercury/
* Stopping Postfix Mail Transport Agent postfix
...done.
* Starting Postfix Mail Transport Agent postfix
...done.
+ /etc/init.d/mysql start
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service mysql start
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the start(8) utility, e.g. start mysql
+ /etc/init.d/varnish start
* Starting HTTP accelerator
...fail!
Error: (-sfile) "/var/lib/
+ echo create database pantheon;
+ mysql -u root
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/
+ date
+ echo Mon Jul 19 21:19:01 UTC 2010
+ echo
#######
# Mercury Setup Complete! #
#######
#######
# Mercury Setup Complete! #
#######
+ wall
+ echo
DEAR SYSADMIN: MERCURY IS READY FOR YOU NOW
Do not forget the README.txt, CHANGELOG.txt and docs!
I'm unable to reproduce this error. On both the 32 and 64 bit version of the Mercury 1.1 Beta 2 (ami-294aa340 and ami-554aa33c), the init script runs fine except for this line (which is related to http:// groups. drupal. org/node/ 80324):
Merging from remembered parent location http:// bazaar. launchpad. net/~pantheon- developers/ pantheon/ 1.1/
bzr: ERROR: Branches have no common ancestor, and no merge base revision was specified.
The solution to this error is:
/etc/init. d/bcfg2- server stop \"3.0\" >\n</Clients> " | sudo tee -a /var/lib/ bcfg2/Metadata/ clients. xml d/bcfg2- server start; tail -f /var/log/syslog
sudo rm -rf /var/lib/bcfg2/
sudo bzr branch lp:pantheon/1.1 /var/lib/bcfg2
echo -e "<Clients version=
sudo /etc/init.
sudo bcfg2 -vqed
As for errors reported by init.sh on your server, i think they are caused by the second instance of init.sh being started while the original (system started) init.sh was still running.
Changing to invalid.