apache on aegir-up could not be restarted. Changes might not be [warning]
available until this has been done. (error: apache2: Syntax error on
line 227 of /etc/apache2/apache2.conf: Syntax error on line 25 of
/etc/apache2/conf.d/aegir.conf: Syntax error on line 21 of
/var/aegir/config/server_master/apache/platform.d/platform_hostmaster.conf:
Could not open configuration file
/var/aegir/hostmaster-6.x-1.9/.htaccess: No such file or directory
Action 'graceful' failed.
The Apache error log may have more information.)
<em>apache</em> on <em>aegir-up</em> could not be restarted. Changes [warning]
might not be available until this has been done. (error: <em>apache2:
Syntax error on line 227 of /etc/apache2/apache2.conf: Syntax error
on line 25 of /etc/apache2/conf.d/aegir.conf: Syntax error on line 21
of
/var/aegir/config/server_master/apache/platform.d/platform_hostmaster.conf:
Could not open configuration file
/var/aegir/hostmaster-6.x-1.9/.htaccess: No such file or directory
Action 'graceful' failed.
The Apache error log may have more information.</em>)
We've been testing updating the front-end as per: http://community.aegirproject.org/upgrading/debian#Keeping_custom_distri...
So, we'd updated the front-end to a new platform with a custom makefile, which worked just fine. After deleting the old platform (from the front-end) and running 'dpkg-reconfigure aegir-hostmaster', we got these errors, though the creating of the new platform, and the migration of the hostmaster site into it appear to have worked fine.
Comments
Comment #1
anarcat commentedYou seem to have removed a platform without removing its apache configuration file, it's normal it freaks out.
Bad puppy, no cookie.
Comment #2
ergonlogicNow, now...
I deleted the platform from the front-end, so that should have cleaned up after itself, no?
Comment #3
anarcat commentedYes, it should have.
The problem is not with dpkg-reconfigure, it's apachectl graceful that fails to find the file. You would run into the same problem running verify or any other task on that server.
I'd be curious to hear how we can reproduce this.
Comment #4
ergonlogicWell, I could probably get a drush-vagrant/aegir-up environment set up to reliably test this. IIRC, it'd basically involve building a standard aegir-up instance (
drush vb --blueprint=aegir), then runninghostmaster-migrate, and thendpkg-reconfigure.Comment #5
anarcat commentedHum. Those steps shouldn't lead to the removal of the old platform. Are you sure you are not manually removing that platform?
Comment #6
ergonlogicUh, yeah... sorry :$
I meant to say the steps followed were:
Comment #7
anarcat commentedSo here step #3 should have removed that configuration file. Can you paste a task log of that step?
Step #4 could also just be
sudo apache2ctl gracefulas the aegir user.Comment #8
ergonlogicPlease confirm whether this is still an issue in Aegir 2.0+.
Comment #9
helmo commentedThe 6.x-2.x branch will go EOL along with Drupal this week. So I'm closing
this issue. If it remains a confirmed issue in 7.x-3.x, feel free to re-open,
or better yet, create a new issue referencing this one.