My environment (I normally wouldn't bother to mention this, but this setup isn't typical):

- Ubuntu 10.04.3
- Nginx 1.0.5
- PHP-FPM 5.3.2
- MySQL 5.1.41

MySQL resides on its own machine, accessible from the Web server at 10.0.0.255, while the Web server is at 10.0.0.254 (on the local network).

Going through the instructions at: http://community.aegirproject.org/node/389 I get to the hostmaster-install step and the installation fails.

The only tweaky thing that had to be done was granting root permissions to the Web server for the database:

grant all privileges on *.* to 'root'@'10.0.0.254' with grant option;

Then the Drush command used to install hostmaster is:

drush hostmaster-install --http_service_type=nginx --aegir_db_host=10.0.0.255

This gets to installing the database and fails, see the attachments for details (they're huge walls of text, so thought it best not to paste them into the issue!):
aegirtrouble-web.txt - command line output from drush hostmaster-install;
aegirtrouble-db.txt - MySQL general query log;

Looking at the MySQL general log, it seems everything goes well but Aegir doesn't even attempt to create any database tables.

What is going wrong?

Comments

Liam McDermott’s picture

Just tried downgrading to PHP 5.2.17 and exactly the same thing happens. :/

Liam McDermott’s picture

FileSize
55.05 KB

Attached is the hostmaster-install with the --debug option on (on PHP 5.2). I stripped domain names and emails out of it, hope that doesn't matter.

Liam McDermott’s picture

Status: Closed (fixed) » Fixed

Finally found out what seems to have been the problem: using the MySQL root account.

Created a MySQL user called 'aegir', ran the same grant statement as above (but including identified by '<password>') and the installation works fine.

*** EDIT ***
Note: use the --aegir_db_user=aegir option when running hostmaster-install to change the user Aegir connects to MySQL with.

Status: Active » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.