Postponed (maintainer needs more info)
Project:
Provision
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
13 Jan 2011 at 19:19 UTC
Updated:
23 Apr 2014 at 18:50 UTC
Jump to comment: Most recent
Comments
Comment #1
iainh commentedBTW Restarting Apache right afterwards raised no such error message from Apache.
BTW BTW I believe it's Aegir 0.4 beta 2 I'm using .... but the Issues drop-down doesn't offer this release.
Comment #2
Anonymous (not verified) commentedYes, this does appear to be a Provision bug, and is simply a problem with order: it tried to restart apache probably after syncing the platform data, but before syncing the apache platform config.
It would have eventually synced the platform config anyway, which is why your subsequent apache restart worked, but it should wait til everything is synced before restarting.
Possibly relates to my comment #30 here http://drupal.org/node/976300#comment-3935510
Comment #3
steven jones commentedI've seen this too.
Comment #4
steven jones commentedAs far as I can tell,
provision_drupal_sync_siteis the actual function that syncs the platform, but don't call it untilhook_drush_exit. Which is of course after we've gotten apache to restart.Comment #5
ergonlogicIs this still an issue on the dev branch (7.x-3.x)?