Hi all, I'm following the wiki documentation for upgrading from a v4.1 instance to v4.2 on Ubuntu 14. I've gone through all the steps including updating the environmental variables. This includes CSPACE_INSTANCE_ID to be "_tenantname" and altering the cspace table column name. When I start up cspace I get this error: Caused by: org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host "127.0.0.1", user "nuxeo_tenantname", database "nuxeo_tenantname", SSL off So I updated pg_hba.conf to include an entry for nuxeo_tenantname. Likewise for cspace_tenantname. This step wasn't explicitly stated in the docs but I figured it would at least let me continue the start up process. I restart Tomcat and then I get this error message: Caused by: org.postgresql.util.PSQLException: FATAL: password authentication failed for user "cspace_tenantname" I'm unsure what to do at this point. Any thoughts? Thanks, Jesse

AFAIK, the 'cspace' username in the database - that is, the default name for the PostgreSQL super-user-with-limitations that administers the CSpace databases - isn't currently instance-qualified. At least, I had to back out instance qualification in the automated installer here: https://github.com/cspace-puppet/cspace_postgresql_server/commit/1063aad78c8057cc48b9ea013f2bec2f7619aac8 Whether the name of this user *should* be instance qualified is another question ... it'd be interesting to try a multi-instance configuration and see whether not doing so results in conflicts - or inadvertent overriding with each successive installation. On Sat, Jul 11, 2015 at 2:04 PM, Jesse Martinez <mjesse@gmail.com> wrote: > Hi all, > > I'm following the wiki documentation for upgrading from a v4.1 instance to > v4.2 on Ubuntu 14. I've gone through all the steps including updating the > environmental variables. This includes CSPACE_INSTANCE_ID to be > "_tenantname" and altering the cspace table column name. > > When I start up cspace I get this error: > Caused by: org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry > for host "127.0.0.1", user "nuxeo_tenantname", database "nuxeo_tenantname", > SSL off > > So I updated pg_hba.conf to include an entry for nuxeo_tenantname. > Likewise for cspace_tenantname. This step wasn't explicitly stated in the > docs but I figured it would at least let me continue the start up process. > > I restart Tomcat and then I get this error message: > Caused by: org.postgresql.util.PSQLException: FATAL: password > authentication failed for user "cspace_tenantname" > > I'm unsure what to do at this point. > > Any thoughts? > > Thanks, > > Jesse > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > >

I see this in the services build.properties file: db.cspace.name=cspace${cspace.instance.id} db.cspace.user=${db.cspace.name} db.cspace.user.password=${env.DB_CSPACE_PASSWORD} But from what I can tell there hasn't been a cspace_tenantname database created for an upgrade from v4.1 When I remove the cspace.instance.id variable for db.cspace.name to this: db.cspace.name=cspace and then rebuild I now get this error message: 2015-07-12 23:39:08,009 ERROR [localhost-startStop-1] [org.collectionspace.services.common.ServiceMain:206] Default accounts and permissions setup failed with exception(s): null java.lang.NullPointerException at org.collectionspace.services.common.authorization_mgt.AuthorizationCommon.persist(AuthorizationCommon.java:1155) at org.collectionspace.services.common.authorization_mgt.AuthorizationCommon.createDefaultWorkflowPermissions(AuthorizationCommon.java:1085) at org.collectionspace.services.common.ServiceMain.initialize(ServiceMain.java:199) at org.collectionspace.services.common.ServiceMain.getInstance(ServiceMain.java:126) at org.collectionspace.services.common.ServiceMain.getInstance(ServiceMain.java:110) at org.collectionspace.services.common.CollectionSpaceServiceContextListener.contextInitialized(CollectionSpaceServiceContextListener.java:23) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4994) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5492) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1081) at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1877) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Any ideas? Jesse On Sat, Jul 11, 2015 at 5:24 PM, Aron Roberts <aron@socrates.berkeley.edu> wrote: > AFAIK, the 'cspace' username in the database - that is, the default name > for the PostgreSQL super-user-with-limitations that administers the CSpace > databases - isn't currently instance-qualified. > > At least, I had to back out instance qualification in the automated > installer here: > > https://github.com/cspace-puppet/cspace_postgresql_server/commit/1063aad78c8057cc48b9ea013f2bec2f7619aac8 > > Whether the name of this user *should* be instance qualified is another > question ... it'd be interesting to try a multi-instance configuration and > see whether not doing so results in conflicts - or inadvertent overriding > with each successive installation. > > On Sat, Jul 11, 2015 at 2:04 PM, Jesse Martinez <mjesse@gmail.com> wrote: > >> Hi all, >> >> I'm following the wiki documentation for upgrading from a v4.1 instance >> to v4.2 on Ubuntu 14. I've gone through all the steps including updating >> the environmental variables. This includes CSPACE_INSTANCE_ID to be >> "_tenantname" and altering the cspace table column name. >> >> When I start up cspace I get this error: >> Caused by: org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry >> for host "127.0.0.1", user "nuxeo_tenantname", database "nuxeo_tenantname", >> SSL off >> >> So I updated pg_hba.conf to include an entry for nuxeo_tenantname. >> Likewise for cspace_tenantname. This step wasn't explicitly stated in the >> docs but I figured it would at least let me continue the start up process. >> >> I restart Tomcat and then I get this error message: >> Caused by: org.postgresql.util.PSQLException: FATAL: password >> authentication failed for user "cspace_tenantname" >> >> I'm unsure what to do at this point. >> >> Any thoughts? >> >> Thanks, >> >> Jesse >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> >> >

