Hi, 
I was having problems with my Jaspersoft report working and while I was doing this I noticed that what I had in my config for the nuxeo_default password (DB_NUXEO_PASSWORD) wasn't working when I logged into through pgAdmin3, by default, I mean the one that is in the config file. So I updated the password in a SQL query to the password that is in the config file. Now I can connect through pgAdmin3 with that configuration, however when I try to login to my tenant. I can't login. I checked the log and there's a lot going on but what caught my attention is this: Caused by: org.postgresql.util.PSQLException: FATAL: password authentication failed for user "nuxeo_default"
I checked at /usr/local/share/apache-tomcat-7.0.57/nuxeo-server/config for the password for my tenant to make sure it was correct and it was. I did notice at one point my password was entered with an extra set of quotes that I removed. Still I cannot login to my site. I've also tried the /init web call and that didn't work either. 
Does anyone have any idea how I can fix this?

Well, there are a few ways you could try to fix this.  Here is one of the simplest:

0. Backup everything you don't want to lose. (It might be useful to make a copy of your tomcat folder)
1. Shutdown tomcat
2. From the top-level source directory of the "Services" layer directory, perform this command
   env | grep DB
3. You should see a list of all the CollectionSpace related database passwords.
4. Pick a new_password for the DB_NUXEO_PASSWORD environment var value and set it with this command:
   export DB_NUXEO_PASSWORD=new_password
5. If you have a script (or something like .bashrc) to set your CollectionSpace environment variables, update that to reflect the new password value you just picked.
6. Verify the password looks correct, run this command
   env | grep DB
7. Now rebuild all the CollectionSpace config files by running this command from the top-level of the "Services" directory:
   ant undeploy deploy
8. After several minutes, all the config files should be updated with your new password copied over into the correct place in the tomcat directory.

Please let us know if that works.

From: Talk talk-bounces@lists.collectionspace.org on behalf of toolhater toolhater@yahoo.com
Sent: Thursday, August 11, 2016 4:17 PM
To: talk@lists.collectionspace.org
Subject: [Talk] db connection hosed.

Hi,

I was having problems with my Jaspersoft report working and while I was doing this I noticed that what I had in my config for the nuxeo_default password (DB_NUXEO_PASSWORD) wasn't working when I logged into through pgAdmin3, by default, I mean the one that is in the config file. So I updated the password in a SQL query to the password that is in the config file. Now I can connect through pgAdmin3 with that configuration, however when I try to login to my tenant. I can't login. I checked the log and there's a lot going on but what caught my attention is this: Caused by: org.postgresql.util.PSQLException: FATAL: password authentication failed for user "nuxeo_default"

I checked at /usr/local/share/apache-tomcat-7.0.57/nuxeo-server/config for the password for my tenant to make sure it was correct and it was. I did notice at one point my password was entered with an extra set of quotes that I removed. Still I cannot login to my site. I've also tried the /init web call and that didn't work either.

Does anyone have any idea how I can fix this?

If it is not obvious, the new password you pick needs to be the actual password for the existing "nuxeo_default" postgres role.  So use the password you're using to successfully connect to the "nuxeo_default" database via the pgadmin tool (or psql).

From: Talk talk-bounces@lists.collectionspace.org on behalf of Richard Millet richard.millet@lyrasis.org
Sent: Thursday, August 11, 2016 6:25 PM
To: talk@lists.collectionspace.org; toolhater
Subject: Re: [Talk] db connection hosed.

Well, there are a few ways you could try to fix this.  Here is one of the simplest:

0. Backup everything you don't want to lose. (It might be useful to make a copy of your tomcat folder)
1. Shutdown tomcat
2. From the top-level source directory of the "Services" layer directory, perform this command
   env | grep DB
3. You should see a list of all the CollectionSpace related database passwords.
4. Pick a new_password for the DB_NUXEO_PASSWORD environment var value and set it with this command:
   export DB_NUXEO_PASSWORD=new_password
