Aegir install/update fails, apache "It Works!" message accesible though

The essence is:

err: /Stage[main]/Aegir-up/Group[aegir group]/ensure: change from absent to present failed: Could not create group aegir: Execution of '/usr/sbin/groupadd -g 20 aegir' returned 4: groupadd: GID '20' already exists

Please try the latest changes in drush-vagrant and aegir-up.

This was from a very old version, before splitting out drush-vagrant. So, I'm closing as 'cannot reproduce'. Feel free to re-open (or start a new issue) if you see this with the current versions.

With the very latest 7.x-2.x branches of aegir up and drush vagrant, I get the same symptoms.

I can SSH in, get the "It Works" apache page, I even see

Welcome to your LAMP virtual machine!
              Built by Vagrant. Managed by Puppet.

              Developed and maintained by Ergon Logic Enterprises.

when I login. But no aegir user.

The error messages that were red flags for me:

[aegir-dev1] Importing base box 'debian-LAMP-2012-03-29'...
[aegir-dev1] The guest additions on this VM do not match the install version of
VirtualBox! This may cause things such as forwarded ports, shared
folders, and more to not work properly. If any of those things fail on
this machine, please update the guest additions and repackage the
box.

Guest Additions Version: 4.1.8
VirtualBox Version: 4.1.18

Then, at the end of the script, I get:

[aegir-dev1] Running Puppet with /tmp/vagrant-puppet/manifests/site.pp...
stdin: is not a tty
notice: Scope(Class[Aegir_up]): 

          Running Puppet manifests to install and/or update Aegir.

          This may take awhile, so please be patient.
          For more detail on the operations being run, edit settings.rb,
          and set 'verbose = 1'.

warning: Dynamic lookup of $aegir_web_group at /tmp/vagrant-puppet/modules-1/aegir_up/manifests/init.pp:22 is deprecated.  Support will be removed in Puppet 2.8.  Use a fully-qualified variable name (e.g., $classname::variable) or parameterized classes.

warning: Dynamic lookup of $aegir_dev_build at /tmp/vagrant-puppet/modules-1/aegir_up/manifests/init.pp:26 is deprecated.  Support will be removed in Puppet 2.8.  Use a fully-qualified variable name (e.g., $classname::variable) or parameterized classes.

warning: Dynamic lookup of $aegir_dev_build at /tmp/vagrant-puppet/modules-1/aegir_up/manifests/init.pp:36 is deprecated.  Support will be removed in Puppet 2.8.  Use a fully-qualified variable name (e.g., $classname::variable) or parameterized classes.

Could not find class aegir::queued for aegir-dev.devshop.local at /tmp/vagrant-puppet/modules-1/aegir_up/manifests/init.pp:38 on node aegir-dev.devshop.local

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

cd /tmp/vagrant-puppet/manifests && FACTER_fqdn='' FACTER_username='jon' FACTER_git_name='Jon Pugh' FACTER_git_email='jon@thinkdrop.net' FACTER_uid='1000' FACTER_gid='1000' FACTER_aegir_user='aegir' FACTER_aegir_root='/var/aegir' FACTER_aegir_user_exists='true' FACTER_aegir_version='6.x-1.9' puppet apply  --modulepath '/tmp/vagrant-puppet/modules-0:/tmp/vagrant-puppet/modules-1' /tmp/vagrant-puppet/manifests/site.pp
The following errors occurred when running "vagrant up":                                                  [error]
Drush command terminated abnormally due to an unrecoverable error.                                        [error]

I installed vagrant via sudo apt-get install vagrant on Linux Mint 12, but I think the problem is the different versions of guest box additions and virtualbox itself.

Forgot to mention, Tizzo's blog tipped me off to the problem of VBox guest additions version problems: http://www.zivtech.com/blog/one-click-automated-vagrant-base-box-builds-...

Could not find class aegir::queued for aegir-dev.devshop.local at /tmp/vagrant-puppet/modules-1/aegir_up/manifests/init.pp:38 on node aegir-dev.devshop.local

This indicates that a puppet class is missing.
Check the 'lib/puppet-modules/aegir' in aegir-up, it's a git submodule.

git submodule init
git submodule update

I just now noticed there are submodules in the repo, then saw your reply. Thanks for the heads up, will try this soon!

Ok, it removed that warning, and I built a new project and got this:

Could not find dependency Exec[drush-dl-hosting_queued] for Exec[drush-en-hosting_queued] at /tmp/vagrant-puppet/modules-0/drush/manifests/en.pp:11

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

