Aegir Serves 404 error during Migrate task before Varnish is restarted

I migrated a site from one platform to another.  In the process, the site went down with a 404 not found error from Apache.  When the Migrate task completed, Apache (not Drupal) still threw a 404 error.  Post 8080 (Apache, behind Varnish) delivered the page.  So I restarted varnish and the site began responding again on port 80.


Hmmm...  Should Varnish be restarted as part of the Migrate task?  Why have I never experienced this with any other Migrate tasks?

Customizing Varnish VCL on Mercury Server

When getting started with Varnish on Mercury (1.1), I decided to use two resources for VCL logic:
  1. Lullabot Nate Haug's article "Configuring Varnish for High-Availability with Multiple Web Servers" (my implementation only utilizes parts of it)
  2. Stewart Robinson's HIT/MISS header set in sub vcl_deliver
Syndicate content