5. If you have a script (or something like .bashrc) to set your CollectionSpace environment variables, update that to reflect the new password value you just picked.
6. Verify the password looks correct, run this command
   env | grep DB
7. Now rebuild all the CollectionSpace config files by running this command from the top-level of the "Services" directory:
   ant undeploy deploy
8. After several minutes, all the config files should be updated with your new password copied over into the correct place in the tomcat directory.

Please let us know if that works.

From: Talk talk-bounces@lists.collectionspace.org on behalf of toolhater toolhater@yahoo.com
Sent: Thursday, August 11, 2016 4:17 PM
To: talk@lists.collectionspace.org
Subject: [Talk] db connection hosed.

Hi,

I was having problems with my Jaspersoft report working and while I was doing this I noticed that what I had in my config for the nuxeo_default password (DB_NUXEO_PASSWORD) wasn't working when I logged into through pgAdmin3, by default, I mean the one that is in the config file. So I updated the password in a SQL query to the password that is in the config file. Now I can connect through pgAdmin3 with that configuration, however when I try to login to my tenant. I can't login. I checked the log and there's a lot going on but what caught my attention is this: Caused by: org.postgresql.util.PSQLException: FATAL: password authentication failed for user "nuxeo_default"

I checked at /usr/local/share/apache-tomcat-7.0.57/nuxeo-server/config for the password for my tenant to make sure it was correct and it was. I did notice at one point my password was entered with an extra set of quotes that I removed. Still I cannot login to my site. I've also tried the /init web call and that didn't work either.

Does anyone have any idea how I can fix this?

Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

This worked. I think the problem was that the password was being created with the quotes in it. 

On Thursday, August 11, 2016 6:25 PM, Richard Millet <richard.millet@lyrasis.org> wrote:

Well, there are a few ways you could try to fix this.  Here is one of the simplest:

0. Backup everything you don't want to lose. (It might be useful to make a copy of your tomcat folder)
1. Shutdown tomcat
2. From the top-level source directory of the "Services" layer directory, perform this command
   env | grep DB
3. You should see a list of all the CollectionSpace related database passwords.
4. Pick a new_password for the DB_NUXEO_PASSWORD environment var value and set it with this command:
   export DB_NUXEO_PASSWORD=new_password
5. If you have a script (or something like .bashrc) to set your CollectionSpace environment variables, update that to reflect the new password value you just picked.
6. Verify the password looks correct, run this command
   env | grep DB
7. Now rebuild all the CollectionSpace config files by running this command from the top-level of the "Services" directory:
   ant undeploy deploy
8. After several minutes, all the config files should be updated with your new password copied over into the correct place in the tomcat directory.

Please let us know if that works. 

From: Talk talk-bounces@lists.collectionspace.org on behalf of toolhater toolhater@yahoo.com
Sent: Thursday, August 11, 2016 4:17 PM
To: talk@lists.collectionspace.org
Subject: [Talk] db connection hosed.

Hi,

I was having problems with my Jaspersoft report working and while I was doing this I noticed that what I had in my config for the nuxeo_default password (DB_NUXEO_PASSWORD) wasn't working when I logged into through pgAdmin3, by default, I mean the one that is in the config file. So I updated the password in a SQL query to the password that is in the config file. Now I can connect through pgAdmin3 with that configuration, however when I try to login to my tenant. I can't login. I checked the log and there's a lot going on but what caught my attention is this: Caused by: org.postgresql.util.PSQLException: FATAL: password authentication failed for user "nuxeo_default"

I checked at /usr/local/share/apache-tomcat-7.0.57/nuxeo-server/config for the password for my tenant to make sure it was correct and it was. I did notice at one point my password was entered with an extra set of quotes that I removed. Still I cannot login to my site. I've also tried the /init web call and that didn't work either.

Does anyone have any idea how I can fix this?