what i did:

1. fresh install on my VDS of Debian Squeeze
2. *.domain.com A record pointing to my IP-address
3. $ apt-get install vim
4. commented out a few lines in .bashrc to get colouring on $ ls
5. $ vim /etc/hosts to include "IP-address vds1.domain.com vds1"
6. followed instructions for BARRACUDA script
7. script completed successfully, no errors or warnings except:
- Dropping test database...
ERROR 1008 (HY000) at line 1: Can't drop database 'test'; database doesn't exist
... Failed! Not critical, keep moving...
- Removing privileges on test database...
8. i visit aegir.domain.com, and i see chive
9. i log in to chive, i log out of chive
10. i try $ service nginx restart, $ service php-fpm restart, $ reboot a few times each
11. i still see chive at aegir.domain.com
12. i notice that in /var/aegir/install.log there is the following line, but am unsure if it is a red herring:
SQLSTATE[HY000] [2003] Can't connect to MySQL server on 'vds1.domain.com.au' (101) ^[[31;40m^[[1m[error]^[[0m
Unable to connect to database server.

i'm not sure if it is worth contacting the host to re-image my VDS to try again, or if there is more i can do now.

from what i've read elsewhere, if you run the script and it doesn't work as expected the usual recourse is to try again from scratch..

Comments

omega8cc’s picture

Your step #5 caused problem at #12. It failed to install Hostmaster.

In short: you should never touch *anything* on the server before running Barracuda or you will get weird results like above.

omega8cc’s picture

Also, you don't need to start from scratch but you need:

1. $ deluser aegir
2. $ rm -f -r /var/aegir
3. set mysql root to be able to connect without password as shown below:

mysql
FLUSH PRIVILEGES;
GRANT ALL PRIVILEGES ON *.* TO 'root'@'localhost' IDENTIFIED BY '' WITH GRANT OPTION;
FLUSH PRIVILEGES;
exit

4. $ rm -f /root/.my.cnf /root/.my.pass.txt

Then run Barracuda again.

thedavidmeister’s picture

i'm confused. I thought that if i didn't do my step 5 then i wouldn't have a FQDN.

when i get a fresh install from the host i get a line in my hosts file that looks like:

"IP-address some-domain.com"

but some-domain.com is not the right domain, it is related to the name of my account with the host (my company name), but not a real-world DNS configuration.

i thought it would be smarter to set this to:

"IP-address correct-domain.com"

but maybe i should delete that line altogether and let Barracuda do its magic for me?

thedavidmeister’s picture

commenting out that line hits me with:

Barracuda [Thu Aug 4 15:07:17 EST 2011] ==> EXIT on error due to invalid DNS setup.

thedavidmeister’s picture

i tried a slightly different workflow after re-imaging and it worked.

i'd love to get omega8cc to close this issue if i didn't do something totally evil that will cause issues down the track.

1. Fresh install from host
2. $ apt-get install vim
3. vim /etc/hosts
4. make sure there's a line that reads "IP-Address server.domain.com server"
5. $ hostname server.domain.com
6. check that "$ hostname -f" returns server.domain.com
7. follow instructions as per INSTALL.txt

without steps 3-6 i was hitting the error mentioned in #4

thedavidmeister’s picture

the workflow i outlined in #5 just worked a second time for me on a different VDS.

i have a feeling that steps 3-6 might be necessary for some hosting configurations. Would it be worth stating them somewhere obvious in the docs, or am i experiencing an edge-case here?

omega8cc’s picture

You shouldn't have any line in /etc/hosts related to any domain or IP other then localhost, normally.

Instead, you should use something like:

_MY_OWNIP="12.34.56.78"
_MY_HOSTN="server.your.domain"
_MY_FRONT="aegir.your.domain"

Then Barracuda should be able to do the magic for you.

If you are still receiving errors like "EXIT on error due to invalid DNS setup." and you are sure that your FQDN hostname resolves properly then it is possible that Barracuda fails to perform the DNS test for some reason we didn't catch yet, so you could try to disable the DNS test and see if that helps.

_DNS_SETUP_TEST=NO

When you are disabling DNS test it is also a good idea to use options:

_HTTP_WILDCARD=YES
_THIS_DB_HOST=localhost

It could be useful for debugging if you will post results of commands:

host your.domain
dig your.domain
uname -n
hostname

thedavidmeister’s picture

the instructions in #7 are a bit different from what is in the readme.

Everything seems to be working for me now, but if i need to re-install BOA i'll try what you've written, thanks.

is it safe for me to post the results of those commands here?

omega8cc’s picture

Status: Active » Closed (duplicate)

If you are using CNAME and not IN A in your DNS, then check this issue for follow-up: #1248432: BOA install fails when its subdomain has CNAME and not IN A DNS record