If I remember correctly the user postgres has no DB password set on Ubuntu by default. That means, that you can login to that account only by using the postgres OS user account.Assuming, that you have root access on the box you can do:sudo -u postgres psqlIf that fails with a database “postgres” does not exists error, then you are most likely not on a Ubunutu or Debian server :- In this case simply add template1 to the command:sudo -u postgres psql template1If any of those commands fail with an error psql: FATAL: password authentication failed for user “postgres” then check the file /etc/postgresql/8.4/main/pg_hba.conf: There must be a line like this as the first non-comment line:local all postgres identFor newer versions of PostgreSQL ident actually might be peer. That’s OK also.Inside the psql shell you can give the DB user postgres a password:ALTER USER postgres PASSWORD ‘newPassword’;You can leave the psql shell by typing CtrlD or with the command \q.Now you should be able to give pgAdmin a valid password for the DB superuser and it will be happy too. :-share|improve this answer
If you still cannot connect: check that Tomcat has indeed started and is listening on port 8080: sudo fuser -v -n tcp 8080 Expected output: USER PID ACCESS COMMAND 8080/tcp: tomcat pid F…. java check that your instance’s security group permits inbound connections to port 8080 from your IP address. To have Tomcat start automatically on instance boot, issue the following commands: sudo chkconfig –level 345 tomcat6 on chkconfig –list Expected output: . . . tomcat6 0:off 1:off 2:off 3:on 4:on 5:on 6:off . . .SummaryAs you can see, installing Tomcat from the official Amazon Linux repo is a breeze, with all the housekeeping taken care of: binaries, config files, and user data are distributed nicely among /usr, /etc, and /var, a dedicated non-privileged account is created, file and directory permissions are set accordingly, log rotation is enabled, and a proper service script is installed.There are just two problems: You get specific versions of Java, Tomcat, and supplementary libraries, whereas your Web application may require or may have been tested on different versions. The tomcat6 package has lots of dependencies some of which you may not need, and others may be specific versions that are incompatible with your Web app. Run yum deplist tomcat6 to see the dependencies. Note that this command only shows the immediate dependencies of the given package.In the follow-up articles, we’ll discuss how to install your preferred versions of Java and Tomcat, advanced configuration topics, and the protection of your Web applications.
Wildcard DNS for WordPress MultisiteIf you are going to be using wildcard subdomains on a WordPress multisite installation then you will need to add a wildcard sub domain to your DNS records, however in Kloxo the process is a little different.To configure subdomains as wildcard you will need to add a server alias in Kloxo, usually you will add a wildcard DNS record in CPanel etc but in Kloxo you will need to add a server alias instead of manage DNS.The server alias option is located under the extra section, to find it you will need to click on the domain you want to add an alias for, then look for server alias under extra. Then in the empty field just add an asterisk and click on add, and kloxo will do the rest for you and now should be able to use wildcard subdomains for your WordPress multisite using Kloxo. So here are the instructions again if the above is a little complicated. click on the domain you want to use click on extra find server alias in the empty field add and asterisk click add.