...
[15:36:32 CST(-0600)] <dmccallum54> so if you run 'psql -U sspadmin -d ssp', assuming 'ssp' is the name of your db and it's running locally, does it prompt for a password?
[15:38:34 CST(-0600)] <gear__> no, I had to use -W to put in a password
[15:38:46 CST(-0600)] <dmccallum54> but that did work?
[15:40:14 CST(-0600)] <gear__> no, I'm sorry to say it did not
[15:45:29 CST(-0600)] <dmccallum54> creating logins from command line or pgadmin?
[15:45:42 CST(-0600)] <gear__> command line
[15:45:50 CST(-0600)] <gear__> technically salt
[15:46:23 CST(-0600)] <dmccallum54> 'createuser' command or SQL?
[15:46:58 CST(-0600)] <gear__> I'll have to circle back with them to know for sure
[15:47:08 CST(-0600)] <dmccallum54> k
[15:47:19 CST(-0600)] <gear__> but no worries, if you are simply curious if it is created right or not, I can track that down
[15:48:02 CST(-0600)] <dmccallum54> well. guessing either the password was miscommunicated or the user doesn't have rights on the ssp db
[15:48:03 CST(-0600)] <gear__> but one question, are you sure you haven't had to add permissions to the postgres.conf ?
[15:49:00 CST(-0600)] <dmccallum54> you might on a linux install. seeing if i can track that down.
[15:49:24 CST(-0600)] <dmccallum54> on OSX i usually just connect as a super user and create the db specifying sspadmin as the owner
[15:51:16 CST(-0600)] <dmccallum54> doesnt look like our linux installs do anything special in postgres.conf other than specify a listen_address
[15:51:25 CST(-0600)] <dmccallum54> then they do this...
[15:51:33 CST(-0600)] <dmccallum54> psql -d template1 -U postgres
[15:51:45 CST(-0600)] <dmccallum54> CREATE DATABASE uportal;
[15:51:45 CST(-0600)] <dmccallum54> CREATE USER ssp WITH PASSWORD 'ssp';
[15:51:45 CST(-0600)] <dmccallum54> CREATE USER sspadmin WITH PASSWORD 'sspadmin';
[15:51:45 CST(-0600)] <dmccallum54> GRANT ALL PRIVILEGES ON DATABASE uportal to sspadmin;
[15:51:45 CST(-0600)] <dmccallum54> GRANT ALL PRIVILEGES ON DATABASE uportal to ssp;
[15:52:02 CST(-0600)] <dmccallum54> all the actual names and passwords are implementation details, of course
[15:54:10 CST(-0600)] <dmccallum54> is pg on the same box?
[15:54:47 CST(-0600)] <gear__> yes
[15:56:21 CST(-0600)] <gear__> interesting, isn't the database named ssp?
[15:56:29 CST(-0600)] <dmccallum54> that's up to you
[15:57:07 CST(-0600)] <gear__> Yes,
[15:57:13 CST(-0600)] <gear__> I'm just double checking the documentation
[15:57:41 CST(-0600)] <dmccallum54> might check pg_hba.conf to see if password auth is enabled for 'host' connections
[16:03:12 CST(-0600)] <gear__> host all all 127.0.0.1/32 ident
[16:03:16 CST(-0600)] <gear__> hmmm, that should cover it
[16:06:23 CST(-0600)] <gear__> I changed all the ident to password, and it logs in now, trying the compile again
[16:06:39 CST(-0600)] <dmccallum54> great
[16:27:05 CST(-0600)] <gear__> thank you very much, I now have it working from start to finish
[16:27:19 CST(-0600)] <dmccallum54> awesome
[16:28:01 CST(-0600)] <gear__> just note that centos users might need to add "local ssp sspadmin password" to their pg_hba.conf
[16:28:15 CST(-0600)] <dmccallum54> i will update the docs
[16:29:14 CST(-0600)] <dmccallum54> looking at our linux install notes...
[16:29:21 CST(-0600)] <dmccallum54> looks like this is what we usually stick in there...
[16:29:37 CST(-0600)] <dmccallum54> # "local" is for Unix domain socket connections only
[16:29:37 CST(-0600)] <dmccallum54> local all all trust
[16:29:37 CST(-0600)] <dmccallum54> host all all 0.0.0.0 0.0.0.0 password
[16:29:37 CST(-0600)] <dmccallum54> # IPv4-style local connections:
[16:29:37 CST(-0600)] <dmccallum54> host all all 127.0.0.1 255.255.255.255 trust
[16:29:37 CST(-0600)] <dmccallum54> # IPv6-style local connections:
[16:29:38 CST(-0600)] <dmccallum54> host all all ::1 ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff trust
[16:29:59 CST(-0600)] <dmccallum54> key thing, i think was the swicth from 'ident' to 'password' tho