[OPEN-ILS-DEV] 1.4.0.4 -> 1.6.0.3 not a smooth upgrade: not seeing copy summaries

[Dan Scott]

On Mon, 2010-03-22 at 18:06 -0500, Victoria Bush wrote:
> Dan, I did what you said, and I've written some of those notes below; however, I am not satisifed with how postgres 8.3 is installed, and I'd like to re-install it before I continue. I keep running into weird problems, and I think things are not well with postgres. 
> 
> An aside: the installation instructions for 1.4.0.4 said to install postgres 8.2 via stow, but the 1.6 and the upgrade instructions give no such help with regards to installing postgres 8.3 in such an environment. This seems to be part of my problem. I'm going to come back in tomorrow and try to do all this from scratch. 
> 
> However, if it is helpful, here is what I was able to see when I tried updating the database again from the 1.4.0.4 dump.......

<snip>

> When I try to run the 1.4.0.5-1.6.0.0 script again, these are the very first results from the script: 
> 
> > psql:Open-ILS/src/sql/Pg/1.4.0.5-1.6.0.0-upgrade-db.sql:19: ERROR:  schema "acq" does not exist
> > psql:Open-ILS/src/sql/Pg/1.4.0.5-1.6.0.0-upgrade-db.sql:20: ERROR:  schema "serial" does not exist
> > BEGIN
> > INSERT 0 1
> > psql:Open-ILS/src/sql/Pg/1.4.0.5-1.6.0.0-upgrade-db.sql:31: NOTICE:  CREATE TABLE will create implicit sequence "standing_penalty_id_seq" for serial column "standing_penalty.id"
> > psql:Open-ILS/src/sql/Pg/1.4.0.5-1.6.0.0-upgrade-db.sql:31: NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index "standing_penalty_pkey" for table "standing_penalty"
> > psql:Open-ILS/src/sql/Pg/1.4.0.5-1.6.0.0-upgrade-db.sql:31: NOTICE:  CREATE TABLE / UNIQUE will create implicit index "standing_penalty_name_key" for table "standing_penalty"
> > CREATE TABLE
> > INSERT 0 1
> > INSERT 0 1
> > INSERT 0 1
> > INSERT 0 1
> > INSERT 0 1
> > ......
> 
> 
> The rest of the messages are notices exactly as shown above: implicit sequences, indices, etc. (The two errors here are supposedly complaining about trying to delete the schemas acq and serial, which don't exist in my 1.4.0.4 data.) When I look at the database after running this script, I do see schemas acq and serial. So they exist now.

Okay, this is good.

> 
> Proceeding, I get this result when I run the script to go from 1.6.0.0 to 1.6.0.1:
> 
> > $ psql -U evergreen -h localhost -f Open-ILS/src/sql/Pg/1.6.0.0-1.6.0.1-upgrade-db.sql evergreen
> > BEGIN
> > INSERT 0 1
> > CREATE FUNCTION
> > ALTER TABLE
> > psql:Open-ILS/src/sql/Pg/1.6.0.0-1.6.0.1-upgrade-db.sql:34: NOTICE:  ALTER TABLE / ADD UNIQUE will create implicit index "penalty_grp_once" for table "grp_penalty_threshold"
> > ALTER TABLE
> > CREATE FUNCTION
> > UPDATE 1
> > COMMIT
> > psql:Open-ILS/src/sql/Pg/1.6.0.0-1.6.0.1-upgrade-db.sql:101: ERROR:  duplicate key violates unique constraint "i18n_locale_name_key"
> > INSERT 0 1
> > CREATE RULE
> > INSERT 0 1
>  
> No errors were generated when upgrading to 1.6.0.2 or 1.6.0.3. 

This is also good.

> Now, if I restart everything and run autogen.sh (which takes a few minutes to run completely), I get something odd: 
> 
> > $ ./autogen.sh -c /openils/conf/opensrf_core.xml -u
> > Updating Evergreen organization tree and IDL using '/openils/conf/opensrf_core.xml'
> > 
> > Updating fieldmapper
> > Updating web_fieldmapper
> > Updating OrgTree
> > Updating OrgTree HTML
> > Updating locales selection HTML
> > Updating Search Groups
> > Can't use an undefined value as an ARRAY reference at org_lasso_js.pl line 30.

This is bad. It's resulting in the JavaScript error "_lasso is not
defined" because OrgLasso.js is empty, and that kills any further
execution of a given OPAC page.

Can you try changing line 30 of /openils/bin/org_lasso_js.pl from:

if (scalar(@$lassos) > 0) {

to:

if ($lassos && scalar(@$lassos) > 0) {

... that should protect against a null response from the list of
actor.org_unit lassos (search groups). Then re-run autogen.sh.

Also, I see the osrf-http-translator request for
open-ils.fielder.i18n_l.atomic timing out with an empty response after
60 seconds. That's a problem. Do you see anything in the logs (either
PostgreSQL or osrfsys.log) about config.i18n_locale? Does that table
have any data?

Actually, switching to your basic catalog, it looks rather like the
connection to your database is wrong or doesn't exist. Can you
double-check the database settings in opensrf.xml to ensure that they
all point to the correct database?