[OPEN-ILS-DEV] Errors Upgrading Evergreen 2.4.4 to 2.5.4

Wed May 21 11:09:03 EDT 2014

Thanks for the additional information Dan. Is this going to carry over when trying to upgrade to the 2.6 branch (or 2.7 etc...) as well? Seems like everyone on 2.4.4+ would be stuck needing to do a fresh install to upgrade then?

I have modified the 2.4.3-2.5.0-upgrade-db.sql script several times trying to flush out all the errors and get a clean run to proceed with the next step, but continue to have issues come up and am at a loss of where to go next (I do have VM snapshots to revert to and try again). So far where I am now is detailed below with attached log files and modified upgrade-db.sql file for reference.

After running into the initial error I commented out lines #592 & 593 and re-ran the script using the command "psql -U evergreen -f 2.4.3-2.5.0-upgrade-db.sql > /tmp/log.apply243-250_2 2>&1 &" (command provided by Galen in a previous response). The resulting file (log.apply243-250_2.rtf) is attached with an added .rtf file extension. This produced more errors in the file so next I commented out lines #12126 through #12133 re-ran script that produced the results shown in log.apply243-250_3 (also attached as an .rtf file)

After more errors, I commented out lines #12148 through #12167 re-ran the script which produced the results detailed in log.apply243-250_4.rtf

Again, more errors. This time commenting out lines #15791 through #15869 and then ran the script again producing log.apply243-250_5.rtf

After running and seeing still more errors, I commented out lines #15872 through #15961 to produce log.apply243-250_6.rtf (Screenshot of the error portion also attached).

I am stuck here, the other error messages gave an error where I could comment out that part of the script where the latest error has to deal with table modifications. I have also attached the 2.4.3-2.5.0-upgrade-db.sql file (renamed to 2.4.4-2.5.0-upgrade-db.sql) I have modified during this process.

Thanks for all the help.

Jesse McCarty
City of Burlington
IT Technical Assistant

-----Original Message-----
From: open-ils-dev-bounces at list.georgialibraries.org [mailto:open-ils-dev-bounces at list.georgialibraries.org] On Behalf Of Dan Wells
Sent: Tuesday, May 20, 2014 10:56 AM
To: Evergreen Development Discussion List
Subject: Re: [OPEN-ILS-DEV] Errors Upgrading Evergreen 2.4.4 to 2.5.4

Hello Jesse,

You want to comment everything from the failing "SELECT evergreen.upgrade_deps_block_check..." up to (but not including) the next " SELECT evergreen.upgrade_deps_block_check...".  You may need to do this several times before you find them all.

Those checks exist precisely to cause the upgrade to fail if a piece of the script has already been applied.  Commenting out only these check lines *might* work (depending on the content of that section), but is certainly not recommended.

Also, the root of this problem is that there is no supported way to upgrade from 2.4.4+ to 2.5.0.  This is a known issue with no simple fix, other than to say the 2.x maintainer needs to make a new upgrade script for every 2.(x-1) release.  I am not outright opposed to that, but up to this point nobody has argued that the benefits would justify the cost.

Thanks,
Dan

Daniel Wells
Library Programmer/Analyst
Hekman Library, Calvin College
616.526.7133

-----Original Message-----
From: open-ils-dev-bounces at list.georgialibraries.org [mailto:open-ils-dev-bounces at list.georgialibraries.org] On Behalf Of Jesse McCarty
Sent: Tuesday, May 20, 2014 11:19 AM
To: 'Evergreen Development Discussion List'
Subject: Re: [OPEN-ILS-DEV] Errors Upgrading Evergreen 2.4.4 to 2.5.4

Thanks Martha,

How much is there to comment out? Is it just the single line(s) that reads:

SELECT evergreen.upgrade_deps_block_check('0841', :eg_version); SELECT evergreen.upgrade_deps_block_check('0842', :eg_version);

Thanks again,

Jesse McCarty
City of Burlington
IT Technical Assistant

-----Original Message-----
From: open-ils-dev-bounces at list.georgialibraries.org [mailto:open-ils-dev-bounces at list.georgialibraries.org] On Behalf Of Martha Driscoll
Sent: Monday, May 19, 2014 2:30 PM
To: open-ils-dev at list.georgialibraries.org
Subject: Re: [OPEN-ILS-DEV] Errors Upgrading Evergreen 2.4.4 to 2.5.4

Jesse,
I found that upgrade scripts 0841 and 0842 which are contained in the
2.4.3-2.5.0 upgrade script were already applied in the upgrade to 2.4.4. 
  I commented out those two parts of the upgrade script.

Martha Driscoll
Systems Manager
North of Boston Library Exchange
Danvers, Massachusetts
www.noblenet.org

On 5/19/2014 1:31 PM, Jesse McCarty wrote:
> Hi,
>
>
> I am going through the process of upgrading our 2.4.4 installation of 
> Evergreen to 2.5.4. Currently running through the install on a test 
> server (which is an exact copy of our production server as it sat 
> several weeks ago, albeit with a different IP Address).
>
> After upgrading OpenSRF to 2.2.2 and the Evergreen code, I started 
> getting errors when running the update DB scripts. I started by 
> running the 2.4.3-2.5.0-upgrade-db.sql (There was no
> 2.4.4-2.5.0-upgrade-db.sql) with more errors that could fit on a 
> screen shot, then ran into additional errors on different update scripts:
>
> For 2.4.3-2.5.0-upgrade-db.sql errors see attached 243-250Error.JPG 
> (this also shows the reingest records script information, which I ran 
> after running all the DB upgrade scripts).
>
> For 2.5.0-2.5.1-upgrade-db.sql errors see attached 250-251Error.JPG
>
> No errors where reported when running the 2.5.1-2.5.2-upgrade-db.sql script.
>
> For 2.5.2-2.5.3-upgrade-db.sql errors see attached 252-253Error.JPG
>
> For 2.5.3-2.5.4-upgrade-db.sql errors see attached 253-254Error.JPG
>
>
> After starting Evergreen, I can connect via the web browser and login 
> to my account with no issues, searching the catalog produces and 
> internal server error. I can also connect to the staff client and 
> register the workstation and test/add SSL exemption with no issues.
> Once the work station is registered I get a Network error (can ping 
> the server from the workstation connecting) show in the attached 
> StaffClientError.JPG file. If I close that error the Staff Client 
> loads and then I can browse patrons and interact with the Server OK.
>
> I have a snapshot of the VM I can revert to that was taken prior to 
> any update scripts running against the DB to work through the process 
> again for further testing if needed.
>
> Thanks,
>
>
> Jesse McCarty
>
> City of Burlington
>
> IT Technical Assistant
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: log.apply243-250_2.rtf
Type: application/rtf
Size: 12977 bytes
Desc: log.apply243-250_2.rtf
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20140521/0d8f3b3d/attachment-0005.rtf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: log.apply243-250_3.rtf
Type: application/rtf
Size: 12544 bytes
Desc: log.apply243-250_3.rtf
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20140521/0d8f3b3d/attachment-0006.rtf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: log.apply243-250_4.rtf
Type: application/rtf
Size: 11146 bytes
Desc: log.apply243-250_4.rtf
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20140521/0d8f3b3d/attachment-0007.rtf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: log.apply243-250_5.rtf
Type: application/rtf
Size: 10892 bytes
Desc: log.apply243-250_5.rtf
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20140521/0d8f3b3d/attachment-0008.rtf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: log.apply243-250_6.rtf
Type: application/rtf
Size: 10480 bytes
Desc: log.apply243-250_6.rtf
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20140521/0d8f3b3d/attachment-0009.rtf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 243-250UpgradeError_6.JPG
Type: image/jpeg
Size: 51781 bytes
Desc: 243-250UpgradeError_6.JPG
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20140521/0d8f3b3d/attachment-0001.jpeg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2.4.4-2.5.0-upgrade-db.sql
Type: application/octet-stream
Size: 595016 bytes
Desc: 2.4.4-2.5.0-upgrade-db.sql
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20140521/0d8f3b3d/attachment-0001.obj>