On Fri, Nov 4, 2011 at 21:13, Thornton, Susan M. (LARC-B702)[LITES] <[email protected]> wrote: > 1. I can connect to the server via port 22 with secure shell and > secure ftp clients, but I cannot connect to the postgres databases on port > 5432 (via PGAdminIII). The postgres error says the “Server doesn’t > listen”. Postgres is up and running on the machine – the old 1.5.1 instance > is still up and using it. Normally I see this error if the postmaster is > not running on the server and this can be corrected by starting it. I can > connect to the databases on the server using psql – command line, but of > course this is cumbersome.
Hi Sue, regardless of your firewall setting, Postgres restricts in its default configuration that you can connect to it only from localhost. There are actually 2 places in configuration that control this. You can verify that this is the problem by looking at output from sudo netstat -tulpn | grep 5432 If you see only "127.0.0.1:5432", it means it is listening only to connections from localhost (that means you can psql from localhost, but not from another machine). What you want to see there is that it listens on your real network interface or on all network interfaces: "0.0.0.0:5432". To achieve that, edit /etc/postgresql/8.4/main/postgresql.conf and change the listen_addresses = 'localhost' line to listen_addresses = '*' (that means postgres should listen on all network interfaces). That by itself is still not enough, you have to explicitly say which machines are allowed to access postgres. Look at the bottom of the /etc/postgresql/8.4/main/pg_hba.conf file and add a line like this to allow a single IP to access postgres: host all all 1.2.3.4/32 md5 That /32 is CIDR notation for netmask 255.255.255.255, meaning only this one IP. Of course you can allow a whole subnet this way, too. Don't forget to run "service postgresql restart" (or whatever the latest fashion on Solaris is) after you change the configuration. You may need to restart Tomcat afterwards to reconnect, I don't remember. > 2. I am getting errors when I try to assemble the 1.7.1 application as > follows: > > mvn -U clean package > > [INFO] Scanning for projects... > > Downloading: > http://repo1.maven.org/maven2/org/dspace/dspace-pom/10/dspace-pom-10.pom This is a pretty common error, you will find solutions if you search dspace-tech. Since you ran "clean", you have to download dependencies from maven again. The problem is your machine cannot fetch the file. This is usually a firewall problem. To verify, just run wget http://repo1.maven.org/maven2/org/dspace/dspace-pom/10/dspace-pom-10.pom The solution depends on how you're allowed to access the internet from the dspace machine. If you're using a firewall, unblock outgoing connections so that you can download from the internet. If you have to use a proxy, configure maven to use proxy (search this list). If you cannot allow the machine to connect to the internet at all, run mvn package in [dspace-src] on another machine which is allowed to download; it will fetch the artifacts; then copy the [dspace-src] directory to your dspace machine and always run "mvn package" without "clean". Let us know if it helps, good luck. Regards, ~~helix84 ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
