Verifying servers, platforms and sites

One of the common tasks available to all three of the major entities in Aegir (Servers, Platforms and Sites) is the Verify task.

You can think of the Verify task as a sort of routine 'sanity check' of that specific entity, with a sort of checklist of expected behaviour with which it runs through to confirm that the entity is operating as normal.

The Verify task also can be used to regularly 'sync' your platform or site with the Aegir package registry, to keep it up to date on whether any modules have changed (been removed or enabled/disabled). This will aid running Migration and Clone tasks, since Aegir needs to have a precise knowledge of what modules, themes or profiles are on the system before it can accurately judge whether an upgrade is possible.

It is recommended to run the Verify task on your entities routinely to keep them in sync with the Aegir database, and to run a Verify of your site, current platform and target platform prior to attempting a Migration or Clone task.

What happens in a Verify task?


  • When you add a new server node in the Aegir frontend, a Verify task is spawned for the first time.
  • The configuration directories are created if they don't exist and set to the correct permissions, or set to the correct permissions if they already existed but were incorrectly set.
  • If the server is the master server, some additional configuration and backup directories are created.
  • Aegir generates or updates a Drush alias file for the server.
  • Some configuration directories are synced from the master server to remote servers.
  • Checks that new databases and database users can be created.
  • Checks that the HTTP web server can be restarted.


  • When you add a new platform node in the Aegir frontend, a Verify task is spawned for the first time.
  • If the platform directory didn't exist on the file system and a Drush makefile was provided, Drush Make will be called to build the platform in that location.
  • If the platform directory didn't exist and no Drush makefile was provided, the task will fail with the error 'Does not contain a valid Drupal installation'.
  • Checks that the permissions are correct, at least of the 'sites' folder of the platform directory (so we can create new sites here).
  • Searches for existing sites on the platform that are not yet in the system.
  • These sites will be 'imported' into Aegir.
  • Scans the platform and builds or updates the package registry in the Aegir database.
  • Generates or updates a Drush alias for the platform, and a drushrc.php file in the platform's directory root.
  • Reads in the platform's .htaccess file into a platform-wide web server vhost configuration file.
  • Restart the web server.


  • When you add a new site in the Aegir system, an Install task is spawned.
  • This is contrasted with the above entities which spawn only Verify tasks initially.
  • Scans the site and builds or updates the package registry in the Aegir database.
  • Creates important directories in the site folder, such as 'files'.
  • Sets or corrects the appropriate permissions.
  • Manages/updates any site aliases (symlinks, redirects etc).
  • Re-generates the settings.php.
  • Re-generates the site's web server vhost configuration file.
  • Re-generates the site's drushrc.php and a Drush alias.
  • Clears caches.
  • Restart the web server.

You can run or re-run the Verify task at any time on a server, platform or site, and it is encouraged to do so.

Certain tasks, such as 'deploy' when a site is being imported, automatically imply a verify of the site.

Each Verify task, like all tasks generated by Aegir, emit a 'task log' available for review after the task has completed (or failed).

If a Verify task fails, and the task log does not provide enough information to help you resolve the problem, trying running drush provision-verify --debug from the command line to find out what caused the problem. Remember to replace '' with the URL of the site you are trying to verify.