The Aegir project is proud to announce the eighth alpha of our 0.4 release cycle. Adrian and Neil have been working like crazy on the also crazy multi-server developpment branch(es) for a while and they are getting stable enough so that we can merge with the master development branch. Not stable enough, however, to not warrant a nice and routine release for you people to bundle the quiet but stable fixes we have been doing during that time. So here's the last release before we go on the multi-server development spree for good.
This release focuses on stability and bug fixes but also introduces the "rename site" functionality.
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-alpha7, 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.
We also highly recommend you use the latest stable drush release, 3.0 as of this writing.
Backend changes and fixes:
- fix for #767568 on drupal 7 - install_mail function can't find custom welcome mail
- #772616, include the rewrite above the default drupal one. Also wrap backupmigrate rewrite in IfModule tags
- dispatcher fixes to improved reliability under heavy load and lots of tasks
- do not start more than N tasks at a time
- #500362 - don't run queue if it's already running
- avoid the "always queued task" phenomenon that would happen when a task was killed before execution under high load
- we do not manage or touch site-specific packages anymore, which should ease upgrades
Frontend changes and fixes:
- site rename support
- #783808 by cap10morgan - OSX install hints
- count and display the number of sites per platform
- #814368, #814356 - fix warnings occuring in E_ALL environments
- #599790 by q0rban - fix CSS for views
- #761498 - fix 5.3 warning in hook_load
- #752076 by ivanbueno - expose hosting_site.status as a filter for views
- #599758 - allow main aegir site node to be editable
Comments
We love you.
We love you.
++
++
Well done guys
Aegir's a great system. Well done getting another release out.
All seems to have gone well, mostly
But I did have to do what someone else had to do for alpha7:
mkdir /var/aegir/config/apache.d/Otherwise I got this:
Web server could not be restarted. Changes might not be available [error]until this has been done. (error: apache2: Syntax error on line 282
of /etc/apache2/apache2.conf: Syntax error on line 17 of
/var/aegir/config/apache.conf: Could not open configuration file
/var/aegir/config/apache.d/: No such file or directory)
An error occurred at function : [error]
drush_provision_apache_provision_verify
Web server could not be restarted. Changes might not be available [error]
until this has been done. (error: apache2: Syntax error on line 282
of /etc/apache2/apache2.conf: Syntax error on line 17 of
/var/aegir/config/apache.conf: Could not open configuration file
/var/aegir/config/apache.d/: No such file or directory)
An error occurred at function : [error]
drush_provision_apache_provision_verify
Web server could not be restarted. Changes might not be available [error]
until this has been done. (error: <em>apache2: Syntax error on line
282 of /etc/apache2/apache2.conf: Syntax error on line 17 of
/var/aegir/config/apache.conf: Could not open configuration file
/var/aegir/config/apache.d/: No such file or directory</em>)
An error occurred at function : [error]
drush_provision_apache_provision_verify
An error occurred at function : [error]
drush_provision_hostmaster_migrate_validate
That step is covered in the
That step is covered in the UPGRADE.txt. Were you upgrading? You did RTFM, right? :)
If you weren't upgrading, you used some old install.sh script. The install.sh script in alpha7 and alpha8 automatically. makes that directory.
Read the manual?
Now why would I do that? My apologies, I do see that at the end now. I was going off of my notes for the alpha 7 upgrade and the instructions "looked" the same, but I see you fixed it even in the alpha7 instructions by now.
Congrats!
on the new release of what has become an cornerstone of Drupal good practices.
A little remark : I believe that in the UPGRADE.TXT file :
export AEGIR_VERSION=HEAD
should be
export AEGIR_VERSION=0.4-alpha8
Best,
Jun.
Good catch. This version tag
Good catch. This version tag (there are many we change in various places when making a new release) must've been forgotten.
Indeed I did... I fixed the
Indeed I did... I fixed the release process to incorporate that, hopefully we'll stop forgetting all those bits one day...
http://groups.drupal.org/node/17634
While I'm at it...
I always get carried away when upgrading and forget to change this line:
$DRUSH hostmaster-migrate aegir.example.com $DRUPAL_DIR
how about an
export AEGIR_URL = aegir.example.com
and replacing with:
$DRUSH hostmaster-migrate $AEGIR_URL $DRUPAL_DIR
What do you think?
Jun.
Good idea! I just committed
Good idea! I just committed that change to git.
Thanks :)
Some trouble with a fresh install on a BSD
Hello all
I wanted to follow the evolution of aegir and decided to upgrade from scratch (re install) one of my FreeBSD install.
Except the fact that PDO is required now and is not bundled with PhP on the FreeBSD package system (maybe the PDO requirement should be in the install/upgrade stuff), the preparation went mostly fine.
I am tripped by this line :
Shell commands::su -s /bin/sh aegir -c "sh install.sh.txt"
[...]
Note you must run this as root or prefix with sudo.
I don't get what the third word "aegir" (user ? group ? ) is supposed to do in linux, and so I don't know how to translate it in BSD.
I also don't follow the logic because the install.sh script refuse to run as root
==> Aegir automated install script==> This script should be ran as a non-root user
but the su command purpose seem to be just that ;)
I suppose the "aegir" is the user name and supposed to be some gnu/linux trickery about running as root but with ownership of files to the aegir user or something like that.
Running the script as the aegir user fails like this
The external command could not be executed due to an application error. [error]
chgrp(): Operation not permitted provision.file.inc:212 [warning]
Could not change group ownership of /var/aegir/hostmaster-HEAD/sites/aegir.assemblee-nationale.fr/settings.php to nogroup (chgrp to [warning]
nogroup failed on /var/aegir/hostmaster-HEAD/sites/aegir.assemblee-nationale.fr/settings.php)
Drush command could not be completed. [error]
Output from failed command : [error]
An error occurred at function : drush_provision_hostmaster_install [error]
[aegir@DrupalDev ~]$
It is quite often that aegir command fails on chown/chmod commands probably because BSD and GNU ways of managing permission varies (sticky bit meaning and setting mostly I think ), maybe such things should not be failures but warning with a big nice message saying the intend like "you MUST set the right so that only the user WWW can write to and this file should only belong to group XXX".
I know the FreeBSD is not a major platform, I just wanted to report the experience in case it helps make the code more generic/robust.
Sorry if it is not the place to report such things but I did not know where to fill "bug/support request" for the global install of the AEgir system (provision ? hosting ? ).
Thanks a lot for your work.
Did you get this resolved?
Hi there,
I realise this is going back a while, but I've hit a simiar problem with MacOSX when trying to migrate a site from one platform to another.
The migration fails, and the same error is displayed in the log.
Almost certainly some permissions issue, but I'm unable to resolve it as of now.
Regards
Alan
site rename support I LOVE
I LOVE YOU GUYS!!!! LOL!!
Easy upgrade with one minor suggestion
Thanks guys. I'll contribute when I can.
There is one improvement with the documentation that will make life less trippy for some.
In the UPGRADE.txt, might I suggest that you also include in the "shell environment variables" section the following:
And then later, when upgrading the front end:
The documentation seems to get me in the momentum of copy-paste since 95% of the variables are set up top. Then this one line has tripped me up during two different upgrades now.
I've probably learned my lesson (one can never be too sure), but it may trip others up, and it's good practice to have all of the variables at the top anyways.
Thanks again!
Yep, this has been raised
Yep, this has been raised a few comments earlier in this thread, and the UPGRADE.txt has been updated to make that a variable. (so the next release will have it included)
See the change in the version currently in the master branch
Cheers!
Did I succeed?
Soooo anyway ...
I believe that I successfully updated from Alpha7 to Alpha8 BUT I can't see the site rename function.
Everything works but no joy with Drupal 7 Alpha 6.
Some warning re revoking permissions or privileges after running (from /var/aegir/hostmaster-0.4-alpha6) "drush hostmaster-migrate subdomain.domain.com /var/aegir/hostmaster-0.4-alpha8. (And yes, I did use an actual domain name).
Any assistance will be greatly appreciated. Melbourne-based successful assistance usually results in gift of fancy beer (or similar tipple).
:) S.
ps: Linode - Ubuntu Server 9.1
Stewart, I believe you've
Stewart,
I believe you've unfortunately been bitten by the bug in UPGRADE.txt which states to set 'AEGIR_VERSION=HEAD'. meaning you've accidentally ended up upgrading to HEAD.
See the earlier comment where a user spotted this.
In HEAD, the 'Rename' feature has been merged into the 'Migrate' feature. So you can now 'Migrate' your site to the same platform and change its name in the process (where earlier you could not change the name).
This is the most likely reason for why you aren't seeing it - you're on the bleeding edge codebase :/ sorry about that.
Now that that's the case, I suggest simply leaving it as is and waiting til 0.4 alpha9 is released - you're practically on the codebase for alpha9 now anyway (and you can officially 'upgrade' to it later and get back on track)
Re: Drupal 7 - no idea, but I'm also not surprised if it doesn't work. Drupal 7 is a moving target and Aegir doesn't always work with it, however you might have more luck with an earlier alpha or even bleeding edge from cvs.
However if you try again and provide some more specific errors, it can be looked at (could even be a bug in Aegir, but if it only occurs on Drupal 7 I doubt it and suspect just another incompatability with the latest changes in d7)
Thanks Miguel
Appreciate your taking the time to clarify my situation.
I'm sure this will assist others in similar situation to myself.
Thanks again,
:) S.
I don't see a site re-name
I don't see a site re-name function actually, which is kinda weird.
What is your problem with 7a6? I tried creating a site yesterday which died with something like "The profile your have chosen (standard) is not available" or similar. I tried again and it worked.
Me neither
No site rename Feature is available to me (and no option is available in site management).
Letharion, was yours an upgrade or fresh install?
Re D7a6 ... it was late and I had a few wines to get through the tedium ... Sorry but I don't recall the specific issue, BUT it was different to yours. I couldn't create a site. I'll check it out again and report the specifics.
:) S.
Disabled by default?
Check that the feature is enabled - I believe the feature is disabled by default on upgrades (it is on my upgraded instance). Go to Hosting->Features in the admin menu and check if it is enabled - if not tick the checkbox and submit to save. Cannot add anything after this as I have not tried it yet..
HTH ;).
JamieT
New install or upgrade?
Hey JamieT,
I did an upgrade ... I don't have the feature option.
Just following a hunch .. was your's a fresh install?
Also, which OS are you using?
Cheers mate,
:) S.
Upgraded from alpha 7
I upgraded from alpha 7 - not sure if that helps or not?
Check your module page (site building->modules) under hosting group and make sure package management is checked and there is a site rename module there - however this may not enable correctly as it is not through the hosting menu ymmv?
HTH?
JamieT