cd /tmp/vagrant-puppet/manifests && FACTER_fqdn='' FACTER_username='jon' FACTER_git_name='Jon Pugh' FACTER_git_email='jon@thinkdrop.net' FACTER_uid='1000' FACTER_gid='1000' FACTER_aegir_user='aegir' FACTER_aegir_root='/var/aegir' FACTER_aegir_user_exists='true' FACTER_aegir_version='6.x-1.9' puppet apply  --modulepath '/tmp/vagrant-puppet/modules-0:/tmp/vagrant-puppet/modules-1' /tmp/vagrant-puppet/manifests/site.pp
The following errors occurred when running "vagrant up":                                                  [error]
d7
Drush command terminated abnormally due to an unrecoverable error.   

I too am getting a similar error, seen below.

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

cd /tmp/vagrant-puppet/manifests && FACTER_fqdn='' FACTER_username='root' FACTER_git_name='Paul McCrodden' FACTER_git_email='mccrodp@678774.no-reply.drupal.org' FACTER_uid='0' FACTER_gid='0' FACTER_aegir_user='aegir' FACTER_aegir_root='/var/aegir' FACTER_aegir_user_exists='true' FACTER_aegir_version='6.x-1.9' puppet apply  --modulepath '/tmp/vagrant-puppet/modules-0:/tmp/vagrant-puppet/modules-1' /tmp/vagrant-puppet/manifests/site.pp --detailed-exitcodes || [ $? -eq 2 ]
Retrieved the FQDN for the aegir-up1 VM.                                                              [ok]
Retrieved the IP address for the aegir-up1 VM.                                                        [ok]
Wrote project aliases file to /var/root/.drush/myaegirbox.aliases.drushrc.php.                        [ok]
Enter your password to add entries for the VMs in your project to your /etc/hosts file.
Your project was successfully initialized.
The root for your project is "/var/root/vagrant/projects/myaegirbox"
The subnet for your project has been set to 192.168.11.0, and an initial entry in your /etc/hosts file written.
You can now: * Alter the behaviour of your project by editing /var/root/vagrant/projects/myaegirbox/settings.rb.
             * Redefine the VM(s) by editing the Puppet manifest(s) in /var/root/vagrant/projects/myaegirbox/manifests.
             * Add additional Puppet modules by copying them to /var/root/vagrant/projects/myaegirbox/modules.

I can ssh into the box using vagrant ssh but the aegir directory is not mounted and I cannot mount it using (Connect to server) nfs://192.168.11.0 or smb://192.168.11.0 or using the path nfs://192.168.11.0/var/aegir, seems like the ip is invalid, I get a timeout when I ping 192.168.11.0 too. I am not sure if this is related to the above error however. I am looking for a pointer in the right direction (info or link to docs) on.

• Solving the above error
• How to mount on Mac Os X (Mountain Lion)
• How to test Hostmaster 6.x-2.0 and specific code branches, do I edit settings.rb and somehow refresh?

Any help at all on any of the above is appreciated. Thanks,
Paul.

I believe the problem stems from FACTER_fqdn=''. That should have the URL of the vm inserted by Vagrant. Try replacing $hostname in .config/config.rb, with a string of the hostname for the project, and re-run provisioning.

running into this on 2.x

i tried replacing $hostname with "myhost" and rebuilt the machine (which seems to rerun provisioning)
but to no avail. the errormessage just reads FACTER_fqdn='myhostname'.

using drush_vagrant 3.x

using drush vagrant 2.x i get a different result, it seems drush cannot be located. is this the same issue as http://drupal.org/node/1889668 ?

Hi ergonlogic, I guess when you say 're-run provisioning', you don't mean build a new project by running drush vagrant-build --blueprint=aegir because it won't proceed with a project of the same name when it already exists. If I delete my project 'aegir-test1' I'll also be deleting $hostname replacement in ./vagrant/projects/aegir-test1/.config/config.rb

I've run drush vagrant rebuild and drush vagrant rebuild aegir-test1, but I'm not getting anywhere. I know this is a standard vagrant error, but I'm not sure if this is how I should re-provision. Do you have any specific instructions that may help or plausible methods to fix this 'FACTER_fqdn' issue for the project itself? Thanks

