Problems with Provision Verify on CentOS 5.3

I guess I will have to start over again. The installation instructions are a tad crufty. I basically follow the ones in the INSTALL.txt but want to run from a CVS checkout.

When does the drushrc.php get created in the platform directories? Do the platform directories need to be own by the apache users so it can get written?

--
Christian

I got the same problem even on version 0.3. After spending nearly half day on try and error. I found out that the system doesn't allow password contain symbols for the master DB user. It would be nice if someone could fix it.

Why not use Debian/Ubuntu?

I dont think much focus has been applied outside debian/ubuntu just yet .. tho the time will come im sure.
Is there some particular reason your using centOS? Most of what ive read and heard around Aegir is most if not all testing and instructions are Debian/Ubuntu, its the starting point before branching out to other os's. Prolly have a lot less trouble going that route.

Just my two cents. ^_^

@gmmurugan

You really need to follow the directions .. when I first started working with Aegir .. I was messing things up .. also known as "user error" I can tell you that since then I have successfully installed Aegir on ubuntu more than 20 times. And have several servers running it without any trouble.

var/aegir should be the home directory because thats how its supposed to be .. sure you may be able to change it but you'd have to probably hack the code which is not a good idea.

To answer your questions..
1. Never used CentOS for Aegir .. and im not sure its supported, its an unknown .. so why bother? Ubuntu/Debian is supported and therefore a smarter route to go since we are all using it successfully.
2. Drush can be anywhere you want it to be .. just make sure that you create a proper link to it so its usable .. and also enter that link when filling out the hostmaster installation pages. I have my drush installed in /var/aegir/drush
3. If you followed the directions exactly then perhaps there is something extraneous going on with your server? Try starting with a clean fresh ubuntu/debian.
4. The directions explain each step pretty well ... make sure your reading the latest install.txt
5. Did you also look in... http://groups.drupal.org/node/4701/documentation there is a shell install script that's a handy shortcut and worked for me when I tested it.

I'm sorry your having some trouble with this but stay strong and keep trying because you will be very happy you did, Aegir rocks!

Cheers!

I am learning both Aegir and Drupal, but I got them working on an existing SUSE Enterprise Linux server that was already running Apache, PHP, and MySQL for other purposes. My Apache server is not dedicated to Aegir, and I can add and remove Aegir without affecting the other non-Drupal Apache virtual hosts.

I am a career Unix / Linux administrator and I admit I encountered some problems. I got it working on the second installation attempt by starting over, by deleting the aegir user and directories and using what I learned the first time.

I did not use /var/aegir. I used /srv/www/aegir for the "aegir" user $HOME, but this did not cause any of my problems. You can put the $HOME anywhere you want and the user does not have to be called "aegir." My problems were largely with drush, provision, PEAR, and settings.php. The PEAR issue may have been a "red herring" (a possibly unrelated problem with an earlier version and the Console_Table library).

Over a year ago, I installed SLES (OpenSUSE is nearly identical). At the time, I used the SUSE software installer YaST2 to install Apache and PHP. This is where various Linux "brands" create problems for us - location of various parts of Apache can vary greatly from Linux to Linux (to Unix to Unix).

I installed PEAR manually for the user "aegir" in the "aegir" $HOME (e.g., /var/aegir/pear). This may have been unnecessary.

Important: Follow the latest Aegir INSTALL.txt revision! ...and adapt any Linux "brand"-specific (e.g., Debian) instructions to your own methods (RPM, YaST, yum, ...). I read 2 or 3 tutorials for installing Aegir that I found using Google. These tutorials combined helped me better understand the Aegir installation structure and how the parts are related.

Check $HOME/drupal*/ for the file drushrc.php. This is created during the install process and must contain the proper MySQL data (I found it near the end of my drushrc.php).

Ensure you copy sites/default/default.settings.php to sites/default/settings.php. I think this addressed in INSTALL.txt.

If you do not use the drush --root= option, then you must run drush from the drupal directory or the specific site directory. The command "drush status" should produce something like:

  PHP configuration : /etc/php5/cli/php.ini
  Drupal Root       : /srv/aegir/drupal
  Drupal version    : 6.13
  Site Path         : sites/default  (or sites/mysite.mydomain.tld)
  Site URI          : http://default (or http://mysite.mydomain.tld)
  Database Driver   : mysql
  Database Hostname : localhost
  Database Username : aegiruser
  Database Name     : aegirdb
  Database Password : S00per.secret.passwort.known.only.2.me.and.my.housecat
  Database          : Connected
  Drupal Bootstrap  : Successful
  Drupal User       : Anonymous

I apologize both for the length and the disorganization of this post. Also - this post is growing off-topic, sorry to contribute to its delinquency. If my notes above are in error, please politely let me know. I installed this six days ago and do not clearly remember what I did -- I tried many things and didn't take notes at the time.

Jason

Very cool to know about the other linux flavors .. I just figured since all the directions were debian/ubuntu thats the easier route to go. The bonus is that I prefer ubuntu and am not required to use anything on my servers. Makes total sense that it would work with any and apparently it does.

Sorry... I didnt mean to imply that debian/ubuntu was the only choice .. just that its the easiest.