Hi,
Just trying to get my head around how the install works, what needs doing and the best way to set it up.
I grabbed the install file from :
http://drupalcode.org/viewvc/drupal/contributions/profiles/hostmaster/in...
As directed from here :
http://drupalcode.org/viewvc/drupal/contributions/profiles/hostmaster/IN...
The insall failed as I haven't changed the WEB_GROUP to the user I'm running the aegir set up as, changed that and then :
Do you want to proceed with the install? [Y/n] Y
==> Creating basic directory structure
==> Drush found in /home/tadmin/drush/drush.php, good
==> Drush seems to be functionning properly
==> Drush make already seems to be installed
==> Provision already seems to be installed
sed: can't read /home/tadmin/hostmaster-6.x-0.4-alpha2/profiles/hostmaster/apache2.conf.txt: No such file or directory
And it's installed hostmaster-6.x-0.4-alpha2 into the home dir opposed to the web root, or even the hostmaster/ folder I set up for it and ran install.sh from.
Comments
Comment #1
Anonymous (not verified) commentedIt installs it into the location defined by HOSTMASTER_DIR in the script, not from where you run the install.sh.
What I'm confused about is that the version you're saying has been installed is 6.x-0.4-alpha2 - did you set this in the install.sh as the AEGIR_VERSION? Out of the box, it will currently install HEAD.
The sed error means that the dir or the file isn't actually there, so perhaps something else went wrong during the install.
You may need to just remove stuff from /home/tadmin (all hostmaster dirs, drush, and .drush) and rerun the install script. I would recommend leaving the AEGIR_VERSION as HEAD at the moment as opposed to 6.x-0.4-alpha2, as all the drush_make logic that the install script uses, is newer than that of 0.4-alpha2.
Comment #2
JerryH commentedHave updated install so these are correct now :
AEGIR_DOMAIN=hostmaster.mysite.com
AEGIR_VERSION=HEAD
AEGIR_HOME=/home/tadmin/www/hostmaster
WEB_GROUP=tadmin
HOSTMASTER_DIR=/home/tadmin/www/hostmaster/hostmaster-HEAD
DRUSH=/home/tadmin/www/hostmaster/drush/drush.php
DRUSH_VERSION=All-Versions-2.1
Running again.
Comment #3
JerryH commentedYup, seems to be looking for a non-exsistant file :
I'll carry on and see how it did.
No profile
Same in sites/all/modules, no hostmaster modules or set up etc.
Comment #4
Anonymous (not verified) commentedPer IRC conversations. The issue (there were in fact several) here was that the AEGIR_HOME parameter had been set to something other than ~, so .drush and drush_make/provision were getting put into an erroneous dir that in turn caused $DRUSH make hostmaster make to fail.
Comment #5
JerryH commentedTesting now to see that it is the requirement that aegir be in the doc root and can't be installed in a sub dir to be part of a larger set up, that it has to be stand alone.
Comment #6
JerryH commentedSo I sed up a whole new VPS just to ensure it's own doc root as advised and now it just fails in another way.
Comment #7
Anonymous (not verified) commentedThis is clearly either a) an issue with your network/firewall on your VPS or b) network/firewall issues at cvs.drupal.org
Drush_make depends on a working network to be able to retrieve packages from various locations (in this case cvs)
Comment #8
Anonymous (not verified) commentedAlso note that you didn't modify the aegir domain name in the install.sh:
You'll have to do a bit of editing later to sort this out if you don't change it here! Or are you modifying them here for the sake of the ticket.
Why is this blank?
Comment #9
JerryH commentedI did edit example.com to what it is, I suppose I should quote with mysite.com....... I just don't fancy sharing the TLD atm.
I've updated WEB_GROUP=aegir, not sure why I missed that.
Comment #10
Anonymous (not verified) commentedNo worries.
WEB_GROUP should be www-data. And you will have added aegir to the www-data group per the instructions you first followed in INSTALL.txt :)
Comment #11
JerryH commentedEven if the group www-data doesn't exist I take it ? opposed to the group aeigr that does exist and which the context for the webserver and set up is running as.
Maybe I have to set that up, reconfigure apache and the group systems on the whole server, given the way this is set up I'd think it would be easier to release a ISO with a server build image ;) !
I'm going to give it a go with the group aeigr.
Comment #12
Anonymous (not verified) commentedIt isn't that the www-data group needs to exist: whatever OS you are running with Apache, you have an Apache group of some sort (sometimes called www-data, sometimes apache, etc). Aegir user needs to be a member of this group.
I don't know if it would be easier to release an ISO. I don't want to maintain a full Linux distribution with Aegir on top, that is something already sort of being achieved by the guys at Chapter Three with their Aegir AMI. This install should only take minutes :)
Comment #13
JerryH commentedOK massively closer now I think ............
I used aegir for the group as it's all the same in this VPS (which I set up just for this) and that seems fine.
All the way down to :
OK> Choose profile
OK> Choose language
OK> Verify requirements
OK> Set up database
OK> Install profile
OK> Configure site
OK> Getting started
OK> Web server
OK> Filesystem
OK> Database server
OK> Features
Here > Initialize system
13. Verify settings
14. Import sites
15. Finalize
16. Finished
And tripped up on the permissions, just getting the correct user perms set up to run :
Though from the error it gave me (where I spotted that I needed to sort out the permissions) :
It appears that it's not using the table prefix, which is aegir_ so it should be : aegir_aegir.aegir_node ( yes the dB is called aegir_aegir !).
Is there a {node} or prefix add missing some where ?
I'm going to have to check out the script for "hosting setup" as well before I run that as root on the server, I want/need to know exactly what it does.
Comment #14
JerryH commentedAny clues as where to look for what :
drush.php hosting setup
Will do ?
Before I run things like that I want to know what it's going to do.
Comment #15
Anonymous (not verified) commentedhosting_setup() in hosting.module
It runs the initial dispatch to verify the first platform / import the main aegir site. It then adds the dispatch command to the aegir user's crontab, which does the job of polling the queue to execute any pending tasks created via the frontend.
Comment #16
Anonymous (not verified) commentedThe instructions state that you must *not* run this command as the root user. It must be run as the aegir user, and executed while your pwd is /var/aegir/(platform) .
Comment #17
JerryH commentedWhich when I do I get this :
I typically don't accept "Oh just run it" instructions either, hence why I'm dredging though the code to try and find it, so I can see what it's going to do.
Comment #18
Anonymous (not verified) commentedYes that is a clear error that shouldn't occur and needs investigating. I also don't give 'just run it' instructions so we're a good match :) .
The first thing that comes to mind is that you haven't run the command whilst cd'd into the /var/aegir/(your platform) directory. That's what that rather concise error usually means - the inability to *find* Drupal.
Comment #19
JerryH commentedWell the installer itself says to run it and I'm not 100% sure what it does, and I get that error from the dir I ran install.sh in, so I'm looking for an explanation of what it does before I do figure out how to get it, running and then do so.
Back at home now opposed to work, so it can wait for Monday and now is beer o'clock !
Comment #20
Anonymous (not verified) commentedI gave you the explanation in #15 on what the command does.
The installer says to run it as the aegir user, from inside the directory of the main aegir platform (i.e /var/aegir/hostmaster-0.4-alpha3 or somesuch) .
If you get the error from running it from where you ran the install.sh, and the install.sh is not in the directory of your main aegir platform, then yes, you will get an error.. if you instead run it per the instructions, you'll likely not get an error. :)
Good luck!
Comment #21
JerryH commentedWell irrespective of the RTFM .......... ;)
The error is the same.
The instructions :
Are followed to the letter, and result it :
That line is :
Elsewhere {node} is correctly used it seems, so I suspect that someone is developing on a site with no table prefix (tsk tsk ;) ), or table prefixes not allowed in Aegir ?
And the function above for that matter :
Comment #22
JerryH commentedWell opposed to "run it per the instructions" as I was, fixing those errors in coding seemed to do the trick ;)
Not sure what the "Password:" echo is about, investigating now.
Comment #23
JerryH commentedSo the only 3 things on the next page were :
Apache I know about and can deal with that, that's just adding the user to the group that is allowed to run 'apachectl graceful'.
I have no sites to import at the moment, so am now playing in what looks like a set up Aegir with a very sexy theme !
Now ................. just have to figure out how to use it to create sites :)
Comment #24
Anonymous (not verified) commentedAnd the user not having sudo rights to restart apache without a password was the cause of the Password: prompt.
The references to the node table are indeed missing their curly brackets here, I will fix that up, thanks for bringing that to our attention.
Comment #25
Anonymous (not verified) commentedtable prefix bracket stuff fixed in git http://git.aegirproject.org/?p=hostmaster.git;a=commitdiff;h=e51a542fc85...
Comment #26
JerryH commentedYippie I helped out :) !!!