Macbook:~ root# drush vagrant rebuild
!!! WARNING: This operation cannot be undone. !!!
This operation will destroy all VMs in "projects". And build a fresh set afterwards.
Are you certain that you want to proceed? (y/n): y
A Vagrant environment is required to run this command. Run `vagrant init`
to set one up.
Macbook:~ root# vagrant init
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
Macbook:~ root# drush vagrant rebuild
!!! WARNING: This operation cannot be undone. !!!
This operation will destroy all VMs in "projects". And build a fresh set afterwards.
Are you certain that you want to proceed? (y/n): y
[default] VM not created. Moving on...
There was a problem with the configuration of Vagrant. The error message(s)
are printed below:

vm:
* The box 'base' could not be found.


Macbook:~ root# drush vagrant rebuild aegir-test1
!!! WARNING: This operation cannot be undone. !!!
This operation will destroy all VMs in "projects". And build a fresh set afterwards.
Are you certain that you want to proceed? (y/n): y
[default] VM not created. Moving on...
There was a problem with the configuration of Vagrant. The error message(s)
are printed below:

vm:
* The box 'base' could not be found.

I believe you are looking for the command vagrant provision [vm-name]

Thanks DanyO, I ended up finding this command a bit after posting the above, but still unsure how to use it in this case with aegir-up.

I built a project using drush vagrant-build --blueprint=aegir called 'aegir-up-test' and after seeing the empty FACTER_fqdn I edited the $hostname in ./vagrant/projects/aegir-up-test/.config/config.rb. As this is a project and not a VM, vagrant provision aegir-up-test obviously doesn't work. The VM that vagrant-build downloads is a lucid32 box, so to re-provision I ran the following commands as the VM needs to be 'up' when you re-provision it seems.

• vagrant init lucid32
• vagrant up
• vagrant provision

It doesn't seem to re-run or at least output the same logging to the screen as is output when you run drush vagrant-build, so I'm not sure if I have re-provisioned correctly or how to test if I have. I guess this is still an issue though if it fails in the first place? I'm just not sure how to go about helping with solving it yet with my current knowledge of Aegir-Up and where the $hostname value is supposed to come from.

It'd be great to get some testing of the latest release: 7.x-2.0-alpha3.

I think the fqdn thing is a red herring, as I don't think it's even used anymore... That is, I get the same FACTER_fqdn='' output whenever an unrelated error occurs, but otherwise this works fine. I'll need to clean that up, but I don't think it's the root of this issue.

