Hi Al,

Does that message really say, "password authentication failed for
user "space"' - rather than 'user "cspace"'?

The script you're running when you type "ant create_db import" (an
Ant 'buildfile'), uses the value of a variable called
"${db.cspace.user}".  That value is set (hard-coded) to 'cspace' in
the file /Users/admin/Downloads/services/build.properties.  If you're
truly seeing "space" in the error message, you might first check the
value of 'db.cspace.user' in build.properties, and make sure it's
"cspace", not "space".

You can also run "ant create_db import -v" (note the '-v" flag to
generate very verbose messages), and look at the value of
db.cspace.user right before the script terminates in that error.

Second, assuming that you are using 'cspace' as your database user
name, you'll want to check that the password for the 'cspace' user
used by this script, which attempts to log into the database as that
user - which in turn is the password you've set in the
$DB_PASSWORD_CSPACE environment variable - is the same as the actual
password for the PostgreSQL database user named "cspace".  In other
words, you might try resetting the password for the PostgreSQL
database user named "cspace" to match the value of that password in
$DB_PASSWORD_CSPACE.

http://www.postgresql.org/docs/9.1/static/sql-alterrole.html

• Log into PostgreSQL as an administrative user, such as the
  'postgresql' user.
• Enter:
  ALTER ROLE cspace WITH PASSWORD 'password_from_DB_PASSWORD_CSPACE_goes_here';

Aron Roberts
UC Berkeley

On Thu, May 24, 2012 at 4:27 PM, Al Bersch abersch@museumca.org wrote:

Hi Aron,

Thanks for getting back to me so quickly. Shame on me - "space" was my typo.

We did reset the password for the PostgreSQL
database user named "cspace" to match the value of that password in
$DB_PASSWORD_CSPACE, but were still getting error messages.

We then tried resetting the password as unencrypted , and that seemed to resolve the authentication issue. So I believe we are set.

Thanks for your help!

Al

Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
----- Original Message -----

From: "Aron Roberts" aron@socrates.berkeley.edu
To: "Al Bersch" abersch@museumca.org
Cc: talk@lists.collectionspace.org
Sent: Thursday, May 24, 2012 5:03:32 PM
Subject: Re: [Talk] space user password error

Hi Al,

Does that message really say, "password authentication failed for
user "space"' - rather than 'user "cspace"'?

The script you're running when you type "ant create_db import" (an
Ant 'buildfile'), uses the value of a variable called
"${db.cspace.user}". That value is set (hard-coded) to 'cspace' in
the file /Users/admin/Downloads/services/build.properties. If you're
truly seeing "space" in the error message, you might first check the
value of 'db.cspace.user' in build.properties, and make sure it's
"cspace", not "space".

You can also run "ant create_db import -v" (note the '-v" flag to
generate very verbose messages), and look at the value of
db.cspace.user right before the script terminates in that error.

Second, assuming that you are using 'cspace' as your database user
name, you'll want to check that the password for the 'cspace' user
used by this script, which attempts to log into the database as that
user - which in turn is the password you've set in the
$DB_PASSWORD_CSPACE environment variable - is the same as the actual
password for the PostgreSQL database user named "cspace". In other
words, you might try resetting the password for the PostgreSQL
database user named "cspace" to match the value of that password in
$DB_PASSWORD_CSPACE.

http://www.postgresql.org/docs/9.1/static/sql-alterrole.html

• Log into PostgreSQL as an administrative user, such as the
  'postgresql' user.
• Enter:
  ALTER ROLE cspace WITH PASSWORD 'password_from_DB_PASSWORD_CSPACE_goes_here';

Aron Roberts
UC Berkeley

On Thu, May 24, 2012 at 4:27 PM, Al Bersch abersch@museumca.org wrote: