Aegir 0.4 Alpha 12 released
Just in time for our drupalcon presentation, the aegir project would like to present our 0.4 alpha 12 release.
This release was primarily about cleaning up file permission problems related to the last fixes, and also improving our views 2 support. We as usual bundle a bunch of bugfixes and a few new features.
Features :
#454452 : tasks can now be canceled before they are picked up by the queue dispatcher
#715482 : Keep other values of db_url when specified as an array
#537032 : SSL wildcard and multi-domain certificate support (n to n)
#666898 : Allow user to specify db name suggestion - db names are automatically generated from the site name now
Bugs fixed :
#859120 : receipt file in /var/aegir/config/server_master/ssl.d not removed blocks re-assigning ssl for another domain
#874286 : aegir remote server mysql passwords not allowed to have apostrophe
#884538 : Cloning a non-english site results in an english site
#610912 : Changes to file download method (public/private downloads) not supported
#883412 : Confusing Create Site form and broken Signup form
#880660 : Error during upgrade from 0.4-alpha9 to 0.4-alpha10
#882210 : Parameter 1 to hosting_site_nodeapi_site_presave() expected to be a reference
#882558 : Provision-save segmentation fault when migrating sites between drupal 6.17 to 6.19 in Aegir alpha 11
#881342 : Issues with upgrade from alpha9 to alpha10
#824346 : Import of sites does not work with the new drush call mechanism.
#840474 : Platform fails to verify if there's a space at the end of the path. Validate platform form.
#724472 : Backup task fails when MySQL password requires urlencoding
--
The Aegir Project
Installing and upgrading :
The canonical source of installation documentation is as usual the excellent INSTALL.txt. We have an automated and scripted upgrade process for the front end, which you can read more about in UPGRADE.txt.
For those updating from before 0.4-alpha8, please note that there are instructions at the bottom of the UPGRADE.txt for you. This obviously also applies to people upgrading from 0.3.
NOTE REGARDING SSL: If you had the SSL module/hosting feature installed that was included in 0.4 Alpha 8, you need to disable it first before attempting an upgrade.
This release also requires fixes that are only present in the 3.3 release of Drush. The install script will automatically fetch the correct release of Drush for you, but you need to upgrade Drush manually when upgrading Aegir.
great
just did the update from 11 to 12 and all is working ;p
thanks
Upgrade from alpha8 fails
Hi,
I tried upgrading from 8 to 11, but it failed (see my last post: http://groups.drupal.org/node/86604#comment-273169). When trying to upgrade to alpha12 I get the same error messages.
A few questions regarding the workings of aegir:
Is the server configuration supposed to be in ~/config or in ~/config/server_master/apache (where ~/ is the aegir home)? In alpha8 the config is in ~/config, but the upgrades alters the paths in ~/config/apache.conf to ~/config/server_master/apache and creates three empty folders there (sites.d, platform.d and conf.d), thus disabling my already hosted sites. Maybe this is intentional and the sites would be reenabled if the upgrade eventually completes?
Is there supposed to be a settings.php file in hostmaster-$AEGIR_VERSION/sites/default? My aegir site is in hostmaster-$AEGIR_VERSION/sites/aegir.example.com, but the upgrade throws an error about not being able to ind a settings.php file in ./sites/default.
Thanks
ulrikls: I have the exact
ulrikls:
I have the exact same issue as you trying to go from alpha8 to alpha11 last week - which got borked during the migrate which meant I had to scramble and move/copy some .conf files to make the websites available again.
I haven't had cron since then either since it got wiped out and not put back in
trying to do the alpha12 upgrade results in same issue as you mention too.
I've tried everything and looked in every file possible.
I almost am at the point of archiving all the files and doing a fresh install instead.
Last night I decided to
Last night I decided to backup the config directory, the old hostmaster directory, and the not used yet new hostmaster directory.
Then ran the install.sh script and everything went fine on install and importing all platforms and sites.
Wish I had just done that 2 weeks ago when the upgrade issue started.
When I upgrade from beta 8 to beta 12
When I upgrade from beta8 to beta11 and from beta8 to beta12 I get the same error:
http://drupal.org/node/883688#comment-3377870
When I setup beta8, I setup aegir_root with a password.
When the upgrade script runs for beta12, it gives me another password. Am i supposed to reset my aegir_root password to this new value? Is it done automatically?
I ask because on both beta11 and 12, the error stems from not being able to connect to the database.
(yes I performed all the directions at the end of the upgrade file prior to these errors and posting this message).
Edit:
It does create the correct aegir_root entries for localhost, fqdn, and ip address.
I did additional trouble shooting here. The hostmaster install script was returning "site_test" instead of the aegir_host. I am hoping this will help others find the cause
http://drupal.org/node/895806#comment-3381952
Social Niche Guru
New platform... "does not contain a valid Drupal installation"
I'm using
aegir/hostmaster-0.4-alpha12installed fresh from http://www.linode.com/stackscripts/view/?StackScriptID=1027 and haven't managed to verify any new platforms. For example I thought I was doing the right thing using drush to download drupal...root@aegir:/var/aegir/platforms# drush dlProject drupal (6.19) downloaded to [success]
/var/aegir/platforms/drupal-6.19/.
and yet upon creating a platform with the path
platforms/drupal-6.19I always get...The directory drupal-6.19 does not contain a valid Drupal installationDrupal sites directory drupal-6.19/sites is not writable by the provisioning script
...help?
It looks like you are running
It looks like you are running drush as root user which means the directory downloaded under /var/aegir/platforms is going to be owned by root which is why the provision script cannot read it as it expects it to be owned by the aegir_user (defaults to aegir). You can confirm this as follows (do this as root):
cd /var/aegir/platformsls-al
Check the owner / group of the download drupal directory if it is root root then do the following as root user:
chown -R aegir.aegir drupal-6.19This assumes that aegir is your aegir_user. Now verify the platform and you should be good to go.
Next time you want to create a platform with drush (or drush make) switch to the aegir user first and then run the commands and the permissions should be all set.
Hope that helps.
JamieT
Aegir alias command
I use an alias command to make switching to the Aegir user easier, since it doesn't have a shell associated with it by default. Simply add the line below to your /etc/profile or ~/.bash_aliases. Login and logout of your session or source the file you've added the alias to. Then you can switch to the Aegir user by just typing "aegir" (without quotes).
alias aegir="sudo su -l -s /bin/bash aegir"Thank you
Many thanks jamiet and timwood, that did the trick, cheers!
Same problem, ownership right
Hello:
I had the exact identical issue with a newly alpha 14 installed. I did as you suggested - up and down all the directories- and the files ownership are all correct: Everything belongs to user "aegir". I even checked with the original hostmaster files to compare and everything is the same across the board.
Any ideas of what else can this be?
EDIT: Never-embarrassing-mind. I am not even going to say what was actually wrong because I chance ridicule from all. (Watch you paste, watch your paste!!)...
I did a completely new server
I did a completely new server install but finally got 12 working.
When I goto create a site, it asks for both the platform and the install profile.
If I select, the install profile, the the platform is not changed.
Is this a bug or a feature?
Social Niche Guru
Problems upgrading from alpha 6
Hi there!
First off, thank you for your amazing work with Ægir! :D
Second, I'm having serious trouble upgrading our ægir server from alpha6.
I've been trying for two days now but I can't seem to find the solution. I'd be eternally grateful if anyone could help :)
So I started with the bottom of the UPGRADE.txt file.
- /etc/host looks like this
127.0.0.1 localhost aegir.mydomain.com
- I've commented out bind-address in my.cnf
- I've done the changes to the apache configuration files
I then upgrade the backend without problems.
It's when I run:
$DRUSH hostmaster-migrate $AEGIR_DOMAIN $DRUPAL_DIRI get errors.Prepending --debug gives me:
Running: /var/aegir/drush/drush.php --old_uri='aegir.mydomain.com' @hostmaster provision-deploy '/var/aegir/backups/aegir.mydomain.com-20100908.083126.tar.gz' --backend [58.53 sec, [command] 9.37 MB]The external command could not be executed due to an application error. [58.53 sec, 9.38 MB] [error]
An error occurred at function : drush_provision_drupal_provision_migrate [58.53 sec, 9.38 MB] [error]
I tried upgrading to alpha 7 and got no further but the error I get is instead:
Failed to extract the contents of /var/aegir/backups/aegir.mydomain.com-20100908.080453.tar.gz (The target directory could not be written to) [18.67 sec, 7.86 MB] [error]If i chmod the backups dir with 777 I still get the error (yes, I'm running this as the aegir user) and after running the script the permission changes has been reverted.
I've got a live site running Ægir with ~600 sites and working bulk migration would be really nice! ;)
Alright. You need to have
Alright. You need to have more then 32M memory_limit in your /etc/php5/cli/php.ini
Thank you mig5 for helping me! :)