I suspect it has to do with having switched to Git submodules for Puppet modules, which isn't supported by drupal.org's packaging script (see:#1532248: Remove --recursive from git clone text on Drupal.org's version control tab ). As a result, git cloning the repo with '--recursive' will also clone the relevant repos containing the Puppet modules, while installing via 'drush dl aegir-up' won't. This made for difficult debugging, since I assumed that the packaged version would match what's in the git repo.

I've switched to using librarian-puppet to manage Puppet modules in Aegir-up. Basically, it'll fetch the modules, and I can then just commit them directly into the repo. I'll have to check whether there are some straggler in drush-vagrant though.

I had the problem mentioned in #7 - basically the whole setup of aegir that where supposed to happen before the module was attempted enabled never did so.

So - I cloned the aegir-up repo, checked out 7.x-2.0-alpha3 and did a fresh drush vagrant-build --blueprint=aegir-dev

The provisioning of the box seems to be working better now, but I now get the following errors

err: /Stage[main]/Aegir_up/Group[aegir group]/ensure: change from absent to present failed: Could not create group aegir: Execution of '/usr/sbin/groupadd -g 20 aegir' returned 4: groupadd: GID '20' already exists

notice: /Stage[main]/Aegir_up/User[aegir user]: Dependency Group[aegir group] has failures: true
warning: /Stage[main]/Aegir_up/User[aegir user]: Skipping because of failed dependencies
notice: /Stage[main]/Aegir::Manual_build::Backend/File[/var/aegir]: Dependency Group[aegir group] has failures: true
warning: /Stage[main]/Aegir::Manual_build::Backend/File[/var/aegir]: Skipping because of failed dependencies

A group with GID 20 already exists (dialout) which causes all sorts of problems as a lot of things depends on this step (such as the creation of the aegir user).

I ssh'ed in, deleted the dialout group, and did a vagrant provision. This time I got my login link and aegir is up and running :)

Two things i noticed during my debugging:
1: On the first run I got the following error

err: /Stage[main]/Apt/Exec[/usr/bin/apt-get update && /usr/bin/apt-get autoclean]/returns: change from notrun to 0 failed: /usr/bin/apt-get update && /usr/bin/apt-get autoclean returned 100 instead of one of [0] at /tmp/vagrant-puppet/modules-0/apt/manifests/init.pp:80

I ssh'ed in and did an apt-get update and it seems that there are some problems with the kumbit apt repo

vagrant@aegir-dev:~$ sudo apt-get update
Hit http://security.debian.org squeeze/updates Release.gpg
Ign http://security.debian.org/ squeeze/updates/contrib Translation-en
Ign http://security.debian.org/ squeeze/updates/contrib Translation-en_US
Ign http://security.debian.org/ squeeze/updates/main Translation-en
Ign http://security.debian.org/ squeeze/updates/main Translation-en_US
Ign http://security.debian.org/ squeeze/updates/non-free Translation-en
Ign http://security.debian.org/ squeeze/updates/non-free Translation-en_US
Hit http://security.debian.org squeeze/updates Release
Hit http://security.debian.org squeeze/updates/main amd64 Packages
Hit http://security.debian.org squeeze/updates/contrib amd64 Packages
Hit http://security.debian.org squeeze/updates/non-free amd64 Packages
Ign http://debian.koumbit.net squeeze Release.gpg
Ign http://debian.koumbit.net/debian/ squeeze/main Translation-en
Ign http://debian.koumbit.net/debian/ squeeze/main Translation-en_US
Hit http://debian.mirror.iweb.ca squeeze Release.gpg
Ign http://debian.koumbit.net squeeze Release
Hit http://backports.debian.org squeeze-backports Release.gpg
Ign http://backports.debian.org/debian-backports/ squeeze-backports/main Translation-en
Ign http://backports.debian.org/debian-backports/ squeeze-backports/main Translation-en_US
Ign http://debian.mirror.iweb.ca/debian/ squeeze/contrib Translation-en
Ign http://debian.koumbit.net squeeze/main amd64 Packages
Err http://debian.koumbit.net squeeze/main amd64 Packages
  404  Not Found
Hit http://backports.debian.org squeeze-backports Release
Ign http://debian.mirror.iweb.ca/debian/ squeeze/contrib Translation-en_US
Hit http://backports.debian.org squeeze-backports/main amd64 Packages
Ign http://debian.mirror.iweb.ca/debian/ squeeze/main Translation-en
Ign http://debian.mirror.iweb.ca/debian/ squeeze/main Translation-en_US
Ign http://debian.mirror.iweb.ca/debian/ squeeze/non-free Translation-en
Ign http://debian.mirror.iweb.ca/debian/ squeeze/non-free Translation-en_US
Hit http://debian.mirror.iweb.ca squeeze Release
Hit http://debian.mirror.iweb.ca squeeze/main amd64 Packages
Hit http://debian.mirror.iweb.ca squeeze/contrib amd64 Packages
Hit http://debian.mirror.iweb.ca squeeze/non-free amd64 Packages
W: Failed to fetch http://debian.koumbit.net/debian/dists/squeeze/main/binary-amd64/Packages.gz  404  Not Found

E: Some index files failed to download, they have been ignored, or old ones used instead.

2: In general I get a number of errors when i re-run provision such as a "git clone" of drush failing because it has already been done once. As it did not prevent me from getting everything up and running in the end it is not a dealbreaker, but it does make the whole process a bit harder to debug as you end up chasing error-messages that has nothing to do with the actual problem you are trying to fix.

Leaving the current issue as "needs work" in case someone has fixes for the above "sub" issues

@danquah Thanks for testing!

A group with GID 20 already exists (dialout) which causes all sorts of problems as a lot of things depends on this step (such as the creation of the aegir user).

Yeah, that group juggling is all legacy of trying to work around Vagrant limited NFS support. I think I'll just rip all that out, as it's not doing any good at this point.

I think the other problems were due to the puppet modules (apt, drush) being out-of-date. I'll try to tackle that shortly.

For the latter stuff, I updated drush-vagrant to use librarian-puppet in the 2.x branch, and updated the apt and drush modules. I also pushed a new release, as there had been quite a few changes since the last one. Try out drush-vagrant 7.x-2.0-beta7, as it should clear those up.

I still don't get this, re-downloaded latest version of drush, drush-host, drush-vagrant and aegir-up, followed the new "My Aegir Development Environment" and ran drush vagrant-build --blueprint=aegir-dev it bombs out at the end. The duplicate declaration I'm guessing is due to this being the second time I ran it, I deleted the project folder in the intrim and re-ran and got the below.

Duplicate declaration: Drush-vagrant::User_account[root] is already declared in file /tmp/vagrant-puppet/modules-0/drush-vagrant/manifests/init.pp at line 13; cannot redeclare at /tmp/vagrant-puppet/modules-0/drush-vagrant/manifests/init.pp:17 on node aegir-dev.aegir2-dev.local

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

cd /tmp/vagrant-puppet/manifests && FACTER_fqdn='' FACTER_username='root' FACTER_git_name='Paul McCrodden' FACTER_git_email='mccrodp@678774.no-reply.drupal.org' FACTER_uid='0' FACTER_gid='0' FACTER_aegir_user='aegir' FACTER_aegir_root='/var/aegir' FACTER_aegir_user_exists='true' FACTER_aegir_version='6.x-1.9' puppet apply  --modulepath '/tmp/vagrant-puppet/modules-0:/tmp/vagrant-puppet/modules-1' /tmp/vagrant-puppet/manifests/site.pp --detailed-exitcodes || [ $? -eq 2 ]
The following errors occurred when running "vagrant up":                                                                   [error]
Drush command terminated abnormally due to an unrecoverable error.                                                         [error]

It creates no Vagrantfile, so is that the reason vagrant up isn't working here. If so, where do I get you more information or logs for the error? I then ran vagrant init debian-LAMP-2012-03-29 and everything seems to be installed correctly. But this isn't the way to init the project, is it?

On a side note I don't understand how to re-provision using say my project name 'aegir2-dev' as mentioned earlier in the thread, but maybe I should post that over on aegir community page.

Which one do I edit and what do I run to take in these changes / branches as obviously after running vagrant-build, the defaults are already downloaded.

• ./.drush/aegir-up/blueprints/aegir-dev/manifests/nodes.pp
• ./.drush/drush-vagrant/blueprints/default/manifests/nodes.pp
• ./vagrant/projects/aegir2-dev/manifests/nodes.pp

As you stated, if the FACTER_fqdn='' is not related to the error in this issue, please let me know if there is another related ticket or if I should open a support request or separate bug issue.

Thanks.

@mccrodp The 'duplicate declaration' is due to 2 things. First, in updating the Puppet modules, the 7.x-3.x branch drush-vagrant module got included by mistake. I've fixed it, and pushed a new release.

In the 3.x branch, I have prototype code to add user dot files to the 'vagrant', 'root' and 'aegir' users. It appears that you are operating as the 'root' user (note: this is generally a bad idea). So, when it tries to create your user, it's conflicting with the settings it's trying to apply to 'root' by default.

It creates no Vagrantfile

I don't understand how that could be, since you couldn't have received the error above if that were the case. I guess technically it isn't creating a makefile, but rather it creates a symlink to a Vagrantfile in the drush-vagrant directory. If it's not creating that symlink, then that's a new issue. Please confirm it, and post a new bug report, if that's the case.

Which one do I edit [...] ?

You'll probably want to edit the one in the project itself. './vagrant/projects/aegir2-dev/manifests/nodes.pp' in your case.

To solve the following err :

err: /Stage[main]/Aegir_up/Group[aegir group]/ensure: change from absent to present failed: Could not create group aegir: Execution of '/usr/sbin/groupadd -g 20 aegir' returned 4: groupadd: GID '20' already exists

change your .drushrc.php GID variable to something else. I used 1001.
Destroy the vagrant instance and make a new one with the GID change in the .drushrc.php file and it won't show this error anymore.

As for the apt-get errors and empty FACTER_fqdn=''" variable, I was still able to ssh in and run these commands as root. By following these steps I got my aegir machine working in vagrant. Just remember to change to the user aegir to use drush commands, since it won't let you with root user. Hope this helps.

Thanks DanyO's, your solution in #20 above worked for me, it got to end of the build without errors (making sure not to run as root on my local machine). The Vagrantfile was being created in ./vagrant/projects/aegir2-dev, for some reason I expected it in the directory I ran vagrant-build. I do have some errors when running an update on the VM though.

apt-get update
.
.
.
W: GPG error: http://debian.koumbit.net stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6DC388D8B7C0A70A

I wanted to then use for example a different provision branch and edited ./vagrant/projects/aegir2-dev/manifests/nodes.pp to use the branch 'dev-1205458-move_sites_out_of_platforms' described in My Aegir Development Environment

I then ran the following, but it doesn't pick up the 'dev-1205458-move_sites_out_of_platforms' branch.

vagrant halt

vagrant up

vagrant ssh

apt-get update

cd /var/aegir/.drush/provision
git branch
* 6.x-2.x