Hello, Am 20.11.2007 um 13:23 schrieb Robert Roggenbuck:
> ####begin pg_hba.conf######### > local all postgres ident sameuser > # TYPE DATABASE USER CIDR-ADDRESS METHOD > # "local" is for Unix domain socket connections only > local all all ident sameuser > # IPv4 local connections: > host all all 127.0.0.1/32 md5 > # IPv6 local connections: > host all all ::1/128 md5 > # DSpace settings: > host dspace dspace 127.0.0.1 255.255.255.255 md5 > # host dspace dspace 131.173.148.100 255.255.255.255 md5 > ####end pg_hba.conf######## First, I would try a very open setting temporarily and also find out whether the notation of the mask as /32 is accepted. I would use a config with a single line like one of these to start with: host all all 127.0.0.1 255.255.255.0 password or host all all 127.0.0.1 0.0.0.0 trust or host all all 0.0.0.0 0.0.0.0 trust (check the state of your firewall before) I guess the last active line in your pg_hba.conf will never be evaluated because host all all matches all requests for db dspace by user dspace before they come to this line. But that should not stop your config from working. Then, did you update anything that might have placed a different version of the jdbc driver in a generic place where java might pick it up before it looks into your dspace directory? Or anything that might have modified the jdbc driver? Allways the same stupid questions but that is all that comes to my mind. Bye, Christian ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
