AR
Aron Roberts
Sat, May 26, 2012 12:42 AM
Thanks, Al. This all sounds good so far. Here's hoping the reinstall
takes care of the problem!
If for any reason it doesn't, some more thoughts:
- Make sure you're running all your 'ant' commands from the VERY top
level of the CollectionSpace services source code tree; e.g. from
/services
and not anywhere else down in the tree; e.g. /services/services
- In $HOME/bash_profile:
export CSPACE_JEESERVER_HOME="/usr/local/share/apache-tomcat-6.0.33"
export CATALINA_HOME=$CSPACE_JEESERVER_HOME
export CATALINA_PID="$CSPACE_JEESERVER_HOME/bin/tomcat.pid"
export CATALINA_OPTS="-Xmx1024m -XX:MaxPermSize=384m"
export JAVA_HOME="/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home"
export DB_USER="..."
export DB_PASSWORD="..."
export DB_PASSWORD_NUXEO="..."
export DB_PASSWORD_CSPACE="...."
export ANT_OPTS="-Xmx768m -XX:MaxPermSize=512m"
export MAVEN_OPTS="-Xmx768m -XX:MaxPermSize=512m -Dfile.encoding=UTF-8"
- This may also potentially be important, and is experimenting
with; in $HOME/.bashrc, there is this entry:
$HOME/.bash_profile
- If 1) isn't relevant, 2) checks out, and you try 3), and the
environment variables are all present, in whatever shell you may be
in, the next thing to check is whether Ant is picking them up out of
the environment.
You can try running the simple Ant buildfile pasted into an earlier
message to check on this. If Ant isn't seeing these variables, you
might try looking at the Nabble discussion thread mentioned earlier,
for any clues about issues that might be present on your system.
Aron
P.S. Jesse Martinez, I believe, added the following note to the
installation instructions,
http://wiki.collectionspace.org/display/DOC/Installing+2.3+on+Mac+OS+X+10.6.8:
If you added these lines to ~/.bashrc, to ensure these environment
variables are present in every new login shell, edit or create the
~/.bash_profile file and add the following line to that file:
. ~/.bashrc
I've basically done the converse of this, above, in part as a result
of reading posts like http://hacktux.com/bash/bashrc/bash_profile and
http://stefaanlippens.net/bashrc_and_others:
"In this case of an interactive but non-login shell, only ~/.bashrc is
executed."
(Ultimately, this may hint at necessary changes to the existing
documentation ...)
On Fri, May 25, 2012 at 4:18 PM, Al Bersch abersch@museumca.org wrote:
Hi Aron,
Thanks for your response.
In answer to your questions - yes, the installation is on a Mac OS X system,
and yes, there entries in the appropriate shell configuration file to export
the environment variables (we thinks so - we put them in the .bash profile).
As for the third question, I believe that each and every one of the
environment variables is visible upon the command 'env'.
Our plan is to reinstall and see if we can resolve the issue that way. I'll
let you know what we find out.
Thanks again,
Al
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
From: "Aron Roberts" aron@socrates.berkeley.edu
To: "Al Bersch" abersch@museumca.org
Cc: talk@lists.collectionspace.org
Sent: Friday, May 25, 2012 2:33:32 PM
Subject: Re: [Talk] space user password error
Al,
Thanks much for this update!
There are a number of environment variables that must be available
to Ant in order to successfully build the CollectionSpace services
layer, create and populate databases, and import roles, permissions,
etc. If any of those is missing, you may not have a completely
working CollectionSpace system.
It's likely to be more productive to resolve the environment
variables problem once and for all, and get a clean installation, then
to try to resolve individual problems caused by their absence, one
after the other. That will, I'm concerned, be more consuming of your
time than getting an environment in place where the installation steps
'just work.'
Just to start out, is it the case that:
- The installation is occurring on a Unix-like system (Linux, Mac OS
X, or even a Unix variant)?
- There are entries in the appropriate shell configuration file to
export these environment variables, so that they're present in every
new instance of your command shell?
- When you open a new shell / terminal window, you can type the
command 'env', and, in the output from that command, see each and
every one of the environment variables listed in the "Setting Up
CollectionSpace" section of the various installation documents, such
as http://wiki.collectionspace.org/x/1oHyBQ ?
Aron
On Fri, May 25, 2012 at 2:21 PM, Al Bersch abersch@museumca.org wrote:
Hi Aron, Jesse,
Thanks for getting back. We ended up hard-coding our password to the
variable, and that worked. So ant create_db import ran successfully.
However, I still want to run the Ant buildfile you sent to try to locate
the
problem the environment variables.
We started the servers, but can't find our tenant, which leaves us with
more questions (and thanks again for all your help). What should we have
in
our Tables, and what should we have listed for Tenants? After we created
our
tenant, our tenant table is showing up empty.
Also, can someone share an example of a host file (we didn't put in a DNS,
just used localhost)? It would be great to see what it is supposed to look
like.
Thank you,
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
From: "Aron Roberts" aron@socrates.berkeley.edu
To: "Al Bersch" abersch@museumca.org
Cc: talk@lists.collectionspace.org
Sent: Friday, May 25, 2012 1:22:50 PM
Subject: Re: [Talk] space user password error
Al,
You can try pasting this simple Ant buildfile into a file named
"build.xml" in some temporary directory:
<project name="test-env-vars" default="test-env-vars" basedir=".">
<!-- environment should be declared first -->
<property environment="env" />
<target name="test-env-vars">
<echo
message="CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}"/>
</target>
</project>
and then invoke it, from that directory, via 'ant'. This will let you
know - in a simple way, without any filtering - whether Ant can 'see'
your environment variables. If it succeeds at finding the values in
your environment variables, you'll see something like:
test-env-vars:
[echo] CSPACE_JEESERVER_HOME=/usr/local/share/apache-tomcat-6.0.33
BUILD SUCCESSFUL
and if it fails, you'll see:
test-env-vars:
[echo] CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}
BUILD SUCCESSFUL
If it can't find the values in your environment variables, then you
might look into that discussion thread in that Nabble-archived post,
included in a previous message on this topic, to see if any of the
issues mentioned there might apply in your situation.
Aron
On Fri, May 25, 2012 at 1:13 PM, Jesse Martinez
jmartinez@movingimage.us wrote:
Hi Al,
Just a quick thought, are you using special characters or punctuation
in your cspace password? I once had an issue using dollar signs $ in a
postgresql password.
On Fri, May 25, 2012 at 2:17 PM, Al Bersch abersch@museumca.org wrote:
Hi Aron and talk,
It looks like I spoke too soon. We are still getting a build failed
message
(verbose version below) and it appears that our environment variables
are
not being recognized, even though we can find the right path if we echo
the
environment variables. We continue to get the message that the cspace
user
password can't be authenticated. We verified that the password is set in
the
environment variable. We can echo and it kicks back the password. Once
we
set the cspace user password, we can log into postgres with that user
password, until we run the script and after that we can't log in until
we
reset the password.
Any thoughts? Much appreciated!
Thanks,
Al
museumcatest:services admin$ ant create_db import -v
Apache Ant(TM) version 1.8.2 compiled on June 3 2011
Trying the default build file: build.xml
Buildfile: /Users/admin/Downloads/services/build.xml
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
parsing buildfile /Users/admin/Downloads/services/build.xml with URI =
file:/Users/admin/Downloads/services/build.xml
Project base dir set to: /Users/admin/Downloads/services
parsing buildfile
jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
with
URI =
jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
from a zip file
[property] Loading Environment env.
[property] Loading /Users/admin/Downloads/services/build.properties
Build sequence for target(s) `create_db' is [create_base_db, create_db]
Complete build sequence is [create_base_db, create_db, undeploy,
clean-windows, checkvars, install-unix, install-windows, install,
setup_initdb.sql, deploy, package-unix, package-windows, package,
eclipse-unix, dist_installer, dist, dist-jee-nuxeo, import,
test-windows,
hotdeploy, init, dist-jee-domains, clean-unix, clean, eclipse-windows,
eclipse, test-unix, gen_ddl, test, dist-jee-cspace, doc, ]
create_base_db:
[sql] connecting to jdbc:postgresql://localhost:5432
[sql] Loading org.postgresql.Driver using AntClassLoader with
classpath
/usr/local/share/apache-tomcat-6.0.33/cspace/services/db/jdbc_drivers/postgresql-8.4-702.jdbc4.jar
[sql] Executing resource:
/usr/local/share/apache-tomcat-6.0.33/cspace/services/db/postgresql/init_db.sql
[sql] SQL: DROP database IF EXISTS cspace
[sql] 0 rows affected
[sql] SQL: DROP database IF EXISTS nuxeo
[sql] 0 rows affected
[sql] SQL: DROP USER IF EXISTS nuxeo
[sql] 0 rows affected
[sql] SQL: DROP USER IF EXISTS cspace
[sql] 0 rows affected
[sql] SQL: DROP USER IF EXISTS reader
[sql] 0 rows affected
[sql] SQL: CREATE ROLE nuxeo WITH PASSWORD
'your_nuxeo_database_user_password_here' LOGIN
[sql] 0 rows affected
[sql] SQL: CREATE ROLE cspace WITH PASSWORD
'your_cspace_database_user_password_here' LOGIN
[sql] 0 rows affected
[sql] SQL: CREATE ROLE reader WITH PASSWORD 'read' LOGIN
[sql] 0 rows affected
[sql] SQL: CREATE DATABASE cspace ENCODING 'UTF8' OWNER cspace
[sql] 0 rows affected
[sql] SQL: CREATE DATABASE nuxeo ENCODING 'UTF8' OWNER nuxeo
[sql] 0 rows affected
[sql] SQL: GRANT CONNECT ON DATABASE nuxeo TO reader
[sql] 0 rows affected
[sql] 11 of 11 SQL statements executed successfully
create_db:
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
[ant] calling target(s) [create_db] in build file
/Users/admin/Downloads/services/services/build.xml
parsing buildfile /Users/admin/Downloads/services/services/build.xml
with
URI = file:/Users/admin/Downloads/services/services/build.xml
Project base dir set to: /Users/admin/Downloads/services/services
[property] Loading /Users/admin/Downloads/services/build.properties
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.DB_PASSWORD_NUXEO" has not been set
Property "env.DB_PASSWORD" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.DB_USER" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.DB_PASSWORD_CSPACE" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
[ant] Entering
/Users/admin/Downloads/services/services/build.xml...
Build sequence for target(s) `create_db' is [create_db]
Complete build sequence is [create_db, undeploy, clean-windows,
install-unix, install-windows, install, deploy, doc-windows,
package-unix,
package-windows, package, dist_installer, import,
copy-dependencies-reports,
test-windows, doc-unix, doc, dist, hotdeploy, clean-unix, clean,
test-unix,
gen_ddl, test, generate-dependencies-reports, ]
create_db:
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
[ant] calling target(s) [create_db] in build file
/Users/admin/Downloads/services/services/authentication/build.xml
parsing buildfile
/Users/admin/Downloads/services/services/authentication/build.xml with
URI =
file:/Users/admin/Downloads/services/services/authentication/build.xml
Project base dir set to:
/Users/admin/Downloads/services/services/authentication
[property] Loading Environment env.
[property] Loading /Users/admin/Downloads/services/build.properties
[ant] Entering
/Users/admin/Downloads/services/services/authentication/build.xml...
Build sequence for target(s) `create_db' is [create_db]
Complete build sequence is [create_db, undeploy, clean-windows,
install-unix, install-windows, install, deploy, package-unix,
package-windows, package, test-windows, dist, clean-unix, clean,
test-unix,
gen_ddl, test, ]
create_db:
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
[ant] calling target(s) [create_db] in build file
/Users/admin/Downloads/services/services/authentication/pstore/build.xml
parsing buildfile
/Users/admin/Downloads/services/services/authentication/pstore/build.xml
with URI =
file:/Users/admin/Downloads/services/services/authentication/pstore/build.xml
Project base dir set to:
/Users/admin/Downloads/services/services/authentication/pstore
[property] Loading Environment env.
[property] Loading /Users/admin/Downloads/services/build.properties
[ant] Entering
/Users/admin/Downloads/services/services/authentication/pstore/build.xml...
Build sequence for target(s) `create_db' is [create_db]
Complete build sequence is [create_db, check.db.scripts.deploy.dir,
undeploy, clean-windows, setup_hibernate.cfg, install-unix,
install-windows,
install, deploy, package-unix, package-windows, package, gen_ddl-unix,
test-windows, gen_ddl-windows, dist, clean-unix, clean, init, test-unix,
gen_ddl, test, ]
create_db:
[sql] connecting to jdbc:postgresql://localhost:5432/cspace
[sql] Loading org.postgresql.Driver using a cached AntClassLoader.
[ant] Exiting
/Users/admin/Downloads/services/services/authentication/pstore/build.xml.
[ant] Exiting
/Users/admin/Downloads/services/services/authentication/build.xml.
[ant] Exiting /Users/admin/Downloads/services/services/build.xml.
BUILD FAILED
/Users/admin/Downloads/services/build.xml:210: The following error
occurred
while executing this line:
/Users/admin/Downloads/services/services/build.xml:136: The following
error
occurred while executing this line:
/Users/admin/Downloads/services/services/authentication/build.xml:117:
The
following error occurred while executing this line:
/Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
org.postgresql.util.PSQLException: FATAL: password authentication failed
for
user "cspace"
at
org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:291)
at
org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:108)
at
org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)
at
org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:125)
at
org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Connection.java:30)
at
org.postgresql.jdbc3g.AbstractJdbc3gConnection.<init>(AbstractJdbc3gConnection.java:22)
at
org.postgresql.jdbc4.AbstractJdbc4Connection.<init>(AbstractJdbc4Connection.java:30)
at org.postgresql.jdbc4.Jdbc4Connection.<init>(Jdbc4Connection.java:24)
at org.postgresql.Driver.makeConnection(Driver.java:393)
at org.postgresql.Driver.connect(Driver.java:267)
at
org.apache.tools.ant.taskdefs.JDBCTask.getConnection(JDBCTask.java:370)
at org.apache.tools.ant.taskdefs.SQLExec.getConnection(SQLExec.java:942)
at org.apache.tools.ant.taskdefs.SQLExec.execute(SQLExec.java:614)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.Main.runBuild(Main.java:809)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
Total time: 1 second
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
From: "Aron Roberts" aron@socrates.berkeley.edu
To: "Al Bersch" abersch@museumca.org
Sent: Friday, May 25, 2012 9:32:47 AM
Subject: Re: [Talk] space user password error
Hi Al,
Many thanks - it's terrific you resolved this in this way! And
your note on the Talk list will help others who may run into the same
situation.
(Until reading your note, I wasn't aware of the ENCRYPTED option for
passwords in PostgreSQL:
http://www.postgresql.org/docs/9.1/static/sql-createuser.html).
Best,
Aron
On Fri, May 25, 2012 at 8:56 AM, 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
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:
Hello,
After following the steps for creating our tenant we get an error when
we
run the ant create_db import. With the following error:
/Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
org.postgresql.util.PSQLException: FATAL: password authentication
failed
for
user "space".
We believe we verified the password is set to what our environment
variable
is set to: $DB_PASSWORD_CSPACE.
We would appreciate any ideas/advice!
Thank you!
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Thanks, Al. This all sounds good so far. Here's hoping the reinstall
takes care of the problem!
If for any reason it doesn't, some more thoughts:
1) Make sure you're running all your 'ant' commands from the VERY top
level of the CollectionSpace services source code tree; e.g. from
/services
and not anywhere else down in the tree; e.g. /services/services
2) In $HOME/bash_profile:
export CSPACE_JEESERVER_HOME="/usr/local/share/apache-tomcat-6.0.33"
export CATALINA_HOME=$CSPACE_JEESERVER_HOME
export CATALINA_PID="$CSPACE_JEESERVER_HOME/bin/tomcat.pid"
export CATALINA_OPTS="-Xmx1024m -XX:MaxPermSize=384m"
export JAVA_HOME="/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home"
export DB_USER="..."
export DB_PASSWORD="..."
export DB_PASSWORD_NUXEO="..."
export DB_PASSWORD_CSPACE="...."
export ANT_OPTS="-Xmx768m -XX:MaxPermSize=512m"
export MAVEN_OPTS="-Xmx768m -XX:MaxPermSize=512m -Dfile.encoding=UTF-8"
3) This *may* also potentially be important, and is experimenting
with; in $HOME/.bashrc, there is this entry:
$HOME/.bash_profile
4) If 1) isn't relevant, 2) checks out, and you try 3), and the
environment variables are all present, in whatever shell you may be
in, the next thing to check is whether Ant is picking them up out of
the environment.
You can try running the simple Ant buildfile pasted into an earlier
message to check on this. If Ant isn't seeing these variables, you
might try looking at the Nabble discussion thread mentioned earlier,
for any clues about issues that might be present on your system.
Aron
P.S. Jesse Martinez, I believe, added the following note to the
installation instructions,
http://wiki.collectionspace.org/display/DOC/Installing+2.3+on+Mac+OS+X+10.6.8:
If you added these lines to ~/.bashrc, to ensure these environment
variables are present in every new login shell, edit or create the
~/.bash_profile file and add the following line to that file:
. ~/.bashrc
I've basically done the converse of this, above, in part as a result
of reading posts like http://hacktux.com/bash/bashrc/bash_profile and
http://stefaanlippens.net/bashrc_and_others:
"In this case of an interactive but non-login shell, only ~/.bashrc is
executed."
(Ultimately, this may hint at necessary changes to the existing
documentation ...)
On Fri, May 25, 2012 at 4:18 PM, Al Bersch <abersch@museumca.org> wrote:
> Hi Aron,
>
> Thanks for your response.
>
> In answer to your questions - yes, the installation is on a Mac OS X system,
> and yes, there entries in the appropriate shell configuration file to export
> the environment variables (we thinks so - we put them in the .bash profile).
> As for the third question, I believe that each and every one of the
> environment variables is visible upon the command 'env'.
>
> Our plan is to reinstall and see if we can resolve the issue that way. I'll
> let you know what we find out.
>
> Thanks again,
>
> Al
>
> Al Bersch
> Digital Project Coordinator
> Oakland Museum of California
> 1000 Oak Street, Oakland, CA 94607
> abersch@museumca.org
> 510-318-8468
> ________________________________
> From: "Aron Roberts" <aron@socrates.berkeley.edu>
> To: "Al Bersch" <abersch@museumca.org>
> Cc: talk@lists.collectionspace.org
> Sent: Friday, May 25, 2012 2:33:32 PM
>
> Subject: Re: [Talk] space user password error
>
> Al,
>
> Thanks much for this update!
>
> There are a number of environment variables that must be available
> to Ant in order to successfully build the CollectionSpace services
> layer, create and populate databases, and import roles, permissions,
> etc. If any of those is missing, you may not have a completely
> working CollectionSpace system.
>
> It's likely to be more productive to resolve the environment
> variables problem once and for all, and get a clean installation, then
> to try to resolve individual problems caused by their absence, one
> after the other. That will, I'm concerned, be more consuming of your
> time than getting an environment in place where the installation steps
> 'just work.'
>
> Just to start out, is it the case that:
>
> * The installation is occurring on a Unix-like system (Linux, Mac OS
> X, or even a Unix variant)?
> * There are entries in the appropriate shell configuration file to
> export these environment variables, so that they're present in every
> new instance of your command shell?
> * When you open a new shell / terminal window, you can type the
> command 'env', and, in the output from that command, see each and
> every one of the environment variables listed in the "Setting Up
> CollectionSpace" section of the various installation documents, such
> as http://wiki.collectionspace.org/x/1oHyBQ ?
>
> Aron
>
> On Fri, May 25, 2012 at 2:21 PM, Al Bersch <abersch@museumca.org> wrote:
>> Hi Aron, Jesse,
>>
>> Thanks for getting back. We ended up hard-coding our password to the
>> variable, and that worked. So ant create_db import ran successfully.
>> However, I still want to run the Ant buildfile you sent to try to locate
>> the
>> problem the environment variables.
>>
>> We started the servers, but can't find our tenant, which leaves us with
>> more questions (and thanks again for all your help). What should we have
>> in
>> our Tables, and what should we have listed for Tenants? After we created
>> our
>> tenant, our tenant table is showing up empty.
>>
>> Also, can someone share an example of a host file (we didn't put in a DNS,
>> just used localhost)? It would be great to see what it is supposed to look
>> like.
>>
>> Thank you,
>>
>> Al Bersch
>> Digital Project Coordinator
>> Oakland Museum of California
>> 1000 Oak Street, Oakland, CA 94607
>> abersch@museumca.org
>> 510-318-8468
>> ________________________________
>> From: "Aron Roberts" <aron@socrates.berkeley.edu>
>> To: "Al Bersch" <abersch@museumca.org>
>> Cc: talk@lists.collectionspace.org
>> Sent: Friday, May 25, 2012 1:22:50 PM
>>
>> Subject: Re: [Talk] space user password error
>>
>> Al,
>>
>> You can try pasting this simple Ant buildfile into a file named
>> "build.xml" in some temporary directory:
>>
>> <project name="test-env-vars" default="test-env-vars" basedir=".">
>> <!-- environment should be declared first -->
>> <property environment="env" />
>> <target name="test-env-vars">
>> <echo
>> message="CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}"/>
>> </target>
>> </project>
>>
>> and then invoke it, from that directory, via 'ant'. This will let you
>> know - in a simple way, without any filtering - whether Ant can 'see'
>> your environment variables. If it succeeds at finding the values in
>> your environment variables, you'll see something like:
>>
>> test-env-vars:
>> [echo] CSPACE_JEESERVER_HOME=/usr/local/share/apache-tomcat-6.0.33
>> BUILD SUCCESSFUL
>>
>> and if it fails, you'll see:
>>
>> test-env-vars:
>> [echo] CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}
>> BUILD SUCCESSFUL
>>
>> If it can't find the values in your environment variables, then you
>> might look into that discussion thread in that Nabble-archived post,
>> included in a previous message on this topic, to see if any of the
>> issues mentioned there might apply in your situation.
>>
>> Aron
>>
>> On Fri, May 25, 2012 at 1:13 PM, Jesse Martinez
>> <jmartinez@movingimage.us> wrote:
>>> Hi Al,
>>>
>>> Just a quick thought, are you using special characters or punctuation
>>> in your cspace password? I once had an issue using dollar signs $ in a
>>> postgresql password.
>>>
>>> - Jesse
>>>
>>> On Fri, May 25, 2012 at 2:17 PM, Al Bersch <abersch@museumca.org> wrote:
>>>> Hi Aron and talk,
>>>>
>>>> It looks like I spoke too soon. We are still getting a build failed
>>>> message
>>>> (verbose version below) and it appears that our environment variables
>>>> are
>>>> not being recognized, even though we can find the right path if we echo
>>>> the
>>>> environment variables. We continue to get the message that the cspace
>>>> user
>>>> password can't be authenticated. We verified that the password is set in
>>>> the
>>>> environment variable. We can echo and it kicks back the password. Once
>>>> we
>>>> set the cspace user password, we can log into postgres with that user
>>>> password, until we run the script and after that we can't log in until
>>>> we
>>>> reset the password.
>>>>
>>>> Any thoughts? Much appreciated!
>>>>
>>>> Thanks,
>>>>
>>>> Al
>>>>
>>>> museumcatest:services admin$ ant create_db import -v
>>>> Apache Ant(TM) version 1.8.2 compiled on June 3 2011
>>>> Trying the default build file: build.xml
>>>> Buildfile: /Users/admin/Downloads/services/build.xml
>>>> Detected Java version: 1.6 in:
>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>> Detected OS: Mac OS X
>>>> parsing buildfile /Users/admin/Downloads/services/build.xml with URI =
>>>> file:/Users/admin/Downloads/services/build.xml
>>>> Project base dir set to: /Users/admin/Downloads/services
>>>> parsing buildfile
>>>> jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
>>>> with
>>>> URI =
>>>> jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
>>>> from a zip file
>>>> [property] Loading Environment env.
>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>> Build sequence for target(s) `create_db' is [create_base_db, create_db]
>>>> Complete build sequence is [create_base_db, create_db, undeploy,
>>>> clean-windows, checkvars, install-unix, install-windows, install,
>>>> setup_initdb.sql, deploy, package-unix, package-windows, package,
>>>> eclipse-unix, dist_installer, dist, dist-jee-nuxeo, import,
>>>> test-windows,
>>>> hotdeploy, init, dist-jee-domains, clean-unix, clean, eclipse-windows,
>>>> eclipse, test-unix, gen_ddl, test, dist-jee-cspace, doc, ]
>>>>
>>>> create_base_db:
>>>> [sql] connecting to jdbc:postgresql://localhost:5432
>>>> [sql] Loading org.postgresql.Driver using AntClassLoader with
>>>> classpath
>>>>
>>>>
>>>> /usr/local/share/apache-tomcat-6.0.33/cspace/services/db/jdbc_drivers/postgresql-8.4-702.jdbc4.jar
>>>> [sql] Executing resource:
>>>>
>>>>
>>>> /usr/local/share/apache-tomcat-6.0.33/cspace/services/db/postgresql/init_db.sql
>>>> [sql] SQL: DROP database IF EXISTS cspace
>>>> [sql] 0 rows affected
>>>> [sql] SQL: DROP database IF EXISTS nuxeo
>>>> [sql] 0 rows affected
>>>> [sql] SQL: DROP USER IF EXISTS nuxeo
>>>> [sql] 0 rows affected
>>>> [sql] SQL: DROP USER IF EXISTS cspace
>>>> [sql] 0 rows affected
>>>> [sql] SQL: DROP USER IF EXISTS reader
>>>> [sql] 0 rows affected
>>>> [sql] SQL: CREATE ROLE nuxeo WITH PASSWORD
>>>> 'your_nuxeo_database_user_password_here' LOGIN
>>>> [sql] 0 rows affected
>>>> [sql] SQL: CREATE ROLE cspace WITH PASSWORD
>>>> 'your_cspace_database_user_password_here' LOGIN
>>>> [sql] 0 rows affected
>>>> [sql] SQL: CREATE ROLE reader WITH PASSWORD 'read' LOGIN
>>>> [sql] 0 rows affected
>>>> [sql] SQL: CREATE DATABASE cspace ENCODING 'UTF8' OWNER cspace
>>>> [sql] 0 rows affected
>>>> [sql] SQL: CREATE DATABASE nuxeo ENCODING 'UTF8' OWNER nuxeo
>>>> [sql] 0 rows affected
>>>> [sql] SQL: GRANT CONNECT ON DATABASE nuxeo TO reader
>>>> [sql] 0 rows affected
>>>> [sql] 11 of 11 SQL statements executed successfully
>>>>
>>>> create_db:
>>>> Detected Java version: 1.6 in:
>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>> Detected OS: Mac OS X
>>>> [ant] calling target(s) [create_db] in build file
>>>> /Users/admin/Downloads/services/services/build.xml
>>>> parsing buildfile /Users/admin/Downloads/services/services/build.xml
>>>> with
>>>> URI = file:/Users/admin/Downloads/services/services/build.xml
>>>> Project base dir set to: /Users/admin/Downloads/services/services
>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.DB_PASSWORD_NUXEO" has not been set
>>>> Property "env.DB_PASSWORD" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.DB_USER" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.DB_PASSWORD_CSPACE" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> [ant] Entering
>>>> /Users/admin/Downloads/services/services/build.xml...
>>>> Build sequence for target(s) `create_db' is [create_db]
>>>> Complete build sequence is [create_db, undeploy, clean-windows,
>>>> install-unix, install-windows, install, deploy, doc-windows,
>>>> package-unix,
>>>> package-windows, package, dist_installer, import,
>>>> copy-dependencies-reports,
>>>> test-windows, doc-unix, doc, dist, hotdeploy, clean-unix, clean,
>>>> test-unix,
>>>> gen_ddl, test, generate-dependencies-reports, ]
>>>>
>>>> create_db:
>>>> Detected Java version: 1.6 in:
>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>> Detected OS: Mac OS X
>>>> [ant] calling target(s) [create_db] in build file
>>>> /Users/admin/Downloads/services/services/authentication/build.xml
>>>> parsing buildfile
>>>> /Users/admin/Downloads/services/services/authentication/build.xml with
>>>> URI =
>>>> file:/Users/admin/Downloads/services/services/authentication/build.xml
>>>> Project base dir set to:
>>>> /Users/admin/Downloads/services/services/authentication
>>>> [property] Loading Environment env.
>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>> [ant] Entering
>>>> /Users/admin/Downloads/services/services/authentication/build.xml...
>>>> Build sequence for target(s) `create_db' is [create_db]
>>>> Complete build sequence is [create_db, undeploy, clean-windows,
>>>> install-unix, install-windows, install, deploy, package-unix,
>>>> package-windows, package, test-windows, dist, clean-unix, clean,
>>>> test-unix,
>>>> gen_ddl, test, ]
>>>>
>>>> create_db:
>>>> Detected Java version: 1.6 in:
>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>> Detected OS: Mac OS X
>>>> [ant] calling target(s) [create_db] in build file
>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml
>>>> parsing buildfile
>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml
>>>> with URI =
>>>>
>>>>
>>>> file:/Users/admin/Downloads/services/services/authentication/pstore/build.xml
>>>> Project base dir set to:
>>>> /Users/admin/Downloads/services/services/authentication/pstore
>>>> [property] Loading Environment env.
>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>> [ant] Entering
>>>>
>>>>
>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml...
>>>> Build sequence for target(s) `create_db' is [create_db]
>>>> Complete build sequence is [create_db, check.db.scripts.deploy.dir,
>>>> undeploy, clean-windows, setup_hibernate.cfg, install-unix,
>>>> install-windows,
>>>> install, deploy, package-unix, package-windows, package, gen_ddl-unix,
>>>> test-windows, gen_ddl-windows, dist, clean-unix, clean, init, test-unix,
>>>> gen_ddl, test, ]
>>>>
>>>> create_db:
>>>> [sql] connecting to jdbc:postgresql://localhost:5432/cspace
>>>> [sql] Loading org.postgresql.Driver using a cached AntClassLoader.
>>>> [ant] Exiting
>>>>
>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml.
>>>> [ant] Exiting
>>>> /Users/admin/Downloads/services/services/authentication/build.xml.
>>>> [ant] Exiting /Users/admin/Downloads/services/services/build.xml.
>>>>
>>>> BUILD FAILED
>>>> /Users/admin/Downloads/services/build.xml:210: The following error
>>>> occurred
>>>> while executing this line:
>>>> /Users/admin/Downloads/services/services/build.xml:136: The following
>>>> error
>>>> occurred while executing this line:
>>>> /Users/admin/Downloads/services/services/authentication/build.xml:117:
>>>> The
>>>> following error occurred while executing this line:
>>>>
>>>>
>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
>>>> org.postgresql.util.PSQLException: FATAL: password authentication failed
>>>> for
>>>> user "cspace"
>>>> at
>>>>
>>>>
>>>> org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:291)
>>>> at
>>>>
>>>>
>>>> org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:108)
>>>> at
>>>>
>>>>
>>>> org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)
>>>> at
>>>>
>>>>
>>>> org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:125)
>>>> at
>>>>
>>>>
>>>> org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Connection.java:30)
>>>> at
>>>>
>>>>
>>>> org.postgresql.jdbc3g.AbstractJdbc3gConnection.<init>(AbstractJdbc3gConnection.java:22)
>>>> at
>>>>
>>>>
>>>> org.postgresql.jdbc4.AbstractJdbc4Connection.<init>(AbstractJdbc4Connection.java:30)
>>>> at org.postgresql.jdbc4.Jdbc4Connection.<init>(Jdbc4Connection.java:24)
>>>> at org.postgresql.Driver.makeConnection(Driver.java:393)
>>>> at org.postgresql.Driver.connect(Driver.java:267)
>>>> at
>>>> org.apache.tools.ant.taskdefs.JDBCTask.getConnection(JDBCTask.java:370)
>>>> at org.apache.tools.ant.taskdefs.SQLExec.getConnection(SQLExec.java:942)
>>>> at org.apache.tools.ant.taskdefs.SQLExec.execute(SQLExec.java:614)
>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>>>> at
>>>>
>>>>
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>> at
>>>>
>>>>
>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>> at
>>>>
>>>>
>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>>>> at
>>>>
>>>>
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>> at
>>>>
>>>>
>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>> at
>>>>
>>>>
>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>>>> at
>>>>
>>>>
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>> at
>>>>
>>>>
>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>> at
>>>>
>>>>
>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>>
>>>>
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>> at
>>>>
>>>>
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>> at
>>>>
>>>>
>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>> at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
>>>> at
>>>>
>>>>
>>>> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>> at org.apache.tools.ant.Main.runBuild(Main.java:809)
>>>> at org.apache.tools.ant.Main.startAnt(Main.java:217)
>>>> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
>>>> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
>>>>
>>>> Total time: 1 second
>>>>
>>>> Al Bersch
>>>> Digital Project Coordinator
>>>> Oakland Museum of California
>>>> 1000 Oak Street, Oakland, CA 94607
>>>> abersch@museumca.org
>>>> 510-318-8468
>>>> ________________________________
>>>> From: "Aron Roberts" <aron@socrates.berkeley.edu>
>>>> To: "Al Bersch" <abersch@museumca.org>
>>>> Sent: Friday, May 25, 2012 9:32:47 AM
>>>>
>>>> Subject: Re: [Talk] space user password error
>>>>
>>>> Hi Al,
>>>>
>>>> Many thanks - it's terrific you resolved this in this way! And
>>>> your note on the Talk list will help others who may run into the same
>>>> situation.
>>>>
>>>> (Until reading your note, I wasn't aware of the ENCRYPTED option for
>>>> passwords in PostgreSQL:
>>>> http://www.postgresql.org/docs/9.1/static/sql-createuser.html).
>>>>
>>>> Best,
>>>> Aron
>>>>
>>>>
>>>> On Fri, May 25, 2012 at 8:56 AM, 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
>>>>> ________________________________
>>>>> 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:
>>>>>> Hello,
>>>>>>
>>>>>> After following the steps for creating our tenant we get an error when
>>>>>> we
>>>>>> run the ant create_db import. With the following error:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
>>>>>> org.postgresql.util.PSQLException: FATAL: password authentication
>>>>>> failed
>>>>>> for
>>>>>> user "space".
>>>>>>
>>>>>> We believe we verified the password is set to what our environment
>>>>>> variable
>>>>>> is set to: $DB_PASSWORD_CSPACE.
>>>>>>
>>>>>> We would appreciate any ideas/advice!
>>>>>>
>>>>>> Thank you!
>>>>>> Al Bersch
>>>>>> Digital Project Coordinator
>>>>>> Oakland Museum of California
>>>>>> 1000 Oak Street, Oakland, CA 94607
>>>>>> abersch@museumca.org
>>>>>> 510-318-8468
>>>>>>
>>>>>> _______________________________________________
>>>>>> Talk mailing list
>>>>>> Talk@lists.collectionspace.org
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>>>>
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Talk mailing list
>>>> Talk@lists.collectionspace.org
>>>>
>>>>
>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>>
>>>
>>> _______________________________________________
>>> Talk mailing list
>>> Talk@lists.collectionspace.org
>>>
>>>
>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>
>
>
> _______________________________________________
> Talk mailing list
> Talk@lists.collectionspace.org
> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>
CP
Christopher Pott
Thu, May 31, 2012 1:30 PM
Hi Al,
I'm working on configuring CollectionSpace at the National Gallery in Denmark.
I just thought there was also a chance your earlier problems with environment variables could be related to using different OS user permissions during various stages of the installation. For example, at least in Debian Linux, if you export your environment variables as 'myuser' in "/home/myuser/.bashrc", but then run the build command as 'root' (via 'sudo') then your current variables won't be preserved (unless you use 'sudo -E').
Regards,
Chris
-----Oprindelig meddelelse-----
Fra: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] På vegne af Aron Roberts
Sendt: 26. maj 2012 02:42
Til: Al Bersch
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] space user password error
Thanks, Al. This all sounds good so far. Here's hoping the reinstall
takes care of the problem!
If for any reason it doesn't, some more thoughts:
- Make sure you're running all your 'ant' commands from the VERY top
level of the CollectionSpace services source code tree; e.g. from
/services
and not anywhere else down in the tree; e.g. /services/services
- In $HOME/bash_profile:
export CSPACE_JEESERVER_HOME="/usr/local/share/apache-tomcat-6.0.33"
export CATALINA_HOME=$CSPACE_JEESERVER_HOME
export CATALINA_PID="$CSPACE_JEESERVER_HOME/bin/tomcat.pid"
export CATALINA_OPTS="-Xmx1024m -XX:MaxPermSize=384m"
export JAVA_HOME="/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home"
export DB_USER="..."
export DB_PASSWORD="..."
export DB_PASSWORD_NUXEO="..."
export DB_PASSWORD_CSPACE="...."
export ANT_OPTS="-Xmx768m -XX:MaxPermSize=512m"
export MAVEN_OPTS="-Xmx768m -XX:MaxPermSize=512m -Dfile.encoding=UTF-8"
- This may also potentially be important, and is experimenting
with; in $HOME/.bashrc, there is this entry:
$HOME/.bash_profile
- If 1) isn't relevant, 2) checks out, and you try 3), and the
environment variables are all present, in whatever shell you may be
in, the next thing to check is whether Ant is picking them up out of
the environment.
You can try running the simple Ant buildfile pasted into an earlier
message to check on this. If Ant isn't seeing these variables, you
might try looking at the Nabble discussion thread mentioned earlier,
for any clues about issues that might be present on your system.
Aron
P.S. Jesse Martinez, I believe, added the following note to the
installation instructions,
http://wiki.collectionspace.org/display/DOC/Installing+2.3+on+Mac+OS+X+10.6.8:
If you added these lines to ~/.bashrc, to ensure these environment
variables are present in every new login shell, edit or create the
~/.bash_profile file and add the following line to that file:
. ~/.bashrc
I've basically done the converse of this, above, in part as a result
of reading posts like http://hacktux.com/bash/bashrc/bash_profile and
http://stefaanlippens.net/bashrc_and_others:
"In this case of an interactive but non-login shell, only ~/.bashrc is
executed."
(Ultimately, this may hint at necessary changes to the existing
documentation ...)
On Fri, May 25, 2012 at 4:18 PM, Al Bersch abersch@museumca.org wrote:
Hi Aron,
Thanks for your response.
In answer to your questions - yes, the installation is on a Mac OS X system,
and yes, there entries in the appropriate shell configuration file to export
the environment variables (we thinks so - we put them in the .bash profile).
As for the third question, I believe that each and every one of the
environment variables is visible upon the command 'env'.
Our plan is to reinstall and see if we can resolve the issue that way. I'll
let you know what we find out.
Thanks again,
Al
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
From: "Aron Roberts" aron@socrates.berkeley.edu
To: "Al Bersch" abersch@museumca.org
Cc: talk@lists.collectionspace.org
Sent: Friday, May 25, 2012 2:33:32 PM
Subject: Re: [Talk] space user password error
Al,
Thanks much for this update!
There are a number of environment variables that must be available
to Ant in order to successfully build the CollectionSpace services
layer, create and populate databases, and import roles, permissions,
etc. If any of those is missing, you may not have a completely
working CollectionSpace system.
It's likely to be more productive to resolve the environment
variables problem once and for all, and get a clean installation, then
to try to resolve individual problems caused by their absence, one
after the other. That will, I'm concerned, be more consuming of your
time than getting an environment in place where the installation steps
'just work.'
Just to start out, is it the case that:
- The installation is occurring on a Unix-like system (Linux, Mac OS
X, or even a Unix variant)?
- There are entries in the appropriate shell configuration file to
export these environment variables, so that they're present in every
new instance of your command shell?
- When you open a new shell / terminal window, you can type the
command 'env', and, in the output from that command, see each and
every one of the environment variables listed in the "Setting Up
CollectionSpace" section of the various installation documents, such
as http://wiki.collectionspace.org/x/1oHyBQ ?
Aron
On Fri, May 25, 2012 at 2:21 PM, Al Bersch abersch@museumca.org wrote:
Hi Aron, Jesse,
Thanks for getting back. We ended up hard-coding our password to the
variable, and that worked. So ant create_db import ran successfully.
However, I still want to run the Ant buildfile you sent to try to locate
the
problem the environment variables.
We started the servers, but can't find our tenant, which leaves us with
more questions (and thanks again for all your help). What should we have
in
our Tables, and what should we have listed for Tenants? After we created
our
tenant, our tenant table is showing up empty.
Also, can someone share an example of a host file (we didn't put in a DNS,
just used localhost)? It would be great to see what it is supposed to look
like.
Thank you,
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
From: "Aron Roberts" aron@socrates.berkeley.edu
To: "Al Bersch" abersch@museumca.org
Cc: talk@lists.collectionspace.org
Sent: Friday, May 25, 2012 1:22:50 PM
Subject: Re: [Talk] space user password error
Al,
You can try pasting this simple Ant buildfile into a file named
"build.xml" in some temporary directory:
<project name="test-env-vars" default="test-env-vars" basedir=".">
<!-- environment should be declared first -->
<property environment="env" />
<target name="test-env-vars">
<echo
message="CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}"/>
</target>
</project>
and then invoke it, from that directory, via 'ant'. This will let you
know - in a simple way, without any filtering - whether Ant can 'see'
your environment variables. If it succeeds at finding the values in
your environment variables, you'll see something like:
test-env-vars:
[echo] CSPACE_JEESERVER_HOME=/usr/local/share/apache-tomcat-6.0.33
BUILD SUCCESSFUL
and if it fails, you'll see:
test-env-vars:
[echo] CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}
BUILD SUCCESSFUL
If it can't find the values in your environment variables, then you
might look into that discussion thread in that Nabble-archived post,
included in a previous message on this topic, to see if any of the
issues mentioned there might apply in your situation.
Aron
On Fri, May 25, 2012 at 1:13 PM, Jesse Martinez
jmartinez@movingimage.us wrote:
Hi Al,
Just a quick thought, are you using special characters or punctuation
in your cspace password? I once had an issue using dollar signs $ in a
postgresql password.
On Fri, May 25, 2012 at 2:17 PM, Al Bersch abersch@museumca.org wrote:
Hi Aron and talk,
It looks like I spoke too soon. We are still getting a build failed
message
(verbose version below) and it appears that our environment variables
are
not being recognized, even though we can find the right path if we echo
the
environment variables. We continue to get the message that the cspace
user
password can't be authenticated. We verified that the password is set in
the
environment variable. We can echo and it kicks back the password. Once
we
set the cspace user password, we can log into postgres with that user
password, until we run the script and after that we can't log in until
we
reset the password.
Any thoughts? Much appreciated!
Thanks,
Al
museumcatest:services admin$ ant create_db import -v
Apache Ant(TM) version 1.8.2 compiled on June 3 2011
Trying the default build file: build.xml
Buildfile: /Users/admin/Downloads/services/build.xml
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
parsing buildfile /Users/admin/Downloads/services/build.xml with URI =
file:/Users/admin/Downloads/services/build.xml
Project base dir set to: /Users/admin/Downloads/services
parsing buildfile
jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
with
URI =
jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
from a zip file
[property] Loading Environment env.
[property] Loading /Users/admin/Downloads/services/build.properties
Build sequence for target(s) `create_db' is [create_base_db, create_db]
Complete build sequence is [create_base_db, create_db, undeploy,
clean-windows, checkvars, install-unix, install-windows, install,
setup_initdb.sql, deploy, package-unix, package-windows, package,
eclipse-unix, dist_installer, dist, dist-jee-nuxeo, import,
test-windows,
hotdeploy, init, dist-jee-domains, clean-unix, clean, eclipse-windows,
eclipse, test-unix, gen_ddl, test, dist-jee-cspace, doc, ]
create_base_db:
[sql] connecting to jdbc:postgresql://localhost:5432
[sql] Loading org.postgresql.Driver using AntClassLoader with
classpath
/usr/local/share/apache-tomcat-6.0.33/cspace/services/db/jdbc_drivers/postgresql-8.4-702.jdbc4.jar
[sql] Executing resource:
/usr/local/share/apache-tomcat-6.0.33/cspace/services/db/postgresql/init_db.sql
[sql] SQL: DROP database IF EXISTS cspace
[sql] 0 rows affected
[sql] SQL: DROP database IF EXISTS nuxeo
[sql] 0 rows affected
[sql] SQL: DROP USER IF EXISTS nuxeo
[sql] 0 rows affected
[sql] SQL: DROP USER IF EXISTS cspace
[sql] 0 rows affected
[sql] SQL: DROP USER IF EXISTS reader
[sql] 0 rows affected
[sql] SQL: CREATE ROLE nuxeo WITH PASSWORD
'your_nuxeo_database_user_password_here' LOGIN
[sql] 0 rows affected
[sql] SQL: CREATE ROLE cspace WITH PASSWORD
'your_cspace_database_user_password_here' LOGIN
[sql] 0 rows affected
[sql] SQL: CREATE ROLE reader WITH PASSWORD 'read' LOGIN
[sql] 0 rows affected
[sql] SQL: CREATE DATABASE cspace ENCODING 'UTF8' OWNER cspace
[sql] 0 rows affected
[sql] SQL: CREATE DATABASE nuxeo ENCODING 'UTF8' OWNER nuxeo
[sql] 0 rows affected
[sql] SQL: GRANT CONNECT ON DATABASE nuxeo TO reader
[sql] 0 rows affected
[sql] 11 of 11 SQL statements executed successfully
create_db:
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
[ant] calling target(s) [create_db] in build file
/Users/admin/Downloads/services/services/build.xml
parsing buildfile /Users/admin/Downloads/services/services/build.xml
with
URI = file:/Users/admin/Downloads/services/services/build.xml
Project base dir set to: /Users/admin/Downloads/services/services
[property] Loading /Users/admin/Downloads/services/build.properties
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.DB_PASSWORD_NUXEO" has not been set
Property "env.DB_PASSWORD" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.DB_USER" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.DB_PASSWORD_CSPACE" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
[ant] Entering
/Users/admin/Downloads/services/services/build.xml...
Build sequence for target(s) `create_db' is [create_db]
Complete build sequence is [create_db, undeploy, clean-windows,
install-unix, install-windows, install, deploy, doc-windows,
package-unix,
package-windows, package, dist_installer, import,
copy-dependencies-reports,
test-windows, doc-unix, doc, dist, hotdeploy, clean-unix, clean,
test-unix,
gen_ddl, test, generate-dependencies-reports, ]
create_db:
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
[ant] calling target(s) [create_db] in build file
/Users/admin/Downloads/services/services/authentication/build.xml
parsing buildfile
/Users/admin/Downloads/services/services/authentication/build.xml with
URI =
file:/Users/admin/Downloads/services/services/authentication/build.xml
Project base dir set to:
/Users/admin/Downloads/services/services/authentication
[property] Loading Environment env.
[property] Loading /Users/admin/Downloads/services/build.properties
[ant] Entering
/Users/admin/Downloads/services/services/authentication/build.xml...
Build sequence for target(s) `create_db' is [create_db]
Complete build sequence is [create_db, undeploy, clean-windows,
install-unix, install-windows, install, deploy, package-unix,
package-windows, package, test-windows, dist, clean-unix, clean,
test-unix,
gen_ddl, test, ]
create_db:
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
[ant] calling target(s) [create_db] in build file
/Users/admin/Downloads/services/services/authentication/pstore/build.xml
parsing buildfile
/Users/admin/Downloads/services/services/authentication/pstore/build.xml
with URI =
file:/Users/admin/Downloads/services/services/authentication/pstore/build.xml
Project base dir set to:
/Users/admin/Downloads/services/services/authentication/pstore
[property] Loading Environment env.
[property] Loading /Users/admin/Downloads/services/build.properties
[ant] Entering
/Users/admin/Downloads/services/services/authentication/pstore/build.xml...
Build sequence for target(s) `create_db' is [create_db]
Complete build sequence is [create_db, check.db.scripts.deploy.dir,
undeploy, clean-windows, setup_hibernate.cfg, install-unix,
install-windows,
install, deploy, package-unix, package-windows, package, gen_ddl-unix,
test-windows, gen_ddl-windows, dist, clean-unix, clean, init, test-unix,
gen_ddl, test, ]
create_db:
[sql] connecting to jdbc:postgresql://localhost:5432/cspace
[sql] Loading org.postgresql.Driver using a cached AntClassLoader.
[ant] Exiting
/Users/admin/Downloads/services/services/authentication/pstore/build.xml.
[ant] Exiting
/Users/admin/Downloads/services/services/authentication/build.xml.
[ant] Exiting /Users/admin/Downloads/services/services/build.xml.
BUILD FAILED
/Users/admin/Downloads/services/build.xml:210: The following error
occurred
while executing this line:
/Users/admin/Downloads/services/services/build.xml:136: The following
error
occurred while executing this line:
/Users/admin/Downloads/services/services/authentication/build.xml:117:
The
following error occurred while executing this line:
/Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
org.postgresql.util.PSQLException: FATAL: password authentication failed
for
user "cspace"
at
org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:291)
at
org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:108)
at
org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)
at
org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:125)
at
org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Connection.java:30)
at
org.postgresql.jdbc3g.AbstractJdbc3gConnection.<init>(AbstractJdbc3gConnection.java:22)
at
org.postgresql.jdbc4.AbstractJdbc4Connection.<init>(AbstractJdbc4Connection.java:30)
at org.postgresql.jdbc4.Jdbc4Connection.<init>(Jdbc4Connection.java:24)
at org.postgresql.Driver.makeConnection(Driver.java:393)
at org.postgresql.Driver.connect(Driver.java:267)
at
org.apache.tools.ant.taskdefs.JDBCTask.getConnection(JDBCTask.java:370)
at org.apache.tools.ant.taskdefs.SQLExec.getConnection(SQLExec.java:942)
at org.apache.tools.ant.taskdefs.SQLExec.execute(SQLExec.java:614)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.Main.runBuild(Main.java:809)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
Total time: 1 second
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
From: "Aron Roberts" aron@socrates.berkeley.edu
To: "Al Bersch" abersch@museumca.org
Sent: Friday, May 25, 2012 9:32:47 AM
Subject: Re: [Talk] space user password error
Hi Al,
Many thanks - it's terrific you resolved this in this way! And
your note on the Talk list will help others who may run into the same
situation.
(Until reading your note, I wasn't aware of the ENCRYPTED option for
passwords in PostgreSQL:
http://www.postgresql.org/docs/9.1/static/sql-createuser.html).
Best,
Aron
On Fri, May 25, 2012 at 8:56 AM, 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
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:
Hello,
After following the steps for creating our tenant we get an error when
we
run the ant create_db import. With the following error:
/Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
org.postgresql.util.PSQLException: FATAL: password authentication
failed
for
user "space".
We believe we verified the password is set to what our environment
variable
is set to: $DB_PASSWORD_CSPACE.
We would appreciate any ideas/advice!
Thank you!
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Hi Al,
I'm working on configuring CollectionSpace at the National Gallery in Denmark.
I just thought there was also a chance your earlier problems with environment variables could be related to using different OS user permissions during various stages of the installation. For example, at least in Debian Linux, if you export your environment variables as 'myuser' in "/home/myuser/.bashrc", but then run the build command as 'root' (via 'sudo') then your current variables won't be preserved (unless you use 'sudo -E').
Regards,
Chris
-----Oprindelig meddelelse-----
Fra: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] På vegne af Aron Roberts
Sendt: 26. maj 2012 02:42
Til: Al Bersch
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] space user password error
Thanks, Al. This all sounds good so far. Here's hoping the reinstall
takes care of the problem!
If for any reason it doesn't, some more thoughts:
1) Make sure you're running all your 'ant' commands from the VERY top
level of the CollectionSpace services source code tree; e.g. from
/services
and not anywhere else down in the tree; e.g. /services/services
2) In $HOME/bash_profile:
export CSPACE_JEESERVER_HOME="/usr/local/share/apache-tomcat-6.0.33"
export CATALINA_HOME=$CSPACE_JEESERVER_HOME
export CATALINA_PID="$CSPACE_JEESERVER_HOME/bin/tomcat.pid"
export CATALINA_OPTS="-Xmx1024m -XX:MaxPermSize=384m"
export JAVA_HOME="/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home"
export DB_USER="..."
export DB_PASSWORD="..."
export DB_PASSWORD_NUXEO="..."
export DB_PASSWORD_CSPACE="...."
export ANT_OPTS="-Xmx768m -XX:MaxPermSize=512m"
export MAVEN_OPTS="-Xmx768m -XX:MaxPermSize=512m -Dfile.encoding=UTF-8"
3) This *may* also potentially be important, and is experimenting
with; in $HOME/.bashrc, there is this entry:
$HOME/.bash_profile
4) If 1) isn't relevant, 2) checks out, and you try 3), and the
environment variables are all present, in whatever shell you may be
in, the next thing to check is whether Ant is picking them up out of
the environment.
You can try running the simple Ant buildfile pasted into an earlier
message to check on this. If Ant isn't seeing these variables, you
might try looking at the Nabble discussion thread mentioned earlier,
for any clues about issues that might be present on your system.
Aron
P.S. Jesse Martinez, I believe, added the following note to the
installation instructions,
http://wiki.collectionspace.org/display/DOC/Installing+2.3+on+Mac+OS+X+10.6.8:
If you added these lines to ~/.bashrc, to ensure these environment
variables are present in every new login shell, edit or create the
~/.bash_profile file and add the following line to that file:
. ~/.bashrc
I've basically done the converse of this, above, in part as a result
of reading posts like http://hacktux.com/bash/bashrc/bash_profile and
http://stefaanlippens.net/bashrc_and_others:
"In this case of an interactive but non-login shell, only ~/.bashrc is
executed."
(Ultimately, this may hint at necessary changes to the existing
documentation ...)
On Fri, May 25, 2012 at 4:18 PM, Al Bersch <abersch@museumca.org> wrote:
> Hi Aron,
>
> Thanks for your response.
>
> In answer to your questions - yes, the installation is on a Mac OS X system,
> and yes, there entries in the appropriate shell configuration file to export
> the environment variables (we thinks so - we put them in the .bash profile).
> As for the third question, I believe that each and every one of the
> environment variables is visible upon the command 'env'.
>
> Our plan is to reinstall and see if we can resolve the issue that way. I'll
> let you know what we find out.
>
> Thanks again,
>
> Al
>
> Al Bersch
> Digital Project Coordinator
> Oakland Museum of California
> 1000 Oak Street, Oakland, CA 94607
> abersch@museumca.org
> 510-318-8468
> ________________________________
> From: "Aron Roberts" <aron@socrates.berkeley.edu>
> To: "Al Bersch" <abersch@museumca.org>
> Cc: talk@lists.collectionspace.org
> Sent: Friday, May 25, 2012 2:33:32 PM
>
> Subject: Re: [Talk] space user password error
>
> Al,
>
> Thanks much for this update!
>
> There are a number of environment variables that must be available
> to Ant in order to successfully build the CollectionSpace services
> layer, create and populate databases, and import roles, permissions,
> etc. If any of those is missing, you may not have a completely
> working CollectionSpace system.
>
> It's likely to be more productive to resolve the environment
> variables problem once and for all, and get a clean installation, then
> to try to resolve individual problems caused by their absence, one
> after the other. That will, I'm concerned, be more consuming of your
> time than getting an environment in place where the installation steps
> 'just work.'
>
> Just to start out, is it the case that:
>
> * The installation is occurring on a Unix-like system (Linux, Mac OS
> X, or even a Unix variant)?
> * There are entries in the appropriate shell configuration file to
> export these environment variables, so that they're present in every
> new instance of your command shell?
> * When you open a new shell / terminal window, you can type the
> command 'env', and, in the output from that command, see each and
> every one of the environment variables listed in the "Setting Up
> CollectionSpace" section of the various installation documents, such
> as http://wiki.collectionspace.org/x/1oHyBQ ?
>
> Aron
>
> On Fri, May 25, 2012 at 2:21 PM, Al Bersch <abersch@museumca.org> wrote:
>> Hi Aron, Jesse,
>>
>> Thanks for getting back. We ended up hard-coding our password to the
>> variable, and that worked. So ant create_db import ran successfully.
>> However, I still want to run the Ant buildfile you sent to try to locate
>> the
>> problem the environment variables.
>>
>> We started the servers, but can't find our tenant, which leaves us with
>> more questions (and thanks again for all your help). What should we have
>> in
>> our Tables, and what should we have listed for Tenants? After we created
>> our
>> tenant, our tenant table is showing up empty.
>>
>> Also, can someone share an example of a host file (we didn't put in a DNS,
>> just used localhost)? It would be great to see what it is supposed to look
>> like.
>>
>> Thank you,
>>
>> Al Bersch
>> Digital Project Coordinator
>> Oakland Museum of California
>> 1000 Oak Street, Oakland, CA 94607
>> abersch@museumca.org
>> 510-318-8468
>> ________________________________
>> From: "Aron Roberts" <aron@socrates.berkeley.edu>
>> To: "Al Bersch" <abersch@museumca.org>
>> Cc: talk@lists.collectionspace.org
>> Sent: Friday, May 25, 2012 1:22:50 PM
>>
>> Subject: Re: [Talk] space user password error
>>
>> Al,
>>
>> You can try pasting this simple Ant buildfile into a file named
>> "build.xml" in some temporary directory:
>>
>> <project name="test-env-vars" default="test-env-vars" basedir=".">
>> <!-- environment should be declared first -->
>> <property environment="env" />
>> <target name="test-env-vars">
>> <echo
>> message="CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}"/>
>> </target>
>> </project>
>>
>> and then invoke it, from that directory, via 'ant'. This will let you
>> know - in a simple way, without any filtering - whether Ant can 'see'
>> your environment variables. If it succeeds at finding the values in
>> your environment variables, you'll see something like:
>>
>> test-env-vars:
>> [echo] CSPACE_JEESERVER_HOME=/usr/local/share/apache-tomcat-6.0.33
>> BUILD SUCCESSFUL
>>
>> and if it fails, you'll see:
>>
>> test-env-vars:
>> [echo] CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}
>> BUILD SUCCESSFUL
>>
>> If it can't find the values in your environment variables, then you
>> might look into that discussion thread in that Nabble-archived post,
>> included in a previous message on this topic, to see if any of the
>> issues mentioned there might apply in your situation.
>>
>> Aron
>>
>> On Fri, May 25, 2012 at 1:13 PM, Jesse Martinez
>> <jmartinez@movingimage.us> wrote:
>>> Hi Al,
>>>
>>> Just a quick thought, are you using special characters or punctuation
>>> in your cspace password? I once had an issue using dollar signs $ in a
>>> postgresql password.
>>>
>>> - Jesse
>>>
>>> On Fri, May 25, 2012 at 2:17 PM, Al Bersch <abersch@museumca.org> wrote:
>>>> Hi Aron and talk,
>>>>
>>>> It looks like I spoke too soon. We are still getting a build failed
>>>> message
>>>> (verbose version below) and it appears that our environment variables
>>>> are
>>>> not being recognized, even though we can find the right path if we echo
>>>> the
>>>> environment variables. We continue to get the message that the cspace
>>>> user
>>>> password can't be authenticated. We verified that the password is set in
>>>> the
>>>> environment variable. We can echo and it kicks back the password. Once
>>>> we
>>>> set the cspace user password, we can log into postgres with that user
>>>> password, until we run the script and after that we can't log in until
>>>> we
>>>> reset the password.
>>>>
>>>> Any thoughts? Much appreciated!
>>>>
>>>> Thanks,
>>>>
>>>> Al
>>>>
>>>> museumcatest:services admin$ ant create_db import -v
>>>> Apache Ant(TM) version 1.8.2 compiled on June 3 2011
>>>> Trying the default build file: build.xml
>>>> Buildfile: /Users/admin/Downloads/services/build.xml
>>>> Detected Java version: 1.6 in:
>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>> Detected OS: Mac OS X
>>>> parsing buildfile /Users/admin/Downloads/services/build.xml with URI =
>>>> file:/Users/admin/Downloads/services/build.xml
>>>> Project base dir set to: /Users/admin/Downloads/services
>>>> parsing buildfile
>>>> jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
>>>> with
>>>> URI =
>>>> jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
>>>> from a zip file
>>>> [property] Loading Environment env.
>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>> Build sequence for target(s) `create_db' is [create_base_db, create_db]
>>>> Complete build sequence is [create_base_db, create_db, undeploy,
>>>> clean-windows, checkvars, install-unix, install-windows, install,
>>>> setup_initdb.sql, deploy, package-unix, package-windows, package,
>>>> eclipse-unix, dist_installer, dist, dist-jee-nuxeo, import,
>>>> test-windows,
>>>> hotdeploy, init, dist-jee-domains, clean-unix, clean, eclipse-windows,
>>>> eclipse, test-unix, gen_ddl, test, dist-jee-cspace, doc, ]
>>>>
>>>> create_base_db:
>>>> [sql] connecting to jdbc:postgresql://localhost:5432
>>>> [sql] Loading org.postgresql.Driver using AntClassLoader with
>>>> classpath
>>>>
>>>>
>>>> /usr/local/share/apache-tomcat-6.0.33/cspace/services/db/jdbc_drivers/postgresql-8.4-702.jdbc4.jar
>>>> [sql] Executing resource:
>>>>
>>>>
>>>> /usr/local/share/apache-tomcat-6.0.33/cspace/services/db/postgresql/init_db.sql
>>>> [sql] SQL: DROP database IF EXISTS cspace
>>>> [sql] 0 rows affected
>>>> [sql] SQL: DROP database IF EXISTS nuxeo
>>>> [sql] 0 rows affected
>>>> [sql] SQL: DROP USER IF EXISTS nuxeo
>>>> [sql] 0 rows affected
>>>> [sql] SQL: DROP USER IF EXISTS cspace
>>>> [sql] 0 rows affected
>>>> [sql] SQL: DROP USER IF EXISTS reader
>>>> [sql] 0 rows affected
>>>> [sql] SQL: CREATE ROLE nuxeo WITH PASSWORD
>>>> 'your_nuxeo_database_user_password_here' LOGIN
>>>> [sql] 0 rows affected
>>>> [sql] SQL: CREATE ROLE cspace WITH PASSWORD
>>>> 'your_cspace_database_user_password_here' LOGIN
>>>> [sql] 0 rows affected
>>>> [sql] SQL: CREATE ROLE reader WITH PASSWORD 'read' LOGIN
>>>> [sql] 0 rows affected
>>>> [sql] SQL: CREATE DATABASE cspace ENCODING 'UTF8' OWNER cspace
>>>> [sql] 0 rows affected
>>>> [sql] SQL: CREATE DATABASE nuxeo ENCODING 'UTF8' OWNER nuxeo
>>>> [sql] 0 rows affected
>>>> [sql] SQL: GRANT CONNECT ON DATABASE nuxeo TO reader
>>>> [sql] 0 rows affected
>>>> [sql] 11 of 11 SQL statements executed successfully
>>>>
>>>> create_db:
>>>> Detected Java version: 1.6 in:
>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>> Detected OS: Mac OS X
>>>> [ant] calling target(s) [create_db] in build file
>>>> /Users/admin/Downloads/services/services/build.xml
>>>> parsing buildfile /Users/admin/Downloads/services/services/build.xml
>>>> with
>>>> URI = file:/Users/admin/Downloads/services/services/build.xml
>>>> Project base dir set to: /Users/admin/Downloads/services/services
>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.DB_PASSWORD_NUXEO" has not been set
>>>> Property "env.DB_PASSWORD" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.DB_USER" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.DB_PASSWORD_CSPACE" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>> [ant] Entering
>>>> /Users/admin/Downloads/services/services/build.xml...
>>>> Build sequence for target(s) `create_db' is [create_db]
>>>> Complete build sequence is [create_db, undeploy, clean-windows,
>>>> install-unix, install-windows, install, deploy, doc-windows,
>>>> package-unix,
>>>> package-windows, package, dist_installer, import,
>>>> copy-dependencies-reports,
>>>> test-windows, doc-unix, doc, dist, hotdeploy, clean-unix, clean,
>>>> test-unix,
>>>> gen_ddl, test, generate-dependencies-reports, ]
>>>>
>>>> create_db:
>>>> Detected Java version: 1.6 in:
>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>> Detected OS: Mac OS X
>>>> [ant] calling target(s) [create_db] in build file
>>>> /Users/admin/Downloads/services/services/authentication/build.xml
>>>> parsing buildfile
>>>> /Users/admin/Downloads/services/services/authentication/build.xml with
>>>> URI =
>>>> file:/Users/admin/Downloads/services/services/authentication/build.xml
>>>> Project base dir set to:
>>>> /Users/admin/Downloads/services/services/authentication
>>>> [property] Loading Environment env.
>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>> [ant] Entering
>>>> /Users/admin/Downloads/services/services/authentication/build.xml...
>>>> Build sequence for target(s) `create_db' is [create_db]
>>>> Complete build sequence is [create_db, undeploy, clean-windows,
>>>> install-unix, install-windows, install, deploy, package-unix,
>>>> package-windows, package, test-windows, dist, clean-unix, clean,
>>>> test-unix,
>>>> gen_ddl, test, ]
>>>>
>>>> create_db:
>>>> Detected Java version: 1.6 in:
>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>> Detected OS: Mac OS X
>>>> [ant] calling target(s) [create_db] in build file
>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml
>>>> parsing buildfile
>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml
>>>> with URI =
>>>>
>>>>
>>>> file:/Users/admin/Downloads/services/services/authentication/pstore/build.xml
>>>> Project base dir set to:
>>>> /Users/admin/Downloads/services/services/authentication/pstore
>>>> [property] Loading Environment env.
>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>> [ant] Entering
>>>>
>>>>
>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml...
>>>> Build sequence for target(s) `create_db' is [create_db]
>>>> Complete build sequence is [create_db, check.db.scripts.deploy.dir,
>>>> undeploy, clean-windows, setup_hibernate.cfg, install-unix,
>>>> install-windows,
>>>> install, deploy, package-unix, package-windows, package, gen_ddl-unix,
>>>> test-windows, gen_ddl-windows, dist, clean-unix, clean, init, test-unix,
>>>> gen_ddl, test, ]
>>>>
>>>> create_db:
>>>> [sql] connecting to jdbc:postgresql://localhost:5432/cspace
>>>> [sql] Loading org.postgresql.Driver using a cached AntClassLoader.
>>>> [ant] Exiting
>>>>
>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml.
>>>> [ant] Exiting
>>>> /Users/admin/Downloads/services/services/authentication/build.xml.
>>>> [ant] Exiting /Users/admin/Downloads/services/services/build.xml.
>>>>
>>>> BUILD FAILED
>>>> /Users/admin/Downloads/services/build.xml:210: The following error
>>>> occurred
>>>> while executing this line:
>>>> /Users/admin/Downloads/services/services/build.xml:136: The following
>>>> error
>>>> occurred while executing this line:
>>>> /Users/admin/Downloads/services/services/authentication/build.xml:117:
>>>> The
>>>> following error occurred while executing this line:
>>>>
>>>>
>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
>>>> org.postgresql.util.PSQLException: FATAL: password authentication failed
>>>> for
>>>> user "cspace"
>>>> at
>>>>
>>>>
>>>> org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:291)
>>>> at
>>>>
>>>>
>>>> org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:108)
>>>> at
>>>>
>>>>
>>>> org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)
>>>> at
>>>>
>>>>
>>>> org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:125)
>>>> at
>>>>
>>>>
>>>> org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Connection.java:30)
>>>> at
>>>>
>>>>
>>>> org.postgresql.jdbc3g.AbstractJdbc3gConnection.<init>(AbstractJdbc3gConnection.java:22)
>>>> at
>>>>
>>>>
>>>> org.postgresql.jdbc4.AbstractJdbc4Connection.<init>(AbstractJdbc4Connection.java:30)
>>>> at org.postgresql.jdbc4.Jdbc4Connection.<init>(Jdbc4Connection.java:24)
>>>> at org.postgresql.Driver.makeConnection(Driver.java:393)
>>>> at org.postgresql.Driver.connect(Driver.java:267)
>>>> at
>>>> org.apache.tools.ant.taskdefs.JDBCTask.getConnection(JDBCTask.java:370)
>>>> at org.apache.tools.ant.taskdefs.SQLExec.getConnection(SQLExec.java:942)
>>>> at org.apache.tools.ant.taskdefs.SQLExec.execute(SQLExec.java:614)
>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>>>> at
>>>>
>>>>
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>> at
>>>>
>>>>
>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>> at
>>>>
>>>>
>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>>>> at
>>>>
>>>>
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>> at
>>>>
>>>>
>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>> at
>>>>
>>>>
>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>>>> at
>>>>
>>>>
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>> at
>>>>
>>>>
>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>> at
>>>>
>>>>
>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>>
>>>>
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>> at
>>>>
>>>>
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>> at
>>>>
>>>>
>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>> at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
>>>> at
>>>>
>>>>
>>>> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>> at org.apache.tools.ant.Main.runBuild(Main.java:809)
>>>> at org.apache.tools.ant.Main.startAnt(Main.java:217)
>>>> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
>>>> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
>>>>
>>>> Total time: 1 second
>>>>
>>>> Al Bersch
>>>> Digital Project Coordinator
>>>> Oakland Museum of California
>>>> 1000 Oak Street, Oakland, CA 94607
>>>> abersch@museumca.org
>>>> 510-318-8468
>>>> ________________________________
>>>> From: "Aron Roberts" <aron@socrates.berkeley.edu>
>>>> To: "Al Bersch" <abersch@museumca.org>
>>>> Sent: Friday, May 25, 2012 9:32:47 AM
>>>>
>>>> Subject: Re: [Talk] space user password error
>>>>
>>>> Hi Al,
>>>>
>>>> Many thanks - it's terrific you resolved this in this way! And
>>>> your note on the Talk list will help others who may run into the same
>>>> situation.
>>>>
>>>> (Until reading your note, I wasn't aware of the ENCRYPTED option for
>>>> passwords in PostgreSQL:
>>>> http://www.postgresql.org/docs/9.1/static/sql-createuser.html).
>>>>
>>>> Best,
>>>> Aron
>>>>
>>>>
>>>> On Fri, May 25, 2012 at 8:56 AM, 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
>>>>> ________________________________
>>>>> 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:
>>>>>> Hello,
>>>>>>
>>>>>> After following the steps for creating our tenant we get an error when
>>>>>> we
>>>>>> run the ant create_db import. With the following error:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
>>>>>> org.postgresql.util.PSQLException: FATAL: password authentication
>>>>>> failed
>>>>>> for
>>>>>> user "space".
>>>>>>
>>>>>> We believe we verified the password is set to what our environment
>>>>>> variable
>>>>>> is set to: $DB_PASSWORD_CSPACE.
>>>>>>
>>>>>> We would appreciate any ideas/advice!
>>>>>>
>>>>>> Thank you!
>>>>>> Al Bersch
>>>>>> Digital Project Coordinator
>>>>>> Oakland Museum of California
>>>>>> 1000 Oak Street, Oakland, CA 94607
>>>>>> abersch@museumca.org
>>>>>> 510-318-8468
>>>>>>
>>>>>> _______________________________________________
>>>>>> Talk mailing list
>>>>>> Talk@lists.collectionspace.org
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>>>>
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Talk mailing list
>>>> Talk@lists.collectionspace.org
>>>>
>>>>
>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>>
>>>
>>> _______________________________________________
>>> Talk mailing list
>>> Talk@lists.collectionspace.org
>>>
>>>
>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>
>
>
> _______________________________________________
> Talk mailing list
> Talk@lists.collectionspace.org
> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>
_______________________________________________
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
AR
Aron Roberts
Thu, May 31, 2012 4:11 PM
Ahh ... excellent suggestion, Chris!
(Will make a note to add this to the install documents.)
Al, when you can, we'd welcome an update on whether Chris might have
identified what was happening in your situation - thanks!
Aron
On Thu, May 31, 2012 at 6:30 AM, Christopher Pott
Christopher.Pott@smk.dk wrote:
Hi Al,
I'm working on configuring CollectionSpace at the National Gallery in Denmark.
I just thought there was also a chance your earlier problems with environment variables could be related to using different OS user permissions during various stages of the installation. For example, at least in Debian Linux, if you export your environment variables as 'myuser' in "/home/myuser/.bashrc", but then run the build command as 'root' (via 'sudo') then your current variables won't be preserved (unless you use 'sudo -E').
Regards,
Chris
-----Oprindelig meddelelse-----
Fra: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] På vegne af Aron Roberts
Sendt: 26. maj 2012 02:42
Til: Al Bersch
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] space user password error
Thanks, Al. This all sounds good so far. Here's hoping the reinstall
takes care of the problem!
If for any reason it doesn't, some more thoughts:
- Make sure you're running all your 'ant' commands from the VERY top
level of the CollectionSpace services source code tree; e.g. from
/services
and not anywhere else down in the tree; e.g. /services/services
- In $HOME/bash_profile:
export CSPACE_JEESERVER_HOME="/usr/local/share/apache-tomcat-6.0.33"
export CATALINA_HOME=$CSPACE_JEESERVER_HOME
export CATALINA_PID="$CSPACE_JEESERVER_HOME/bin/tomcat.pid"
export CATALINA_OPTS="-Xmx1024m -XX:MaxPermSize=384m"
export JAVA_HOME="/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home"
export DB_USER="..."
export DB_PASSWORD="..."
export DB_PASSWORD_NUXEO="..."
export DB_PASSWORD_CSPACE="...."
export ANT_OPTS="-Xmx768m -XX:MaxPermSize=512m"
export MAVEN_OPTS="-Xmx768m -XX:MaxPermSize=512m -Dfile.encoding=UTF-8"
- This may also potentially be important, and is experimenting
with; in $HOME/.bashrc, there is this entry:
$HOME/.bash_profile
- If 1) isn't relevant, 2) checks out, and you try 3), and the
environment variables are all present, in whatever shell you may be
in, the next thing to check is whether Ant is picking them up out of
the environment.
You can try running the simple Ant buildfile pasted into an earlier
message to check on this. If Ant isn't seeing these variables, you
might try looking at the Nabble discussion thread mentioned earlier,
for any clues about issues that might be present on your system.
Aron
P.S. Jesse Martinez, I believe, added the following note to the
installation instructions,
http://wiki.collectionspace.org/display/DOC/Installing+2.3+on+Mac+OS+X+10.6.8:
If you added these lines to ~/.bashrc, to ensure these environment
variables are present in every new login shell, edit or create the
~/.bash_profile file and add the following line to that file:
. ~/.bashrc
I've basically done the converse of this, above, in part as a result
of reading posts like http://hacktux.com/bash/bashrc/bash_profile and
http://stefaanlippens.net/bashrc_and_others:
"In this case of an interactive but non-login shell, only ~/.bashrc is
executed."
(Ultimately, this may hint at necessary changes to the existing
documentation ...)
On Fri, May 25, 2012 at 4:18 PM, Al Bersch abersch@museumca.org wrote:
Hi Aron,
Thanks for your response.
In answer to your questions - yes, the installation is on a Mac OS X system,
and yes, there entries in the appropriate shell configuration file to export
the environment variables (we thinks so - we put them in the .bash profile).
As for the third question, I believe that each and every one of the
environment variables is visible upon the command 'env'.
Our plan is to reinstall and see if we can resolve the issue that way. I'll
let you know what we find out.
Thanks again,
Al
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
From: "Aron Roberts" aron@socrates.berkeley.edu
To: "Al Bersch" abersch@museumca.org
Cc: talk@lists.collectionspace.org
Sent: Friday, May 25, 2012 2:33:32 PM
Subject: Re: [Talk] space user password error
Al,
Thanks much for this update!
There are a number of environment variables that must be available
to Ant in order to successfully build the CollectionSpace services
layer, create and populate databases, and import roles, permissions,
etc. If any of those is missing, you may not have a completely
working CollectionSpace system.
It's likely to be more productive to resolve the environment
variables problem once and for all, and get a clean installation, then
to try to resolve individual problems caused by their absence, one
after the other. That will, I'm concerned, be more consuming of your
time than getting an environment in place where the installation steps
'just work.'
Just to start out, is it the case that:
- The installation is occurring on a Unix-like system (Linux, Mac OS
X, or even a Unix variant)?
- There are entries in the appropriate shell configuration file to
export these environment variables, so that they're present in every
new instance of your command shell?
- When you open a new shell / terminal window, you can type the
command 'env', and, in the output from that command, see each and
every one of the environment variables listed in the "Setting Up
CollectionSpace" section of the various installation documents, such
as http://wiki.collectionspace.org/x/1oHyBQ ?
Aron
On Fri, May 25, 2012 at 2:21 PM, Al Bersch abersch@museumca.org wrote:
Hi Aron, Jesse,
Thanks for getting back. We ended up hard-coding our password to the
variable, and that worked. So ant create_db import ran successfully.
However, I still want to run the Ant buildfile you sent to try to locate
the
problem the environment variables.
We started the servers, but can't find our tenant, which leaves us with
more questions (and thanks again for all your help). What should we have
in
our Tables, and what should we have listed for Tenants? After we created
our
tenant, our tenant table is showing up empty.
Also, can someone share an example of a host file (we didn't put in a DNS,
just used localhost)? It would be great to see what it is supposed to look
like.
Thank you,
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
From: "Aron Roberts" aron@socrates.berkeley.edu
To: "Al Bersch" abersch@museumca.org
Cc: talk@lists.collectionspace.org
Sent: Friday, May 25, 2012 1:22:50 PM
Subject: Re: [Talk] space user password error
Al,
You can try pasting this simple Ant buildfile into a file named
"build.xml" in some temporary directory:
<project name="test-env-vars" default="test-env-vars" basedir=".">
<!-- environment should be declared first -->
<property environment="env" />
<target name="test-env-vars">
<echo
message="CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}"/>
</target>
</project>
and then invoke it, from that directory, via 'ant'. This will let you
know - in a simple way, without any filtering - whether Ant can 'see'
your environment variables. If it succeeds at finding the values in
your environment variables, you'll see something like:
test-env-vars:
[echo] CSPACE_JEESERVER_HOME=/usr/local/share/apache-tomcat-6.0.33
BUILD SUCCESSFUL
and if it fails, you'll see:
test-env-vars:
[echo] CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}
BUILD SUCCESSFUL
If it can't find the values in your environment variables, then you
might look into that discussion thread in that Nabble-archived post,
included in a previous message on this topic, to see if any of the
issues mentioned there might apply in your situation.
Aron
On Fri, May 25, 2012 at 1:13 PM, Jesse Martinez
jmartinez@movingimage.us wrote:
Hi Al,
Just a quick thought, are you using special characters or punctuation
in your cspace password? I once had an issue using dollar signs $ in a
postgresql password.
On Fri, May 25, 2012 at 2:17 PM, Al Bersch abersch@museumca.org wrote:
Hi Aron and talk,
It looks like I spoke too soon. We are still getting a build failed
message
(verbose version below) and it appears that our environment variables
are
not being recognized, even though we can find the right path if we echo
the
environment variables. We continue to get the message that the cspace
user
password can't be authenticated. We verified that the password is set in
the
environment variable. We can echo and it kicks back the password. Once
we
set the cspace user password, we can log into postgres with that user
password, until we run the script and after that we can't log in until
we
reset the password.
Any thoughts? Much appreciated!
Thanks,
Al
museumcatest:services admin$ ant create_db import -v
Apache Ant(TM) version 1.8.2 compiled on June 3 2011
Trying the default build file: build.xml
Buildfile: /Users/admin/Downloads/services/build.xml
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
parsing buildfile /Users/admin/Downloads/services/build.xml with URI =
file:/Users/admin/Downloads/services/build.xml
Project base dir set to: /Users/admin/Downloads/services
parsing buildfile
jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
with
URI =
jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
from a zip file
[property] Loading Environment env.
[property] Loading /Users/admin/Downloads/services/build.properties
Build sequence for target(s) `create_db' is [create_base_db, create_db]
Complete build sequence is [create_base_db, create_db, undeploy,
clean-windows, checkvars, install-unix, install-windows, install,
setup_initdb.sql, deploy, package-unix, package-windows, package,
eclipse-unix, dist_installer, dist, dist-jee-nuxeo, import,
test-windows,
hotdeploy, init, dist-jee-domains, clean-unix, clean, eclipse-windows,
eclipse, test-unix, gen_ddl, test, dist-jee-cspace, doc, ]
create_base_db:
[sql] connecting to jdbc:postgresql://localhost:5432
[sql] Loading org.postgresql.Driver using AntClassLoader with
classpath
/usr/local/share/apache-tomcat-6.0.33/cspace/services/db/jdbc_drivers/postgresql-8.4-702.jdbc4.jar
[sql] Executing resource:
/usr/local/share/apache-tomcat-6.0.33/cspace/services/db/postgresql/init_db.sql
[sql] SQL: DROP database IF EXISTS cspace
[sql] 0 rows affected
[sql] SQL: DROP database IF EXISTS nuxeo
[sql] 0 rows affected
[sql] SQL: DROP USER IF EXISTS nuxeo
[sql] 0 rows affected
[sql] SQL: DROP USER IF EXISTS cspace
[sql] 0 rows affected
[sql] SQL: DROP USER IF EXISTS reader
[sql] 0 rows affected
[sql] SQL: CREATE ROLE nuxeo WITH PASSWORD
'your_nuxeo_database_user_password_here' LOGIN
[sql] 0 rows affected
[sql] SQL: CREATE ROLE cspace WITH PASSWORD
'your_cspace_database_user_password_here' LOGIN
[sql] 0 rows affected
[sql] SQL: CREATE ROLE reader WITH PASSWORD 'read' LOGIN
[sql] 0 rows affected
[sql] SQL: CREATE DATABASE cspace ENCODING 'UTF8' OWNER cspace
[sql] 0 rows affected
[sql] SQL: CREATE DATABASE nuxeo ENCODING 'UTF8' OWNER nuxeo
[sql] 0 rows affected
[sql] SQL: GRANT CONNECT ON DATABASE nuxeo TO reader
[sql] 0 rows affected
[sql] 11 of 11 SQL statements executed successfully
create_db:
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
[ant] calling target(s) [create_db] in build file
/Users/admin/Downloads/services/services/build.xml
parsing buildfile /Users/admin/Downloads/services/services/build.xml
with
URI = file:/Users/admin/Downloads/services/services/build.xml
Project base dir set to: /Users/admin/Downloads/services/services
[property] Loading /Users/admin/Downloads/services/build.properties
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.DB_PASSWORD_NUXEO" has not been set
Property "env.DB_PASSWORD" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.DB_USER" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.DB_PASSWORD_CSPACE" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
[ant] Entering
/Users/admin/Downloads/services/services/build.xml...
Build sequence for target(s) `create_db' is [create_db]
Complete build sequence is [create_db, undeploy, clean-windows,
install-unix, install-windows, install, deploy, doc-windows,
package-unix,
package-windows, package, dist_installer, import,
copy-dependencies-reports,
test-windows, doc-unix, doc, dist, hotdeploy, clean-unix, clean,
test-unix,
gen_ddl, test, generate-dependencies-reports, ]
create_db:
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
[ant] calling target(s) [create_db] in build file
/Users/admin/Downloads/services/services/authentication/build.xml
parsing buildfile
/Users/admin/Downloads/services/services/authentication/build.xml with
URI =
file:/Users/admin/Downloads/services/services/authentication/build.xml
Project base dir set to:
/Users/admin/Downloads/services/services/authentication
[property] Loading Environment env.
[property] Loading /Users/admin/Downloads/services/build.properties
[ant] Entering
/Users/admin/Downloads/services/services/authentication/build.xml...
Build sequence for target(s) `create_db' is [create_db]
Complete build sequence is [create_db, undeploy, clean-windows,
install-unix, install-windows, install, deploy, package-unix,
package-windows, package, test-windows, dist, clean-unix, clean,
test-unix,
gen_ddl, test, ]
create_db:
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
[ant] calling target(s) [create_db] in build file
/Users/admin/Downloads/services/services/authentication/pstore/build.xml
parsing buildfile
/Users/admin/Downloads/services/services/authentication/pstore/build.xml
with URI =
file:/Users/admin/Downloads/services/services/authentication/pstore/build.xml
Project base dir set to:
/Users/admin/Downloads/services/services/authentication/pstore
[property] Loading Environment env.
[property] Loading /Users/admin/Downloads/services/build.properties
[ant] Entering
/Users/admin/Downloads/services/services/authentication/pstore/build.xml...
Build sequence for target(s) `create_db' is [create_db]
Complete build sequence is [create_db, check.db.scripts.deploy.dir,
undeploy, clean-windows, setup_hibernate.cfg, install-unix,
install-windows,
install, deploy, package-unix, package-windows, package, gen_ddl-unix,
test-windows, gen_ddl-windows, dist, clean-unix, clean, init, test-unix,
gen_ddl, test, ]
create_db:
[sql] connecting to jdbc:postgresql://localhost:5432/cspace
[sql] Loading org.postgresql.Driver using a cached AntClassLoader.
[ant] Exiting
/Users/admin/Downloads/services/services/authentication/pstore/build.xml.
[ant] Exiting
/Users/admin/Downloads/services/services/authentication/build.xml.
[ant] Exiting /Users/admin/Downloads/services/services/build.xml.
BUILD FAILED
/Users/admin/Downloads/services/build.xml:210: The following error
occurred
while executing this line:
/Users/admin/Downloads/services/services/build.xml:136: The following
error
occurred while executing this line:
/Users/admin/Downloads/services/services/authentication/build.xml:117:
The
following error occurred while executing this line:
/Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
org.postgresql.util.PSQLException: FATAL: password authentication failed
for
user "cspace"
at
org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:291)
at
org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:108)
at
org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)
at
org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:125)
at
org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Connection.java:30)
at
org.postgresql.jdbc3g.AbstractJdbc3gConnection.<init>(AbstractJdbc3gConnection.java:22)
at
org.postgresql.jdbc4.AbstractJdbc4Connection.<init>(AbstractJdbc4Connection.java:30)
at org.postgresql.jdbc4.Jdbc4Connection.<init>(Jdbc4Connection.java:24)
at org.postgresql.Driver.makeConnection(Driver.java:393)
at org.postgresql.Driver.connect(Driver.java:267)
at
org.apache.tools.ant.taskdefs.JDBCTask.getConnection(JDBCTask.java:370)
at org.apache.tools.ant.taskdefs.SQLExec.getConnection(SQLExec.java:942)
at org.apache.tools.ant.taskdefs.SQLExec.execute(SQLExec.java:614)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.Main.runBuild(Main.java:809)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
Total time: 1 second
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
From: "Aron Roberts" aron@socrates.berkeley.edu
To: "Al Bersch" abersch@museumca.org
Sent: Friday, May 25, 2012 9:32:47 AM
Subject: Re: [Talk] space user password error
Hi Al,
Many thanks - it's terrific you resolved this in this way! And
your note on the Talk list will help others who may run into the same
situation.
(Until reading your note, I wasn't aware of the ENCRYPTED option for
passwords in PostgreSQL:
http://www.postgresql.org/docs/9.1/static/sql-createuser.html).
Best,
Aron
On Fri, May 25, 2012 at 8:56 AM, 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
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:
Hello,
After following the steps for creating our tenant we get an error when
we
run the ant create_db import. With the following error:
/Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
org.postgresql.util.PSQLException: FATAL: password authentication
failed
for
user "space".
We believe we verified the password is set to what our environment
variable
is set to: $DB_PASSWORD_CSPACE.
We would appreciate any ideas/advice!
Thank you!
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Ahh ... excellent suggestion, Chris!
(Will make a note to add this to the install documents.)
Al, when you can, we'd welcome an update on whether Chris might have
identified what was happening in your situation - thanks!
Aron
On Thu, May 31, 2012 at 6:30 AM, Christopher Pott
<Christopher.Pott@smk.dk> wrote:
> Hi Al,
>
> I'm working on configuring CollectionSpace at the National Gallery in Denmark.
>
> I just thought there was also a chance your earlier problems with environment variables could be related to using different OS user permissions during various stages of the installation. For example, at least in Debian Linux, if you export your environment variables as 'myuser' in "/home/myuser/.bashrc", but then run the build command as 'root' (via 'sudo') then your current variables won't be preserved (unless you use 'sudo -E').
>
> Regards,
> Chris
>
>
> -----Oprindelig meddelelse-----
> Fra: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] På vegne af Aron Roberts
> Sendt: 26. maj 2012 02:42
> Til: Al Bersch
> Cc: talk@lists.collectionspace.org
> Emne: Re: [Talk] space user password error
>
> Thanks, Al. This all sounds good so far. Here's hoping the reinstall
> takes care of the problem!
>
> If for any reason it doesn't, some more thoughts:
>
> 1) Make sure you're running all your 'ant' commands from the VERY top
> level of the CollectionSpace services source code tree; e.g. from
>
> /services
>
> and not anywhere else down in the tree; e.g. /services/services
>
> 2) In $HOME/bash_profile:
>
> export CSPACE_JEESERVER_HOME="/usr/local/share/apache-tomcat-6.0.33"
> export CATALINA_HOME=$CSPACE_JEESERVER_HOME
> export CATALINA_PID="$CSPACE_JEESERVER_HOME/bin/tomcat.pid"
> export CATALINA_OPTS="-Xmx1024m -XX:MaxPermSize=384m"
> export JAVA_HOME="/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home"
> export DB_USER="..."
> export DB_PASSWORD="..."
> export DB_PASSWORD_NUXEO="..."
> export DB_PASSWORD_CSPACE="...."
> export ANT_OPTS="-Xmx768m -XX:MaxPermSize=512m"
> export MAVEN_OPTS="-Xmx768m -XX:MaxPermSize=512m -Dfile.encoding=UTF-8"
>
> 3) This *may* also potentially be important, and is experimenting
> with; in $HOME/.bashrc, there is this entry:
>
> $HOME/.bash_profile
>
> 4) If 1) isn't relevant, 2) checks out, and you try 3), and the
> environment variables are all present, in whatever shell you may be
> in, the next thing to check is whether Ant is picking them up out of
> the environment.
>
> You can try running the simple Ant buildfile pasted into an earlier
> message to check on this. If Ant isn't seeing these variables, you
> might try looking at the Nabble discussion thread mentioned earlier,
> for any clues about issues that might be present on your system.
>
> Aron
>
> P.S. Jesse Martinez, I believe, added the following note to the
> installation instructions,
> http://wiki.collectionspace.org/display/DOC/Installing+2.3+on+Mac+OS+X+10.6.8:
>
> If you added these lines to ~/.bashrc, to ensure these environment
> variables are present in every new login shell, edit or create the
> ~/.bash_profile file and add the following line to that file:
> . ~/.bashrc
>
> I've basically done the converse of this, above, in part as a result
> of reading posts like http://hacktux.com/bash/bashrc/bash_profile and
> http://stefaanlippens.net/bashrc_and_others:
>
> "In this case of an interactive but non-login shell, only ~/.bashrc is
> executed."
>
> (Ultimately, this may hint at necessary changes to the existing
> documentation ...)
>
> On Fri, May 25, 2012 at 4:18 PM, Al Bersch <abersch@museumca.org> wrote:
>> Hi Aron,
>>
>> Thanks for your response.
>>
>> In answer to your questions - yes, the installation is on a Mac OS X system,
>> and yes, there entries in the appropriate shell configuration file to export
>> the environment variables (we thinks so - we put them in the .bash profile).
>> As for the third question, I believe that each and every one of the
>> environment variables is visible upon the command 'env'.
>>
>> Our plan is to reinstall and see if we can resolve the issue that way. I'll
>> let you know what we find out.
>>
>> Thanks again,
>>
>> Al
>>
>> Al Bersch
>> Digital Project Coordinator
>> Oakland Museum of California
>> 1000 Oak Street, Oakland, CA 94607
>> abersch@museumca.org
>> 510-318-8468
>> ________________________________
>> From: "Aron Roberts" <aron@socrates.berkeley.edu>
>> To: "Al Bersch" <abersch@museumca.org>
>> Cc: talk@lists.collectionspace.org
>> Sent: Friday, May 25, 2012 2:33:32 PM
>>
>> Subject: Re: [Talk] space user password error
>>
>> Al,
>>
>> Thanks much for this update!
>>
>> There are a number of environment variables that must be available
>> to Ant in order to successfully build the CollectionSpace services
>> layer, create and populate databases, and import roles, permissions,
>> etc. If any of those is missing, you may not have a completely
>> working CollectionSpace system.
>>
>> It's likely to be more productive to resolve the environment
>> variables problem once and for all, and get a clean installation, then
>> to try to resolve individual problems caused by their absence, one
>> after the other. That will, I'm concerned, be more consuming of your
>> time than getting an environment in place where the installation steps
>> 'just work.'
>>
>> Just to start out, is it the case that:
>>
>> * The installation is occurring on a Unix-like system (Linux, Mac OS
>> X, or even a Unix variant)?
>> * There are entries in the appropriate shell configuration file to
>> export these environment variables, so that they're present in every
>> new instance of your command shell?
>> * When you open a new shell / terminal window, you can type the
>> command 'env', and, in the output from that command, see each and
>> every one of the environment variables listed in the "Setting Up
>> CollectionSpace" section of the various installation documents, such
>> as http://wiki.collectionspace.org/x/1oHyBQ ?
>>
>> Aron
>>
>> On Fri, May 25, 2012 at 2:21 PM, Al Bersch <abersch@museumca.org> wrote:
>>> Hi Aron, Jesse,
>>>
>>> Thanks for getting back. We ended up hard-coding our password to the
>>> variable, and that worked. So ant create_db import ran successfully.
>>> However, I still want to run the Ant buildfile you sent to try to locate
>>> the
>>> problem the environment variables.
>>>
>>> We started the servers, but can't find our tenant, which leaves us with
>>> more questions (and thanks again for all your help). What should we have
>>> in
>>> our Tables, and what should we have listed for Tenants? After we created
>>> our
>>> tenant, our tenant table is showing up empty.
>>>
>>> Also, can someone share an example of a host file (we didn't put in a DNS,
>>> just used localhost)? It would be great to see what it is supposed to look
>>> like.
>>>
>>> Thank you,
>>>
>>> Al Bersch
>>> Digital Project Coordinator
>>> Oakland Museum of California
>>> 1000 Oak Street, Oakland, CA 94607
>>> abersch@museumca.org
>>> 510-318-8468
>>> ________________________________
>>> From: "Aron Roberts" <aron@socrates.berkeley.edu>
>>> To: "Al Bersch" <abersch@museumca.org>
>>> Cc: talk@lists.collectionspace.org
>>> Sent: Friday, May 25, 2012 1:22:50 PM
>>>
>>> Subject: Re: [Talk] space user password error
>>>
>>> Al,
>>>
>>> You can try pasting this simple Ant buildfile into a file named
>>> "build.xml" in some temporary directory:
>>>
>>> <project name="test-env-vars" default="test-env-vars" basedir=".">
>>> <!-- environment should be declared first -->
>>> <property environment="env" />
>>> <target name="test-env-vars">
>>> <echo
>>> message="CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}"/>
>>> </target>
>>> </project>
>>>
>>> and then invoke it, from that directory, via 'ant'. This will let you
>>> know - in a simple way, without any filtering - whether Ant can 'see'
>>> your environment variables. If it succeeds at finding the values in
>>> your environment variables, you'll see something like:
>>>
>>> test-env-vars:
>>> [echo] CSPACE_JEESERVER_HOME=/usr/local/share/apache-tomcat-6.0.33
>>> BUILD SUCCESSFUL
>>>
>>> and if it fails, you'll see:
>>>
>>> test-env-vars:
>>> [echo] CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}
>>> BUILD SUCCESSFUL
>>>
>>> If it can't find the values in your environment variables, then you
>>> might look into that discussion thread in that Nabble-archived post,
>>> included in a previous message on this topic, to see if any of the
>>> issues mentioned there might apply in your situation.
>>>
>>> Aron
>>>
>>> On Fri, May 25, 2012 at 1:13 PM, Jesse Martinez
>>> <jmartinez@movingimage.us> wrote:
>>>> Hi Al,
>>>>
>>>> Just a quick thought, are you using special characters or punctuation
>>>> in your cspace password? I once had an issue using dollar signs $ in a
>>>> postgresql password.
>>>>
>>>> - Jesse
>>>>
>>>> On Fri, May 25, 2012 at 2:17 PM, Al Bersch <abersch@museumca.org> wrote:
>>>>> Hi Aron and talk,
>>>>>
>>>>> It looks like I spoke too soon. We are still getting a build failed
>>>>> message
>>>>> (verbose version below) and it appears that our environment variables
>>>>> are
>>>>> not being recognized, even though we can find the right path if we echo
>>>>> the
>>>>> environment variables. We continue to get the message that the cspace
>>>>> user
>>>>> password can't be authenticated. We verified that the password is set in
>>>>> the
>>>>> environment variable. We can echo and it kicks back the password. Once
>>>>> we
>>>>> set the cspace user password, we can log into postgres with that user
>>>>> password, until we run the script and after that we can't log in until
>>>>> we
>>>>> reset the password.
>>>>>
>>>>> Any thoughts? Much appreciated!
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Al
>>>>>
>>>>> museumcatest:services admin$ ant create_db import -v
>>>>> Apache Ant(TM) version 1.8.2 compiled on June 3 2011
>>>>> Trying the default build file: build.xml
>>>>> Buildfile: /Users/admin/Downloads/services/build.xml
>>>>> Detected Java version: 1.6 in:
>>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>>> Detected OS: Mac OS X
>>>>> parsing buildfile /Users/admin/Downloads/services/build.xml with URI =
>>>>> file:/Users/admin/Downloads/services/build.xml
>>>>> Project base dir set to: /Users/admin/Downloads/services
>>>>> parsing buildfile
>>>>> jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
>>>>> with
>>>>> URI =
>>>>> jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
>>>>> from a zip file
>>>>> [property] Loading Environment env.
>>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>>> Build sequence for target(s) `create_db' is [create_base_db, create_db]
>>>>> Complete build sequence is [create_base_db, create_db, undeploy,
>>>>> clean-windows, checkvars, install-unix, install-windows, install,
>>>>> setup_initdb.sql, deploy, package-unix, package-windows, package,
>>>>> eclipse-unix, dist_installer, dist, dist-jee-nuxeo, import,
>>>>> test-windows,
>>>>> hotdeploy, init, dist-jee-domains, clean-unix, clean, eclipse-windows,
>>>>> eclipse, test-unix, gen_ddl, test, dist-jee-cspace, doc, ]
>>>>>
>>>>> create_base_db:
>>>>> [sql] connecting to jdbc:postgresql://localhost:5432
>>>>> [sql] Loading org.postgresql.Driver using AntClassLoader with
>>>>> classpath
>>>>>
>>>>>
>>>>> /usr/local/share/apache-tomcat-6.0.33/cspace/services/db/jdbc_drivers/postgresql-8.4-702.jdbc4.jar
>>>>> [sql] Executing resource:
>>>>>
>>>>>
>>>>> /usr/local/share/apache-tomcat-6.0.33/cspace/services/db/postgresql/init_db.sql
>>>>> [sql] SQL: DROP database IF EXISTS cspace
>>>>> [sql] 0 rows affected
>>>>> [sql] SQL: DROP database IF EXISTS nuxeo
>>>>> [sql] 0 rows affected
>>>>> [sql] SQL: DROP USER IF EXISTS nuxeo
>>>>> [sql] 0 rows affected
>>>>> [sql] SQL: DROP USER IF EXISTS cspace
>>>>> [sql] 0 rows affected
>>>>> [sql] SQL: DROP USER IF EXISTS reader
>>>>> [sql] 0 rows affected
>>>>> [sql] SQL: CREATE ROLE nuxeo WITH PASSWORD
>>>>> 'your_nuxeo_database_user_password_here' LOGIN
>>>>> [sql] 0 rows affected
>>>>> [sql] SQL: CREATE ROLE cspace WITH PASSWORD
>>>>> 'your_cspace_database_user_password_here' LOGIN
>>>>> [sql] 0 rows affected
>>>>> [sql] SQL: CREATE ROLE reader WITH PASSWORD 'read' LOGIN
>>>>> [sql] 0 rows affected
>>>>> [sql] SQL: CREATE DATABASE cspace ENCODING 'UTF8' OWNER cspace
>>>>> [sql] 0 rows affected
>>>>> [sql] SQL: CREATE DATABASE nuxeo ENCODING 'UTF8' OWNER nuxeo
>>>>> [sql] 0 rows affected
>>>>> [sql] SQL: GRANT CONNECT ON DATABASE nuxeo TO reader
>>>>> [sql] 0 rows affected
>>>>> [sql] 11 of 11 SQL statements executed successfully
>>>>>
>>>>> create_db:
>>>>> Detected Java version: 1.6 in:
>>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>>> Detected OS: Mac OS X
>>>>> [ant] calling target(s) [create_db] in build file
>>>>> /Users/admin/Downloads/services/services/build.xml
>>>>> parsing buildfile /Users/admin/Downloads/services/services/build.xml
>>>>> with
>>>>> URI = file:/Users/admin/Downloads/services/services/build.xml
>>>>> Project base dir set to: /Users/admin/Downloads/services/services
>>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>> Property "env.DB_PASSWORD_NUXEO" has not been set
>>>>> Property "env.DB_PASSWORD" has not been set
>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>> Property "env.DB_USER" has not been set
>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>> Property "env.DB_PASSWORD_CSPACE" has not been set
>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>> [ant] Entering
>>>>> /Users/admin/Downloads/services/services/build.xml...
>>>>> Build sequence for target(s) `create_db' is [create_db]
>>>>> Complete build sequence is [create_db, undeploy, clean-windows,
>>>>> install-unix, install-windows, install, deploy, doc-windows,
>>>>> package-unix,
>>>>> package-windows, package, dist_installer, import,
>>>>> copy-dependencies-reports,
>>>>> test-windows, doc-unix, doc, dist, hotdeploy, clean-unix, clean,
>>>>> test-unix,
>>>>> gen_ddl, test, generate-dependencies-reports, ]
>>>>>
>>>>> create_db:
>>>>> Detected Java version: 1.6 in:
>>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>>> Detected OS: Mac OS X
>>>>> [ant] calling target(s) [create_db] in build file
>>>>> /Users/admin/Downloads/services/services/authentication/build.xml
>>>>> parsing buildfile
>>>>> /Users/admin/Downloads/services/services/authentication/build.xml with
>>>>> URI =
>>>>> file:/Users/admin/Downloads/services/services/authentication/build.xml
>>>>> Project base dir set to:
>>>>> /Users/admin/Downloads/services/services/authentication
>>>>> [property] Loading Environment env.
>>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>>> [ant] Entering
>>>>> /Users/admin/Downloads/services/services/authentication/build.xml...
>>>>> Build sequence for target(s) `create_db' is [create_db]
>>>>> Complete build sequence is [create_db, undeploy, clean-windows,
>>>>> install-unix, install-windows, install, deploy, package-unix,
>>>>> package-windows, package, test-windows, dist, clean-unix, clean,
>>>>> test-unix,
>>>>> gen_ddl, test, ]
>>>>>
>>>>> create_db:
>>>>> Detected Java version: 1.6 in:
>>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>>> Detected OS: Mac OS X
>>>>> [ant] calling target(s) [create_db] in build file
>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml
>>>>> parsing buildfile
>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml
>>>>> with URI =
>>>>>
>>>>>
>>>>> file:/Users/admin/Downloads/services/services/authentication/pstore/build.xml
>>>>> Project base dir set to:
>>>>> /Users/admin/Downloads/services/services/authentication/pstore
>>>>> [property] Loading Environment env.
>>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>>> [ant] Entering
>>>>>
>>>>>
>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml...
>>>>> Build sequence for target(s) `create_db' is [create_db]
>>>>> Complete build sequence is [create_db, check.db.scripts.deploy.dir,
>>>>> undeploy, clean-windows, setup_hibernate.cfg, install-unix,
>>>>> install-windows,
>>>>> install, deploy, package-unix, package-windows, package, gen_ddl-unix,
>>>>> test-windows, gen_ddl-windows, dist, clean-unix, clean, init, test-unix,
>>>>> gen_ddl, test, ]
>>>>>
>>>>> create_db:
>>>>> [sql] connecting to jdbc:postgresql://localhost:5432/cspace
>>>>> [sql] Loading org.postgresql.Driver using a cached AntClassLoader.
>>>>> [ant] Exiting
>>>>>
>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml.
>>>>> [ant] Exiting
>>>>> /Users/admin/Downloads/services/services/authentication/build.xml.
>>>>> [ant] Exiting /Users/admin/Downloads/services/services/build.xml.
>>>>>
>>>>> BUILD FAILED
>>>>> /Users/admin/Downloads/services/build.xml:210: The following error
>>>>> occurred
>>>>> while executing this line:
>>>>> /Users/admin/Downloads/services/services/build.xml:136: The following
>>>>> error
>>>>> occurred while executing this line:
>>>>> /Users/admin/Downloads/services/services/authentication/build.xml:117:
>>>>> The
>>>>> following error occurred while executing this line:
>>>>>
>>>>>
>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
>>>>> org.postgresql.util.PSQLException: FATAL: password authentication failed
>>>>> for
>>>>> user "cspace"
>>>>> at
>>>>>
>>>>>
>>>>> org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:291)
>>>>> at
>>>>>
>>>>>
>>>>> org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:108)
>>>>> at
>>>>>
>>>>>
>>>>> org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)
>>>>> at
>>>>>
>>>>>
>>>>> org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:125)
>>>>> at
>>>>>
>>>>>
>>>>> org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Connection.java:30)
>>>>> at
>>>>>
>>>>>
>>>>> org.postgresql.jdbc3g.AbstractJdbc3gConnection.<init>(AbstractJdbc3gConnection.java:22)
>>>>> at
>>>>>
>>>>>
>>>>> org.postgresql.jdbc4.AbstractJdbc4Connection.<init>(AbstractJdbc4Connection.java:30)
>>>>> at org.postgresql.jdbc4.Jdbc4Connection.<init>(Jdbc4Connection.java:24)
>>>>> at org.postgresql.Driver.makeConnection(Driver.java:393)
>>>>> at org.postgresql.Driver.connect(Driver.java:267)
>>>>> at
>>>>> org.apache.tools.ant.taskdefs.JDBCTask.getConnection(JDBCTask.java:370)
>>>>> at org.apache.tools.ant.taskdefs.SQLExec.getConnection(SQLExec.java:942)
>>>>> at org.apache.tools.ant.taskdefs.SQLExec.execute(SQLExec.java:614)
>>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>>> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>>>>> at
>>>>>
>>>>>
>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>> at
>>>>>
>>>>>
>>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>>> at
>>>>>
>>>>>
>>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
>>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
>>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>>> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>>>>> at
>>>>>
>>>>>
>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>> at
>>>>>
>>>>>
>>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>>> at
>>>>>
>>>>>
>>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
>>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
>>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>>> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>>>>> at
>>>>>
>>>>>
>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>> at
>>>>>
>>>>>
>>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>>> at
>>>>>
>>>>>
>>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
>>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
>>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>> at
>>>>>
>>>>>
>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>> at
>>>>>
>>>>>
>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>> at
>>>>>
>>>>>
>>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>>> at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
>>>>> at
>>>>>
>>>>>
>>>>> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
>>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>>> at org.apache.tools.ant.Main.runBuild(Main.java:809)
>>>>> at org.apache.tools.ant.Main.startAnt(Main.java:217)
>>>>> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
>>>>> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
>>>>>
>>>>> Total time: 1 second
>>>>>
>>>>> Al Bersch
>>>>> Digital Project Coordinator
>>>>> Oakland Museum of California
>>>>> 1000 Oak Street, Oakland, CA 94607
>>>>> abersch@museumca.org
>>>>> 510-318-8468
>>>>> ________________________________
>>>>> From: "Aron Roberts" <aron@socrates.berkeley.edu>
>>>>> To: "Al Bersch" <abersch@museumca.org>
>>>>> Sent: Friday, May 25, 2012 9:32:47 AM
>>>>>
>>>>> Subject: Re: [Talk] space user password error
>>>>>
>>>>> Hi Al,
>>>>>
>>>>> Many thanks - it's terrific you resolved this in this way! And
>>>>> your note on the Talk list will help others who may run into the same
>>>>> situation.
>>>>>
>>>>> (Until reading your note, I wasn't aware of the ENCRYPTED option for
>>>>> passwords in PostgreSQL:
>>>>> http://www.postgresql.org/docs/9.1/static/sql-createuser.html).
>>>>>
>>>>> Best,
>>>>> Aron
>>>>>
>>>>>
>>>>> On Fri, May 25, 2012 at 8:56 AM, 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
>>>>>> ________________________________
>>>>>> 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:
>>>>>>> Hello,
>>>>>>>
>>>>>>> After following the steps for creating our tenant we get an error when
>>>>>>> we
>>>>>>> run the ant create_db import. With the following error:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
>>>>>>> org.postgresql.util.PSQLException: FATAL: password authentication
>>>>>>> failed
>>>>>>> for
>>>>>>> user "space".
>>>>>>>
>>>>>>> We believe we verified the password is set to what our environment
>>>>>>> variable
>>>>>>> is set to: $DB_PASSWORD_CSPACE.
>>>>>>>
>>>>>>> We would appreciate any ideas/advice!
>>>>>>>
>>>>>>> Thank you!
>>>>>>> Al Bersch
>>>>>>> Digital Project Coordinator
>>>>>>> Oakland Museum of California
>>>>>>> 1000 Oak Street, Oakland, CA 94607
>>>>>>> abersch@museumca.org
>>>>>>> 510-318-8468
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Talk mailing list
>>>>>>> Talk@lists.collectionspace.org
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Talk mailing list
>>>>> Talk@lists.collectionspace.org
>>>>>
>>>>>
>>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>>>
>>>>
>>>> _______________________________________________
>>>> Talk mailing list
>>>> Talk@lists.collectionspace.org
>>>>
>>>>
>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>
>>
>>
>> _______________________________________________
>> Talk mailing list
>> Talk@lists.collectionspace.org
>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>
>
> _______________________________________________
> Talk mailing list
> Talk@lists.collectionspace.org
> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>
> _______________________________________________
> Talk mailing list
> Talk@lists.collectionspace.org
> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
JM
Jesse Martinez
Thu, May 31, 2012 4:38 PM
Chris makes a good point.
I think we should assert using a dedicated user to run
CollectionSpace, at least on *nix based systems. This would help keep
environmental variables contained as well as maintaining a level of
separation from root privileges. On nightly and QA I use a 'bamboo'
user, which also owns the Bamboo CI processes, to run and own CSpace
files. On development servers I tend to use a 'cspace' user for the
same purpose.
On Thu, May 31, 2012 at 12:11 PM, Aron Roberts
aron@socrates.berkeley.edu wrote:
Ahh ... excellent suggestion, Chris!
(Will make a note to add this to the install documents.)
Al, when you can, we'd welcome an update on whether Chris might have
identified what was happening in your situation - thanks!
Aron
On Thu, May 31, 2012 at 6:30 AM, Christopher Pott
Christopher.Pott@smk.dk wrote:
Hi Al,
I'm working on configuring CollectionSpace at the National Gallery in Denmark.
I just thought there was also a chance your earlier problems with environment variables could be related to using different OS user permissions during various stages of the installation. For example, at least in Debian Linux, if you export your environment variables as 'myuser' in "/home/myuser/.bashrc", but then run the build command as 'root' (via 'sudo') then your current variables won't be preserved (unless you use 'sudo -E').
Regards,
Chris
-----Oprindelig meddelelse-----
Fra: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] På vegne af Aron Roberts
Sendt: 26. maj 2012 02:42
Til: Al Bersch
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] space user password error
Thanks, Al. This all sounds good so far. Here's hoping the reinstall
takes care of the problem!
If for any reason it doesn't, some more thoughts:
- Make sure you're running all your 'ant' commands from the VERY top
level of the CollectionSpace services source code tree; e.g. from
/services
and not anywhere else down in the tree; e.g. /services/services
- In $HOME/bash_profile:
export CSPACE_JEESERVER_HOME="/usr/local/share/apache-tomcat-6.0.33"
export CATALINA_HOME=$CSPACE_JEESERVER_HOME
export CATALINA_PID="$CSPACE_JEESERVER_HOME/bin/tomcat.pid"
export CATALINA_OPTS="-Xmx1024m -XX:MaxPermSize=384m"
export JAVA_HOME="/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home"
export DB_USER="..."
export DB_PASSWORD="..."
export DB_PASSWORD_NUXEO="..."
export DB_PASSWORD_CSPACE="...."
export ANT_OPTS="-Xmx768m -XX:MaxPermSize=512m"
export MAVEN_OPTS="-Xmx768m -XX:MaxPermSize=512m -Dfile.encoding=UTF-8"
- This may also potentially be important, and is experimenting
with; in $HOME/.bashrc, there is this entry:
$HOME/.bash_profile
- If 1) isn't relevant, 2) checks out, and you try 3), and the
environment variables are all present, in whatever shell you may be
in, the next thing to check is whether Ant is picking them up out of
the environment.
You can try running the simple Ant buildfile pasted into an earlier
message to check on this. If Ant isn't seeing these variables, you
might try looking at the Nabble discussion thread mentioned earlier,
for any clues about issues that might be present on your system.
Aron
P.S. Jesse Martinez, I believe, added the following note to the
installation instructions,
http://wiki.collectionspace.org/display/DOC/Installing+2.3+on+Mac+OS+X+10.6.8:
If you added these lines to ~/.bashrc, to ensure these environment
variables are present in every new login shell, edit or create the
~/.bash_profile file and add the following line to that file:
. ~/.bashrc
I've basically done the converse of this, above, in part as a result
of reading posts like http://hacktux.com/bash/bashrc/bash_profile and
http://stefaanlippens.net/bashrc_and_others:
"In this case of an interactive but non-login shell, only ~/.bashrc is
executed."
(Ultimately, this may hint at necessary changes to the existing
documentation ...)
On Fri, May 25, 2012 at 4:18 PM, Al Bersch abersch@museumca.org wrote:
Hi Aron,
Thanks for your response.
In answer to your questions - yes, the installation is on a Mac OS X system,
and yes, there entries in the appropriate shell configuration file to export
the environment variables (we thinks so - we put them in the .bash profile).
As for the third question, I believe that each and every one of the
environment variables is visible upon the command 'env'.
Our plan is to reinstall and see if we can resolve the issue that way. I'll
let you know what we find out.
Thanks again,
Al
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
From: "Aron Roberts" aron@socrates.berkeley.edu
To: "Al Bersch" abersch@museumca.org
Cc: talk@lists.collectionspace.org
Sent: Friday, May 25, 2012 2:33:32 PM
Subject: Re: [Talk] space user password error
Al,
Thanks much for this update!
There are a number of environment variables that must be available
to Ant in order to successfully build the CollectionSpace services
layer, create and populate databases, and import roles, permissions,
etc. If any of those is missing, you may not have a completely
working CollectionSpace system.
It's likely to be more productive to resolve the environment
variables problem once and for all, and get a clean installation, then
to try to resolve individual problems caused by their absence, one
after the other. That will, I'm concerned, be more consuming of your
time than getting an environment in place where the installation steps
'just work.'
Just to start out, is it the case that:
- The installation is occurring on a Unix-like system (Linux, Mac OS
X, or even a Unix variant)?
- There are entries in the appropriate shell configuration file to
export these environment variables, so that they're present in every
new instance of your command shell?
- When you open a new shell / terminal window, you can type the
command 'env', and, in the output from that command, see each and
every one of the environment variables listed in the "Setting Up
CollectionSpace" section of the various installation documents, such
as http://wiki.collectionspace.org/x/1oHyBQ ?
Aron
On Fri, May 25, 2012 at 2:21 PM, Al Bersch abersch@museumca.org wrote:
Hi Aron, Jesse,
Thanks for getting back. We ended up hard-coding our password to the
variable, and that worked. So ant create_db import ran successfully.
However, I still want to run the Ant buildfile you sent to try to locate
the
problem the environment variables.
We started the servers, but can't find our tenant, which leaves us with
more questions (and thanks again for all your help). What should we have
in
our Tables, and what should we have listed for Tenants? After we created
our
tenant, our tenant table is showing up empty.
Also, can someone share an example of a host file (we didn't put in a DNS,
just used localhost)? It would be great to see what it is supposed to look
like.
Thank you,
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
From: "Aron Roberts" aron@socrates.berkeley.edu
To: "Al Bersch" abersch@museumca.org
Cc: talk@lists.collectionspace.org
Sent: Friday, May 25, 2012 1:22:50 PM
Subject: Re: [Talk] space user password error
Al,
You can try pasting this simple Ant buildfile into a file named
"build.xml" in some temporary directory:
<project name="test-env-vars" default="test-env-vars" basedir=".">
<!-- environment should be declared first -->
<property environment="env" />
<target name="test-env-vars">
<echo
message="CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}"/>
</target>
</project>
and then invoke it, from that directory, via 'ant'. This will let you
know - in a simple way, without any filtering - whether Ant can 'see'
your environment variables. If it succeeds at finding the values in
your environment variables, you'll see something like:
test-env-vars:
[echo] CSPACE_JEESERVER_HOME=/usr/local/share/apache-tomcat-6.0.33
BUILD SUCCESSFUL
and if it fails, you'll see:
test-env-vars:
[echo] CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}
BUILD SUCCESSFUL
If it can't find the values in your environment variables, then you
might look into that discussion thread in that Nabble-archived post,
included in a previous message on this topic, to see if any of the
issues mentioned there might apply in your situation.
Aron
On Fri, May 25, 2012 at 1:13 PM, Jesse Martinez
jmartinez@movingimage.us wrote:
Hi Al,
Just a quick thought, are you using special characters or punctuation
in your cspace password? I once had an issue using dollar signs $ in a
postgresql password.
On Fri, May 25, 2012 at 2:17 PM, Al Bersch abersch@museumca.org wrote:
Hi Aron and talk,
It looks like I spoke too soon. We are still getting a build failed
message
(verbose version below) and it appears that our environment variables
are
not being recognized, even though we can find the right path if we echo
the
environment variables. We continue to get the message that the cspace
user
password can't be authenticated. We verified that the password is set in
the
environment variable. We can echo and it kicks back the password. Once
we
set the cspace user password, we can log into postgres with that user
password, until we run the script and after that we can't log in until
we
reset the password.
Any thoughts? Much appreciated!
Thanks,
Al
museumcatest:services admin$ ant create_db import -v
Apache Ant(TM) version 1.8.2 compiled on June 3 2011
Trying the default build file: build.xml
Buildfile: /Users/admin/Downloads/services/build.xml
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
parsing buildfile /Users/admin/Downloads/services/build.xml with URI =
file:/Users/admin/Downloads/services/build.xml
Project base dir set to: /Users/admin/Downloads/services
parsing buildfile
jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
with
URI =
jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
from a zip file
[property] Loading Environment env.
[property] Loading /Users/admin/Downloads/services/build.properties
Build sequence for target(s) `create_db' is [create_base_db, create_db]
Complete build sequence is [create_base_db, create_db, undeploy,
clean-windows, checkvars, install-unix, install-windows, install,
setup_initdb.sql, deploy, package-unix, package-windows, package,
eclipse-unix, dist_installer, dist, dist-jee-nuxeo, import,
test-windows,
hotdeploy, init, dist-jee-domains, clean-unix, clean, eclipse-windows,
eclipse, test-unix, gen_ddl, test, dist-jee-cspace, doc, ]
create_base_db:
[sql] connecting to jdbc:postgresql://localhost:5432
[sql] Loading org.postgresql.Driver using AntClassLoader with
classpath
/usr/local/share/apache-tomcat-6.0.33/cspace/services/db/jdbc_drivers/postgresql-8.4-702.jdbc4.jar
[sql] Executing resource:
/usr/local/share/apache-tomcat-6.0.33/cspace/services/db/postgresql/init_db.sql
[sql] SQL: DROP database IF EXISTS cspace
[sql] 0 rows affected
[sql] SQL: DROP database IF EXISTS nuxeo
[sql] 0 rows affected
[sql] SQL: DROP USER IF EXISTS nuxeo
[sql] 0 rows affected
[sql] SQL: DROP USER IF EXISTS cspace
[sql] 0 rows affected
[sql] SQL: DROP USER IF EXISTS reader
[sql] 0 rows affected
[sql] SQL: CREATE ROLE nuxeo WITH PASSWORD
'your_nuxeo_database_user_password_here' LOGIN
[sql] 0 rows affected
[sql] SQL: CREATE ROLE cspace WITH PASSWORD
'your_cspace_database_user_password_here' LOGIN
[sql] 0 rows affected
[sql] SQL: CREATE ROLE reader WITH PASSWORD 'read' LOGIN
[sql] 0 rows affected
[sql] SQL: CREATE DATABASE cspace ENCODING 'UTF8' OWNER cspace
[sql] 0 rows affected
[sql] SQL: CREATE DATABASE nuxeo ENCODING 'UTF8' OWNER nuxeo
[sql] 0 rows affected
[sql] SQL: GRANT CONNECT ON DATABASE nuxeo TO reader
[sql] 0 rows affected
[sql] 11 of 11 SQL statements executed successfully
create_db:
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
[ant] calling target(s) [create_db] in build file
/Users/admin/Downloads/services/services/build.xml
parsing buildfile /Users/admin/Downloads/services/services/build.xml
with
URI = file:/Users/admin/Downloads/services/services/build.xml
Project base dir set to: /Users/admin/Downloads/services/services
[property] Loading /Users/admin/Downloads/services/build.properties
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.DB_PASSWORD_NUXEO" has not been set
Property "env.DB_PASSWORD" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.DB_USER" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.DB_PASSWORD_CSPACE" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
[ant] Entering
/Users/admin/Downloads/services/services/build.xml...
Build sequence for target(s) `create_db' is [create_db]
Complete build sequence is [create_db, undeploy, clean-windows,
install-unix, install-windows, install, deploy, doc-windows,
package-unix,
package-windows, package, dist_installer, import,
copy-dependencies-reports,
test-windows, doc-unix, doc, dist, hotdeploy, clean-unix, clean,
test-unix,
gen_ddl, test, generate-dependencies-reports, ]
create_db:
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
[ant] calling target(s) [create_db] in build file
/Users/admin/Downloads/services/services/authentication/build.xml
parsing buildfile
/Users/admin/Downloads/services/services/authentication/build.xml with
URI =
file:/Users/admin/Downloads/services/services/authentication/build.xml
Project base dir set to:
/Users/admin/Downloads/services/services/authentication
[property] Loading Environment env.
[property] Loading /Users/admin/Downloads/services/build.properties
[ant] Entering
/Users/admin/Downloads/services/services/authentication/build.xml...
Build sequence for target(s) `create_db' is [create_db]
Complete build sequence is [create_db, undeploy, clean-windows,
install-unix, install-windows, install, deploy, package-unix,
package-windows, package, test-windows, dist, clean-unix, clean,
test-unix,
gen_ddl, test, ]
create_db:
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
[ant] calling target(s) [create_db] in build file
/Users/admin/Downloads/services/services/authentication/pstore/build.xml
parsing buildfile
/Users/admin/Downloads/services/services/authentication/pstore/build.xml
with URI =
file:/Users/admin/Downloads/services/services/authentication/pstore/build.xml
Project base dir set to:
/Users/admin/Downloads/services/services/authentication/pstore
[property] Loading Environment env.
[property] Loading /Users/admin/Downloads/services/build.properties
[ant] Entering
/Users/admin/Downloads/services/services/authentication/pstore/build.xml...
Build sequence for target(s) `create_db' is [create_db]
Complete build sequence is [create_db, check.db.scripts.deploy.dir,
undeploy, clean-windows, setup_hibernate.cfg, install-unix,
install-windows,
install, deploy, package-unix, package-windows, package, gen_ddl-unix,
test-windows, gen_ddl-windows, dist, clean-unix, clean, init, test-unix,
gen_ddl, test, ]
create_db:
[sql] connecting to jdbc:postgresql://localhost:5432/cspace
[sql] Loading org.postgresql.Driver using a cached AntClassLoader.
[ant] Exiting
/Users/admin/Downloads/services/services/authentication/pstore/build.xml.
[ant] Exiting
/Users/admin/Downloads/services/services/authentication/build.xml.
[ant] Exiting /Users/admin/Downloads/services/services/build.xml.
BUILD FAILED
/Users/admin/Downloads/services/build.xml:210: The following error
occurred
while executing this line:
/Users/admin/Downloads/services/services/build.xml:136: The following
error
occurred while executing this line:
/Users/admin/Downloads/services/services/authentication/build.xml:117:
The
following error occurred while executing this line:
/Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
org.postgresql.util.PSQLException: FATAL: password authentication failed
for
user "cspace"
at
org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:291)
at
org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:108)
at
org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)
at
org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:125)
at
org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Connection.java:30)
at
org.postgresql.jdbc3g.AbstractJdbc3gConnection.<init>(AbstractJdbc3gConnection.java:22)
at
org.postgresql.jdbc4.AbstractJdbc4Connection.<init>(AbstractJdbc4Connection.java:30)
at org.postgresql.jdbc4.Jdbc4Connection.<init>(Jdbc4Connection.java:24)
at org.postgresql.Driver.makeConnection(Driver.java:393)
at org.postgresql.Driver.connect(Driver.java:267)
at
org.apache.tools.ant.taskdefs.JDBCTask.getConnection(JDBCTask.java:370)
at org.apache.tools.ant.taskdefs.SQLExec.getConnection(SQLExec.java:942)
at org.apache.tools.ant.taskdefs.SQLExec.execute(SQLExec.java:614)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.Main.runBuild(Main.java:809)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
Total time: 1 second
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
From: "Aron Roberts" aron@socrates.berkeley.edu
To: "Al Bersch" abersch@museumca.org
Sent: Friday, May 25, 2012 9:32:47 AM
Subject: Re: [Talk] space user password error
Hi Al,
Many thanks - it's terrific you resolved this in this way! And
your note on the Talk list will help others who may run into the same
situation.
(Until reading your note, I wasn't aware of the ENCRYPTED option for
passwords in PostgreSQL:
http://www.postgresql.org/docs/9.1/static/sql-createuser.html).
Best,
Aron
On Fri, May 25, 2012 at 8:56 AM, 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
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:
Hello,
After following the steps for creating our tenant we get an error when
we
run the ant create_db import. With the following error:
/Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
org.postgresql.util.PSQLException: FATAL: password authentication
failed
for
user "space".
We believe we verified the password is set to what our environment
variable
is set to: $DB_PASSWORD_CSPACE.
We would appreciate any ideas/advice!
Thank you!
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Chris makes a good point.
I think we should assert using a dedicated user to run
CollectionSpace, at least on *nix based systems. This would help keep
environmental variables contained as well as maintaining a level of
separation from root privileges. On nightly and QA I use a 'bamboo'
user, which also owns the Bamboo CI processes, to run and own CSpace
files. On development servers I tend to use a 'cspace' user for the
same purpose.
- Jesse
On Thu, May 31, 2012 at 12:11 PM, Aron Roberts
<aron@socrates.berkeley.edu> wrote:
> Ahh ... excellent suggestion, Chris!
>
> (Will make a note to add this to the install documents.)
>
> Al, when you can, we'd welcome an update on whether Chris might have
> identified what was happening in your situation - thanks!
>
> Aron
>
> On Thu, May 31, 2012 at 6:30 AM, Christopher Pott
> <Christopher.Pott@smk.dk> wrote:
>> Hi Al,
>>
>> I'm working on configuring CollectionSpace at the National Gallery in Denmark.
>>
>> I just thought there was also a chance your earlier problems with environment variables could be related to using different OS user permissions during various stages of the installation. For example, at least in Debian Linux, if you export your environment variables as 'myuser' in "/home/myuser/.bashrc", but then run the build command as 'root' (via 'sudo') then your current variables won't be preserved (unless you use 'sudo -E').
>>
>> Regards,
>> Chris
>>
>>
>> -----Oprindelig meddelelse-----
>> Fra: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] På vegne af Aron Roberts
>> Sendt: 26. maj 2012 02:42
>> Til: Al Bersch
>> Cc: talk@lists.collectionspace.org
>> Emne: Re: [Talk] space user password error
>>
>> Thanks, Al. This all sounds good so far. Here's hoping the reinstall
>> takes care of the problem!
>>
>> If for any reason it doesn't, some more thoughts:
>>
>> 1) Make sure you're running all your 'ant' commands from the VERY top
>> level of the CollectionSpace services source code tree; e.g. from
>>
>> /services
>>
>> and not anywhere else down in the tree; e.g. /services/services
>>
>> 2) In $HOME/bash_profile:
>>
>> export CSPACE_JEESERVER_HOME="/usr/local/share/apache-tomcat-6.0.33"
>> export CATALINA_HOME=$CSPACE_JEESERVER_HOME
>> export CATALINA_PID="$CSPACE_JEESERVER_HOME/bin/tomcat.pid"
>> export CATALINA_OPTS="-Xmx1024m -XX:MaxPermSize=384m"
>> export JAVA_HOME="/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home"
>> export DB_USER="..."
>> export DB_PASSWORD="..."
>> export DB_PASSWORD_NUXEO="..."
>> export DB_PASSWORD_CSPACE="...."
>> export ANT_OPTS="-Xmx768m -XX:MaxPermSize=512m"
>> export MAVEN_OPTS="-Xmx768m -XX:MaxPermSize=512m -Dfile.encoding=UTF-8"
>>
>> 3) This *may* also potentially be important, and is experimenting
>> with; in $HOME/.bashrc, there is this entry:
>>
>> $HOME/.bash_profile
>>
>> 4) If 1) isn't relevant, 2) checks out, and you try 3), and the
>> environment variables are all present, in whatever shell you may be
>> in, the next thing to check is whether Ant is picking them up out of
>> the environment.
>>
>> You can try running the simple Ant buildfile pasted into an earlier
>> message to check on this. If Ant isn't seeing these variables, you
>> might try looking at the Nabble discussion thread mentioned earlier,
>> for any clues about issues that might be present on your system.
>>
>> Aron
>>
>> P.S. Jesse Martinez, I believe, added the following note to the
>> installation instructions,
>> http://wiki.collectionspace.org/display/DOC/Installing+2.3+on+Mac+OS+X+10.6.8:
>>
>> If you added these lines to ~/.bashrc, to ensure these environment
>> variables are present in every new login shell, edit or create the
>> ~/.bash_profile file and add the following line to that file:
>> . ~/.bashrc
>>
>> I've basically done the converse of this, above, in part as a result
>> of reading posts like http://hacktux.com/bash/bashrc/bash_profile and
>> http://stefaanlippens.net/bashrc_and_others:
>>
>> "In this case of an interactive but non-login shell, only ~/.bashrc is
>> executed."
>>
>> (Ultimately, this may hint at necessary changes to the existing
>> documentation ...)
>>
>> On Fri, May 25, 2012 at 4:18 PM, Al Bersch <abersch@museumca.org> wrote:
>>> Hi Aron,
>>>
>>> Thanks for your response.
>>>
>>> In answer to your questions - yes, the installation is on a Mac OS X system,
>>> and yes, there entries in the appropriate shell configuration file to export
>>> the environment variables (we thinks so - we put them in the .bash profile).
>>> As for the third question, I believe that each and every one of the
>>> environment variables is visible upon the command 'env'.
>>>
>>> Our plan is to reinstall and see if we can resolve the issue that way. I'll
>>> let you know what we find out.
>>>
>>> Thanks again,
>>>
>>> Al
>>>
>>> Al Bersch
>>> Digital Project Coordinator
>>> Oakland Museum of California
>>> 1000 Oak Street, Oakland, CA 94607
>>> abersch@museumca.org
>>> 510-318-8468
>>> ________________________________
>>> From: "Aron Roberts" <aron@socrates.berkeley.edu>
>>> To: "Al Bersch" <abersch@museumca.org>
>>> Cc: talk@lists.collectionspace.org
>>> Sent: Friday, May 25, 2012 2:33:32 PM
>>>
>>> Subject: Re: [Talk] space user password error
>>>
>>> Al,
>>>
>>> Thanks much for this update!
>>>
>>> There are a number of environment variables that must be available
>>> to Ant in order to successfully build the CollectionSpace services
>>> layer, create and populate databases, and import roles, permissions,
>>> etc. If any of those is missing, you may not have a completely
>>> working CollectionSpace system.
>>>
>>> It's likely to be more productive to resolve the environment
>>> variables problem once and for all, and get a clean installation, then
>>> to try to resolve individual problems caused by their absence, one
>>> after the other. That will, I'm concerned, be more consuming of your
>>> time than getting an environment in place where the installation steps
>>> 'just work.'
>>>
>>> Just to start out, is it the case that:
>>>
>>> * The installation is occurring on a Unix-like system (Linux, Mac OS
>>> X, or even a Unix variant)?
>>> * There are entries in the appropriate shell configuration file to
>>> export these environment variables, so that they're present in every
>>> new instance of your command shell?
>>> * When you open a new shell / terminal window, you can type the
>>> command 'env', and, in the output from that command, see each and
>>> every one of the environment variables listed in the "Setting Up
>>> CollectionSpace" section of the various installation documents, such
>>> as http://wiki.collectionspace.org/x/1oHyBQ ?
>>>
>>> Aron
>>>
>>> On Fri, May 25, 2012 at 2:21 PM, Al Bersch <abersch@museumca.org> wrote:
>>>> Hi Aron, Jesse,
>>>>
>>>> Thanks for getting back. We ended up hard-coding our password to the
>>>> variable, and that worked. So ant create_db import ran successfully.
>>>> However, I still want to run the Ant buildfile you sent to try to locate
>>>> the
>>>> problem the environment variables.
>>>>
>>>> We started the servers, but can't find our tenant, which leaves us with
>>>> more questions (and thanks again for all your help). What should we have
>>>> in
>>>> our Tables, and what should we have listed for Tenants? After we created
>>>> our
>>>> tenant, our tenant table is showing up empty.
>>>>
>>>> Also, can someone share an example of a host file (we didn't put in a DNS,
>>>> just used localhost)? It would be great to see what it is supposed to look
>>>> like.
>>>>
>>>> Thank you,
>>>>
>>>> Al Bersch
>>>> Digital Project Coordinator
>>>> Oakland Museum of California
>>>> 1000 Oak Street, Oakland, CA 94607
>>>> abersch@museumca.org
>>>> 510-318-8468
>>>> ________________________________
>>>> From: "Aron Roberts" <aron@socrates.berkeley.edu>
>>>> To: "Al Bersch" <abersch@museumca.org>
>>>> Cc: talk@lists.collectionspace.org
>>>> Sent: Friday, May 25, 2012 1:22:50 PM
>>>>
>>>> Subject: Re: [Talk] space user password error
>>>>
>>>> Al,
>>>>
>>>> You can try pasting this simple Ant buildfile into a file named
>>>> "build.xml" in some temporary directory:
>>>>
>>>> <project name="test-env-vars" default="test-env-vars" basedir=".">
>>>> <!-- environment should be declared first -->
>>>> <property environment="env" />
>>>> <target name="test-env-vars">
>>>> <echo
>>>> message="CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}"/>
>>>> </target>
>>>> </project>
>>>>
>>>> and then invoke it, from that directory, via 'ant'. This will let you
>>>> know - in a simple way, without any filtering - whether Ant can 'see'
>>>> your environment variables. If it succeeds at finding the values in
>>>> your environment variables, you'll see something like:
>>>>
>>>> test-env-vars:
>>>> [echo] CSPACE_JEESERVER_HOME=/usr/local/share/apache-tomcat-6.0.33
>>>> BUILD SUCCESSFUL
>>>>
>>>> and if it fails, you'll see:
>>>>
>>>> test-env-vars:
>>>> [echo] CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}
>>>> BUILD SUCCESSFUL
>>>>
>>>> If it can't find the values in your environment variables, then you
>>>> might look into that discussion thread in that Nabble-archived post,
>>>> included in a previous message on this topic, to see if any of the
>>>> issues mentioned there might apply in your situation.
>>>>
>>>> Aron
>>>>
>>>> On Fri, May 25, 2012 at 1:13 PM, Jesse Martinez
>>>> <jmartinez@movingimage.us> wrote:
>>>>> Hi Al,
>>>>>
>>>>> Just a quick thought, are you using special characters or punctuation
>>>>> in your cspace password? I once had an issue using dollar signs $ in a
>>>>> postgresql password.
>>>>>
>>>>> - Jesse
>>>>>
>>>>> On Fri, May 25, 2012 at 2:17 PM, Al Bersch <abersch@museumca.org> wrote:
>>>>>> Hi Aron and talk,
>>>>>>
>>>>>> It looks like I spoke too soon. We are still getting a build failed
>>>>>> message
>>>>>> (verbose version below) and it appears that our environment variables
>>>>>> are
>>>>>> not being recognized, even though we can find the right path if we echo
>>>>>> the
>>>>>> environment variables. We continue to get the message that the cspace
>>>>>> user
>>>>>> password can't be authenticated. We verified that the password is set in
>>>>>> the
>>>>>> environment variable. We can echo and it kicks back the password. Once
>>>>>> we
>>>>>> set the cspace user password, we can log into postgres with that user
>>>>>> password, until we run the script and after that we can't log in until
>>>>>> we
>>>>>> reset the password.
>>>>>>
>>>>>> Any thoughts? Much appreciated!
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Al
>>>>>>
>>>>>> museumcatest:services admin$ ant create_db import -v
>>>>>> Apache Ant(TM) version 1.8.2 compiled on June 3 2011
>>>>>> Trying the default build file: build.xml
>>>>>> Buildfile: /Users/admin/Downloads/services/build.xml
>>>>>> Detected Java version: 1.6 in:
>>>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>>>> Detected OS: Mac OS X
>>>>>> parsing buildfile /Users/admin/Downloads/services/build.xml with URI =
>>>>>> file:/Users/admin/Downloads/services/build.xml
>>>>>> Project base dir set to: /Users/admin/Downloads/services
>>>>>> parsing buildfile
>>>>>> jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
>>>>>> with
>>>>>> URI =
>>>>>> jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
>>>>>> from a zip file
>>>>>> [property] Loading Environment env.
>>>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>>>> Build sequence for target(s) `create_db' is [create_base_db, create_db]
>>>>>> Complete build sequence is [create_base_db, create_db, undeploy,
>>>>>> clean-windows, checkvars, install-unix, install-windows, install,
>>>>>> setup_initdb.sql, deploy, package-unix, package-windows, package,
>>>>>> eclipse-unix, dist_installer, dist, dist-jee-nuxeo, import,
>>>>>> test-windows,
>>>>>> hotdeploy, init, dist-jee-domains, clean-unix, clean, eclipse-windows,
>>>>>> eclipse, test-unix, gen_ddl, test, dist-jee-cspace, doc, ]
>>>>>>
>>>>>> create_base_db:
>>>>>> [sql] connecting to jdbc:postgresql://localhost:5432
>>>>>> [sql] Loading org.postgresql.Driver using AntClassLoader with
>>>>>> classpath
>>>>>>
>>>>>>
>>>>>> /usr/local/share/apache-tomcat-6.0.33/cspace/services/db/jdbc_drivers/postgresql-8.4-702.jdbc4.jar
>>>>>> [sql] Executing resource:
>>>>>>
>>>>>>
>>>>>> /usr/local/share/apache-tomcat-6.0.33/cspace/services/db/postgresql/init_db.sql
>>>>>> [sql] SQL: DROP database IF EXISTS cspace
>>>>>> [sql] 0 rows affected
>>>>>> [sql] SQL: DROP database IF EXISTS nuxeo
>>>>>> [sql] 0 rows affected
>>>>>> [sql] SQL: DROP USER IF EXISTS nuxeo
>>>>>> [sql] 0 rows affected
>>>>>> [sql] SQL: DROP USER IF EXISTS cspace
>>>>>> [sql] 0 rows affected
>>>>>> [sql] SQL: DROP USER IF EXISTS reader
>>>>>> [sql] 0 rows affected
>>>>>> [sql] SQL: CREATE ROLE nuxeo WITH PASSWORD
>>>>>> 'your_nuxeo_database_user_password_here' LOGIN
>>>>>> [sql] 0 rows affected
>>>>>> [sql] SQL: CREATE ROLE cspace WITH PASSWORD
>>>>>> 'your_cspace_database_user_password_here' LOGIN
>>>>>> [sql] 0 rows affected
>>>>>> [sql] SQL: CREATE ROLE reader WITH PASSWORD 'read' LOGIN
>>>>>> [sql] 0 rows affected
>>>>>> [sql] SQL: CREATE DATABASE cspace ENCODING 'UTF8' OWNER cspace
>>>>>> [sql] 0 rows affected
>>>>>> [sql] SQL: CREATE DATABASE nuxeo ENCODING 'UTF8' OWNER nuxeo
>>>>>> [sql] 0 rows affected
>>>>>> [sql] SQL: GRANT CONNECT ON DATABASE nuxeo TO reader
>>>>>> [sql] 0 rows affected
>>>>>> [sql] 11 of 11 SQL statements executed successfully
>>>>>>
>>>>>> create_db:
>>>>>> Detected Java version: 1.6 in:
>>>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>>>> Detected OS: Mac OS X
>>>>>> [ant] calling target(s) [create_db] in build file
>>>>>> /Users/admin/Downloads/services/services/build.xml
>>>>>> parsing buildfile /Users/admin/Downloads/services/services/build.xml
>>>>>> with
>>>>>> URI = file:/Users/admin/Downloads/services/services/build.xml
>>>>>> Project base dir set to: /Users/admin/Downloads/services/services
>>>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.DB_PASSWORD_NUXEO" has not been set
>>>>>> Property "env.DB_PASSWORD" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.DB_USER" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.DB_PASSWORD_CSPACE" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> [ant] Entering
>>>>>> /Users/admin/Downloads/services/services/build.xml...
>>>>>> Build sequence for target(s) `create_db' is [create_db]
>>>>>> Complete build sequence is [create_db, undeploy, clean-windows,
>>>>>> install-unix, install-windows, install, deploy, doc-windows,
>>>>>> package-unix,
>>>>>> package-windows, package, dist_installer, import,
>>>>>> copy-dependencies-reports,
>>>>>> test-windows, doc-unix, doc, dist, hotdeploy, clean-unix, clean,
>>>>>> test-unix,
>>>>>> gen_ddl, test, generate-dependencies-reports, ]
>>>>>>
>>>>>> create_db:
>>>>>> Detected Java version: 1.6 in:
>>>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>>>> Detected OS: Mac OS X
>>>>>> [ant] calling target(s) [create_db] in build file
>>>>>> /Users/admin/Downloads/services/services/authentication/build.xml
>>>>>> parsing buildfile
>>>>>> /Users/admin/Downloads/services/services/authentication/build.xml with
>>>>>> URI =
>>>>>> file:/Users/admin/Downloads/services/services/authentication/build.xml
>>>>>> Project base dir set to:
>>>>>> /Users/admin/Downloads/services/services/authentication
>>>>>> [property] Loading Environment env.
>>>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>>>> [ant] Entering
>>>>>> /Users/admin/Downloads/services/services/authentication/build.xml...
>>>>>> Build sequence for target(s) `create_db' is [create_db]
>>>>>> Complete build sequence is [create_db, undeploy, clean-windows,
>>>>>> install-unix, install-windows, install, deploy, package-unix,
>>>>>> package-windows, package, test-windows, dist, clean-unix, clean,
>>>>>> test-unix,
>>>>>> gen_ddl, test, ]
>>>>>>
>>>>>> create_db:
>>>>>> Detected Java version: 1.6 in:
>>>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>>>> Detected OS: Mac OS X
>>>>>> [ant] calling target(s) [create_db] in build file
>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml
>>>>>> parsing buildfile
>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml
>>>>>> with URI =
>>>>>>
>>>>>>
>>>>>> file:/Users/admin/Downloads/services/services/authentication/pstore/build.xml
>>>>>> Project base dir set to:
>>>>>> /Users/admin/Downloads/services/services/authentication/pstore
>>>>>> [property] Loading Environment env.
>>>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>>>> [ant] Entering
>>>>>>
>>>>>>
>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml...
>>>>>> Build sequence for target(s) `create_db' is [create_db]
>>>>>> Complete build sequence is [create_db, check.db.scripts.deploy.dir,
>>>>>> undeploy, clean-windows, setup_hibernate.cfg, install-unix,
>>>>>> install-windows,
>>>>>> install, deploy, package-unix, package-windows, package, gen_ddl-unix,
>>>>>> test-windows, gen_ddl-windows, dist, clean-unix, clean, init, test-unix,
>>>>>> gen_ddl, test, ]
>>>>>>
>>>>>> create_db:
>>>>>> [sql] connecting to jdbc:postgresql://localhost:5432/cspace
>>>>>> [sql] Loading org.postgresql.Driver using a cached AntClassLoader.
>>>>>> [ant] Exiting
>>>>>>
>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml.
>>>>>> [ant] Exiting
>>>>>> /Users/admin/Downloads/services/services/authentication/build.xml.
>>>>>> [ant] Exiting /Users/admin/Downloads/services/services/build.xml.
>>>>>>
>>>>>> BUILD FAILED
>>>>>> /Users/admin/Downloads/services/build.xml:210: The following error
>>>>>> occurred
>>>>>> while executing this line:
>>>>>> /Users/admin/Downloads/services/services/build.xml:136: The following
>>>>>> error
>>>>>> occurred while executing this line:
>>>>>> /Users/admin/Downloads/services/services/authentication/build.xml:117:
>>>>>> The
>>>>>> following error occurred while executing this line:
>>>>>>
>>>>>>
>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
>>>>>> org.postgresql.util.PSQLException: FATAL: password authentication failed
>>>>>> for
>>>>>> user "cspace"
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:291)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:108)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:125)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Connection.java:30)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.postgresql.jdbc3g.AbstractJdbc3gConnection.<init>(AbstractJdbc3gConnection.java:22)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.postgresql.jdbc4.AbstractJdbc4Connection.<init>(AbstractJdbc4Connection.java:30)
>>>>>> at org.postgresql.jdbc4.Jdbc4Connection.<init>(Jdbc4Connection.java:24)
>>>>>> at org.postgresql.Driver.makeConnection(Driver.java:393)
>>>>>> at org.postgresql.Driver.connect(Driver.java:267)
>>>>>> at
>>>>>> org.apache.tools.ant.taskdefs.JDBCTask.getConnection(JDBCTask.java:370)
>>>>>> at org.apache.tools.ant.taskdefs.SQLExec.getConnection(SQLExec.java:942)
>>>>>> at org.apache.tools.ant.taskdefs.SQLExec.execute(SQLExec.java:614)
>>>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>>>> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
>>>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
>>>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>>>> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
>>>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
>>>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>>>> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
>>>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
>>>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>>>> at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
>>>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>>>> at org.apache.tools.ant.Main.runBuild(Main.java:809)
>>>>>> at org.apache.tools.ant.Main.startAnt(Main.java:217)
>>>>>> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
>>>>>> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
>>>>>>
>>>>>> Total time: 1 second
>>>>>>
>>>>>> Al Bersch
>>>>>> Digital Project Coordinator
>>>>>> Oakland Museum of California
>>>>>> 1000 Oak Street, Oakland, CA 94607
>>>>>> abersch@museumca.org
>>>>>> 510-318-8468
>>>>>> ________________________________
>>>>>> From: "Aron Roberts" <aron@socrates.berkeley.edu>
>>>>>> To: "Al Bersch" <abersch@museumca.org>
>>>>>> Sent: Friday, May 25, 2012 9:32:47 AM
>>>>>>
>>>>>> Subject: Re: [Talk] space user password error
>>>>>>
>>>>>> Hi Al,
>>>>>>
>>>>>> Many thanks - it's terrific you resolved this in this way! And
>>>>>> your note on the Talk list will help others who may run into the same
>>>>>> situation.
>>>>>>
>>>>>> (Until reading your note, I wasn't aware of the ENCRYPTED option for
>>>>>> passwords in PostgreSQL:
>>>>>> http://www.postgresql.org/docs/9.1/static/sql-createuser.html).
>>>>>>
>>>>>> Best,
>>>>>> Aron
>>>>>>
>>>>>>
>>>>>> On Fri, May 25, 2012 at 8:56 AM, 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
>>>>>>> ________________________________
>>>>>>> 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:
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> After following the steps for creating our tenant we get an error when
>>>>>>>> we
>>>>>>>> run the ant create_db import. With the following error:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
>>>>>>>> org.postgresql.util.PSQLException: FATAL: password authentication
>>>>>>>> failed
>>>>>>>> for
>>>>>>>> user "space".
>>>>>>>>
>>>>>>>> We believe we verified the password is set to what our environment
>>>>>>>> variable
>>>>>>>> is set to: $DB_PASSWORD_CSPACE.
>>>>>>>>
>>>>>>>> We would appreciate any ideas/advice!
>>>>>>>>
>>>>>>>> Thank you!
>>>>>>>> Al Bersch
>>>>>>>> Digital Project Coordinator
>>>>>>>> Oakland Museum of California
>>>>>>>> 1000 Oak Street, Oakland, CA 94607
>>>>>>>> abersch@museumca.org
>>>>>>>> 510-318-8468
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Talk mailing list
>>>>>>>> Talk@lists.collectionspace.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Talk mailing list
>>>>>> Talk@lists.collectionspace.org
>>>>>>
>>>>>>
>>>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Talk mailing list
>>>>> Talk@lists.collectionspace.org
>>>>>
>>>>>
>>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>>
>>>
>>>
>>> _______________________________________________
>>> Talk mailing list
>>> Talk@lists.collectionspace.org
>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>
>>
>> _______________________________________________
>> Talk mailing list
>> Talk@lists.collectionspace.org
>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>
>> _______________________________________________
>> Talk mailing list
>> Talk@lists.collectionspace.org
>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>
> _______________________________________________
> Talk mailing list
> Talk@lists.collectionspace.org
> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
AB
Al Bersch
Thu, May 31, 2012 4:49 PM
Thank you so much for your suggestion Chris! I think that may have contributed to the problem. I am new to command language but I believe we were switching between root and other users during the configuration set-up.
I have been swamped this week with other work, so haven't had a chance to jump back into the process. I'm hoping to re-install later this afternoon or tomorrow morning, and will let you know how it goes.
Thanks again,
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: "Jesse Martinez" jmartinez@movingimage.us
To: "Aron Roberts" aron@socrates.berkeley.edu
Cc: "Christopher Pott" Christopher.Pott@smk.dk, "Al Bersch" abersch@museumca.org, talk@lists.collectionspace.org
Sent: Thursday, May 31, 2012 9:38:20 AM
Subject: Re: [Talk] space user password error
Chris makes a good point.
I think we should assert using a dedicated user to run
CollectionSpace, at least on *nix based systems. This would help keep
environmental variables contained as well as maintaining a level of
separation from root privileges. On nightly and QA I use a 'bamboo'
user, which also owns the Bamboo CI processes, to run and own CSpace
files. On development servers I tend to use a 'cspace' user for the
same purpose.
On Thu, May 31, 2012 at 12:11 PM, Aron Roberts
aron@socrates.berkeley.edu wrote:
Ahh ... excellent suggestion, Chris!
(Will make a note to add this to the install documents.)
Al, when you can, we'd welcome an update on whether Chris might have
identified what was happening in your situation - thanks!
Aron
On Thu, May 31, 2012 at 6:30 AM, Christopher Pott
Christopher.Pott@smk.dk wrote:
Hi Al,
I'm working on configuring CollectionSpace at the National Gallery in Denmark.
I just thought there was also a chance your earlier problems with environment variables could be related to using different OS user permissions during various stages of the installation. For example, at least in Debian Linux, if you export your environment variables as 'myuser' in "/home/myuser/.bashrc", but then run the build command as 'root' (via 'sudo') then your current variables won't be preserved (unless you use 'sudo -E').
Regards,
Chris
-----Oprindelig meddelelse-----
Fra: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] På vegne af Aron Roberts
Sendt: 26. maj 2012 02:42
Til: Al Bersch
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] space user password error
Thanks, Al. This all sounds good so far. Here's hoping the reinstall
takes care of the problem!
If for any reason it doesn't, some more thoughts:
- Make sure you're running all your 'ant' commands from the VERY top
level of the CollectionSpace services source code tree; e.g. from
/services
and not anywhere else down in the tree; e.g. /services/services
- In $HOME/bash_profile:
export CSPACE_JEESERVER_HOME="/usr/local/share/apache-tomcat-6.0.33"
export CATALINA_HOME=$CSPACE_JEESERVER_HOME
export CATALINA_PID="$CSPACE_JEESERVER_HOME/bin/tomcat.pid"
export CATALINA_OPTS="-Xmx1024m -XX:MaxPermSize=384m"
export JAVA_HOME="/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home"
export DB_USER="..."
export DB_PASSWORD="..."
export DB_PASSWORD_NUXEO="..."
export DB_PASSWORD_CSPACE="...."
export ANT_OPTS="-Xmx768m -XX:MaxPermSize=512m"
export MAVEN_OPTS="-Xmx768m -XX:MaxPermSize=512m -Dfile.encoding=UTF-8"
- This may also potentially be important, and is experimenting
with; in $HOME/.bashrc, there is this entry:
$HOME/.bash_profile
- If 1) isn't relevant, 2) checks out, and you try 3), and the
environment variables are all present, in whatever shell you may be
in, the next thing to check is whether Ant is picking them up out of
the environment.
You can try running the simple Ant buildfile pasted into an earlier
message to check on this. If Ant isn't seeing these variables, you
might try looking at the Nabble discussion thread mentioned earlier,
for any clues about issues that might be present on your system.
Aron
P.S. Jesse Martinez, I believe, added the following note to the
installation instructions,
http://wiki.collectionspace.org/display/DOC/Installing+2.3+on+Mac+OS+X+10.6.8:
If you added these lines to ~/.bashrc, to ensure these environment
variables are present in every new login shell, edit or create the
~/.bash_profile file and add the following line to that file:
. ~/.bashrc
I've basically done the converse of this, above, in part as a result
of reading posts like http://hacktux.com/bash/bashrc/bash_profile and
http://stefaanlippens.net/bashrc_and_others:
"In this case of an interactive but non-login shell, only ~/.bashrc is
executed."
(Ultimately, this may hint at necessary changes to the existing
documentation ...)
On Fri, May 25, 2012 at 4:18 PM, Al Bersch abersch@museumca.org wrote:
Hi Aron,
Thanks for your response.
In answer to your questions - yes, the installation is on a Mac OS X system,
and yes, there entries in the appropriate shell configuration file to export
the environment variables (we thinks so - we put them in the .bash profile).
As for the third question, I believe that each and every one of the
environment variables is visible upon the command 'env'.
Our plan is to reinstall and see if we can resolve the issue that way. I'll
let you know what we find out.
Thanks again,
Al
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
From: "Aron Roberts" aron@socrates.berkeley.edu
To: "Al Bersch" abersch@museumca.org
Cc: talk@lists.collectionspace.org
Sent: Friday, May 25, 2012 2:33:32 PM
Subject: Re: [Talk] space user password error
Al,
Thanks much for this update!
There are a number of environment variables that must be available
to Ant in order to successfully build the CollectionSpace services
layer, create and populate databases, and import roles, permissions,
etc. If any of those is missing, you may not have a completely
working CollectionSpace system.
It's likely to be more productive to resolve the environment
variables problem once and for all, and get a clean installation, then
to try to resolve individual problems caused by their absence, one
after the other. That will, I'm concerned, be more consuming of your
time than getting an environment in place where the installation steps
'just work.'
Just to start out, is it the case that:
- The installation is occurring on a Unix-like system (Linux, Mac OS
X, or even a Unix variant)?
- There are entries in the appropriate shell configuration file to
export these environment variables, so that they're present in every
new instance of your command shell?
- When you open a new shell / terminal window, you can type the
command 'env', and, in the output from that command, see each and
every one of the environment variables listed in the "Setting Up
CollectionSpace" section of the various installation documents, such
as http://wiki.collectionspace.org/x/1oHyBQ ?
Aron
On Fri, May 25, 2012 at 2:21 PM, Al Bersch abersch@museumca.org wrote:
Hi Aron, Jesse,
Thanks for getting back. We ended up hard-coding our password to the
variable, and that worked. So ant create_db import ran successfully.
However, I still want to run the Ant buildfile you sent to try to locate
the
problem the environment variables.
We started the servers, but can't find our tenant, which leaves us with
more questions (and thanks again for all your help). What should we have
in
our Tables, and what should we have listed for Tenants? After we created
our
tenant, our tenant table is showing up empty.
Also, can someone share an example of a host file (we didn't put in a DNS,
just used localhost)? It would be great to see what it is supposed to look
like.
Thank you,
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
From: "Aron Roberts" aron@socrates.berkeley.edu
To: "Al Bersch" abersch@museumca.org
Cc: talk@lists.collectionspace.org
Sent: Friday, May 25, 2012 1:22:50 PM
Subject: Re: [Talk] space user password error
Al,
You can try pasting this simple Ant buildfile into a file named
"build.xml" in some temporary directory:
<project name="test-env-vars" default="test-env-vars" basedir=".">
<!-- environment should be declared first -->
<property environment="env" />
<target name="test-env-vars">
<echo
message="CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}"/>
</target>
</project>
and then invoke it, from that directory, via 'ant'. This will let you
know - in a simple way, without any filtering - whether Ant can 'see'
your environment variables. If it succeeds at finding the values in
your environment variables, you'll see something like:
test-env-vars:
[echo] CSPACE_JEESERVER_HOME=/usr/local/share/apache-tomcat-6.0.33
BUILD SUCCESSFUL
and if it fails, you'll see:
test-env-vars:
[echo] CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}
BUILD SUCCESSFUL
If it can't find the values in your environment variables, then you
might look into that discussion thread in that Nabble-archived post,
included in a previous message on this topic, to see if any of the
issues mentioned there might apply in your situation.
Aron
On Fri, May 25, 2012 at 1:13 PM, Jesse Martinez
jmartinez@movingimage.us wrote:
Hi Al,
Just a quick thought, are you using special characters or punctuation
in your cspace password? I once had an issue using dollar signs $ in a
postgresql password.
On Fri, May 25, 2012 at 2:17 PM, Al Bersch abersch@museumca.org wrote:
Hi Aron and talk,
It looks like I spoke too soon. We are still getting a build failed
message
(verbose version below) and it appears that our environment variables
are
not being recognized, even though we can find the right path if we echo
the
environment variables. We continue to get the message that the cspace
user
password can't be authenticated. We verified that the password is set in
the
environment variable. We can echo and it kicks back the password. Once
we
set the cspace user password, we can log into postgres with that user
password, until we run the script and after that we can't log in until
we
reset the password.
Any thoughts? Much appreciated!
Thanks,
Al
museumcatest:services admin$ ant create_db import -v
Apache Ant(TM) version 1.8.2 compiled on June 3 2011
Trying the default build file: build.xml
Buildfile: /Users/admin/Downloads/services/build.xml
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
parsing buildfile /Users/admin/Downloads/services/build.xml with URI =
file:/Users/admin/Downloads/services/build.xml
Project base dir set to: /Users/admin/Downloads/services
parsing buildfile
jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
with
URI =
jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
from a zip file
[property] Loading Environment env.
[property] Loading /Users/admin/Downloads/services/build.properties
Build sequence for target(s) `create_db' is [create_base_db, create_db]
Complete build sequence is [create_base_db, create_db, undeploy,
clean-windows, checkvars, install-unix, install-windows, install,
setup_initdb.sql, deploy, package-unix, package-windows, package,
eclipse-unix, dist_installer, dist, dist-jee-nuxeo, import,
test-windows,
hotdeploy, init, dist-jee-domains, clean-unix, clean, eclipse-windows,
eclipse, test-unix, gen_ddl, test, dist-jee-cspace, doc, ]
create_base_db:
[sql] connecting to jdbc:postgresql://localhost:5432
[sql] Loading org.postgresql.Driver using AntClassLoader with
classpath
/usr/local/share/apache-tomcat-6.0.33/cspace/services/db/jdbc_drivers/postgresql-8.4-702.jdbc4.jar
[sql] Executing resource:
/usr/local/share/apache-tomcat-6.0.33/cspace/services/db/postgresql/init_db.sql
[sql] SQL: DROP database IF EXISTS cspace
[sql] 0 rows affected
[sql] SQL: DROP database IF EXISTS nuxeo
[sql] 0 rows affected
[sql] SQL: DROP USER IF EXISTS nuxeo
[sql] 0 rows affected
[sql] SQL: DROP USER IF EXISTS cspace
[sql] 0 rows affected
[sql] SQL: DROP USER IF EXISTS reader
[sql] 0 rows affected
[sql] SQL: CREATE ROLE nuxeo WITH PASSWORD
'your_nuxeo_database_user_password_here' LOGIN
[sql] 0 rows affected
[sql] SQL: CREATE ROLE cspace WITH PASSWORD
'your_cspace_database_user_password_here' LOGIN
[sql] 0 rows affected
[sql] SQL: CREATE ROLE reader WITH PASSWORD 'read' LOGIN
[sql] 0 rows affected
[sql] SQL: CREATE DATABASE cspace ENCODING 'UTF8' OWNER cspace
[sql] 0 rows affected
[sql] SQL: CREATE DATABASE nuxeo ENCODING 'UTF8' OWNER nuxeo
[sql] 0 rows affected
[sql] SQL: GRANT CONNECT ON DATABASE nuxeo TO reader
[sql] 0 rows affected
[sql] 11 of 11 SQL statements executed successfully
create_db:
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
[ant] calling target(s) [create_db] in build file
/Users/admin/Downloads/services/services/build.xml
parsing buildfile /Users/admin/Downloads/services/services/build.xml
with
URI = file:/Users/admin/Downloads/services/services/build.xml
Project base dir set to: /Users/admin/Downloads/services/services
[property] Loading /Users/admin/Downloads/services/build.properties
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.DB_PASSWORD_NUXEO" has not been set
Property "env.DB_PASSWORD" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.DB_USER" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.DB_PASSWORD_CSPACE" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
[ant] Entering
/Users/admin/Downloads/services/services/build.xml...
Build sequence for target(s) `create_db' is [create_db]
Complete build sequence is [create_db, undeploy, clean-windows,
install-unix, install-windows, install, deploy, doc-windows,
package-unix,
package-windows, package, dist_installer, import,
copy-dependencies-reports,
test-windows, doc-unix, doc, dist, hotdeploy, clean-unix, clean,
test-unix,
gen_ddl, test, generate-dependencies-reports, ]
create_db:
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
[ant] calling target(s) [create_db] in build file
/Users/admin/Downloads/services/services/authentication/build.xml
parsing buildfile
/Users/admin/Downloads/services/services/authentication/build.xml with
URI =
file:/Users/admin/Downloads/services/services/authentication/build.xml
Project base dir set to:
/Users/admin/Downloads/services/services/authentication
[property] Loading Environment env.
[property] Loading /Users/admin/Downloads/services/build.properties
[ant] Entering
/Users/admin/Downloads/services/services/authentication/build.xml...
Build sequence for target(s) `create_db' is [create_db]
Complete build sequence is [create_db, undeploy, clean-windows,
install-unix, install-windows, install, deploy, package-unix,
package-windows, package, test-windows, dist, clean-unix, clean,
test-unix,
gen_ddl, test, ]
create_db:
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
[ant] calling target(s) [create_db] in build file
/Users/admin/Downloads/services/services/authentication/pstore/build.xml
parsing buildfile
/Users/admin/Downloads/services/services/authentication/pstore/build.xml
with URI =
file:/Users/admin/Downloads/services/services/authentication/pstore/build.xml
Project base dir set to:
/Users/admin/Downloads/services/services/authentication/pstore
[property] Loading Environment env.
[property] Loading /Users/admin/Downloads/services/build.properties
[ant] Entering
/Users/admin/Downloads/services/services/authentication/pstore/build.xml...
Build sequence for target(s) `create_db' is [create_db]
Complete build sequence is [create_db, check.db.scripts.deploy.dir,
undeploy, clean-windows, setup_hibernate.cfg, install-unix,
install-windows,
install, deploy, package-unix, package-windows, package, gen_ddl-unix,
test-windows, gen_ddl-windows, dist, clean-unix, clean, init, test-unix,
gen_ddl, test, ]
create_db:
[sql] connecting to jdbc:postgresql://localhost:5432/cspace
[sql] Loading org.postgresql.Driver using a cached AntClassLoader.
[ant] Exiting
/Users/admin/Downloads/services/services/authentication/pstore/build.xml.
[ant] Exiting
/Users/admin/Downloads/services/services/authentication/build.xml.
[ant] Exiting /Users/admin/Downloads/services/services/build.xml.
BUILD FAILED
/Users/admin/Downloads/services/build.xml:210: The following error
occurred
while executing this line:
/Users/admin/Downloads/services/services/build.xml:136: The following
error
occurred while executing this line:
/Users/admin/Downloads/services/services/authentication/build.xml:117:
The
following error occurred while executing this line:
/Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
org.postgresql.util.PSQLException: FATAL: password authentication failed
for
user "cspace"
at
org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:291)
at
org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:108)
at
org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)
at
org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:125)
at
org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Connection.java:30)
at
org.postgresql.jdbc3g.AbstractJdbc3gConnection.<init>(AbstractJdbc3gConnection.java:22)
at
org.postgresql.jdbc4.AbstractJdbc4Connection.<init>(AbstractJdbc4Connection.java:30)
at org.postgresql.jdbc4.Jdbc4Connection.<init>(Jdbc4Connection.java:24)
at org.postgresql.Driver.makeConnection(Driver.java:393)
at org.postgresql.Driver.connect(Driver.java:267)
at
org.apache.tools.ant.taskdefs.JDBCTask.getConnection(JDBCTask.java:370)
at org.apache.tools.ant.taskdefs.SQLExec.getConnection(SQLExec.java:942)
at org.apache.tools.ant.taskdefs.SQLExec.execute(SQLExec.java:614)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.Main.runBuild(Main.java:809)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
Total time: 1 second
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
From: "Aron Roberts" aron@socrates.berkeley.edu
To: "Al Bersch" abersch@museumca.org
Sent: Friday, May 25, 2012 9:32:47 AM
Subject: Re: [Talk] space user password error
Hi Al,
Many thanks - it's terrific you resolved this in this way! And
your note on the Talk list will help others who may run into the same
situation.
(Until reading your note, I wasn't aware of the ENCRYPTED option for
passwords in PostgreSQL:
http://www.postgresql.org/docs/9.1/static/sql-createuser.html).
Best,
Aron
On Fri, May 25, 2012 at 8:56 AM, 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
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:
Hello,
After following the steps for creating our tenant we get an error when
we
run the ant create_db import. With the following error:
/Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
org.postgresql.util.PSQLException: FATAL: password authentication
failed
for
user "space".
We believe we verified the password is set to what our environment
variable
is set to: $DB_PASSWORD_CSPACE.
We would appreciate any ideas/advice!
Thank you!
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Thank you so much for your suggestion Chris! I think that may have contributed to the problem. I am new to command language but I believe we were switching between root and other users during the configuration set-up.
I have been swamped this week with other work, so haven't had a chance to jump back into the process. I'm hoping to re-install later this afternoon or tomorrow morning, and will let you know how it goes.
Thanks again,
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: "Jesse Martinez" <jmartinez@movingimage.us>
To: "Aron Roberts" <aron@socrates.berkeley.edu>
Cc: "Christopher Pott" <Christopher.Pott@smk.dk>, "Al Bersch" <abersch@museumca.org>, talk@lists.collectionspace.org
Sent: Thursday, May 31, 2012 9:38:20 AM
Subject: Re: [Talk] space user password error
Chris makes a good point.
I think we should assert using a dedicated user to run
CollectionSpace, at least on *nix based systems. This would help keep
environmental variables contained as well as maintaining a level of
separation from root privileges. On nightly and QA I use a 'bamboo'
user, which also owns the Bamboo CI processes, to run and own CSpace
files. On development servers I tend to use a 'cspace' user for the
same purpose.
- Jesse
On Thu, May 31, 2012 at 12:11 PM, Aron Roberts
<aron@socrates.berkeley.edu> wrote:
> Ahh ... excellent suggestion, Chris!
>
> (Will make a note to add this to the install documents.)
>
> Al, when you can, we'd welcome an update on whether Chris might have
> identified what was happening in your situation - thanks!
>
> Aron
>
> On Thu, May 31, 2012 at 6:30 AM, Christopher Pott
> <Christopher.Pott@smk.dk> wrote:
>> Hi Al,
>>
>> I'm working on configuring CollectionSpace at the National Gallery in Denmark.
>>
>> I just thought there was also a chance your earlier problems with environment variables could be related to using different OS user permissions during various stages of the installation. For example, at least in Debian Linux, if you export your environment variables as 'myuser' in "/home/myuser/.bashrc", but then run the build command as 'root' (via 'sudo') then your current variables won't be preserved (unless you use 'sudo -E').
>>
>> Regards,
>> Chris
>>
>>
>> -----Oprindelig meddelelse-----
>> Fra: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] På vegne af Aron Roberts
>> Sendt: 26. maj 2012 02:42
>> Til: Al Bersch
>> Cc: talk@lists.collectionspace.org
>> Emne: Re: [Talk] space user password error
>>
>> Thanks, Al. This all sounds good so far. Here's hoping the reinstall
>> takes care of the problem!
>>
>> If for any reason it doesn't, some more thoughts:
>>
>> 1) Make sure you're running all your 'ant' commands from the VERY top
>> level of the CollectionSpace services source code tree; e.g. from
>>
>> /services
>>
>> and not anywhere else down in the tree; e.g. /services/services
>>
>> 2) In $HOME/bash_profile:
>>
>> export CSPACE_JEESERVER_HOME="/usr/local/share/apache-tomcat-6.0.33"
>> export CATALINA_HOME=$CSPACE_JEESERVER_HOME
>> export CATALINA_PID="$CSPACE_JEESERVER_HOME/bin/tomcat.pid"
>> export CATALINA_OPTS="-Xmx1024m -XX:MaxPermSize=384m"
>> export JAVA_HOME="/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home"
>> export DB_USER="..."
>> export DB_PASSWORD="..."
>> export DB_PASSWORD_NUXEO="..."
>> export DB_PASSWORD_CSPACE="...."
>> export ANT_OPTS="-Xmx768m -XX:MaxPermSize=512m"
>> export MAVEN_OPTS="-Xmx768m -XX:MaxPermSize=512m -Dfile.encoding=UTF-8"
>>
>> 3) This *may* also potentially be important, and is experimenting
>> with; in $HOME/.bashrc, there is this entry:
>>
>> $HOME/.bash_profile
>>
>> 4) If 1) isn't relevant, 2) checks out, and you try 3), and the
>> environment variables are all present, in whatever shell you may be
>> in, the next thing to check is whether Ant is picking them up out of
>> the environment.
>>
>> You can try running the simple Ant buildfile pasted into an earlier
>> message to check on this. If Ant isn't seeing these variables, you
>> might try looking at the Nabble discussion thread mentioned earlier,
>> for any clues about issues that might be present on your system.
>>
>> Aron
>>
>> P.S. Jesse Martinez, I believe, added the following note to the
>> installation instructions,
>> http://wiki.collectionspace.org/display/DOC/Installing+2.3+on+Mac+OS+X+10.6.8:
>>
>> If you added these lines to ~/.bashrc, to ensure these environment
>> variables are present in every new login shell, edit or create the
>> ~/.bash_profile file and add the following line to that file:
>> . ~/.bashrc
>>
>> I've basically done the converse of this, above, in part as a result
>> of reading posts like http://hacktux.com/bash/bashrc/bash_profile and
>> http://stefaanlippens.net/bashrc_and_others:
>>
>> "In this case of an interactive but non-login shell, only ~/.bashrc is
>> executed."
>>
>> (Ultimately, this may hint at necessary changes to the existing
>> documentation ...)
>>
>> On Fri, May 25, 2012 at 4:18 PM, Al Bersch <abersch@museumca.org> wrote:
>>> Hi Aron,
>>>
>>> Thanks for your response.
>>>
>>> In answer to your questions - yes, the installation is on a Mac OS X system,
>>> and yes, there entries in the appropriate shell configuration file to export
>>> the environment variables (we thinks so - we put them in the .bash profile).
>>> As for the third question, I believe that each and every one of the
>>> environment variables is visible upon the command 'env'.
>>>
>>> Our plan is to reinstall and see if we can resolve the issue that way. I'll
>>> let you know what we find out.
>>>
>>> Thanks again,
>>>
>>> Al
>>>
>>> Al Bersch
>>> Digital Project Coordinator
>>> Oakland Museum of California
>>> 1000 Oak Street, Oakland, CA 94607
>>> abersch@museumca.org
>>> 510-318-8468
>>> ________________________________
>>> From: "Aron Roberts" <aron@socrates.berkeley.edu>
>>> To: "Al Bersch" <abersch@museumca.org>
>>> Cc: talk@lists.collectionspace.org
>>> Sent: Friday, May 25, 2012 2:33:32 PM
>>>
>>> Subject: Re: [Talk] space user password error
>>>
>>> Al,
>>>
>>> Thanks much for this update!
>>>
>>> There are a number of environment variables that must be available
>>> to Ant in order to successfully build the CollectionSpace services
>>> layer, create and populate databases, and import roles, permissions,
>>> etc. If any of those is missing, you may not have a completely
>>> working CollectionSpace system.
>>>
>>> It's likely to be more productive to resolve the environment
>>> variables problem once and for all, and get a clean installation, then
>>> to try to resolve individual problems caused by their absence, one
>>> after the other. That will, I'm concerned, be more consuming of your
>>> time than getting an environment in place where the installation steps
>>> 'just work.'
>>>
>>> Just to start out, is it the case that:
>>>
>>> * The installation is occurring on a Unix-like system (Linux, Mac OS
>>> X, or even a Unix variant)?
>>> * There are entries in the appropriate shell configuration file to
>>> export these environment variables, so that they're present in every
>>> new instance of your command shell?
>>> * When you open a new shell / terminal window, you can type the
>>> command 'env', and, in the output from that command, see each and
>>> every one of the environment variables listed in the "Setting Up
>>> CollectionSpace" section of the various installation documents, such
>>> as http://wiki.collectionspace.org/x/1oHyBQ ?
>>>
>>> Aron
>>>
>>> On Fri, May 25, 2012 at 2:21 PM, Al Bersch <abersch@museumca.org> wrote:
>>>> Hi Aron, Jesse,
>>>>
>>>> Thanks for getting back. We ended up hard-coding our password to the
>>>> variable, and that worked. So ant create_db import ran successfully.
>>>> However, I still want to run the Ant buildfile you sent to try to locate
>>>> the
>>>> problem the environment variables.
>>>>
>>>> We started the servers, but can't find our tenant, which leaves us with
>>>> more questions (and thanks again for all your help). What should we have
>>>> in
>>>> our Tables, and what should we have listed for Tenants? After we created
>>>> our
>>>> tenant, our tenant table is showing up empty.
>>>>
>>>> Also, can someone share an example of a host file (we didn't put in a DNS,
>>>> just used localhost)? It would be great to see what it is supposed to look
>>>> like.
>>>>
>>>> Thank you,
>>>>
>>>> Al Bersch
>>>> Digital Project Coordinator
>>>> Oakland Museum of California
>>>> 1000 Oak Street, Oakland, CA 94607
>>>> abersch@museumca.org
>>>> 510-318-8468
>>>> ________________________________
>>>> From: "Aron Roberts" <aron@socrates.berkeley.edu>
>>>> To: "Al Bersch" <abersch@museumca.org>
>>>> Cc: talk@lists.collectionspace.org
>>>> Sent: Friday, May 25, 2012 1:22:50 PM
>>>>
>>>> Subject: Re: [Talk] space user password error
>>>>
>>>> Al,
>>>>
>>>> You can try pasting this simple Ant buildfile into a file named
>>>> "build.xml" in some temporary directory:
>>>>
>>>> <project name="test-env-vars" default="test-env-vars" basedir=".">
>>>> <!-- environment should be declared first -->
>>>> <property environment="env" />
>>>> <target name="test-env-vars">
>>>> <echo
>>>> message="CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}"/>
>>>> </target>
>>>> </project>
>>>>
>>>> and then invoke it, from that directory, via 'ant'. This will let you
>>>> know - in a simple way, without any filtering - whether Ant can 'see'
>>>> your environment variables. If it succeeds at finding the values in
>>>> your environment variables, you'll see something like:
>>>>
>>>> test-env-vars:
>>>> [echo] CSPACE_JEESERVER_HOME=/usr/local/share/apache-tomcat-6.0.33
>>>> BUILD SUCCESSFUL
>>>>
>>>> and if it fails, you'll see:
>>>>
>>>> test-env-vars:
>>>> [echo] CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}
>>>> BUILD SUCCESSFUL
>>>>
>>>> If it can't find the values in your environment variables, then you
>>>> might look into that discussion thread in that Nabble-archived post,
>>>> included in a previous message on this topic, to see if any of the
>>>> issues mentioned there might apply in your situation.
>>>>
>>>> Aron
>>>>
>>>> On Fri, May 25, 2012 at 1:13 PM, Jesse Martinez
>>>> <jmartinez@movingimage.us> wrote:
>>>>> Hi Al,
>>>>>
>>>>> Just a quick thought, are you using special characters or punctuation
>>>>> in your cspace password? I once had an issue using dollar signs $ in a
>>>>> postgresql password.
>>>>>
>>>>> - Jesse
>>>>>
>>>>> On Fri, May 25, 2012 at 2:17 PM, Al Bersch <abersch@museumca.org> wrote:
>>>>>> Hi Aron and talk,
>>>>>>
>>>>>> It looks like I spoke too soon. We are still getting a build failed
>>>>>> message
>>>>>> (verbose version below) and it appears that our environment variables
>>>>>> are
>>>>>> not being recognized, even though we can find the right path if we echo
>>>>>> the
>>>>>> environment variables. We continue to get the message that the cspace
>>>>>> user
>>>>>> password can't be authenticated. We verified that the password is set in
>>>>>> the
>>>>>> environment variable. We can echo and it kicks back the password. Once
>>>>>> we
>>>>>> set the cspace user password, we can log into postgres with that user
>>>>>> password, until we run the script and after that we can't log in until
>>>>>> we
>>>>>> reset the password.
>>>>>>
>>>>>> Any thoughts? Much appreciated!
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Al
>>>>>>
>>>>>> museumcatest:services admin$ ant create_db import -v
>>>>>> Apache Ant(TM) version 1.8.2 compiled on June 3 2011
>>>>>> Trying the default build file: build.xml
>>>>>> Buildfile: /Users/admin/Downloads/services/build.xml
>>>>>> Detected Java version: 1.6 in:
>>>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>>>> Detected OS: Mac OS X
>>>>>> parsing buildfile /Users/admin/Downloads/services/build.xml with URI =
>>>>>> file:/Users/admin/Downloads/services/build.xml
>>>>>> Project base dir set to: /Users/admin/Downloads/services
>>>>>> parsing buildfile
>>>>>> jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
>>>>>> with
>>>>>> URI =
>>>>>> jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
>>>>>> from a zip file
>>>>>> [property] Loading Environment env.
>>>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>>>> Build sequence for target(s) `create_db' is [create_base_db, create_db]
>>>>>> Complete build sequence is [create_base_db, create_db, undeploy,
>>>>>> clean-windows, checkvars, install-unix, install-windows, install,
>>>>>> setup_initdb.sql, deploy, package-unix, package-windows, package,
>>>>>> eclipse-unix, dist_installer, dist, dist-jee-nuxeo, import,
>>>>>> test-windows,
>>>>>> hotdeploy, init, dist-jee-domains, clean-unix, clean, eclipse-windows,
>>>>>> eclipse, test-unix, gen_ddl, test, dist-jee-cspace, doc, ]
>>>>>>
>>>>>> create_base_db:
>>>>>> [sql] connecting to jdbc:postgresql://localhost:5432
>>>>>> [sql] Loading org.postgresql.Driver using AntClassLoader with
>>>>>> classpath
>>>>>>
>>>>>>
>>>>>> /usr/local/share/apache-tomcat-6.0.33/cspace/services/db/jdbc_drivers/postgresql-8.4-702.jdbc4.jar
>>>>>> [sql] Executing resource:
>>>>>>
>>>>>>
>>>>>> /usr/local/share/apache-tomcat-6.0.33/cspace/services/db/postgresql/init_db.sql
>>>>>> [sql] SQL: DROP database IF EXISTS cspace
>>>>>> [sql] 0 rows affected
>>>>>> [sql] SQL: DROP database IF EXISTS nuxeo
>>>>>> [sql] 0 rows affected
>>>>>> [sql] SQL: DROP USER IF EXISTS nuxeo
>>>>>> [sql] 0 rows affected
>>>>>> [sql] SQL: DROP USER IF EXISTS cspace
>>>>>> [sql] 0 rows affected
>>>>>> [sql] SQL: DROP USER IF EXISTS reader
>>>>>> [sql] 0 rows affected
>>>>>> [sql] SQL: CREATE ROLE nuxeo WITH PASSWORD
>>>>>> 'your_nuxeo_database_user_password_here' LOGIN
>>>>>> [sql] 0 rows affected
>>>>>> [sql] SQL: CREATE ROLE cspace WITH PASSWORD
>>>>>> 'your_cspace_database_user_password_here' LOGIN
>>>>>> [sql] 0 rows affected
>>>>>> [sql] SQL: CREATE ROLE reader WITH PASSWORD 'read' LOGIN
>>>>>> [sql] 0 rows affected
>>>>>> [sql] SQL: CREATE DATABASE cspace ENCODING 'UTF8' OWNER cspace
>>>>>> [sql] 0 rows affected
>>>>>> [sql] SQL: CREATE DATABASE nuxeo ENCODING 'UTF8' OWNER nuxeo
>>>>>> [sql] 0 rows affected
>>>>>> [sql] SQL: GRANT CONNECT ON DATABASE nuxeo TO reader
>>>>>> [sql] 0 rows affected
>>>>>> [sql] 11 of 11 SQL statements executed successfully
>>>>>>
>>>>>> create_db:
>>>>>> Detected Java version: 1.6 in:
>>>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>>>> Detected OS: Mac OS X
>>>>>> [ant] calling target(s) [create_db] in build file
>>>>>> /Users/admin/Downloads/services/services/build.xml
>>>>>> parsing buildfile /Users/admin/Downloads/services/services/build.xml
>>>>>> with
>>>>>> URI = file:/Users/admin/Downloads/services/services/build.xml
>>>>>> Project base dir set to: /Users/admin/Downloads/services/services
>>>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.DB_PASSWORD_NUXEO" has not been set
>>>>>> Property "env.DB_PASSWORD" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.DB_USER" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.DB_PASSWORD_CSPACE" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>> [ant] Entering
>>>>>> /Users/admin/Downloads/services/services/build.xml...
>>>>>> Build sequence for target(s) `create_db' is [create_db]
>>>>>> Complete build sequence is [create_db, undeploy, clean-windows,
>>>>>> install-unix, install-windows, install, deploy, doc-windows,
>>>>>> package-unix,
>>>>>> package-windows, package, dist_installer, import,
>>>>>> copy-dependencies-reports,
>>>>>> test-windows, doc-unix, doc, dist, hotdeploy, clean-unix, clean,
>>>>>> test-unix,
>>>>>> gen_ddl, test, generate-dependencies-reports, ]
>>>>>>
>>>>>> create_db:
>>>>>> Detected Java version: 1.6 in:
>>>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>>>> Detected OS: Mac OS X
>>>>>> [ant] calling target(s) [create_db] in build file
>>>>>> /Users/admin/Downloads/services/services/authentication/build.xml
>>>>>> parsing buildfile
>>>>>> /Users/admin/Downloads/services/services/authentication/build.xml with
>>>>>> URI =
>>>>>> file:/Users/admin/Downloads/services/services/authentication/build.xml
>>>>>> Project base dir set to:
>>>>>> /Users/admin/Downloads/services/services/authentication
>>>>>> [property] Loading Environment env.
>>>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>>>> [ant] Entering
>>>>>> /Users/admin/Downloads/services/services/authentication/build.xml...
>>>>>> Build sequence for target(s) `create_db' is [create_db]
>>>>>> Complete build sequence is [create_db, undeploy, clean-windows,
>>>>>> install-unix, install-windows, install, deploy, package-unix,
>>>>>> package-windows, package, test-windows, dist, clean-unix, clean,
>>>>>> test-unix,
>>>>>> gen_ddl, test, ]
>>>>>>
>>>>>> create_db:
>>>>>> Detected Java version: 1.6 in:
>>>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>>>> Detected OS: Mac OS X
>>>>>> [ant] calling target(s) [create_db] in build file
>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml
>>>>>> parsing buildfile
>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml
>>>>>> with URI =
>>>>>>
>>>>>>
>>>>>> file:/Users/admin/Downloads/services/services/authentication/pstore/build.xml
>>>>>> Project base dir set to:
>>>>>> /Users/admin/Downloads/services/services/authentication/pstore
>>>>>> [property] Loading Environment env.
>>>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>>>> [ant] Entering
>>>>>>
>>>>>>
>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml...
>>>>>> Build sequence for target(s) `create_db' is [create_db]
>>>>>> Complete build sequence is [create_db, check.db.scripts.deploy.dir,
>>>>>> undeploy, clean-windows, setup_hibernate.cfg, install-unix,
>>>>>> install-windows,
>>>>>> install, deploy, package-unix, package-windows, package, gen_ddl-unix,
>>>>>> test-windows, gen_ddl-windows, dist, clean-unix, clean, init, test-unix,
>>>>>> gen_ddl, test, ]
>>>>>>
>>>>>> create_db:
>>>>>> [sql] connecting to jdbc:postgresql://localhost:5432/cspace
>>>>>> [sql] Loading org.postgresql.Driver using a cached AntClassLoader.
>>>>>> [ant] Exiting
>>>>>>
>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml.
>>>>>> [ant] Exiting
>>>>>> /Users/admin/Downloads/services/services/authentication/build.xml.
>>>>>> [ant] Exiting /Users/admin/Downloads/services/services/build.xml.
>>>>>>
>>>>>> BUILD FAILED
>>>>>> /Users/admin/Downloads/services/build.xml:210: The following error
>>>>>> occurred
>>>>>> while executing this line:
>>>>>> /Users/admin/Downloads/services/services/build.xml:136: The following
>>>>>> error
>>>>>> occurred while executing this line:
>>>>>> /Users/admin/Downloads/services/services/authentication/build.xml:117:
>>>>>> The
>>>>>> following error occurred while executing this line:
>>>>>>
>>>>>>
>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
>>>>>> org.postgresql.util.PSQLException: FATAL: password authentication failed
>>>>>> for
>>>>>> user "cspace"
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:291)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:108)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:125)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Connection.java:30)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.postgresql.jdbc3g.AbstractJdbc3gConnection.<init>(AbstractJdbc3gConnection.java:22)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.postgresql.jdbc4.AbstractJdbc4Connection.<init>(AbstractJdbc4Connection.java:30)
>>>>>> at org.postgresql.jdbc4.Jdbc4Connection.<init>(Jdbc4Connection.java:24)
>>>>>> at org.postgresql.Driver.makeConnection(Driver.java:393)
>>>>>> at org.postgresql.Driver.connect(Driver.java:267)
>>>>>> at
>>>>>> org.apache.tools.ant.taskdefs.JDBCTask.getConnection(JDBCTask.java:370)
>>>>>> at org.apache.tools.ant.taskdefs.SQLExec.getConnection(SQLExec.java:942)
>>>>>> at org.apache.tools.ant.taskdefs.SQLExec.execute(SQLExec.java:614)
>>>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>>>> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
>>>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
>>>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>>>> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
>>>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
>>>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>>>> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
>>>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
>>>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>>>> at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
>>>>>> at
>>>>>>
>>>>>>
>>>>>> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
>>>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>>>> at org.apache.tools.ant.Main.runBuild(Main.java:809)
>>>>>> at org.apache.tools.ant.Main.startAnt(Main.java:217)
>>>>>> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
>>>>>> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
>>>>>>
>>>>>> Total time: 1 second
>>>>>>
>>>>>> Al Bersch
>>>>>> Digital Project Coordinator
>>>>>> Oakland Museum of California
>>>>>> 1000 Oak Street, Oakland, CA 94607
>>>>>> abersch@museumca.org
>>>>>> 510-318-8468
>>>>>> ________________________________
>>>>>> From: "Aron Roberts" <aron@socrates.berkeley.edu>
>>>>>> To: "Al Bersch" <abersch@museumca.org>
>>>>>> Sent: Friday, May 25, 2012 9:32:47 AM
>>>>>>
>>>>>> Subject: Re: [Talk] space user password error
>>>>>>
>>>>>> Hi Al,
>>>>>>
>>>>>> Many thanks - it's terrific you resolved this in this way! And
>>>>>> your note on the Talk list will help others who may run into the same
>>>>>> situation.
>>>>>>
>>>>>> (Until reading your note, I wasn't aware of the ENCRYPTED option for
>>>>>> passwords in PostgreSQL:
>>>>>> http://www.postgresql.org/docs/9.1/static/sql-createuser.html).
>>>>>>
>>>>>> Best,
>>>>>> Aron
>>>>>>
>>>>>>
>>>>>> On Fri, May 25, 2012 at 8:56 AM, 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
>>>>>>> ________________________________
>>>>>>> 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:
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> After following the steps for creating our tenant we get an error when
>>>>>>>> we
>>>>>>>> run the ant create_db import. With the following error:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
>>>>>>>> org.postgresql.util.PSQLException: FATAL: password authentication
>>>>>>>> failed
>>>>>>>> for
>>>>>>>> user "space".
>>>>>>>>
>>>>>>>> We believe we verified the password is set to what our environment
>>>>>>>> variable
>>>>>>>> is set to: $DB_PASSWORD_CSPACE.
>>>>>>>>
>>>>>>>> We would appreciate any ideas/advice!
>>>>>>>>
>>>>>>>> Thank you!
>>>>>>>> Al Bersch
>>>>>>>> Digital Project Coordinator
>>>>>>>> Oakland Museum of California
>>>>>>>> 1000 Oak Street, Oakland, CA 94607
>>>>>>>> abersch@museumca.org
>>>>>>>> 510-318-8468
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Talk mailing list
>>>>>>>> Talk@lists.collectionspace.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Talk mailing list
>>>>>> Talk@lists.collectionspace.org
>>>>>>
>>>>>>
>>>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Talk mailing list
>>>>> Talk@lists.collectionspace.org
>>>>>
>>>>>
>>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>>
>>>
>>>
>>> _______________________________________________
>>> Talk mailing list
>>> Talk@lists.collectionspace.org
>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>
>>
>> _______________________________________________
>> Talk mailing list
>> Talk@lists.collectionspace.org
>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>
>> _______________________________________________
>> Talk mailing list
>> Talk@lists.collectionspace.org
>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>
> _______________________________________________
> Talk mailing list
> Talk@lists.collectionspace.org
> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
AR
Aron Roberts
Thu, May 31, 2012 4:58 PM
I concur, Jesse, with your good suggestion. There are benefits to
setting up a dedicated user account for installing and managing a
CollectionSpace system, and this is, I believe, consistent with
documented best practices for a number of other server-based systems.
As part of that, we will also likely need to document how, on
*nix-based systems, that user can be given 'sudo' privileges.
Aron
On Thu, May 31, 2012 at 9:38 AM, Jesse Martinez
jmartinez@movingimage.us wrote:
Chris makes a good point.
I think we should assert using a dedicated user to run
CollectionSpace, at least on *nix based systems. This would help keep
environmental variables contained as well as maintaining a level of
separation from root privileges. On nightly and QA I use a 'bamboo'
user, which also owns the Bamboo CI processes, to run and own CSpace
files. On development servers I tend to use a 'cspace' user for the
same purpose.
- Jesse
On Thu, May 31, 2012 at 12:11 PM, Aron Roberts
aron@socrates.berkeley.edu wrote:
Ahh ... excellent suggestion, Chris!
(Will make a note to add this to the install documents.)
Al, when you can, we'd welcome an update on whether Chris might have
identified what was happening in your situation - thanks!
Aron
On Thu, May 31, 2012 at 6:30 AM, Christopher Pott
Christopher.Pott@smk.dk wrote:
Hi Al,
I'm working on configuring CollectionSpace at the National Gallery in Denmark.
I just thought there was also a chance your earlier problems with environment variables could be related to using different OS user permissions during various stages of the installation. For example, at least in Debian Linux, if you export your environment variables as 'myuser' in "/home/myuser/.bashrc", but then run the build command as 'root' (via 'sudo') then your current variables won't be preserved (unless you use 'sudo -E').
Regards,
Chris
-----Oprindelig meddelelse-----
Fra: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] På vegne af Aron Roberts
Sendt: 26. maj 2012 02:42
Til: Al Bersch
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] space user password error
Thanks, Al. This all sounds good so far. Here's hoping the reinstall
takes care of the problem!
If for any reason it doesn't, some more thoughts:
- Make sure you're running all your 'ant' commands from the VERY top
level of the CollectionSpace services source code tree; e.g. from
/services
and not anywhere else down in the tree; e.g. /services/services
- In $HOME/bash_profile:
export CSPACE_JEESERVER_HOME="/usr/local/share/apache-tomcat-6.0.33"
export CATALINA_HOME=$CSPACE_JEESERVER_HOME
export CATALINA_PID="$CSPACE_JEESERVER_HOME/bin/tomcat.pid"
export CATALINA_OPTS="-Xmx1024m -XX:MaxPermSize=384m"
export JAVA_HOME="/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home"
export DB_USER="..."
export DB_PASSWORD="..."
export DB_PASSWORD_NUXEO="..."
export DB_PASSWORD_CSPACE="...."
export ANT_OPTS="-Xmx768m -XX:MaxPermSize=512m"
export MAVEN_OPTS="-Xmx768m -XX:MaxPermSize=512m -Dfile.encoding=UTF-8"
- This may also potentially be important, and is experimenting
with; in $HOME/.bashrc, there is this entry:
$HOME/.bash_profile
- If 1) isn't relevant, 2) checks out, and you try 3), and the
environment variables are all present, in whatever shell you may be
in, the next thing to check is whether Ant is picking them up out of
the environment.
You can try running the simple Ant buildfile pasted into an earlier
message to check on this. If Ant isn't seeing these variables, you
might try looking at the Nabble discussion thread mentioned earlier,
for any clues about issues that might be present on your system.
Aron
P.S. Jesse Martinez, I believe, added the following note to the
installation instructions,
http://wiki.collectionspace.org/display/DOC/Installing+2.3+on+Mac+OS+X+10.6.8:
If you added these lines to ~/.bashrc, to ensure these environment
variables are present in every new login shell, edit or create the
~/.bash_profile file and add the following line to that file:
. ~/.bashrc
I've basically done the converse of this, above, in part as a result
of reading posts like http://hacktux.com/bash/bashrc/bash_profile and
http://stefaanlippens.net/bashrc_and_others:
"In this case of an interactive but non-login shell, only ~/.bashrc is
executed."
(Ultimately, this may hint at necessary changes to the existing
documentation ...)
On Fri, May 25, 2012 at 4:18 PM, Al Bersch abersch@museumca.org wrote:
Hi Aron,
Thanks for your response.
In answer to your questions - yes, the installation is on a Mac OS X system,
and yes, there entries in the appropriate shell configuration file to export
the environment variables (we thinks so - we put them in the .bash profile).
As for the third question, I believe that each and every one of the
environment variables is visible upon the command 'env'.
Our plan is to reinstall and see if we can resolve the issue that way. I'll
let you know what we find out.
Thanks again,
Al
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
From: "Aron Roberts" aron@socrates.berkeley.edu
To: "Al Bersch" abersch@museumca.org
Cc: talk@lists.collectionspace.org
Sent: Friday, May 25, 2012 2:33:32 PM
Subject: Re: [Talk] space user password error
Al,
Thanks much for this update!
There are a number of environment variables that must be available
to Ant in order to successfully build the CollectionSpace services
layer, create and populate databases, and import roles, permissions,
etc. If any of those is missing, you may not have a completely
working CollectionSpace system.
It's likely to be more productive to resolve the environment
variables problem once and for all, and get a clean installation, then
to try to resolve individual problems caused by their absence, one
after the other. That will, I'm concerned, be more consuming of your
time than getting an environment in place where the installation steps
'just work.'
Just to start out, is it the case that:
- The installation is occurring on a Unix-like system (Linux, Mac OS
X, or even a Unix variant)?
- There are entries in the appropriate shell configuration file to
export these environment variables, so that they're present in every
new instance of your command shell?
- When you open a new shell / terminal window, you can type the
command 'env', and, in the output from that command, see each and
every one of the environment variables listed in the "Setting Up
CollectionSpace" section of the various installation documents, such
as http://wiki.collectionspace.org/x/1oHyBQ ?
Aron
On Fri, May 25, 2012 at 2:21 PM, Al Bersch abersch@museumca.org wrote:
Hi Aron, Jesse,
Thanks for getting back. We ended up hard-coding our password to the
variable, and that worked. So ant create_db import ran successfully.
However, I still want to run the Ant buildfile you sent to try to locate
the
problem the environment variables.
We started the servers, but can't find our tenant, which leaves us with
more questions (and thanks again for all your help). What should we have
in
our Tables, and what should we have listed for Tenants? After we created
our
tenant, our tenant table is showing up empty.
Also, can someone share an example of a host file (we didn't put in a DNS,
just used localhost)? It would be great to see what it is supposed to look
like.
Thank you,
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
From: "Aron Roberts" aron@socrates.berkeley.edu
To: "Al Bersch" abersch@museumca.org
Cc: talk@lists.collectionspace.org
Sent: Friday, May 25, 2012 1:22:50 PM
Subject: Re: [Talk] space user password error
Al,
You can try pasting this simple Ant buildfile into a file named
"build.xml" in some temporary directory:
<project name="test-env-vars" default="test-env-vars" basedir=".">
<!-- environment should be declared first -->
<property environment="env" />
<target name="test-env-vars">
<echo
message="CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}"/>
</target>
</project>
and then invoke it, from that directory, via 'ant'. This will let you
know - in a simple way, without any filtering - whether Ant can 'see'
your environment variables. If it succeeds at finding the values in
your environment variables, you'll see something like:
test-env-vars:
[echo] CSPACE_JEESERVER_HOME=/usr/local/share/apache-tomcat-6.0.33
BUILD SUCCESSFUL
and if it fails, you'll see:
test-env-vars:
[echo] CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}
BUILD SUCCESSFUL
If it can't find the values in your environment variables, then you
might look into that discussion thread in that Nabble-archived post,
included in a previous message on this topic, to see if any of the
issues mentioned there might apply in your situation.
Aron
On Fri, May 25, 2012 at 1:13 PM, Jesse Martinez
jmartinez@movingimage.us wrote:
Hi Al,
Just a quick thought, are you using special characters or punctuation
in your cspace password? I once had an issue using dollar signs $ in a
postgresql password.
On Fri, May 25, 2012 at 2:17 PM, Al Bersch abersch@museumca.org wrote:
Hi Aron and talk,
It looks like I spoke too soon. We are still getting a build failed
message
(verbose version below) and it appears that our environment variables
are
not being recognized, even though we can find the right path if we echo
the
environment variables. We continue to get the message that the cspace
user
password can't be authenticated. We verified that the password is set in
the
environment variable. We can echo and it kicks back the password. Once
we
set the cspace user password, we can log into postgres with that user
password, until we run the script and after that we can't log in until
we
reset the password.
Any thoughts? Much appreciated!
Thanks,
Al
museumcatest:services admin$ ant create_db import -v
Apache Ant(TM) version 1.8.2 compiled on June 3 2011
Trying the default build file: build.xml
Buildfile: /Users/admin/Downloads/services/build.xml
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
parsing buildfile /Users/admin/Downloads/services/build.xml with URI =
file:/Users/admin/Downloads/services/build.xml
Project base dir set to: /Users/admin/Downloads/services
parsing buildfile
jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
with
URI =
jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
from a zip file
[property] Loading Environment env.
[property] Loading /Users/admin/Downloads/services/build.properties
Build sequence for target(s) `create_db' is [create_base_db, create_db]
Complete build sequence is [create_base_db, create_db, undeploy,
clean-windows, checkvars, install-unix, install-windows, install,
setup_initdb.sql, deploy, package-unix, package-windows, package,
eclipse-unix, dist_installer, dist, dist-jee-nuxeo, import,
test-windows,
hotdeploy, init, dist-jee-domains, clean-unix, clean, eclipse-windows,
eclipse, test-unix, gen_ddl, test, dist-jee-cspace, doc, ]
create_base_db:
[sql] connecting to jdbc:postgresql://localhost:5432
[sql] Loading org.postgresql.Driver using AntClassLoader with
classpath
/usr/local/share/apache-tomcat-6.0.33/cspace/services/db/jdbc_drivers/postgresql-8.4-702.jdbc4.jar
[sql] Executing resource:
/usr/local/share/apache-tomcat-6.0.33/cspace/services/db/postgresql/init_db.sql
[sql] SQL: DROP database IF EXISTS cspace
[sql] 0 rows affected
[sql] SQL: DROP database IF EXISTS nuxeo
[sql] 0 rows affected
[sql] SQL: DROP USER IF EXISTS nuxeo
[sql] 0 rows affected
[sql] SQL: DROP USER IF EXISTS cspace
[sql] 0 rows affected
[sql] SQL: DROP USER IF EXISTS reader
[sql] 0 rows affected
[sql] SQL: CREATE ROLE nuxeo WITH PASSWORD
'your_nuxeo_database_user_password_here' LOGIN
[sql] 0 rows affected
[sql] SQL: CREATE ROLE cspace WITH PASSWORD
'your_cspace_database_user_password_here' LOGIN
[sql] 0 rows affected
[sql] SQL: CREATE ROLE reader WITH PASSWORD 'read' LOGIN
[sql] 0 rows affected
[sql] SQL: CREATE DATABASE cspace ENCODING 'UTF8' OWNER cspace
[sql] 0 rows affected
[sql] SQL: CREATE DATABASE nuxeo ENCODING 'UTF8' OWNER nuxeo
[sql] 0 rows affected
[sql] SQL: GRANT CONNECT ON DATABASE nuxeo TO reader
[sql] 0 rows affected
[sql] 11 of 11 SQL statements executed successfully
create_db:
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
[ant] calling target(s) [create_db] in build file
/Users/admin/Downloads/services/services/build.xml
parsing buildfile /Users/admin/Downloads/services/services/build.xml
with
URI = file:/Users/admin/Downloads/services/services/build.xml
Project base dir set to: /Users/admin/Downloads/services/services
[property] Loading /Users/admin/Downloads/services/build.properties
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.DB_PASSWORD_NUXEO" has not been set
Property "env.DB_PASSWORD" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.DB_USER" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.DB_PASSWORD_CSPACE" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
[ant] Entering
/Users/admin/Downloads/services/services/build.xml...
Build sequence for target(s) `create_db' is [create_db]
Complete build sequence is [create_db, undeploy, clean-windows,
install-unix, install-windows, install, deploy, doc-windows,
package-unix,
package-windows, package, dist_installer, import,
copy-dependencies-reports,
test-windows, doc-unix, doc, dist, hotdeploy, clean-unix, clean,
test-unix,
gen_ddl, test, generate-dependencies-reports, ]
create_db:
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
[ant] calling target(s) [create_db] in build file
/Users/admin/Downloads/services/services/authentication/build.xml
parsing buildfile
/Users/admin/Downloads/services/services/authentication/build.xml with
URI =
file:/Users/admin/Downloads/services/services/authentication/build.xml
Project base dir set to:
/Users/admin/Downloads/services/services/authentication
[property] Loading Environment env.
[property] Loading /Users/admin/Downloads/services/build.properties
[ant] Entering
/Users/admin/Downloads/services/services/authentication/build.xml...
Build sequence for target(s) `create_db' is [create_db]
Complete build sequence is [create_db, undeploy, clean-windows,
install-unix, install-windows, install, deploy, package-unix,
package-windows, package, test-windows, dist, clean-unix, clean,
test-unix,
gen_ddl, test, ]
create_db:
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
[ant] calling target(s) [create_db] in build file
/Users/admin/Downloads/services/services/authentication/pstore/build.xml
parsing buildfile
/Users/admin/Downloads/services/services/authentication/pstore/build.xml
with URI =
file:/Users/admin/Downloads/services/services/authentication/pstore/build.xml
Project base dir set to:
/Users/admin/Downloads/services/services/authentication/pstore
[property] Loading Environment env.
[property] Loading /Users/admin/Downloads/services/build.properties
[ant] Entering
/Users/admin/Downloads/services/services/authentication/pstore/build.xml...
Build sequence for target(s) `create_db' is [create_db]
Complete build sequence is [create_db, check.db.scripts.deploy.dir,
undeploy, clean-windows, setup_hibernate.cfg, install-unix,
install-windows,
install, deploy, package-unix, package-windows, package, gen_ddl-unix,
test-windows, gen_ddl-windows, dist, clean-unix, clean, init, test-unix,
gen_ddl, test, ]
create_db:
[sql] connecting to jdbc:postgresql://localhost:5432/cspace
[sql] Loading org.postgresql.Driver using a cached AntClassLoader.
[ant] Exiting
/Users/admin/Downloads/services/services/authentication/pstore/build.xml.
[ant] Exiting
/Users/admin/Downloads/services/services/authentication/build.xml.
[ant] Exiting /Users/admin/Downloads/services/services/build.xml.
BUILD FAILED
/Users/admin/Downloads/services/build.xml:210: The following error
occurred
while executing this line:
/Users/admin/Downloads/services/services/build.xml:136: The following
error
occurred while executing this line:
/Users/admin/Downloads/services/services/authentication/build.xml:117:
The
following error occurred while executing this line:
/Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
org.postgresql.util.PSQLException: FATAL: password authentication failed
for
user "cspace"
at
org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:291)
at
org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:108)
at
org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)
at
org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:125)
at
org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Connection.java:30)
at
org.postgresql.jdbc3g.AbstractJdbc3gConnection.<init>(AbstractJdbc3gConnection.java:22)
at
org.postgresql.jdbc4.AbstractJdbc4Connection.<init>(AbstractJdbc4Connection.java:30)
at org.postgresql.jdbc4.Jdbc4Connection.<init>(Jdbc4Connection.java:24)
at org.postgresql.Driver.makeConnection(Driver.java:393)
at org.postgresql.Driver.connect(Driver.java:267)
at
org.apache.tools.ant.taskdefs.JDBCTask.getConnection(JDBCTask.java:370)
at org.apache.tools.ant.taskdefs.SQLExec.getConnection(SQLExec.java:942)
at org.apache.tools.ant.taskdefs.SQLExec.execute(SQLExec.java:614)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.Main.runBuild(Main.java:809)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
Total time: 1 second
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
From: "Aron Roberts" aron@socrates.berkeley.edu
To: "Al Bersch" abersch@museumca.org
Sent: Friday, May 25, 2012 9:32:47 AM
Subject: Re: [Talk] space user password error
Hi Al,
Many thanks - it's terrific you resolved this in this way! And
your note on the Talk list will help others who may run into the same
situation.
(Until reading your note, I wasn't aware of the ENCRYPTED option for
passwords in PostgreSQL:
http://www.postgresql.org/docs/9.1/static/sql-createuser.html).
Best,
Aron
On Fri, May 25, 2012 at 8:56 AM, 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
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:
Hello,
After following the steps for creating our tenant we get an error when
we
run the ant create_db import. With the following error:
/Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
org.postgresql.util.PSQLException: FATAL: password authentication
failed
for
user "space".
We believe we verified the password is set to what our environment
variable
is set to: $DB_PASSWORD_CSPACE.
We would appreciate any ideas/advice!
Thank you!
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
I concur, Jesse, with your good suggestion. There are benefits to
setting up a dedicated user account for installing and managing a
CollectionSpace system, and this is, I believe, consistent with
documented best practices for a number of other server-based systems.
As part of that, we will also likely need to document how, on
*nix-based systems, that user can be given 'sudo' privileges.
Aron
On Thu, May 31, 2012 at 9:38 AM, Jesse Martinez
<jmartinez@movingimage.us> wrote:
> Chris makes a good point.
>
> I think we should assert using a dedicated user to run
> CollectionSpace, at least on *nix based systems. This would help keep
> environmental variables contained as well as maintaining a level of
> separation from root privileges. On nightly and QA I use a 'bamboo'
> user, which also owns the Bamboo CI processes, to run and own CSpace
> files. On development servers I tend to use a 'cspace' user for the
> same purpose.
>
> - Jesse
>
> On Thu, May 31, 2012 at 12:11 PM, Aron Roberts
> <aron@socrates.berkeley.edu> wrote:
>> Ahh ... excellent suggestion, Chris!
>>
>> (Will make a note to add this to the install documents.)
>>
>> Al, when you can, we'd welcome an update on whether Chris might have
>> identified what was happening in your situation - thanks!
>>
>> Aron
>>
>> On Thu, May 31, 2012 at 6:30 AM, Christopher Pott
>> <Christopher.Pott@smk.dk> wrote:
>>> Hi Al,
>>>
>>> I'm working on configuring CollectionSpace at the National Gallery in Denmark.
>>>
>>> I just thought there was also a chance your earlier problems with environment variables could be related to using different OS user permissions during various stages of the installation. For example, at least in Debian Linux, if you export your environment variables as 'myuser' in "/home/myuser/.bashrc", but then run the build command as 'root' (via 'sudo') then your current variables won't be preserved (unless you use 'sudo -E').
>>>
>>> Regards,
>>> Chris
>>>
>>>
>>> -----Oprindelig meddelelse-----
>>> Fra: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] På vegne af Aron Roberts
>>> Sendt: 26. maj 2012 02:42
>>> Til: Al Bersch
>>> Cc: talk@lists.collectionspace.org
>>> Emne: Re: [Talk] space user password error
>>>
>>> Thanks, Al. This all sounds good so far. Here's hoping the reinstall
>>> takes care of the problem!
>>>
>>> If for any reason it doesn't, some more thoughts:
>>>
>>> 1) Make sure you're running all your 'ant' commands from the VERY top
>>> level of the CollectionSpace services source code tree; e.g. from
>>>
>>> /services
>>>
>>> and not anywhere else down in the tree; e.g. /services/services
>>>
>>> 2) In $HOME/bash_profile:
>>>
>>> export CSPACE_JEESERVER_HOME="/usr/local/share/apache-tomcat-6.0.33"
>>> export CATALINA_HOME=$CSPACE_JEESERVER_HOME
>>> export CATALINA_PID="$CSPACE_JEESERVER_HOME/bin/tomcat.pid"
>>> export CATALINA_OPTS="-Xmx1024m -XX:MaxPermSize=384m"
>>> export JAVA_HOME="/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home"
>>> export DB_USER="..."
>>> export DB_PASSWORD="..."
>>> export DB_PASSWORD_NUXEO="..."
>>> export DB_PASSWORD_CSPACE="...."
>>> export ANT_OPTS="-Xmx768m -XX:MaxPermSize=512m"
>>> export MAVEN_OPTS="-Xmx768m -XX:MaxPermSize=512m -Dfile.encoding=UTF-8"
>>>
>>> 3) This *may* also potentially be important, and is experimenting
>>> with; in $HOME/.bashrc, there is this entry:
>>>
>>> $HOME/.bash_profile
>>>
>>> 4) If 1) isn't relevant, 2) checks out, and you try 3), and the
>>> environment variables are all present, in whatever shell you may be
>>> in, the next thing to check is whether Ant is picking them up out of
>>> the environment.
>>>
>>> You can try running the simple Ant buildfile pasted into an earlier
>>> message to check on this. If Ant isn't seeing these variables, you
>>> might try looking at the Nabble discussion thread mentioned earlier,
>>> for any clues about issues that might be present on your system.
>>>
>>> Aron
>>>
>>> P.S. Jesse Martinez, I believe, added the following note to the
>>> installation instructions,
>>> http://wiki.collectionspace.org/display/DOC/Installing+2.3+on+Mac+OS+X+10.6.8:
>>>
>>> If you added these lines to ~/.bashrc, to ensure these environment
>>> variables are present in every new login shell, edit or create the
>>> ~/.bash_profile file and add the following line to that file:
>>> . ~/.bashrc
>>>
>>> I've basically done the converse of this, above, in part as a result
>>> of reading posts like http://hacktux.com/bash/bashrc/bash_profile and
>>> http://stefaanlippens.net/bashrc_and_others:
>>>
>>> "In this case of an interactive but non-login shell, only ~/.bashrc is
>>> executed."
>>>
>>> (Ultimately, this may hint at necessary changes to the existing
>>> documentation ...)
>>>
>>> On Fri, May 25, 2012 at 4:18 PM, Al Bersch <abersch@museumca.org> wrote:
>>>> Hi Aron,
>>>>
>>>> Thanks for your response.
>>>>
>>>> In answer to your questions - yes, the installation is on a Mac OS X system,
>>>> and yes, there entries in the appropriate shell configuration file to export
>>>> the environment variables (we thinks so - we put them in the .bash profile).
>>>> As for the third question, I believe that each and every one of the
>>>> environment variables is visible upon the command 'env'.
>>>>
>>>> Our plan is to reinstall and see if we can resolve the issue that way. I'll
>>>> let you know what we find out.
>>>>
>>>> Thanks again,
>>>>
>>>> Al
>>>>
>>>> Al Bersch
>>>> Digital Project Coordinator
>>>> Oakland Museum of California
>>>> 1000 Oak Street, Oakland, CA 94607
>>>> abersch@museumca.org
>>>> 510-318-8468
>>>> ________________________________
>>>> From: "Aron Roberts" <aron@socrates.berkeley.edu>
>>>> To: "Al Bersch" <abersch@museumca.org>
>>>> Cc: talk@lists.collectionspace.org
>>>> Sent: Friday, May 25, 2012 2:33:32 PM
>>>>
>>>> Subject: Re: [Talk] space user password error
>>>>
>>>> Al,
>>>>
>>>> Thanks much for this update!
>>>>
>>>> There are a number of environment variables that must be available
>>>> to Ant in order to successfully build the CollectionSpace services
>>>> layer, create and populate databases, and import roles, permissions,
>>>> etc. If any of those is missing, you may not have a completely
>>>> working CollectionSpace system.
>>>>
>>>> It's likely to be more productive to resolve the environment
>>>> variables problem once and for all, and get a clean installation, then
>>>> to try to resolve individual problems caused by their absence, one
>>>> after the other. That will, I'm concerned, be more consuming of your
>>>> time than getting an environment in place where the installation steps
>>>> 'just work.'
>>>>
>>>> Just to start out, is it the case that:
>>>>
>>>> * The installation is occurring on a Unix-like system (Linux, Mac OS
>>>> X, or even a Unix variant)?
>>>> * There are entries in the appropriate shell configuration file to
>>>> export these environment variables, so that they're present in every
>>>> new instance of your command shell?
>>>> * When you open a new shell / terminal window, you can type the
>>>> command 'env', and, in the output from that command, see each and
>>>> every one of the environment variables listed in the "Setting Up
>>>> CollectionSpace" section of the various installation documents, such
>>>> as http://wiki.collectionspace.org/x/1oHyBQ ?
>>>>
>>>> Aron
>>>>
>>>> On Fri, May 25, 2012 at 2:21 PM, Al Bersch <abersch@museumca.org> wrote:
>>>>> Hi Aron, Jesse,
>>>>>
>>>>> Thanks for getting back. We ended up hard-coding our password to the
>>>>> variable, and that worked. So ant create_db import ran successfully.
>>>>> However, I still want to run the Ant buildfile you sent to try to locate
>>>>> the
>>>>> problem the environment variables.
>>>>>
>>>>> We started the servers, but can't find our tenant, which leaves us with
>>>>> more questions (and thanks again for all your help). What should we have
>>>>> in
>>>>> our Tables, and what should we have listed for Tenants? After we created
>>>>> our
>>>>> tenant, our tenant table is showing up empty.
>>>>>
>>>>> Also, can someone share an example of a host file (we didn't put in a DNS,
>>>>> just used localhost)? It would be great to see what it is supposed to look
>>>>> like.
>>>>>
>>>>> Thank you,
>>>>>
>>>>> Al Bersch
>>>>> Digital Project Coordinator
>>>>> Oakland Museum of California
>>>>> 1000 Oak Street, Oakland, CA 94607
>>>>> abersch@museumca.org
>>>>> 510-318-8468
>>>>> ________________________________
>>>>> From: "Aron Roberts" <aron@socrates.berkeley.edu>
>>>>> To: "Al Bersch" <abersch@museumca.org>
>>>>> Cc: talk@lists.collectionspace.org
>>>>> Sent: Friday, May 25, 2012 1:22:50 PM
>>>>>
>>>>> Subject: Re: [Talk] space user password error
>>>>>
>>>>> Al,
>>>>>
>>>>> You can try pasting this simple Ant buildfile into a file named
>>>>> "build.xml" in some temporary directory:
>>>>>
>>>>> <project name="test-env-vars" default="test-env-vars" basedir=".">
>>>>> <!-- environment should be declared first -->
>>>>> <property environment="env" />
>>>>> <target name="test-env-vars">
>>>>> <echo
>>>>> message="CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}"/>
>>>>> </target>
>>>>> </project>
>>>>>
>>>>> and then invoke it, from that directory, via 'ant'. This will let you
>>>>> know - in a simple way, without any filtering - whether Ant can 'see'
>>>>> your environment variables. If it succeeds at finding the values in
>>>>> your environment variables, you'll see something like:
>>>>>
>>>>> test-env-vars:
>>>>> [echo] CSPACE_JEESERVER_HOME=/usr/local/share/apache-tomcat-6.0.33
>>>>> BUILD SUCCESSFUL
>>>>>
>>>>> and if it fails, you'll see:
>>>>>
>>>>> test-env-vars:
>>>>> [echo] CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}
>>>>> BUILD SUCCESSFUL
>>>>>
>>>>> If it can't find the values in your environment variables, then you
>>>>> might look into that discussion thread in that Nabble-archived post,
>>>>> included in a previous message on this topic, to see if any of the
>>>>> issues mentioned there might apply in your situation.
>>>>>
>>>>> Aron
>>>>>
>>>>> On Fri, May 25, 2012 at 1:13 PM, Jesse Martinez
>>>>> <jmartinez@movingimage.us> wrote:
>>>>>> Hi Al,
>>>>>>
>>>>>> Just a quick thought, are you using special characters or punctuation
>>>>>> in your cspace password? I once had an issue using dollar signs $ in a
>>>>>> postgresql password.
>>>>>>
>>>>>> - Jesse
>>>>>>
>>>>>> On Fri, May 25, 2012 at 2:17 PM, Al Bersch <abersch@museumca.org> wrote:
>>>>>>> Hi Aron and talk,
>>>>>>>
>>>>>>> It looks like I spoke too soon. We are still getting a build failed
>>>>>>> message
>>>>>>> (verbose version below) and it appears that our environment variables
>>>>>>> are
>>>>>>> not being recognized, even though we can find the right path if we echo
>>>>>>> the
>>>>>>> environment variables. We continue to get the message that the cspace
>>>>>>> user
>>>>>>> password can't be authenticated. We verified that the password is set in
>>>>>>> the
>>>>>>> environment variable. We can echo and it kicks back the password. Once
>>>>>>> we
>>>>>>> set the cspace user password, we can log into postgres with that user
>>>>>>> password, until we run the script and after that we can't log in until
>>>>>>> we
>>>>>>> reset the password.
>>>>>>>
>>>>>>> Any thoughts? Much appreciated!
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Al
>>>>>>>
>>>>>>> museumcatest:services admin$ ant create_db import -v
>>>>>>> Apache Ant(TM) version 1.8.2 compiled on June 3 2011
>>>>>>> Trying the default build file: build.xml
>>>>>>> Buildfile: /Users/admin/Downloads/services/build.xml
>>>>>>> Detected Java version: 1.6 in:
>>>>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>>>>> Detected OS: Mac OS X
>>>>>>> parsing buildfile /Users/admin/Downloads/services/build.xml with URI =
>>>>>>> file:/Users/admin/Downloads/services/build.xml
>>>>>>> Project base dir set to: /Users/admin/Downloads/services
>>>>>>> parsing buildfile
>>>>>>> jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
>>>>>>> with
>>>>>>> URI =
>>>>>>> jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
>>>>>>> from a zip file
>>>>>>> [property] Loading Environment env.
>>>>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>>>>> Build sequence for target(s) `create_db' is [create_base_db, create_db]
>>>>>>> Complete build sequence is [create_base_db, create_db, undeploy,
>>>>>>> clean-windows, checkvars, install-unix, install-windows, install,
>>>>>>> setup_initdb.sql, deploy, package-unix, package-windows, package,
>>>>>>> eclipse-unix, dist_installer, dist, dist-jee-nuxeo, import,
>>>>>>> test-windows,
>>>>>>> hotdeploy, init, dist-jee-domains, clean-unix, clean, eclipse-windows,
>>>>>>> eclipse, test-unix, gen_ddl, test, dist-jee-cspace, doc, ]
>>>>>>>
>>>>>>> create_base_db:
>>>>>>> [sql] connecting to jdbc:postgresql://localhost:5432
>>>>>>> [sql] Loading org.postgresql.Driver using AntClassLoader with
>>>>>>> classpath
>>>>>>>
>>>>>>>
>>>>>>> /usr/local/share/apache-tomcat-6.0.33/cspace/services/db/jdbc_drivers/postgresql-8.4-702.jdbc4.jar
>>>>>>> [sql] Executing resource:
>>>>>>>
>>>>>>>
>>>>>>> /usr/local/share/apache-tomcat-6.0.33/cspace/services/db/postgresql/init_db.sql
>>>>>>> [sql] SQL: DROP database IF EXISTS cspace
>>>>>>> [sql] 0 rows affected
>>>>>>> [sql] SQL: DROP database IF EXISTS nuxeo
>>>>>>> [sql] 0 rows affected
>>>>>>> [sql] SQL: DROP USER IF EXISTS nuxeo
>>>>>>> [sql] 0 rows affected
>>>>>>> [sql] SQL: DROP USER IF EXISTS cspace
>>>>>>> [sql] 0 rows affected
>>>>>>> [sql] SQL: DROP USER IF EXISTS reader
>>>>>>> [sql] 0 rows affected
>>>>>>> [sql] SQL: CREATE ROLE nuxeo WITH PASSWORD
>>>>>>> 'your_nuxeo_database_user_password_here' LOGIN
>>>>>>> [sql] 0 rows affected
>>>>>>> [sql] SQL: CREATE ROLE cspace WITH PASSWORD
>>>>>>> 'your_cspace_database_user_password_here' LOGIN
>>>>>>> [sql] 0 rows affected
>>>>>>> [sql] SQL: CREATE ROLE reader WITH PASSWORD 'read' LOGIN
>>>>>>> [sql] 0 rows affected
>>>>>>> [sql] SQL: CREATE DATABASE cspace ENCODING 'UTF8' OWNER cspace
>>>>>>> [sql] 0 rows affected
>>>>>>> [sql] SQL: CREATE DATABASE nuxeo ENCODING 'UTF8' OWNER nuxeo
>>>>>>> [sql] 0 rows affected
>>>>>>> [sql] SQL: GRANT CONNECT ON DATABASE nuxeo TO reader
>>>>>>> [sql] 0 rows affected
>>>>>>> [sql] 11 of 11 SQL statements executed successfully
>>>>>>>
>>>>>>> create_db:
>>>>>>> Detected Java version: 1.6 in:
>>>>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>>>>> Detected OS: Mac OS X
>>>>>>> [ant] calling target(s) [create_db] in build file
>>>>>>> /Users/admin/Downloads/services/services/build.xml
>>>>>>> parsing buildfile /Users/admin/Downloads/services/services/build.xml
>>>>>>> with
>>>>>>> URI = file:/Users/admin/Downloads/services/services/build.xml
>>>>>>> Project base dir set to: /Users/admin/Downloads/services/services
>>>>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>> Property "env.DB_PASSWORD_NUXEO" has not been set
>>>>>>> Property "env.DB_PASSWORD" has not been set
>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>> Property "env.DB_USER" has not been set
>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>> Property "env.DB_PASSWORD_CSPACE" has not been set
>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>> [ant] Entering
>>>>>>> /Users/admin/Downloads/services/services/build.xml...
>>>>>>> Build sequence for target(s) `create_db' is [create_db]
>>>>>>> Complete build sequence is [create_db, undeploy, clean-windows,
>>>>>>> install-unix, install-windows, install, deploy, doc-windows,
>>>>>>> package-unix,
>>>>>>> package-windows, package, dist_installer, import,
>>>>>>> copy-dependencies-reports,
>>>>>>> test-windows, doc-unix, doc, dist, hotdeploy, clean-unix, clean,
>>>>>>> test-unix,
>>>>>>> gen_ddl, test, generate-dependencies-reports, ]
>>>>>>>
>>>>>>> create_db:
>>>>>>> Detected Java version: 1.6 in:
>>>>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>>>>> Detected OS: Mac OS X
>>>>>>> [ant] calling target(s) [create_db] in build file
>>>>>>> /Users/admin/Downloads/services/services/authentication/build.xml
>>>>>>> parsing buildfile
>>>>>>> /Users/admin/Downloads/services/services/authentication/build.xml with
>>>>>>> URI =
>>>>>>> file:/Users/admin/Downloads/services/services/authentication/build.xml
>>>>>>> Project base dir set to:
>>>>>>> /Users/admin/Downloads/services/services/authentication
>>>>>>> [property] Loading Environment env.
>>>>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>>>>> [ant] Entering
>>>>>>> /Users/admin/Downloads/services/services/authentication/build.xml...
>>>>>>> Build sequence for target(s) `create_db' is [create_db]
>>>>>>> Complete build sequence is [create_db, undeploy, clean-windows,
>>>>>>> install-unix, install-windows, install, deploy, package-unix,
>>>>>>> package-windows, package, test-windows, dist, clean-unix, clean,
>>>>>>> test-unix,
>>>>>>> gen_ddl, test, ]
>>>>>>>
>>>>>>> create_db:
>>>>>>> Detected Java version: 1.6 in:
>>>>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>>>>> Detected OS: Mac OS X
>>>>>>> [ant] calling target(s) [create_db] in build file
>>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml
>>>>>>> parsing buildfile
>>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml
>>>>>>> with URI =
>>>>>>>
>>>>>>>
>>>>>>> file:/Users/admin/Downloads/services/services/authentication/pstore/build.xml
>>>>>>> Project base dir set to:
>>>>>>> /Users/admin/Downloads/services/services/authentication/pstore
>>>>>>> [property] Loading Environment env.
>>>>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>>>>> [ant] Entering
>>>>>>>
>>>>>>>
>>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml...
>>>>>>> Build sequence for target(s) `create_db' is [create_db]
>>>>>>> Complete build sequence is [create_db, check.db.scripts.deploy.dir,
>>>>>>> undeploy, clean-windows, setup_hibernate.cfg, install-unix,
>>>>>>> install-windows,
>>>>>>> install, deploy, package-unix, package-windows, package, gen_ddl-unix,
>>>>>>> test-windows, gen_ddl-windows, dist, clean-unix, clean, init, test-unix,
>>>>>>> gen_ddl, test, ]
>>>>>>>
>>>>>>> create_db:
>>>>>>> [sql] connecting to jdbc:postgresql://localhost:5432/cspace
>>>>>>> [sql] Loading org.postgresql.Driver using a cached AntClassLoader.
>>>>>>> [ant] Exiting
>>>>>>>
>>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml.
>>>>>>> [ant] Exiting
>>>>>>> /Users/admin/Downloads/services/services/authentication/build.xml.
>>>>>>> [ant] Exiting /Users/admin/Downloads/services/services/build.xml.
>>>>>>>
>>>>>>> BUILD FAILED
>>>>>>> /Users/admin/Downloads/services/build.xml:210: The following error
>>>>>>> occurred
>>>>>>> while executing this line:
>>>>>>> /Users/admin/Downloads/services/services/build.xml:136: The following
>>>>>>> error
>>>>>>> occurred while executing this line:
>>>>>>> /Users/admin/Downloads/services/services/authentication/build.xml:117:
>>>>>>> The
>>>>>>> following error occurred while executing this line:
>>>>>>>
>>>>>>>
>>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
>>>>>>> org.postgresql.util.PSQLException: FATAL: password authentication failed
>>>>>>> for
>>>>>>> user "cspace"
>>>>>>> at
>>>>>>>
>>>>>>>
>>>>>>> org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:291)
>>>>>>> at
>>>>>>>
>>>>>>>
>>>>>>> org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:108)
>>>>>>> at
>>>>>>>
>>>>>>>
>>>>>>> org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)
>>>>>>> at
>>>>>>>
>>>>>>>
>>>>>>> org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:125)
>>>>>>> at
>>>>>>>
>>>>>>>
>>>>>>> org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Connection.java:30)
>>>>>>> at
>>>>>>>
>>>>>>>
>>>>>>> org.postgresql.jdbc3g.AbstractJdbc3gConnection.<init>(AbstractJdbc3gConnection.java:22)
>>>>>>> at
>>>>>>>
>>>>>>>
>>>>>>> org.postgresql.jdbc4.AbstractJdbc4Connection.<init>(AbstractJdbc4Connection.java:30)
>>>>>>> at org.postgresql.jdbc4.Jdbc4Connection.<init>(Jdbc4Connection.java:24)
>>>>>>> at org.postgresql.Driver.makeConnection(Driver.java:393)
>>>>>>> at org.postgresql.Driver.connect(Driver.java:267)
>>>>>>> at
>>>>>>> org.apache.tools.ant.taskdefs.JDBCTask.getConnection(JDBCTask.java:370)
>>>>>>> at org.apache.tools.ant.taskdefs.SQLExec.getConnection(SQLExec.java:942)
>>>>>>> at org.apache.tools.ant.taskdefs.SQLExec.execute(SQLExec.java:614)
>>>>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>>>>> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>>>>>>> at
>>>>>>>
>>>>>>>
>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>> at
>>>>>>>
>>>>>>>
>>>>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>>>>> at
>>>>>>>
>>>>>>>
>>>>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
>>>>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
>>>>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>>>>> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>>>>>>> at
>>>>>>>
>>>>>>>
>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>> at
>>>>>>>
>>>>>>>
>>>>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>>>>> at
>>>>>>>
>>>>>>>
>>>>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
>>>>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
>>>>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>>>>> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>>>>>>> at
>>>>>>>
>>>>>>>
>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>> at
>>>>>>>
>>>>>>>
>>>>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>>>>> at
>>>>>>>
>>>>>>>
>>>>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
>>>>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
>>>>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>> at
>>>>>>>
>>>>>>>
>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>>> at
>>>>>>>
>>>>>>>
>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>> at
>>>>>>>
>>>>>>>
>>>>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>>>>> at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
>>>>>>> at
>>>>>>>
>>>>>>>
>>>>>>> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
>>>>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>>>>> at org.apache.tools.ant.Main.runBuild(Main.java:809)
>>>>>>> at org.apache.tools.ant.Main.startAnt(Main.java:217)
>>>>>>> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
>>>>>>> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
>>>>>>>
>>>>>>> Total time: 1 second
>>>>>>>
>>>>>>> Al Bersch
>>>>>>> Digital Project Coordinator
>>>>>>> Oakland Museum of California
>>>>>>> 1000 Oak Street, Oakland, CA 94607
>>>>>>> abersch@museumca.org
>>>>>>> 510-318-8468
>>>>>>> ________________________________
>>>>>>> From: "Aron Roberts" <aron@socrates.berkeley.edu>
>>>>>>> To: "Al Bersch" <abersch@museumca.org>
>>>>>>> Sent: Friday, May 25, 2012 9:32:47 AM
>>>>>>>
>>>>>>> Subject: Re: [Talk] space user password error
>>>>>>>
>>>>>>> Hi Al,
>>>>>>>
>>>>>>> Many thanks - it's terrific you resolved this in this way! And
>>>>>>> your note on the Talk list will help others who may run into the same
>>>>>>> situation.
>>>>>>>
>>>>>>> (Until reading your note, I wasn't aware of the ENCRYPTED option for
>>>>>>> passwords in PostgreSQL:
>>>>>>> http://www.postgresql.org/docs/9.1/static/sql-createuser.html).
>>>>>>>
>>>>>>> Best,
>>>>>>> Aron
>>>>>>>
>>>>>>>
>>>>>>> On Fri, May 25, 2012 at 8:56 AM, 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
>>>>>>>> ________________________________
>>>>>>>> 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:
>>>>>>>>> Hello,
>>>>>>>>>
>>>>>>>>> After following the steps for creating our tenant we get an error when
>>>>>>>>> we
>>>>>>>>> run the ant create_db import. With the following error:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
>>>>>>>>> org.postgresql.util.PSQLException: FATAL: password authentication
>>>>>>>>> failed
>>>>>>>>> for
>>>>>>>>> user "space".
>>>>>>>>>
>>>>>>>>> We believe we verified the password is set to what our environment
>>>>>>>>> variable
>>>>>>>>> is set to: $DB_PASSWORD_CSPACE.
>>>>>>>>>
>>>>>>>>> We would appreciate any ideas/advice!
>>>>>>>>>
>>>>>>>>> Thank you!
>>>>>>>>> Al Bersch
>>>>>>>>> Digital Project Coordinator
>>>>>>>>> Oakland Museum of California
>>>>>>>>> 1000 Oak Street, Oakland, CA 94607
>>>>>>>>> abersch@museumca.org
>>>>>>>>> 510-318-8468
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Talk mailing list
>>>>>>>>> Talk@lists.collectionspace.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Talk mailing list
>>>>>>> Talk@lists.collectionspace.org
>>>>>>>
>>>>>>>
>>>>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Talk mailing list
>>>>>> Talk@lists.collectionspace.org
>>>>>>
>>>>>>
>>>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Talk mailing list
>>>> Talk@lists.collectionspace.org
>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>>
>>>
>>> _______________________________________________
>>> Talk mailing list
>>> Talk@lists.collectionspace.org
>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>
>>> _______________________________________________
>>> Talk mailing list
>>> Talk@lists.collectionspace.org
>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>
>> _______________________________________________
>> Talk mailing list
>> Talk@lists.collectionspace.org
>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>
> _______________________________________________
> Talk mailing list
> Talk@lists.collectionspace.org
> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
AR
Aron Roberts
Thu, May 31, 2012 5:01 PM
Al - and all: Ultimately, it is our intention and expectation that a
CollectionSpace system will be installable, in the future, via a
packaged installer, via a 'wizard' or equivalent interface. Most of
the work to date on this system has been around functionality and
stability, and improvements to installation and administration is a
fertile area for future work.
On Thu, May 31, 2012 at 9:58 AM, Aron Roberts
aron@socrates.berkeley.edu wrote:
I concur, Jesse, with your good suggestion. There are benefits to
setting up a dedicated user account for installing and managing a
CollectionSpace system, and this is, I believe, consistent with
documented best practices for a number of other server-based systems.
As part of that, we will also likely need to document how, on
*nix-based systems, that user can be given 'sudo' privileges.
Aron
On Thu, May 31, 2012 at 9:38 AM, Jesse Martinez
jmartinez@movingimage.us wrote:
Chris makes a good point.
I think we should assert using a dedicated user to run
CollectionSpace, at least on *nix based systems. This would help keep
environmental variables contained as well as maintaining a level of
separation from root privileges. On nightly and QA I use a 'bamboo'
user, which also owns the Bamboo CI processes, to run and own CSpace
files. On development servers I tend to use a 'cspace' user for the
same purpose.
- Jesse
On Thu, May 31, 2012 at 12:11 PM, Aron Roberts
aron@socrates.berkeley.edu wrote:
Ahh ... excellent suggestion, Chris!
(Will make a note to add this to the install documents.)
Al, when you can, we'd welcome an update on whether Chris might have
identified what was happening in your situation - thanks!
Aron
On Thu, May 31, 2012 at 6:30 AM, Christopher Pott
Christopher.Pott@smk.dk wrote:
Hi Al,
I'm working on configuring CollectionSpace at the National Gallery in Denmark.
I just thought there was also a chance your earlier problems with environment variables could be related to using different OS user permissions during various stages of the installation. For example, at least in Debian Linux, if you export your environment variables as 'myuser' in "/home/myuser/.bashrc", but then run the build command as 'root' (via 'sudo') then your current variables won't be preserved (unless you use 'sudo -E').
Regards,
Chris
-----Oprindelig meddelelse-----
Fra: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] På vegne af Aron Roberts
Sendt: 26. maj 2012 02:42
Til: Al Bersch
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] space user password error
Thanks, Al. This all sounds good so far. Here's hoping the reinstall
takes care of the problem!
If for any reason it doesn't, some more thoughts:
- Make sure you're running all your 'ant' commands from the VERY top
level of the CollectionSpace services source code tree; e.g. from
/services
and not anywhere else down in the tree; e.g. /services/services
- In $HOME/bash_profile:
export CSPACE_JEESERVER_HOME="/usr/local/share/apache-tomcat-6.0.33"
export CATALINA_HOME=$CSPACE_JEESERVER_HOME
export CATALINA_PID="$CSPACE_JEESERVER_HOME/bin/tomcat.pid"
export CATALINA_OPTS="-Xmx1024m -XX:MaxPermSize=384m"
export JAVA_HOME="/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home"
export DB_USER="..."
export DB_PASSWORD="..."
export DB_PASSWORD_NUXEO="..."
export DB_PASSWORD_CSPACE="...."
export ANT_OPTS="-Xmx768m -XX:MaxPermSize=512m"
export MAVEN_OPTS="-Xmx768m -XX:MaxPermSize=512m -Dfile.encoding=UTF-8"
- This may also potentially be important, and is experimenting
with; in $HOME/.bashrc, there is this entry:
$HOME/.bash_profile
- If 1) isn't relevant, 2) checks out, and you try 3), and the
environment variables are all present, in whatever shell you may be
in, the next thing to check is whether Ant is picking them up out of
the environment.
You can try running the simple Ant buildfile pasted into an earlier
message to check on this. If Ant isn't seeing these variables, you
might try looking at the Nabble discussion thread mentioned earlier,
for any clues about issues that might be present on your system.
Aron
P.S. Jesse Martinez, I believe, added the following note to the
installation instructions,
http://wiki.collectionspace.org/display/DOC/Installing+2.3+on+Mac+OS+X+10.6.8:
If you added these lines to ~/.bashrc, to ensure these environment
variables are present in every new login shell, edit or create the
~/.bash_profile file and add the following line to that file:
. ~/.bashrc
I've basically done the converse of this, above, in part as a result
of reading posts like http://hacktux.com/bash/bashrc/bash_profile and
http://stefaanlippens.net/bashrc_and_others:
"In this case of an interactive but non-login shell, only ~/.bashrc is
executed."
(Ultimately, this may hint at necessary changes to the existing
documentation ...)
On Fri, May 25, 2012 at 4:18 PM, Al Bersch abersch@museumca.org wrote:
Hi Aron,
Thanks for your response.
In answer to your questions - yes, the installation is on a Mac OS X system,
and yes, there entries in the appropriate shell configuration file to export
the environment variables (we thinks so - we put them in the .bash profile).
As for the third question, I believe that each and every one of the
environment variables is visible upon the command 'env'.
Our plan is to reinstall and see if we can resolve the issue that way. I'll
let you know what we find out.
Thanks again,
Al
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
From: "Aron Roberts" aron@socrates.berkeley.edu
To: "Al Bersch" abersch@museumca.org
Cc: talk@lists.collectionspace.org
Sent: Friday, May 25, 2012 2:33:32 PM
Subject: Re: [Talk] space user password error
Al,
Thanks much for this update!
There are a number of environment variables that must be available
to Ant in order to successfully build the CollectionSpace services
layer, create and populate databases, and import roles, permissions,
etc. If any of those is missing, you may not have a completely
working CollectionSpace system.
It's likely to be more productive to resolve the environment
variables problem once and for all, and get a clean installation, then
to try to resolve individual problems caused by their absence, one
after the other. That will, I'm concerned, be more consuming of your
time than getting an environment in place where the installation steps
'just work.'
Just to start out, is it the case that:
- The installation is occurring on a Unix-like system (Linux, Mac OS
X, or even a Unix variant)?
- There are entries in the appropriate shell configuration file to
export these environment variables, so that they're present in every
new instance of your command shell?
- When you open a new shell / terminal window, you can type the
command 'env', and, in the output from that command, see each and
every one of the environment variables listed in the "Setting Up
CollectionSpace" section of the various installation documents, such
as http://wiki.collectionspace.org/x/1oHyBQ ?
Aron
On Fri, May 25, 2012 at 2:21 PM, Al Bersch abersch@museumca.org wrote:
Hi Aron, Jesse,
Thanks for getting back. We ended up hard-coding our password to the
variable, and that worked. So ant create_db import ran successfully.
However, I still want to run the Ant buildfile you sent to try to locate
the
problem the environment variables.
We started the servers, but can't find our tenant, which leaves us with
more questions (and thanks again for all your help). What should we have
in
our Tables, and what should we have listed for Tenants? After we created
our
tenant, our tenant table is showing up empty.
Also, can someone share an example of a host file (we didn't put in a DNS,
just used localhost)? It would be great to see what it is supposed to look
like.
Thank you,
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
From: "Aron Roberts" aron@socrates.berkeley.edu
To: "Al Bersch" abersch@museumca.org
Cc: talk@lists.collectionspace.org
Sent: Friday, May 25, 2012 1:22:50 PM
Subject: Re: [Talk] space user password error
Al,
You can try pasting this simple Ant buildfile into a file named
"build.xml" in some temporary directory:
<project name="test-env-vars" default="test-env-vars" basedir=".">
<!-- environment should be declared first -->
<property environment="env" />
<target name="test-env-vars">
<echo
message="CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}"/>
</target>
</project>
and then invoke it, from that directory, via 'ant'. This will let you
know - in a simple way, without any filtering - whether Ant can 'see'
your environment variables. If it succeeds at finding the values in
your environment variables, you'll see something like:
test-env-vars:
[echo] CSPACE_JEESERVER_HOME=/usr/local/share/apache-tomcat-6.0.33
BUILD SUCCESSFUL
and if it fails, you'll see:
test-env-vars:
[echo] CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}
BUILD SUCCESSFUL
If it can't find the values in your environment variables, then you
might look into that discussion thread in that Nabble-archived post,
included in a previous message on this topic, to see if any of the
issues mentioned there might apply in your situation.
Aron
On Fri, May 25, 2012 at 1:13 PM, Jesse Martinez
jmartinez@movingimage.us wrote:
Hi Al,
Just a quick thought, are you using special characters or punctuation
in your cspace password? I once had an issue using dollar signs $ in a
postgresql password.
On Fri, May 25, 2012 at 2:17 PM, Al Bersch abersch@museumca.org wrote:
Hi Aron and talk,
It looks like I spoke too soon. We are still getting a build failed
message
(verbose version below) and it appears that our environment variables
are
not being recognized, even though we can find the right path if we echo
the
environment variables. We continue to get the message that the cspace
user
password can't be authenticated. We verified that the password is set in
the
environment variable. We can echo and it kicks back the password. Once
we
set the cspace user password, we can log into postgres with that user
password, until we run the script and after that we can't log in until
we
reset the password.
Any thoughts? Much appreciated!
Thanks,
Al
museumcatest:services admin$ ant create_db import -v
Apache Ant(TM) version 1.8.2 compiled on June 3 2011
Trying the default build file: build.xml
Buildfile: /Users/admin/Downloads/services/build.xml
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
parsing buildfile /Users/admin/Downloads/services/build.xml with URI =
file:/Users/admin/Downloads/services/build.xml
Project base dir set to: /Users/admin/Downloads/services
parsing buildfile
jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
with
URI =
jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
from a zip file
[property] Loading Environment env.
[property] Loading /Users/admin/Downloads/services/build.properties
Build sequence for target(s) `create_db' is [create_base_db, create_db]
Complete build sequence is [create_base_db, create_db, undeploy,
clean-windows, checkvars, install-unix, install-windows, install,
setup_initdb.sql, deploy, package-unix, package-windows, package,
eclipse-unix, dist_installer, dist, dist-jee-nuxeo, import,
test-windows,
hotdeploy, init, dist-jee-domains, clean-unix, clean, eclipse-windows,
eclipse, test-unix, gen_ddl, test, dist-jee-cspace, doc, ]
create_base_db:
[sql] connecting to jdbc:postgresql://localhost:5432
[sql] Loading org.postgresql.Driver using AntClassLoader with
classpath
/usr/local/share/apache-tomcat-6.0.33/cspace/services/db/jdbc_drivers/postgresql-8.4-702.jdbc4.jar
[sql] Executing resource:
/usr/local/share/apache-tomcat-6.0.33/cspace/services/db/postgresql/init_db.sql
[sql] SQL: DROP database IF EXISTS cspace
[sql] 0 rows affected
[sql] SQL: DROP database IF EXISTS nuxeo
[sql] 0 rows affected
[sql] SQL: DROP USER IF EXISTS nuxeo
[sql] 0 rows affected
[sql] SQL: DROP USER IF EXISTS cspace
[sql] 0 rows affected
[sql] SQL: DROP USER IF EXISTS reader
[sql] 0 rows affected
[sql] SQL: CREATE ROLE nuxeo WITH PASSWORD
'your_nuxeo_database_user_password_here' LOGIN
[sql] 0 rows affected
[sql] SQL: CREATE ROLE cspace WITH PASSWORD
'your_cspace_database_user_password_here' LOGIN
[sql] 0 rows affected
[sql] SQL: CREATE ROLE reader WITH PASSWORD 'read' LOGIN
[sql] 0 rows affected
[sql] SQL: CREATE DATABASE cspace ENCODING 'UTF8' OWNER cspace
[sql] 0 rows affected
[sql] SQL: CREATE DATABASE nuxeo ENCODING 'UTF8' OWNER nuxeo
[sql] 0 rows affected
[sql] SQL: GRANT CONNECT ON DATABASE nuxeo TO reader
[sql] 0 rows affected
[sql] 11 of 11 SQL statements executed successfully
create_db:
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
[ant] calling target(s) [create_db] in build file
/Users/admin/Downloads/services/services/build.xml
parsing buildfile /Users/admin/Downloads/services/services/build.xml
with
URI = file:/Users/admin/Downloads/services/services/build.xml
Project base dir set to: /Users/admin/Downloads/services/services
[property] Loading /Users/admin/Downloads/services/build.properties
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.DB_PASSWORD_NUXEO" has not been set
Property "env.DB_PASSWORD" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.DB_USER" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.DB_PASSWORD_CSPACE" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
Property "env.CSPACE_JEESERVER_HOME" has not been set
[ant] Entering
/Users/admin/Downloads/services/services/build.xml...
Build sequence for target(s) `create_db' is [create_db]
Complete build sequence is [create_db, undeploy, clean-windows,
install-unix, install-windows, install, deploy, doc-windows,
package-unix,
package-windows, package, dist_installer, import,
copy-dependencies-reports,
test-windows, doc-unix, doc, dist, hotdeploy, clean-unix, clean,
test-unix,
gen_ddl, test, generate-dependencies-reports, ]
create_db:
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
[ant] calling target(s) [create_db] in build file
/Users/admin/Downloads/services/services/authentication/build.xml
parsing buildfile
/Users/admin/Downloads/services/services/authentication/build.xml with
URI =
file:/Users/admin/Downloads/services/services/authentication/build.xml
Project base dir set to:
/Users/admin/Downloads/services/services/authentication
[property] Loading Environment env.
[property] Loading /Users/admin/Downloads/services/build.properties
[ant] Entering
/Users/admin/Downloads/services/services/authentication/build.xml...
Build sequence for target(s) `create_db' is [create_db]
Complete build sequence is [create_db, undeploy, clean-windows,
install-unix, install-windows, install, deploy, package-unix,
package-windows, package, test-windows, dist, clean-unix, clean,
test-unix,
gen_ddl, test, ]
create_db:
Detected Java version: 1.6 in:
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Detected OS: Mac OS X
[ant] calling target(s) [create_db] in build file
/Users/admin/Downloads/services/services/authentication/pstore/build.xml
parsing buildfile
/Users/admin/Downloads/services/services/authentication/pstore/build.xml
with URI =
file:/Users/admin/Downloads/services/services/authentication/pstore/build.xml
Project base dir set to:
/Users/admin/Downloads/services/services/authentication/pstore
[property] Loading Environment env.
[property] Loading /Users/admin/Downloads/services/build.properties
[ant] Entering
/Users/admin/Downloads/services/services/authentication/pstore/build.xml...
Build sequence for target(s) `create_db' is [create_db]
Complete build sequence is [create_db, check.db.scripts.deploy.dir,
undeploy, clean-windows, setup_hibernate.cfg, install-unix,
install-windows,
install, deploy, package-unix, package-windows, package, gen_ddl-unix,
test-windows, gen_ddl-windows, dist, clean-unix, clean, init, test-unix,
gen_ddl, test, ]
create_db:
[sql] connecting to jdbc:postgresql://localhost:5432/cspace
[sql] Loading org.postgresql.Driver using a cached AntClassLoader.
[ant] Exiting
/Users/admin/Downloads/services/services/authentication/pstore/build.xml.
[ant] Exiting
/Users/admin/Downloads/services/services/authentication/build.xml.
[ant] Exiting /Users/admin/Downloads/services/services/build.xml.
BUILD FAILED
/Users/admin/Downloads/services/build.xml:210: The following error
occurred
while executing this line:
/Users/admin/Downloads/services/services/build.xml:136: The following
error
occurred while executing this line:
/Users/admin/Downloads/services/services/authentication/build.xml:117:
The
following error occurred while executing this line:
/Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
org.postgresql.util.PSQLException: FATAL: password authentication failed
for
user "cspace"
at
org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:291)
at
org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:108)
at
org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)
at
org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:125)
at
org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Connection.java:30)
at
org.postgresql.jdbc3g.AbstractJdbc3gConnection.<init>(AbstractJdbc3gConnection.java:22)
at
org.postgresql.jdbc4.AbstractJdbc4Connection.<init>(AbstractJdbc4Connection.java:30)
at org.postgresql.jdbc4.Jdbc4Connection.<init>(Jdbc4Connection.java:24)
at org.postgresql.Driver.makeConnection(Driver.java:393)
at org.postgresql.Driver.connect(Driver.java:267)
at
org.apache.tools.ant.taskdefs.JDBCTask.getConnection(JDBCTask.java:370)
at org.apache.tools.ant.taskdefs.SQLExec.getConnection(SQLExec.java:942)
at org.apache.tools.ant.taskdefs.SQLExec.execute(SQLExec.java:614)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.Main.runBuild(Main.java:809)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
Total time: 1 second
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
From: "Aron Roberts" aron@socrates.berkeley.edu
To: "Al Bersch" abersch@museumca.org
Sent: Friday, May 25, 2012 9:32:47 AM
Subject: Re: [Talk] space user password error
Hi Al,
Many thanks - it's terrific you resolved this in this way! And
your note on the Talk list will help others who may run into the same
situation.
(Until reading your note, I wasn't aware of the ENCRYPTED option for
passwords in PostgreSQL:
http://www.postgresql.org/docs/9.1/static/sql-createuser.html).
Best,
Aron
On Fri, May 25, 2012 at 8:56 AM, 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
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:
Hello,
After following the steps for creating our tenant we get an error when
we
run the ant create_db import. With the following error:
/Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
org.postgresql.util.PSQLException: FATAL: password authentication
failed
for
user "space".
We believe we verified the password is set to what our environment
variable
is set to: $DB_PASSWORD_CSPACE.
We would appreciate any ideas/advice!
Thank you!
Al Bersch
Digital Project Coordinator
Oakland Museum of California
1000 Oak Street, Oakland, CA 94607
abersch@museumca.org
510-318-8468
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Al - and all: Ultimately, it is our intention and expectation that a
CollectionSpace system will be installable, in the future, via a
packaged installer, via a 'wizard' or equivalent interface. Most of
the work to date on this system has been around functionality and
stability, and improvements to installation and administration is a
fertile area for future work.
On Thu, May 31, 2012 at 9:58 AM, Aron Roberts
<aron@socrates.berkeley.edu> wrote:
> I concur, Jesse, with your good suggestion. There are benefits to
> setting up a dedicated user account for installing and managing a
> CollectionSpace system, and this is, I believe, consistent with
> documented best practices for a number of other server-based systems.
>
> As part of that, we will also likely need to document how, on
> *nix-based systems, that user can be given 'sudo' privileges.
>
> Aron
>
> On Thu, May 31, 2012 at 9:38 AM, Jesse Martinez
> <jmartinez@movingimage.us> wrote:
>> Chris makes a good point.
>>
>> I think we should assert using a dedicated user to run
>> CollectionSpace, at least on *nix based systems. This would help keep
>> environmental variables contained as well as maintaining a level of
>> separation from root privileges. On nightly and QA I use a 'bamboo'
>> user, which also owns the Bamboo CI processes, to run and own CSpace
>> files. On development servers I tend to use a 'cspace' user for the
>> same purpose.
>>
>> - Jesse
>>
>> On Thu, May 31, 2012 at 12:11 PM, Aron Roberts
>> <aron@socrates.berkeley.edu> wrote:
>>> Ahh ... excellent suggestion, Chris!
>>>
>>> (Will make a note to add this to the install documents.)
>>>
>>> Al, when you can, we'd welcome an update on whether Chris might have
>>> identified what was happening in your situation - thanks!
>>>
>>> Aron
>>>
>>> On Thu, May 31, 2012 at 6:30 AM, Christopher Pott
>>> <Christopher.Pott@smk.dk> wrote:
>>>> Hi Al,
>>>>
>>>> I'm working on configuring CollectionSpace at the National Gallery in Denmark.
>>>>
>>>> I just thought there was also a chance your earlier problems with environment variables could be related to using different OS user permissions during various stages of the installation. For example, at least in Debian Linux, if you export your environment variables as 'myuser' in "/home/myuser/.bashrc", but then run the build command as 'root' (via 'sudo') then your current variables won't be preserved (unless you use 'sudo -E').
>>>>
>>>> Regards,
>>>> Chris
>>>>
>>>>
>>>> -----Oprindelig meddelelse-----
>>>> Fra: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] På vegne af Aron Roberts
>>>> Sendt: 26. maj 2012 02:42
>>>> Til: Al Bersch
>>>> Cc: talk@lists.collectionspace.org
>>>> Emne: Re: [Talk] space user password error
>>>>
>>>> Thanks, Al. This all sounds good so far. Here's hoping the reinstall
>>>> takes care of the problem!
>>>>
>>>> If for any reason it doesn't, some more thoughts:
>>>>
>>>> 1) Make sure you're running all your 'ant' commands from the VERY top
>>>> level of the CollectionSpace services source code tree; e.g. from
>>>>
>>>> /services
>>>>
>>>> and not anywhere else down in the tree; e.g. /services/services
>>>>
>>>> 2) In $HOME/bash_profile:
>>>>
>>>> export CSPACE_JEESERVER_HOME="/usr/local/share/apache-tomcat-6.0.33"
>>>> export CATALINA_HOME=$CSPACE_JEESERVER_HOME
>>>> export CATALINA_PID="$CSPACE_JEESERVER_HOME/bin/tomcat.pid"
>>>> export CATALINA_OPTS="-Xmx1024m -XX:MaxPermSize=384m"
>>>> export JAVA_HOME="/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home"
>>>> export DB_USER="..."
>>>> export DB_PASSWORD="..."
>>>> export DB_PASSWORD_NUXEO="..."
>>>> export DB_PASSWORD_CSPACE="...."
>>>> export ANT_OPTS="-Xmx768m -XX:MaxPermSize=512m"
>>>> export MAVEN_OPTS="-Xmx768m -XX:MaxPermSize=512m -Dfile.encoding=UTF-8"
>>>>
>>>> 3) This *may* also potentially be important, and is experimenting
>>>> with; in $HOME/.bashrc, there is this entry:
>>>>
>>>> $HOME/.bash_profile
>>>>
>>>> 4) If 1) isn't relevant, 2) checks out, and you try 3), and the
>>>> environment variables are all present, in whatever shell you may be
>>>> in, the next thing to check is whether Ant is picking them up out of
>>>> the environment.
>>>>
>>>> You can try running the simple Ant buildfile pasted into an earlier
>>>> message to check on this. If Ant isn't seeing these variables, you
>>>> might try looking at the Nabble discussion thread mentioned earlier,
>>>> for any clues about issues that might be present on your system.
>>>>
>>>> Aron
>>>>
>>>> P.S. Jesse Martinez, I believe, added the following note to the
>>>> installation instructions,
>>>> http://wiki.collectionspace.org/display/DOC/Installing+2.3+on+Mac+OS+X+10.6.8:
>>>>
>>>> If you added these lines to ~/.bashrc, to ensure these environment
>>>> variables are present in every new login shell, edit or create the
>>>> ~/.bash_profile file and add the following line to that file:
>>>> . ~/.bashrc
>>>>
>>>> I've basically done the converse of this, above, in part as a result
>>>> of reading posts like http://hacktux.com/bash/bashrc/bash_profile and
>>>> http://stefaanlippens.net/bashrc_and_others:
>>>>
>>>> "In this case of an interactive but non-login shell, only ~/.bashrc is
>>>> executed."
>>>>
>>>> (Ultimately, this may hint at necessary changes to the existing
>>>> documentation ...)
>>>>
>>>> On Fri, May 25, 2012 at 4:18 PM, Al Bersch <abersch@museumca.org> wrote:
>>>>> Hi Aron,
>>>>>
>>>>> Thanks for your response.
>>>>>
>>>>> In answer to your questions - yes, the installation is on a Mac OS X system,
>>>>> and yes, there entries in the appropriate shell configuration file to export
>>>>> the environment variables (we thinks so - we put them in the .bash profile).
>>>>> As for the third question, I believe that each and every one of the
>>>>> environment variables is visible upon the command 'env'.
>>>>>
>>>>> Our plan is to reinstall and see if we can resolve the issue that way. I'll
>>>>> let you know what we find out.
>>>>>
>>>>> Thanks again,
>>>>>
>>>>> Al
>>>>>
>>>>> Al Bersch
>>>>> Digital Project Coordinator
>>>>> Oakland Museum of California
>>>>> 1000 Oak Street, Oakland, CA 94607
>>>>> abersch@museumca.org
>>>>> 510-318-8468
>>>>> ________________________________
>>>>> From: "Aron Roberts" <aron@socrates.berkeley.edu>
>>>>> To: "Al Bersch" <abersch@museumca.org>
>>>>> Cc: talk@lists.collectionspace.org
>>>>> Sent: Friday, May 25, 2012 2:33:32 PM
>>>>>
>>>>> Subject: Re: [Talk] space user password error
>>>>>
>>>>> Al,
>>>>>
>>>>> Thanks much for this update!
>>>>>
>>>>> There are a number of environment variables that must be available
>>>>> to Ant in order to successfully build the CollectionSpace services
>>>>> layer, create and populate databases, and import roles, permissions,
>>>>> etc. If any of those is missing, you may not have a completely
>>>>> working CollectionSpace system.
>>>>>
>>>>> It's likely to be more productive to resolve the environment
>>>>> variables problem once and for all, and get a clean installation, then
>>>>> to try to resolve individual problems caused by their absence, one
>>>>> after the other. That will, I'm concerned, be more consuming of your
>>>>> time than getting an environment in place where the installation steps
>>>>> 'just work.'
>>>>>
>>>>> Just to start out, is it the case that:
>>>>>
>>>>> * The installation is occurring on a Unix-like system (Linux, Mac OS
>>>>> X, or even a Unix variant)?
>>>>> * There are entries in the appropriate shell configuration file to
>>>>> export these environment variables, so that they're present in every
>>>>> new instance of your command shell?
>>>>> * When you open a new shell / terminal window, you can type the
>>>>> command 'env', and, in the output from that command, see each and
>>>>> every one of the environment variables listed in the "Setting Up
>>>>> CollectionSpace" section of the various installation documents, such
>>>>> as http://wiki.collectionspace.org/x/1oHyBQ ?
>>>>>
>>>>> Aron
>>>>>
>>>>> On Fri, May 25, 2012 at 2:21 PM, Al Bersch <abersch@museumca.org> wrote:
>>>>>> Hi Aron, Jesse,
>>>>>>
>>>>>> Thanks for getting back. We ended up hard-coding our password to the
>>>>>> variable, and that worked. So ant create_db import ran successfully.
>>>>>> However, I still want to run the Ant buildfile you sent to try to locate
>>>>>> the
>>>>>> problem the environment variables.
>>>>>>
>>>>>> We started the servers, but can't find our tenant, which leaves us with
>>>>>> more questions (and thanks again for all your help). What should we have
>>>>>> in
>>>>>> our Tables, and what should we have listed for Tenants? After we created
>>>>>> our
>>>>>> tenant, our tenant table is showing up empty.
>>>>>>
>>>>>> Also, can someone share an example of a host file (we didn't put in a DNS,
>>>>>> just used localhost)? It would be great to see what it is supposed to look
>>>>>> like.
>>>>>>
>>>>>> Thank you,
>>>>>>
>>>>>> Al Bersch
>>>>>> Digital Project Coordinator
>>>>>> Oakland Museum of California
>>>>>> 1000 Oak Street, Oakland, CA 94607
>>>>>> abersch@museumca.org
>>>>>> 510-318-8468
>>>>>> ________________________________
>>>>>> From: "Aron Roberts" <aron@socrates.berkeley.edu>
>>>>>> To: "Al Bersch" <abersch@museumca.org>
>>>>>> Cc: talk@lists.collectionspace.org
>>>>>> Sent: Friday, May 25, 2012 1:22:50 PM
>>>>>>
>>>>>> Subject: Re: [Talk] space user password error
>>>>>>
>>>>>> Al,
>>>>>>
>>>>>> You can try pasting this simple Ant buildfile into a file named
>>>>>> "build.xml" in some temporary directory:
>>>>>>
>>>>>> <project name="test-env-vars" default="test-env-vars" basedir=".">
>>>>>> <!-- environment should be declared first -->
>>>>>> <property environment="env" />
>>>>>> <target name="test-env-vars">
>>>>>> <echo
>>>>>> message="CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}"/>
>>>>>> </target>
>>>>>> </project>
>>>>>>
>>>>>> and then invoke it, from that directory, via 'ant'. This will let you
>>>>>> know - in a simple way, without any filtering - whether Ant can 'see'
>>>>>> your environment variables. If it succeeds at finding the values in
>>>>>> your environment variables, you'll see something like:
>>>>>>
>>>>>> test-env-vars:
>>>>>> [echo] CSPACE_JEESERVER_HOME=/usr/local/share/apache-tomcat-6.0.33
>>>>>> BUILD SUCCESSFUL
>>>>>>
>>>>>> and if it fails, you'll see:
>>>>>>
>>>>>> test-env-vars:
>>>>>> [echo] CSPACE_JEESERVER_HOME=${env.CSPACE_JEESERVER_HOME}
>>>>>> BUILD SUCCESSFUL
>>>>>>
>>>>>> If it can't find the values in your environment variables, then you
>>>>>> might look into that discussion thread in that Nabble-archived post,
>>>>>> included in a previous message on this topic, to see if any of the
>>>>>> issues mentioned there might apply in your situation.
>>>>>>
>>>>>> Aron
>>>>>>
>>>>>> On Fri, May 25, 2012 at 1:13 PM, Jesse Martinez
>>>>>> <jmartinez@movingimage.us> wrote:
>>>>>>> Hi Al,
>>>>>>>
>>>>>>> Just a quick thought, are you using special characters or punctuation
>>>>>>> in your cspace password? I once had an issue using dollar signs $ in a
>>>>>>> postgresql password.
>>>>>>>
>>>>>>> - Jesse
>>>>>>>
>>>>>>> On Fri, May 25, 2012 at 2:17 PM, Al Bersch <abersch@museumca.org> wrote:
>>>>>>>> Hi Aron and talk,
>>>>>>>>
>>>>>>>> It looks like I spoke too soon. We are still getting a build failed
>>>>>>>> message
>>>>>>>> (verbose version below) and it appears that our environment variables
>>>>>>>> are
>>>>>>>> not being recognized, even though we can find the right path if we echo
>>>>>>>> the
>>>>>>>> environment variables. We continue to get the message that the cspace
>>>>>>>> user
>>>>>>>> password can't be authenticated. We verified that the password is set in
>>>>>>>> the
>>>>>>>> environment variable. We can echo and it kicks back the password. Once
>>>>>>>> we
>>>>>>>> set the cspace user password, we can log into postgres with that user
>>>>>>>> password, until we run the script and after that we can't log in until
>>>>>>>> we
>>>>>>>> reset the password.
>>>>>>>>
>>>>>>>> Any thoughts? Much appreciated!
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> Al
>>>>>>>>
>>>>>>>> museumcatest:services admin$ ant create_db import -v
>>>>>>>> Apache Ant(TM) version 1.8.2 compiled on June 3 2011
>>>>>>>> Trying the default build file: build.xml
>>>>>>>> Buildfile: /Users/admin/Downloads/services/build.xml
>>>>>>>> Detected Java version: 1.6 in:
>>>>>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>>>>>> Detected OS: Mac OS X
>>>>>>>> parsing buildfile /Users/admin/Downloads/services/build.xml with URI =
>>>>>>>> file:/Users/admin/Downloads/services/build.xml
>>>>>>>> Project base dir set to: /Users/admin/Downloads/services
>>>>>>>> parsing buildfile
>>>>>>>> jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
>>>>>>>> with
>>>>>>>> URI =
>>>>>>>> jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
>>>>>>>> from a zip file
>>>>>>>> [property] Loading Environment env.
>>>>>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>>>>>> Build sequence for target(s) `create_db' is [create_base_db, create_db]
>>>>>>>> Complete build sequence is [create_base_db, create_db, undeploy,
>>>>>>>> clean-windows, checkvars, install-unix, install-windows, install,
>>>>>>>> setup_initdb.sql, deploy, package-unix, package-windows, package,
>>>>>>>> eclipse-unix, dist_installer, dist, dist-jee-nuxeo, import,
>>>>>>>> test-windows,
>>>>>>>> hotdeploy, init, dist-jee-domains, clean-unix, clean, eclipse-windows,
>>>>>>>> eclipse, test-unix, gen_ddl, test, dist-jee-cspace, doc, ]
>>>>>>>>
>>>>>>>> create_base_db:
>>>>>>>> [sql] connecting to jdbc:postgresql://localhost:5432
>>>>>>>> [sql] Loading org.postgresql.Driver using AntClassLoader with
>>>>>>>> classpath
>>>>>>>>
>>>>>>>>
>>>>>>>> /usr/local/share/apache-tomcat-6.0.33/cspace/services/db/jdbc_drivers/postgresql-8.4-702.jdbc4.jar
>>>>>>>> [sql] Executing resource:
>>>>>>>>
>>>>>>>>
>>>>>>>> /usr/local/share/apache-tomcat-6.0.33/cspace/services/db/postgresql/init_db.sql
>>>>>>>> [sql] SQL: DROP database IF EXISTS cspace
>>>>>>>> [sql] 0 rows affected
>>>>>>>> [sql] SQL: DROP database IF EXISTS nuxeo
>>>>>>>> [sql] 0 rows affected
>>>>>>>> [sql] SQL: DROP USER IF EXISTS nuxeo
>>>>>>>> [sql] 0 rows affected
>>>>>>>> [sql] SQL: DROP USER IF EXISTS cspace
>>>>>>>> [sql] 0 rows affected
>>>>>>>> [sql] SQL: DROP USER IF EXISTS reader
>>>>>>>> [sql] 0 rows affected
>>>>>>>> [sql] SQL: CREATE ROLE nuxeo WITH PASSWORD
>>>>>>>> 'your_nuxeo_database_user_password_here' LOGIN
>>>>>>>> [sql] 0 rows affected
>>>>>>>> [sql] SQL: CREATE ROLE cspace WITH PASSWORD
>>>>>>>> 'your_cspace_database_user_password_here' LOGIN
>>>>>>>> [sql] 0 rows affected
>>>>>>>> [sql] SQL: CREATE ROLE reader WITH PASSWORD 'read' LOGIN
>>>>>>>> [sql] 0 rows affected
>>>>>>>> [sql] SQL: CREATE DATABASE cspace ENCODING 'UTF8' OWNER cspace
>>>>>>>> [sql] 0 rows affected
>>>>>>>> [sql] SQL: CREATE DATABASE nuxeo ENCODING 'UTF8' OWNER nuxeo
>>>>>>>> [sql] 0 rows affected
>>>>>>>> [sql] SQL: GRANT CONNECT ON DATABASE nuxeo TO reader
>>>>>>>> [sql] 0 rows affected
>>>>>>>> [sql] 11 of 11 SQL statements executed successfully
>>>>>>>>
>>>>>>>> create_db:
>>>>>>>> Detected Java version: 1.6 in:
>>>>>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>>>>>> Detected OS: Mac OS X
>>>>>>>> [ant] calling target(s) [create_db] in build file
>>>>>>>> /Users/admin/Downloads/services/services/build.xml
>>>>>>>> parsing buildfile /Users/admin/Downloads/services/services/build.xml
>>>>>>>> with
>>>>>>>> URI = file:/Users/admin/Downloads/services/services/build.xml
>>>>>>>> Project base dir set to: /Users/admin/Downloads/services/services
>>>>>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>>> Property "env.DB_PASSWORD_NUXEO" has not been set
>>>>>>>> Property "env.DB_PASSWORD" has not been set
>>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>>> Property "env.DB_USER" has not been set
>>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>>> Property "env.DB_PASSWORD_CSPACE" has not been set
>>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>>> Property "env.CSPACE_JEESERVER_HOME" has not been set
>>>>>>>> [ant] Entering
>>>>>>>> /Users/admin/Downloads/services/services/build.xml...
>>>>>>>> Build sequence for target(s) `create_db' is [create_db]
>>>>>>>> Complete build sequence is [create_db, undeploy, clean-windows,
>>>>>>>> install-unix, install-windows, install, deploy, doc-windows,
>>>>>>>> package-unix,
>>>>>>>> package-windows, package, dist_installer, import,
>>>>>>>> copy-dependencies-reports,
>>>>>>>> test-windows, doc-unix, doc, dist, hotdeploy, clean-unix, clean,
>>>>>>>> test-unix,
>>>>>>>> gen_ddl, test, generate-dependencies-reports, ]
>>>>>>>>
>>>>>>>> create_db:
>>>>>>>> Detected Java version: 1.6 in:
>>>>>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>>>>>> Detected OS: Mac OS X
>>>>>>>> [ant] calling target(s) [create_db] in build file
>>>>>>>> /Users/admin/Downloads/services/services/authentication/build.xml
>>>>>>>> parsing buildfile
>>>>>>>> /Users/admin/Downloads/services/services/authentication/build.xml with
>>>>>>>> URI =
>>>>>>>> file:/Users/admin/Downloads/services/services/authentication/build.xml
>>>>>>>> Project base dir set to:
>>>>>>>> /Users/admin/Downloads/services/services/authentication
>>>>>>>> [property] Loading Environment env.
>>>>>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>>>>>> [ant] Entering
>>>>>>>> /Users/admin/Downloads/services/services/authentication/build.xml...
>>>>>>>> Build sequence for target(s) `create_db' is [create_db]
>>>>>>>> Complete build sequence is [create_db, undeploy, clean-windows,
>>>>>>>> install-unix, install-windows, install, deploy, package-unix,
>>>>>>>> package-windows, package, test-windows, dist, clean-unix, clean,
>>>>>>>> test-unix,
>>>>>>>> gen_ddl, test, ]
>>>>>>>>
>>>>>>>> create_db:
>>>>>>>> Detected Java version: 1.6 in:
>>>>>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>>>>>> Detected OS: Mac OS X
>>>>>>>> [ant] calling target(s) [create_db] in build file
>>>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml
>>>>>>>> parsing buildfile
>>>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml
>>>>>>>> with URI =
>>>>>>>>
>>>>>>>>
>>>>>>>> file:/Users/admin/Downloads/services/services/authentication/pstore/build.xml
>>>>>>>> Project base dir set to:
>>>>>>>> /Users/admin/Downloads/services/services/authentication/pstore
>>>>>>>> [property] Loading Environment env.
>>>>>>>> [property] Loading /Users/admin/Downloads/services/build.properties
>>>>>>>> [ant] Entering
>>>>>>>>
>>>>>>>>
>>>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml...
>>>>>>>> Build sequence for target(s) `create_db' is [create_db]
>>>>>>>> Complete build sequence is [create_db, check.db.scripts.deploy.dir,
>>>>>>>> undeploy, clean-windows, setup_hibernate.cfg, install-unix,
>>>>>>>> install-windows,
>>>>>>>> install, deploy, package-unix, package-windows, package, gen_ddl-unix,
>>>>>>>> test-windows, gen_ddl-windows, dist, clean-unix, clean, init, test-unix,
>>>>>>>> gen_ddl, test, ]
>>>>>>>>
>>>>>>>> create_db:
>>>>>>>> [sql] connecting to jdbc:postgresql://localhost:5432/cspace
>>>>>>>> [sql] Loading org.postgresql.Driver using a cached AntClassLoader.
>>>>>>>> [ant] Exiting
>>>>>>>>
>>>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml.
>>>>>>>> [ant] Exiting
>>>>>>>> /Users/admin/Downloads/services/services/authentication/build.xml.
>>>>>>>> [ant] Exiting /Users/admin/Downloads/services/services/build.xml.
>>>>>>>>
>>>>>>>> BUILD FAILED
>>>>>>>> /Users/admin/Downloads/services/build.xml:210: The following error
>>>>>>>> occurred
>>>>>>>> while executing this line:
>>>>>>>> /Users/admin/Downloads/services/services/build.xml:136: The following
>>>>>>>> error
>>>>>>>> occurred while executing this line:
>>>>>>>> /Users/admin/Downloads/services/services/authentication/build.xml:117:
>>>>>>>> The
>>>>>>>> following error occurred while executing this line:
>>>>>>>>
>>>>>>>>
>>>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
>>>>>>>> org.postgresql.util.PSQLException: FATAL: password authentication failed
>>>>>>>> for
>>>>>>>> user "cspace"
>>>>>>>> at
>>>>>>>>
>>>>>>>>
>>>>>>>> org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:291)
>>>>>>>> at
>>>>>>>>
>>>>>>>>
>>>>>>>> org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:108)
>>>>>>>> at
>>>>>>>>
>>>>>>>>
>>>>>>>> org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)
>>>>>>>> at
>>>>>>>>
>>>>>>>>
>>>>>>>> org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:125)
>>>>>>>> at
>>>>>>>>
>>>>>>>>
>>>>>>>> org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Connection.java:30)
>>>>>>>> at
>>>>>>>>
>>>>>>>>
>>>>>>>> org.postgresql.jdbc3g.AbstractJdbc3gConnection.<init>(AbstractJdbc3gConnection.java:22)
>>>>>>>> at
>>>>>>>>
>>>>>>>>
>>>>>>>> org.postgresql.jdbc4.AbstractJdbc4Connection.<init>(AbstractJdbc4Connection.java:30)
>>>>>>>> at org.postgresql.jdbc4.Jdbc4Connection.<init>(Jdbc4Connection.java:24)
>>>>>>>> at org.postgresql.Driver.makeConnection(Driver.java:393)
>>>>>>>> at org.postgresql.Driver.connect(Driver.java:267)
>>>>>>>> at
>>>>>>>> org.apache.tools.ant.taskdefs.JDBCTask.getConnection(JDBCTask.java:370)
>>>>>>>> at org.apache.tools.ant.taskdefs.SQLExec.getConnection(SQLExec.java:942)
>>>>>>>> at org.apache.tools.ant.taskdefs.SQLExec.execute(SQLExec.java:614)
>>>>>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>>>>>> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>>>>>>>> at
>>>>>>>>
>>>>>>>>
>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>>> at
>>>>>>>>
>>>>>>>>
>>>>>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>>>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>>>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>>>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>>>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>>>>>> at
>>>>>>>>
>>>>>>>>
>>>>>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
>>>>>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>>>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
>>>>>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>>>>>> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>>>>>>>> at
>>>>>>>>
>>>>>>>>
>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>>> at
>>>>>>>>
>>>>>>>>
>>>>>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>>>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>>>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>>>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>>>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>>>>>> at
>>>>>>>>
>>>>>>>>
>>>>>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
>>>>>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>>>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
>>>>>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>>>>>> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>>>>>>>> at
>>>>>>>>
>>>>>>>>
>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>>> at
>>>>>>>>
>>>>>>>>
>>>>>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>>>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>>>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>>>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>>>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>>>>>> at
>>>>>>>>
>>>>>>>>
>>>>>>>> org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
>>>>>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>>>>>> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
>>>>>>>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>> at
>>>>>>>>
>>>>>>>>
>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>>>> at
>>>>>>>>
>>>>>>>>
>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>>> at
>>>>>>>>
>>>>>>>>
>>>>>>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>>>>>>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>>>>>>> at org.apache.tools.ant.Target.execute(Target.java:390)
>>>>>>>> at org.apache.tools.ant.Target.performTasks(Target.java:411)
>>>>>>>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>>>>>>> at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
>>>>>>>> at
>>>>>>>>
>>>>>>>>
>>>>>>>> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
>>>>>>>> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>>>>>>>> at org.apache.tools.ant.Main.runBuild(Main.java:809)
>>>>>>>> at org.apache.tools.ant.Main.startAnt(Main.java:217)
>>>>>>>> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
>>>>>>>> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
>>>>>>>>
>>>>>>>> Total time: 1 second
>>>>>>>>
>>>>>>>> Al Bersch
>>>>>>>> Digital Project Coordinator
>>>>>>>> Oakland Museum of California
>>>>>>>> 1000 Oak Street, Oakland, CA 94607
>>>>>>>> abersch@museumca.org
>>>>>>>> 510-318-8468
>>>>>>>> ________________________________
>>>>>>>> From: "Aron Roberts" <aron@socrates.berkeley.edu>
>>>>>>>> To: "Al Bersch" <abersch@museumca.org>
>>>>>>>> Sent: Friday, May 25, 2012 9:32:47 AM
>>>>>>>>
>>>>>>>> Subject: Re: [Talk] space user password error
>>>>>>>>
>>>>>>>> Hi Al,
>>>>>>>>
>>>>>>>> Many thanks - it's terrific you resolved this in this way! And
>>>>>>>> your note on the Talk list will help others who may run into the same
>>>>>>>> situation.
>>>>>>>>
>>>>>>>> (Until reading your note, I wasn't aware of the ENCRYPTED option for
>>>>>>>> passwords in PostgreSQL:
>>>>>>>> http://www.postgresql.org/docs/9.1/static/sql-createuser.html).
>>>>>>>>
>>>>>>>> Best,
>>>>>>>> Aron
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, May 25, 2012 at 8:56 AM, 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
>>>>>>>>> ________________________________
>>>>>>>>> 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:
>>>>>>>>>> Hello,
>>>>>>>>>>
>>>>>>>>>> After following the steps for creating our tenant we get an error when
>>>>>>>>>> we
>>>>>>>>>> run the ant create_db import. With the following error:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> /Users/admin/Downloads/services/services/authentication/pstore/build.xml:160:
>>>>>>>>>> org.postgresql.util.PSQLException: FATAL: password authentication
>>>>>>>>>> failed
>>>>>>>>>> for
>>>>>>>>>> user "space".
>>>>>>>>>>
>>>>>>>>>> We believe we verified the password is set to what our environment
>>>>>>>>>> variable
>>>>>>>>>> is set to: $DB_PASSWORD_CSPACE.
>>>>>>>>>>
>>>>>>>>>> We would appreciate any ideas/advice!
>>>>>>>>>>
>>>>>>>>>> Thank you!
>>>>>>>>>> Al Bersch
>>>>>>>>>> Digital Project Coordinator
>>>>>>>>>> Oakland Museum of California
>>>>>>>>>> 1000 Oak Street, Oakland, CA 94607
>>>>>>>>>> abersch@museumca.org
>>>>>>>>>> 510-318-8468
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Talk mailing list
>>>>>>>>>> Talk@lists.collectionspace.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Talk mailing list
>>>>>>>> Talk@lists.collectionspace.org
>>>>>>>>
>>>>>>>>
>>>>>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Talk mailing list
>>>>>>> Talk@lists.collectionspace.org
>>>>>>>
>>>>>>>
>>>>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Talk mailing list
>>>>> Talk@lists.collectionspace.org
>>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>>>
>>>>
>>>> _______________________________________________
>>>> Talk mailing list
>>>> Talk@lists.collectionspace.org
>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>>
>>>> _______________________________________________
>>>> Talk mailing list
>>>> Talk@lists.collectionspace.org
>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>>
>>> _______________________________________________
>>> Talk mailing list
>>> Talk@lists.collectionspace.org
>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>
>> _______________________________________________
>> Talk mailing list
>> Talk@lists.collectionspace.org
>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
