Hello, I cannot get past the verification phase on my install. I followed the instructions in INSTALL.txt and wizard but I am stuck at the verify task.

Log message is below.

This is very similar to: http://drupal.org/node/446620 but that bug morphed into another bug so I'm opening this one here.

In the wizard, the drush path is set to: /var/aegir/drush/drush.php correctly.

I created an alias to drush for root but it didn't change anything. Do I need to do this for the aegir user "aegir"?

As root, 'drush help' shows only the hosting commands. No provision commands.
As aegir, 'drush help shows the provision and hosting commands

I can't find a drushrc.php file on my system (Ubuntu 8.04)
#find -name drushrc.php
In here I can configure the user drush runs as? Do yall do Aegir admin as user 'root' or as user 'aegir'?

Where did I go wrong? How do I go right?

Thanks for your help!

Mike

====Log message====

Task starts processing
Running: php /var/aegir/drush/drush.php --root='/var/aegir/drupal-5.x' 'provision' 'verify' --backend
Drush bootstrap phase : _drush_bootstrap_drush()
Drush bootstrap phase : _drush_bootstrap_drupal_root()
Initialized Drupal 5.16 root directory at /var/aegir/drupal-5.x
Drush bootstrap phase : _drush_bootstrap_drupal_site()
Initialized Drupal site default at sites/default
Drush bootstrap phase : _drush_bootstrap_drupal_configuration()
Drush bootstrap phase : _drush_bootstrap_drupal_database()
Successfully connected to the Drupal database.
Drush bootstrap phase : _drush_bootstrap_drupal_full()
Drush bootstrap phase : _drush_bootstrap_drupal_login()
The command 'drush.php provision verify' could not be found.
Removing task from hosting queue
An error occurred at function : hosting_hosting_task
Changes for hosting_hosting_task module have been rolled back.

Comments

MichaelCole’s picture

MichaelCole commented
Version: 6.x-0.2-beta1 » 5.x-0.2-alpha1

wrong version reported. Updating to newest code...

MichaelCole’s picture

MichaelCole commented

wrong version reported. Updating to newest code.

MichaelCole’s picture

MichaelCole commented
Version: 5.x-0.2-alpha1 » 6.x-0.2-beta1

Same exact behavior on new beta1

MichaelCole’s picture

MichaelCole commented 
Log message
Task starts processing
Running: php /var/aegir/drush/drush.php --root='/var/aegir/drupal-5.x' 'provision' 'verify' 
--backend
Drush bootstrap phase : _drush_bootstrap_drush()
Drush bootstrap phase : _drush_bootstrap_drupal_root()
Initialized Drupal 5.17 root directory at /var/aegir/drupal-5.x
Drush bootstrap phase : _drush_bootstrap_drupal_site()
Initialized Drupal site default at sites/default
Drush bootstrap phase : _drush_bootstrap_drupal_configuration()
Drush bootstrap phase : _drush_bootstrap_drupal_database()
Successfully connected to the Drupal database.
Drush bootstrap phase : _drush_bootstrap_drupal_full()
Drush bootstrap phase : _drush_bootstrap_drupal_login()
The command 'drush.php provision verify' could not be found.
Removing task from hosting queue
An error occurred at function : drush_hosting_hosting_task
Changes for drush_hosting_hosting_task module have been rolled back.
Command dispatch complete
Garrett Albright’s picture

Garrett Albright commented

I ran into this problem myself. The problem seems to be that Drush is not finding the Provision Drush commands. If I specify the path to the commands using Drush's -i switch (to specify more directories to be included when searching for commands), I can get it to work.

This seems to be the culmination of some errant assumptions on the part of Hosting and/or Hostmaster that the user account the web server is running as ('www' in my case) is a full-blown user, with a shell and a home directory. Thus, upon installation, I'm told to put the provision directory under the .drush directory in the www user's home directory, then later to log in as www and run a command with Drush. Wha? Maybe that's the norm in the Linux world, but not on FreeBSD…

I'm unsure how to progress as well. I guess Aegir isn't going to work for us just yet… Too bad, because it looks waeome. Perhaps I'll take a peek at the code someday and see if I can tweak it, but for now, I've got clients waiting…

adrian’s picture

adrian commented

Ok. stop.

Go look at the install screencast video :

http://developmentseed.org/blog/2009/may/20/aegir-scratch-installing-aeg...

Aegir, is _specifically_ designed to not run as the web server user. It needs an additional user account created.

This is to properly specify the least possible permissions.

If aegir was running as the web server user, the httpd.conf files it created would be owned by the web server user, which would then mean any of your provisioned sites can go modify the httpd.conf file, and do whatever they want with it.

adrian’s picture

adrian commented

re: requiring a home directory.

That's an upstream drush issue, that you can find here : http://drupal.org/node/459678

The issue is that drush has no system wide place to store files , so we're using the user wide location for now.
Our goal is to be able to have .deb / .rpm / bsd ports support for drush and provision, so those can be managed
by the operating system.

Garrett Albright’s picture

Garrett Albright commented

Aegir, is _specifically_ designed to not run as the web server user. It needs an additional user account created.

This was made more clear in the most recent release, which I did eventually manage to get past this step with. With the previous release, though, I could have sworn it was telling me otherwise. Either that, or I'm just dumb, I donno.

adrian’s picture

adrian commented
Status: Active » Fixed

This is solved imo, it's been widely documented and there's also the install screencast

MichaelCole’s picture

MichaelCole commented
Status: Fixed » Closed (fixed)