anarcat@marcos:vagrant_scripts_aegir$ nice fab vagrant aegir_apt_install:distro=unstable
[localhost] local: vagrant ssh-config | grep User
[localhost] local: vagrant ssh-config | grep HostName
[localhost] local: vagrant ssh-config | grep Port
[localhost] local: vagrant ssh-config | grep IdentityFile
[127.0.0.1:2222] Executing task 'aegir_apt_install'
===> Preparing the Aegir user
[127.0.0.1:2222] sudo: useradd -r -U -d /var/aegir -m -G www-data aegir
[127.0.0.1:2222] sudo: echo 'aegir ALL=NOPASSWD: /usr/sbin/apache2ctl' >> /etc/sudoers
===> Adding apt sources
[127.0.0.1:2222] sudo: curl http://debian.aegirproject.org/key.asc | apt-key add -
[127.0.0.1:2222] out: /bin/bash: curl: command not found
[127.0.0.1:2222] out: gpg: no valid OpenPGP data found.


Fatal error: sudo() received nonzero return code 2 while executing!

Requested: curl http://debian.aegirproject.org/key.asc | apt-key add -
Executed: sudo -S -p 'sudo password:'  /bin/bash -l -c "curl http://debian.aegirproject.org/key.asc | apt-key add -"

Aborting.
Disconnecting from 127.0.0.1:2222... done.

boom!

Comments

anarcat’s picture

anarcat commented

Actually, that was my error - I interrupted the first vagrant up and that's what happened ... I have since then destroyed and re-up'd, and now I get this:

WARNING: /etc/aliases exists, but does not have a root alias.

Postfix is now set up with a default configuration.  If you need to make
changes, edit
/etc/postfix/main.cf (and others) as needed.  To view Postfix configuration
values, see postconf(1).

After modifying main.cf, be sure to run '/etc/init.d/postfix reload'.

Running newaliases
newaliases: warning: valid_hostname: misplaced delimiter: lucid64.hsd1.ca.comcast.net.
newaliases: fatal: file /etc/postfix/main.cf: parameter myhostname: bad parameter value: lucid64.hsd1.ca.comcast.net.

Of course the fabfiles then fails too...

Fun times! :)

steven jones’s picture

steven jones commented

Ah, I've had this error before. Seems that the guest machine tries to work out its hostname, and use that as a default setting for postfix, but doesn't actually default to a valid hostname I think.

I'm not sure of the solution, but maybe we should just set the hostname of the machine as part of the box initialisation script, and then postfix wouldn't fail like this.

steven jones’s picture

steven jones commented
Status: Active » Closed (duplicate)

Actually helmo reported this first: #1829968: Postfix fails to install because the hostname has a trailing dot.