The Verify task said it had succeeded, but further inspection of the log showed that Apache2 could not be restarted after the platform had been rsyc'd to the remote server.
This was when creating a new Platform using a make file that creates all the correct files including the root .htaccess file that Aegir complains about. Should I be reporting this in the Provisioning Issues?
apache on {remote_server}.org.uk could not be restarted.
Changes might not be available until this has been done.
(error: apache2: Syntax error on line 233 of /etc/apache2/apache2.conf:
Syntax error on line 25 of /etc/apache2/conf.d/aegir.conf:
Syntax error on line 18 of /var/aegir/config/server_{remote_serverorguk}/apache/platform.d/platform_Atrium10Prodn.conf:
Could not open configuration file /var/aegir/platforms/atriumb10/.htaccess: No such file or directory)
| Comment | File | Size | Author |
|---|---|---|---|
| PlatMake.txt | 12.09 KB | iainh |
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)?