FAQ
Contents
Help!
Installing Aegir
- Can I run Aegir on a shared hosting environment?
- Can I run Aegir on Windows?
- Can Aegir be installed next to CPanel/Plesk/AlternC/etc?
- Where can I get support for Barracuda/Octopus Aegir?
Using Aegir
- The cron isn't running (scheduled tasks/cron on sites aren't being executed), what do I do ?
- How do I get debug/verbose info from Drush when running the hosting commands ?
- How do I update a sites modules using aegir?
- Is it best to set up sites under aegir as www.example.com or just as example.com ? The aim is for both to resolve to the same.
- How can I setup a site to use https:// under Aegir?
- Aegir is not verifying / deleting / migrating my site because of file permission problems.
- I can verify OpenAtrium as a platform but Aegir fails to provision an Atrium site
- A platform with an installation profile has verified okay, but Aegir doesn't seem to be able to use the profile
- What is a patch or 'hotfix', and how can I apply it to fix my site if I can't / don't want to upgrade to HEAD?
- I followed the installation instructions. What directory holds all of my sites now?
- I tried to create a site, but the create task failed and retries don't succeed. How do I delete the partially created site and associated Aegir tasks?
- I tried to migrate a site, but Aegir incorrectly reported an incompatibility between one or more modules in my source and destination platforms. How do I force Aegir to see that the two platforms are compatible?
- What about .htaccess settings?
- How can I tell what version of Aegir I have installed?
- I'm using symlinks (perhaps to a GIT repo) and crazy things are happening!
Help!
1) Where can I get help?
From the Documentation (which should be the first place you look) :
The Issue Queue for all the projects that make up Aegir is here: http://is.gd/ek2Dl
This is the first place to look - chances are someone's had the same problem as you before, and you'll get the quickest answers by searching for what they discovered.
Before asking a question or reporting an issue, you should read the bug reporting guidelines.
You can join the #aegir channel at Freenode on IRC. (IRC instructions for drupal users are at: http://drupal.org/irc). It's a friendly community, but a small one, so ask nicely and be patient!
If you find a solution to a problem that isn't in the documentation or in this FAQ, be the first to login and edit these pages to bring them up to date! The rest of the community thrives on your helpful information!
2) Can I ask you a question?
Of course you can! Don't ask to ask, just ask! It is polite to look if the question has already been answered in the documentation, the issue queue or here, but if not, please do ask around! If you ask a question and we have a nice answer, you can even add it to the FAQ here so that others can have your valuable answer.
3) Who are the Aegir developers?
The Aegir core developers are Adrian Rossouw (Vertice), Antoine Beaupré (anarcat) and Miguel Jacq (mig5).
Installing Aegir
1) Can I run Aegir on a shared hosting environment?
Shared hosting will not give you enough permissions to install new sites. Toughen up, read some Linux beginners tutorials and buy a cheap VPS which will do nicely.
2) Can I run Aegir on Windows?
To install Aegir you need a unix based operating system. Aegir will not work on Windows and there are no plans to add support for it.
3) Can Aegir be installed next to CPanel/Plesk/AlternC/etc?
No, or rather "it's not supported". See http://drupal.org/node/587554
4) Where can I get support for Barracuda/Octopus Aegir?
Barracuda/Octopus are custom scripts for Aegir that install or set up various things that Aegir doesn't do out of the box. This is a custom solution tailored to Nginx systems, provided by Omega8.cc and is not officially supported by the core Aegir project or team. For help or more information, please visit https://github.com/omega8cc/nginx-for-drupal
Using Aegir
1) Cron isn't running (scheduled tasks aren't being executed), what do I do?
At the shell prompt as the aegir user, type
crontab -ea) If you get an error that the command is not found, then you need to install cron on your server (some basic images don't include it - Linode's Ubuntu 9.04 image is one):
sudo apt-get install cronNow go back to the directory /var/aegir/drupal-6.19 and re-execute the hosting dispatch:
/var/aegir/drush/drush.php @hostmaster hosting-setupType 'crontab -e' again.
b) You should see the default entry:
*/1 * * * * (php '/<path to drush>/drush.php' @hostmaster hosting-dispatchBut if this is still not working it may well be a permissions issue. An example error :
Forking : (php /<path to drush>/drush.php --quiet @hostmaster 'hosting' 'task' '266' --backend &) > /dev/null [0.432 sec] [notice]
sh: /dev/null: Permission deniedThis means the system doesn't have permissions to access /dev/null. To resolve it, give the system permissions to write to /dev/null (it should have this anyway), by executing:
sudo chmod a+w /dev/nullc) If this still hasn't worked, have you moved the location of drush?
If so - see http://drupal.org/node/540152
d) If you are a *BSD user (verified on freebsd at least)
You need to add the line :
PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin at the TOP of your cron file.
Simply log in as the aegir user and type crontab -e and insert the above line on top.
Thanks goes to mauror for http://drupal.org/node/323732.
e) When cron for your sites stops working, it is possible that for some reason (system overload, broken site, timeout etc), Aegir failed to release a sites cron semaphore. To release it, use this simple recipe:
$ su -s /bin/bash - aegir
$ cd /path/to/hostmaster/sites/domain
$ drush vdel hosting_queue_cron_running -y2) How do I get debug/verbose info from Drush when running the hosting commands?
Add these to the drush call :
--debugIf you're having specific problems when using the frontend, you can easily run the hosting commands from the command line by:
- Click the view button and then copy the Drush command which was executed at the top of the log;
- While logged in as the aegir user, paste the command in at the terminal and replace --backend with --debug at the end of the commandline.
3) How do I update a site's or platform's modules using Aegir?
Aegir isn't a package management GUI for installing modules or themes on your site.
It's designed to help manage your site between builds. To upgrade sites, you should be using the Migrate tool to move your site between two platforms, which invokes drush updatedb.
If you aren't ready for this paradigm, and are frustrated that Aegir isn't some GUI for wildly updating or installing new modules with no regards for rollback or dealing with when it will inevitably break your site, Aegir is probably not for you.
4) Is it best to set up sites under aegir as www.example.com or just as example.com?
Aegir supports either method and can even automatically create whichever one you didn't use as the main site name. Read more about Aliases and this feature in our documentation.
5) How can I setup a site to use https:// under Aegir?
Aegir ships with an experimental SSL feature, but currently doesn't provide any means of managing SSL certificates.
You can follow the ongoing SSL work here.
In the meantime, to set up SSL with basic self-signed certs, follow our documentation.
6) Aegir is not verifying / deleting / migrating my site because of file permission problems.
Aegir releases prior to 0.3 RC3 encountered an error when the web server has uploaded files and made new directory in the sites/$url/files directory. A prevalent example of this occurring is with the color module and when imagecache is used (such as in atrium).
This bug (see: #203204 ) was introduced with Drupal 6, and has since been fixed with Drupal 7. The patch has however not been backported yet, and the patch won't fix existing files that were created incorrectly.
In Aegir 0.3 RC3 we introduced a work around which sets the umask for the site, which forces new files and directories to be the correct permissions, but this will only take effect after the site has been succesfully verified. To enforce the correct file ownership and permissions on the files, run the following command on each of your Drupal 6 platforms :
sudo chown -R $aegir_user $platform/sites/*/filesThis will allow the verify task to correctly set the permissions and succesfully modify/remove the files.
7) I can verify OpenAtrium as a platform but Aegir fails to provision an Atrium site
Raise your memory_limit in your php cli php.ini file to something like 128MB, or maybe 64MB if that's too much. On Debian-based distributions this is /etc/php5/cli/php.ini. Apache does not need a restart for this: installations fail because the command is being executed via drush using php cli. Atrium requires more memory to run its install profile as it has a lot more to do than a regular Drupal install.
8) A platform with an installation profile has verified okay, but Aegir doesn't seem to be able to use the profile
Your platform has been setup and verified okay, but when you go to create a new site Aegir keeps giving an error message about the profile, or the list doesn't offer you the profile you're expecting. This could be a namespace issue. Modules, themes and profiles in Drupal all have a machine name - which is essentially their folder name. This is also used to prefix their functions etc, so that there are no clashes.
What isn't often recognised or well documented is that Drupal has a single namespace for all items - so your themes, modules and install profiles can't have the same name as each other.
Often an installation profile will be created called 'OpenPotato' and the theme for it will also be called 'OpenPotato'. This makes Drupal unhappy, and when Drupal's unhappy Aegir's unhappy. We don't want that, but it isn't Aegir's fault, it's the developer's limited or lack of understanding of this Drupal caveat.
The easiest thing is to name your installation profile directory 'OpenPotato_install' and name the profile file 'OpenPotato_install.profile'. You'll also need to rename the functions inside this file.
Then everything should work just fine.
9) What is a patch or 'hotfix', and how can I apply it to fix my site if I can't / don't want to upgrade to HEAD?
Sometimes releases are made and bugs are discovered afterward. We commit fixes for such bugs to HEAD, but HEAD is often volatile and you don't want to use a non-stable release in your environment. Fortunately we do (or should: if it's critical, please ask for a patch otherwise) provide a 'hotfix' or patch for users. A patch means that you can 'patch' your Aegir system to fix the bug without running the risks of using HEAD.
To patch an Aegir component, use the following example, in which we fix the Provision module with an imaginary patch. The same or similar steps apply for Hosting or Hostmaster (though you shouldn't need to patch Hostmaster, you only use it once to install!)
Run the steps as the aegir user.
1) Backup /var/aegir/.drush/provision to somewhere else for safety, such as /tmp/provision
2) Download the patch given in the ticket, to your server. Use wget or a similar useful tool for downloading it over the commandline. You can download the file to anywhere.
3) edit your aegir user's crontab (crontab -e) and comment out the dispatch entry (place a '#' in front of the hosting dispatch cron entry). This is a precautionary step in case you patch the module, something goes wrong and it breaks the module. The hosting dispatch cron might come around and try and run the queue dispatcher and break/complain due to a broken component. If you know what you are doing and are fast enough to fix it, you may skip this.
4) cd /var/aegir/.drush/provision/
5) patch -p0 < /path/to/the/patch/file
6) crontab -e and uncomment the dispatch cron task
If the patch doesn't apply or prompts you to enter the filename to patch, try running patch -p1 instead of -p0 above.
If it still asks for clarification, verify that you are in the top-level directory of the component (in this case, we are inside /var/aegir/.drush/provision)
If it still doesn't work, it might be an unclean patch, and you should make a request in the relevant ticket to be given a cleaner patch to apply.
For more information on patches, please read the Drupal documentation.
11) I followed the installation instructions. What directory holds all of my sites now?
For a full overview of a typical Aegir filesystem structure, read this.
12) I tried to create a site, but the create task failed and retries don't succeed. How do I delete the partially created site and associated Aegir tasks?
See the section 'Manually deleting the site' from the documentation
13) I tried to migrate a site, but Aegir incorrectly reported an imcompatibility between one or more modules in my source and destination platforms. How do I force Aegir to see that the two platforms are compatible?
This problem can arise for at least two different reasons. First, you may have updated a module in a platform that you imported and forgotten to run update.php before you imported the site into Aegir. Second, you may have updated a module in a platform and not re-verified the platform in Aegir. Be sure that you have run update.php on a drupal platform that you will be importing into Aegir before you import. Also, if you make any change to the modules in an Aegir Platform, re-verify that platform and all sites using that platform. (At least, experience suggests that doing these things will allow the migration to succeed.
14) What about .htaccess settings?
As of recent 0.4 alpha releases, Aegir now reads in the contents of a platform's .htaccess file when generating the Apache configurations. You can safely make additions/changes to the platform .htaccess and expect the relevant site to respect those changes.
15) How can I tell what version of Aegir I have installed?
This works for 0.4alpha9 and above...maybe earlier too...
grep '[hostmaster][download][url]' /var/aegir/.drush/provision/aegir.makeIf you're still unsure or this didn't work, contact a developer on IRC and we'll be able to tell you after you answer a few questions.
16) I'm using a GIT repo for a site, but symlinks make crazy things happen!
If you're symlinking an entire /sites/
If you are using GIT to version control your themes, custom modules, etc, and symlinking these into your sites folder, you will find that cloning a site will clone those symlinks (by virtue of copying the sites folder). This is probably not what you want to happen!
Themes and custom modules are better off being checked out to or symlinked into the install profile folder. If your site's install profile is 'foobar' (there's an 'install_profile' variable in the variables table), Drupal core understands to look inside the /var/aegir/yourplatform/profiles/foobar/ folder for modules and themes directories.
The files directory for uploads (which I don't think can be efficiently versioned anyway in most cases) and the settings.php file will be all that's left in your sites folder, and Aegir will happily move that all around as you clone or migrate your site between platforms.
Storing your site's dir in git is an archaic and inefficient method of developing sites. It's 2010 and there are more elegant ways of doing things thanks to Drush Make and Aegir. You might like to look at mig5's excellent article where he provides some great tips on how to manage Drupal deployments & workflows with version control, drush_make, and Aegir.
- Login or register to post comments
- Print entire section
- Talk
#1
I am attempting to determine the specific actions needed to secure the mysql database when you get the "Dummy connection failed to fail" message, without running "mysql_secure_installation"...
So far I've determined you should run the following queries:
DELETE FROM mysql.user WHERE User='';DROP DATABASE test;
DELETE FROM mysql.db WHERE Db LIKE 'test%';
Once I confirm this works I will edit the FAQ to include these commands
#2
That and a FLUSH PRIVILEGES; seems to do it.
I'll be testing it a few times more, then update the FAQ and Automatic Install instructions.