Aegir cron queue not running. How to fix?
Hi,
Aegir task cron runs as expected.
But individual site crons are not running.
I looked at my setup under hosting >queues
while my takss queue runs as expected my cron queue has not run for several weeks.
How can I force this to happen?
su - aegir
crontab -e
SHELL=/bin/bash
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
*/1 * * * * /usr/bin/php /var/aegir/drush/drush.php --php=/usr/bin/php '@hostmaster' hosting-dispatchI tried per troubleshooting instructions to reset cron:
alpha6 upgrade - site migration problems.. error in drush_provision_drupal_provision_migrate
alpha6, drupal 6.15
Just upgraded, had to modify aegir.make to use drupal 6.15 and used vset to get verify to work
when attempting site migration, here is what i get:
Status: Failed
Executed: Tue, 04/13/2010 - 01:29
Execution time: 41 sec
Log message
Task starts processing
Running: /var/aegir/drush/drush.php --root='/var/aegir/atrium-1-0-beta3-1' provision-migrate 'intranet.mysite.ca' '/var/aegir/atrium-1-0-beta6' --backend
Drush bootstrap phase : _drush_bootstrap_drush()
Drush bootstrap phase : _drush_bootstrap_drupal_root()
WSOD on verification page: Cant access settings.php file pr db variables
I click on verification and get this:
Warning: include_once(./sites/aegir.example.com/settings.php) [function.include-once]: failed to open stream: Permission denied in /private/var/aegir/hostmaster-HEAD/includes/bootstrap.inc on line 322
It is set to 440
user: aegir
owner: aegir
group: _www (on a mac)
I am using hostmaster-HEAD btw.
I see that /var/aegir/config/vhost.d/aegir.example.com_80 is there and the variables are set
I changed the settings.php permissions to 444 and got:
Read more
Aegir 0.2 released.
We're proud to announce the final 0.2 release of the Aegir hosting system for Drupal.
Ægir is a set of contributed modules for Drupal that aims to solve the problem of managing a large number of Drupal sites. It does this by providing you with a simple Drupal based hosting front end for your entire network of sites. To deploy a new site you simply have to create a new Site node. To backup or upgrade sites, you simply manage your site nodes as you would any other node.
This release is the final release of our 0.2 development cycle, which has been focused on complete support for running multiple concurrent Drupal releases, and managing upgrades of sites between Drupal releases. The only changes from the release candidate were some miscellaneous bug fixes and bringing the system in line with the Drush 2.0 final release.
Read more
Aegir 0.2 beta 1 released.
We're proud to announce the first beta of the 0.2 release of the Aegir hosting system for Drupal.
Ægir is a set of contributed modules for Drupal that aims to solve the problem of managing a large number of Drupal sites. It does this by providing you with a simple Drupal based hosting front end for your entire network of sites. To deploy a new site you simply have to create a new Site node. To backup or upgrade sites, you simply manage your site nodes as you would any other node.
This release is the first beta release of our 0.2 development cycle, which has been focused on complete support for running multiple concurrent Drupal releases, and managing upgrades of sites between Drupal releases. This release has also primarily been focussed on fixing bugs and polishing the final release of the 0.2 release.
Read moreAegir 0.2 ALPHA 1 released.
We're proud to announce the first alpha of the 0.2 release of the Aegir hosting system for Drupal.
Ægir is a set of contributed modules for Drupal that aims to solve the problem of managing a large number of Drupal sites. It does this by providing you with a simple Drupal based hosting front end for your entire network of sites. To deploy a new site you simply have to create a new Site node. To backup or upgrade sites, you simply manage your site nodes as you would any other node.
This release is the first alpha release of our 0.2 development cycle, which has been focused on complete support for running multiple concurrent Drupal releases, and managing upgrades of sites between Drupal releases. This release has also primarily been focussed on improving and simplifying the back end system, by incorporating a lot of our custom API's upstream into the Drush 2.x project.
Update: Check out this screencast for a quick walkthrough of the features available in this release.
Read moreProgress update: Package management and dependency checking
Progress towards our main development goals.
Drush stuff
Last week I completed what is basically a major rewrite of Drush, save the actual command files. Everything is a lot more sensible and normalized now. This also led to me massively refactoring Provision (our drush based back end) to make use of these new API's. I wrote up a small post about what's been happening with Drush for those that want more in depth information.
The major thing that is coming out of Drush becoming more like Provision every day, is that the drush_extras project is being re-integrated into Drush itself, using the provision conditional include API for the Drupal version specific code. Once that is done, we will be migrating Drupal install and update commands upstream to provision, which provide a much larger user base for the code, getting it far more testing. It will also significantly reduce the size of provision, and make it easier to maintain and will hopefully become the standard way that 'real' Drupal developers run update.php on their sites.
Because we are so deeply involved in Drush now, we are also tied to their release cycle. We are at a point where we want to release an alpha, but moshe has decided to re-integrate Drush_extras first, which should take about as long as it would to have gotten each version of drush_extras ready for an alpha too.
Enabled packages on a site
Aegir stuff
I haven't been resting on my laurels though, I've been tackling many of our critical issues (take a look at how good our issue queue is looking). I have been continuing in my crusade to make the Aegir project easier to build and maintain.
In the last week I finally nailed down the biggest issue that was holding us off on an alpha, namely the package management features. With drush 1.x we could rely on each platform being a site, to have access to the database, unfortunately with 0.2 that isn't possible anymore, so I wrote some routines that index entire Drupal platforms and find all the modules, themes etc for the whole platform, all the profiles and each of the sites, which I then import on the front end to build relationships between the package entities and the sites etc.
This now allows us to do some dependency checking, which we sorely needed. Previously it would let you attempt to migrate any site to any platform, no matter of the version.
This is much nicer. Imagine how great it will be once we have spaces, context and features properly playing along with all this stuff. You'll be able to roll out new features incredibly easily, and seeing that you can extract features with Drush, we can automate that too.
Package compatibility between platforms
As you can see, we're already very close to an alpha, so we're going to be working towards that along with the Drush guys. After the alpha there's going to be another phase of refactoring going on, as we'll have solved all our major issues for the release, and now it's time to make sure the codebase is up to scratch. We're also going to take some time and get some of the contrib modules playing nicely with 0.2, so that will take some time too.
I have also spent a few hours today on the community side of things, mostly fixing up the groups.drupal.org page. It looks way better now, and displays the release status proudly (keeps us honest, heh).
We'll be continuing forward in the next week or two on both the Aegir and Drush projects, and we'll probably have more announcements soon.
UPDATE: 0.2 Alpha release soon, even closer relationship to Drush.
We finally have HEAD to a stable enough state that we can work towards releasing an alpha release in the next week or so. This is pretty exciting news because it means that we're nearing the end of the 0.2 Development cycle.
Read moreProgress update - Frontend and Backend are now completely separate. Experimental multi-server support.
One of the major changes to Aegir for the 0.2 release, is integrating with Drush 2.x.
What this comes down to is that, like Drush, Provision has ceased being a 'module' in the traditional sense.
Each server that Aegir manages will now need to have one instance of Drush, and one instance of Provision.
This resulted in some refactoring in the Hosting module, as it was depending on Provision being available as a module for a number of things.
One of the other things that I added to the code in HEAD, once the refactoring had taken place, is the ability to call instances of Drush and Provision on remote servers. This means that you can now install, enable, disable, delete, backup, roll back , and upgrade Drupal sites on multiple servers, that are managed by Aegir.
Read moreAegir Drupal 6 Platform Confusing Site Issues
i'm having a weird experience trying to use a d6 platform
i successfully installed 0.1 with a drupal 5 platform
then i added a d6 platform - following the instructions on the 0.1 release page
tried adding a site (which is actually a subdomain of the main domain - i.e. d6test.example.com where example.com points to the main ip of my server)
i go to that site and do the password reset thingie
then when i log into that site it looks like the main hostmaster install, NOT a drupal content site like I expected (and see with the sites i launched on the drupal 5 platform)
