jasig-ssp IRC Logs-2013-11-15

[10:32:11 CST(-0600)] <gear__> Hello ...

[10:32:38 CST(-0600)] <gear__> I'm having an issue with the "ant initPortal" during the install

[10:33:18 CST(-0600)] <dmccallum54> care to post a gist of the full error?

[10:33:24 CST(-0600)] <gear__> I'm following the instructions and version found here https://wiki.jasig.org/display/SSP/SSP+v2.0.1+Installation+Instructions

[10:33:36 CST(-0600)] <gear__> using the zip file found there too

[10:33:48 CST(-0600)] <gear__> here's the gist of the error message..

[10:36:37 CST(-0600)]

[10:37:22 CST(-0600)] <gear__> this is happening in the 'resource [properties/contexts/jsonRenderingPipelineContext.xml]'

[10:38:19 CST(-0600)] <gear__> now, I'm a novice at SSP and uPortal, granted...

[10:38:42 CST(-0600)] <gear__> I did try to add buildNumber=0 to a few properties and filter files hoping that would help, but it did not

[10:39:44 CST(-0600)] <dmccallum54> this is usually caused by git not being on your path

[10:39:53 CST(-0600)] <dmccallum54> but let me check that zip to see if that would even help. one sec.

[10:41:04 CST(-0600)] <gear__> FWIW, git is installed and available in the path (verified by 'which git')

[10:41:10 CST(-0600)] <dmccallum54> looks like it won't help.

[10:41:29 CST(-0600)] <dmccallum54> let me figure out a workaround. one (more) sec.

[10:41:35 CST(-0600)] <gear__> many thanks

[11:00:50 CST(-0600)] <dmccallum54> ok. so there should be a way to do this from the command line without editing source files, but it doesn't seem to be working. so there are at least two other options...

[11:01:17 CST(-0600)] <dmccallum54> in the exploded zip edit: ./uportal-war/src/main/resources/properties/portal.properties

[11:01:21 CST(-0600)] <dmccallum54> and replace this line:

[11:01:33 CST(-0600)]

[11:01:33 CST(-0600)] <dmccallum54> with:

[11:01:38 CST(-0600)] <dmccallum54> org.jasig.portal.scmRevision=ssp-platform-1.2.1-release

[11:03:28 CST(-0600)] <dmccallum54> the other option is to find the buildnumber-maven-plugin definitions in ./uportal-war/pom.xml and ./uportal-portlets-overlay/pom.xml and add this below the <executions> element:

[11:03:43 CST(-0600)] <dmccallum54> <configuration>

[11:03:43 CST(-0600)] <dmccallum54> <revisionOnScmFailure>ssp-platform-1.2.1-release</revisionOnScmFailure>

[11:03:43 CST(-0600)] <dmccallum54> </configuration>

[11:06:14 CST(-0600)] <gear__> I think the first works better for our purposes, let me give that a try first...

[11:19:49 CST(-0600)] <dmccallum54> i've updated the installation instructions and opened a ticket to get this fixed

[11:21:12 CST(-0600)] <dmccallum54> https://issues.jasig.org/browse/SSP-1909

[14:51:15 CST(-0600)] <gear__> Hello again

[14:51:22 CST(-0600)] <gear__> thanks again for your help this morning

[14:51:54 CST(-0600)] <gear__> I've run into another issue during the 'ant initPortal' command...

[14:52:29 CST(-0600)] <gear__> essentially the error is 'unable to build entitymanagerfactory'

[14:52:41 CST(-0600)] <gear__> it is a pretty long stacktrace

[14:54:13 CST(-0600)] <dmccallum54> post it to gist.github.com

[15:10:36 CST(-0600)] <gear__> https://gist.github.com/anonymous/7491684

[15:12:05 CST(-0600)] <dmccallum54> this is usually caused by one of two things… some sort of db coordinates misconfiguration in ./filters/<env>.properties or an incorrect jdbc driver dependency in ./pom.xml

[15:12:18 CST(-0600)] <dmccallum54> what sort of database are you trying to connect to

[15:12:24 CST(-0600)] <gear__> postgres

[15:12:45 CST(-0600)] <gear__> 8.4

[15:13:51 CST(-0600)] <dmccallum54> ok. so i assume you did not change any of these properties in ./pom.xml?

[15:13:58 CST(-0600)] <dmccallum54> <!-- The JDBC Driver used by SSP -->

[15:13:58 CST(-0600)] <dmccallum54> <jdbc.groupId>postgresql</jdbc.groupId>

[15:13:58 CST(-0600)] <dmccallum54> <jdbc.artifactId>postgresql</jdbc.artifactId>

[15:13:58 CST(-0600)]

[15:15:43 CST(-0600)] <dmccallum54> ah

[15:15:47 CST(-0600)] <dmccallum54> here it is actually...

[15:15:59 CST(-0600)] <dmccallum54> [java] ... 17 more

[15:15:59 CST(-0600)] <dmccallum54> [java] CaWARN [55:22.603] HHH000342: Could not obtain connection to query metadata : FATAL: Ident authentication failed for user "sspadmused by: org.springframework.beans.factory.BeanCr

[15:18:45 CST(-0600)] <dmccallum54> to see what db coordinates have been included in the deployment, look in <tomcat>/webapps/ssp-platform//WEB-INF/classes/properties/rdbm.properties

[15:19:23 CST(-0600)] <dmccallum54> whatever's in there should be traceable back to <src>/filters/<env>.properties

[15:19:36 CST(-0600)] <gear__> hmm

[15:19:56 CST(-0600)] <gear__> that is interesting...

[15:20:38 CST(-0600)] <gear__> shouldn't that be sspadmin ?

[15:21:19 CST(-0600)] <gear__> I'll try to track that down

[15:25:07 CST(-0600)] <dmccallum54> looks like there might be some interleaved log messages there. if the deployed copy of rdbm.properties looks OK w/r/t the actual db username/s that appear there, the next step is probably to make sure those users can actually log in to the db

[15:25:21 CST(-0600)] <dmccallum54> e.g. with psql or SQuirreL or some other external tool

[15:32:48 CST(-0600)] <gear__> yes, all the rdbm properties look goo

[15:32:58 CST(-0600)] <gear__> and no, psql doesn't log in

[15:33:09 CST(-0600)] <gear__> but the password is set right

[15:34:22 CST(-0600)] <gear__> hmmm, it does ask for 9.1 or later, I should try to make sure I have that installed first

[15:34:52 CST(-0600)] <dmccallum54> i doubt that's the cause of the failed login, but yes, you should expect fewer surprises in general with 9.x

[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