Aron, I think you're confusing the postgres role "csadmin" with "cspace"? The role "csadmin" is never instance qualified, but the "cspace" role is. -Richard ________________________________ From: Talk <talk-bounces@lists.collectionspace.org> on behalf of Aron Roberts <aron@socrates.berkeley.edu> Sent: Saturday, July 11, 2015 2:24 PM To: Jesse Martinez Cc: CollectionSpace Talk List Subject: Re: [Talk] Error upgrading to v4.2 AFAIK, the 'cspace' username in the database - that is, the default name for the PostgreSQL super-user-with-limitations that administers the CSpace databases - isn't currently instance-qualified. At least, I had to back out instance qualification in the automated installer here: https://github.com/cspace-puppet/cspace_postgresql_server/commit/1063aad78c8057cc48b9ea013f2bec2f7619aac8 Whether the name of this user *should* be instance qualified is another question ... it'd be interesting to try a multi-instance configuration and see whether not doing so results in conflicts - or inadvertent overriding with each successive installation. On Sat, Jul 11, 2015 at 2:04 PM, Jesse Martinez <mjesse@gmail.com<mailto:mjesse@gmail.com>> wrote: Hi all, I'm following the wiki documentation for upgrading from a v4.1 instance to v4.2 on Ubuntu 14. I've gone through all the steps including updating the environmental variables. This includes CSPACE_INSTANCE_ID to be "_tenantname" and altering the cspace table column name. When I start up cspace I get this error: Caused by: org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host "127.0.0.1", user "nuxeo_tenantname", database "nuxeo_tenantname", SSL off So I updated pg_hba.conf to include an entry for nuxeo_tenantname. Likewise for cspace_tenantname. This step wasn't explicitly stated in the docs but I figured it would at least let me continue the start up process. I restart Tomcat and then I get this error message: Caused by: org.postgresql.util.PSQLException: FATAL: password authentication failed for user "cspace_tenantname" I'm unsure what to do at this point. Any thoughts? Thanks, Jesse _______________________________________________ Talk mailing list Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Aron,

You're correct here, Richard - thanks! Apologies for this confusion on my part; I'm glad to have it reaffirmed publicly here that the 'cspace' user (as well as the 'nuxeo' user) are instance-qualified. (Context: that's essential when allowing multiple CSpace servers to share a single, common PostgreSQL database instance.) On Mon, Jul 13, 2015 at 9:57 AM, Richard Millet <richard.millet@lyrasis.org> wrote: > Aron, > > > I think you're confusing the postgres role "csadmin" with "cspace"? > The role "csadmin" is never instance qualified, but the "cspace" role is. > > -Richard > > ------------------------------ > *From:* Talk <talk-bounces@lists.collectionspace.org> on behalf of Aron > Roberts <aron@socrates.berkeley.edu> > *Sent:* Saturday, July 11, 2015 2:24 PM > *To:* Jesse Martinez > *Cc:* CollectionSpace Talk List > *Subject:* Re: [Talk] Error upgrading to v4.2 > > AFAIK, the 'cspace' username in the database - that is, the default > name for the PostgreSQL super-user-with-limitations that administers the > CSpace databases - isn't currently instance-qualified. > > At least, I had to back out instance qualification in the automated > installer here: > > https://github.com/cspace-puppet/cspace_postgresql_server/commit/1063aad78c8057cc48b9ea013f2bec2f7619aac8 > > Whether the name of this user *should* be instance qualified is another > question ... it'd be interesting to try a multi-instance configuration and > see whether not doing so results in conflicts - or inadvertent overriding > with each successive installation. > > On Sat, Jul 11, 2015 at 2:04 PM, Jesse Martinez <mjesse@gmail.com> wrote: > >> Hi all, >> >> I'm following the wiki documentation for upgrading from a v4.1 instance >> to v4.2 on Ubuntu 14. I've gone through all the steps including updating >> the environmental variables. This includes CSPACE_INSTANCE_ID to be >> "_tenantname" and altering the cspace table column name. >> >> When I start up cspace I get this error: >> Caused by: org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry >> for host "127.0.0.1", user "nuxeo_tenantname", database "nuxeo_tenantname", >> SSL off >> >> So I updated pg_hba.conf to include an entry for nuxeo_tenantname. >> Likewise for cspace_tenantname. This step wasn't explicitly stated in the >> docs but I figured it would at least let me continue the start up process. >> >> I restart Tomcat and then I get this error message: >> Caused by: org.postgresql.util.PSQLException: FATAL: password >> authentication failed for user "cspace_tenantname" >> >> I'm unsure what to do at this point. >> >> Any thoughts? >> >> Thanks, >> >> Jesse >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> >> >

Thanks for reporting this Jesse. Mark Cooper from LYRASIS is seeing a similar (if not the same) problem. I'll try to reproduce the problem and send out an update by the end of tomorrow. ________________________________ From: Talk <talk-bounces@lists.collectionspace.org> on behalf of Jesse Martinez <mjesse@gmail.com> Sent: Saturday, July 11, 2015 2:04 PM To: CollectionSpace Talk List Subject: [Talk] Error upgrading to v4.2 Hi all, I'm following the wiki documentation for upgrading from a v4.1 instance to v4.2 on Ubuntu 14. I've gone through all the steps including updating the environmental variables. This includes CSPACE_INSTANCE_ID to be "_tenantname" and altering the cspace table column name. When I start up cspace I get this error: Caused by: org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host "127.0.0.1", user "nuxeo_tenantname", database "nuxeo_tenantname", SSL off So I updated pg_hba.conf to include an entry for nuxeo_tenantname. Likewise for cspace_tenantname. This step wasn't explicitly stated in the docs but I figured it would at least let me continue the start up process. I restart Tomcat and then I get this error message: Caused by: org.postgresql.util.PSQLException: FATAL: password authentication failed for user "cspace_tenantname" I'm unsure what to do at this point. Any thoughts? Thanks, Jesse