Hello, I think I'm very close to having Aegir-up running on my Ubuntu machine. I'm hoping to use it to test platform builds and sites before deploying to my live server. I'm getting an error during the build that I can't figure out, its below. If this looks like a common n00b mistake, please let me know. Thanks!
[hm] Running Puppet with /tmp/vagrant-puppet/manifests/hm.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'.
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 0 aegir' returned 4: groupadd: GID '0' already exists
Comments
Comment #1
ergonlogicHi there. I'm glad you're getting close to having Aegir-up running. Don't worry about something being a "common n00b mistake". If it were, I should either make it more intuitive, or at least document it better :)
So, as far as the problem you're facing goes, are you perhaps running commands as root? Aegir-up will mount the /var/aegir/ directory via NFS, and thus requires that the 'aegir' user's uid and gid in the VM, match your user's uid & gid on the host. Running 'drush aegir-up-user' will generate a ~/.drushrc.php file that contains your uid & gid, among other things. Perhaps check that it's accurate, and re-run the command to regenerate that, if not.
Comment #2
leevh commentedThanks for that ergonlogic, you were correct, I was having trouble with drush unless I was root, but I got that part solved now. I've made sure the ~/.drushrc.php looks good, and has all my user info correctly. I also used "git config --global" to set my git name and email, thinking that was the issue. I am still getting the following errors that I cannot decipher. I did find changing the git username/email to something else in my .drushrc.php got rid of the first two errors... though I'm not sure why. Thanks for any info, its greatly appreciated
Comment #3
ergonlogicI'm not sure why the Git settings are failing.
For the next stuff, it's basically trying to find some files that don't exist; specifically, '.vimrc' and '.bash_aliases'. I'll add some checks for these in the next release. In the mean-time for this workspace, you can run:
This will create empty files that Aegir-up will pick up, and avoid the errors. To avoid this error on subsequent workspaces, you can run the same in your home folder (e.g., touch ~/.vimrc).
Finally, the installation of the Hostmaster site itself is timing-out. I've seen that occasionally recently, but I haven't figured out why yet. Re-running 'vagrant provision' usually shows that the install worked. Unfortunately, you probably won;t be given the one-time login link, in this case. So, you'll have to do something like the following:
Comment #4
ergonlogicI'm not sure why the Git settings are failing.
For the next stuff, it's basically trying to find some files that don't exist; specifically, '.vimrc' and '.bash_aliases'. I'll add some checks for these in the next release. In the mean-time for this workspace, you can run:
This will create empty files that Aegir-up will pick up, and avoid the errors. To avoid this error on subsequent workspaces, you can run the same in your home folder (e.g., touch ~/.vimrc).
Finally, the installation of the Hostmaster site itself is timing-out. I've seen that occasionally recently, but I haven't figured out why yet. Re-running 'vagrant provision' usually shows that the install worked. Unfortunately, you probably won;t be given the one-time login link, in this case. So, you'll have to do something like the following:
Comment #5
ergonlogicI'm closing this issue, since I'm cleaning up the queue for a 0.2 release based on drush-vagrant, and this is likely no longer relevant. Feel free to re-open, or better yet, post a new issue referencing this one, if needed.