Drupal 10, the latest version of the open-source digital experience platform with even more features, is here.I've seen this a couple times (i.e., it's not new to rc5), but I haven't been able to reproduce it reliably. From what I can tell, if an apt-get upgrade of the package fails, it can sometimes result in the loss of the symlink from /var/aegir/config/apache.conf to /etc/apache2/conf.d/aegir.conf. Bear in mind, this after the the .deb thinks it's properly installed, and results in the default 'It works' page from Apache.
I'm marking as 'critical' since this breaks Aegir entirely, including all hosted sites. However, if we still can't reproduce it, I don't think we should block the release.
The work-around is quite simple:
/etc/apache2/conf.d# ln -s /var/aegir/config/apache.conf aegir.conf










Comments
Comment #1
anarcat CreditAttribution: anarcat commentedI have seen this on a failed upgrade, but once the upgrade completes, this works again. It was on an upgrade from 1.x, FWIW - I am not sure this would happen on minor upgrades.
Comment #2
ergonlogicMost recently, I saw this on a rc4 to rc5 upgrade.
Comment #3
ergonlogicIt looks like we do this explicitly in aegir2-provision.postrm:
I've attached a patch that moves this bit into 'purge|abort-install|disappear', and does nothing for 'remove|upgrade'.
Comment #4
ergonlogicSorry, 'needs review', @anarcat :)
Comment #5
AlfTheCat CreditAttribution: AlfTheCat commentedI just had this issue. I removed postfix and re-installed it. I ran apt-get update and apt-get autoremove in the process.
Re-creating the symlink solved the issue that resulted in the "It works!" message appearing in my browser instead of my websites.
Comment #6
anarcat CreditAttribution: anarcat commented@ergonlogic - there's no patch attached here... furthermore, the name of the symlink needs to be specified otherwise you'll end up with dupes, updated issue summary accordingly.
Comment #7
anarcat CreditAttribution: anarcat commentedyet i see what you mean and committed a fix