I'm going to make a shameless plug for something that I use all the time
to generate "custom" upgrade scripts to go between arbitrary Evergreen
releases:
https://gist.github.com/Dyrcona/00bd6b6290b6fbbb579c7f93b360ab0d
The above is a shell script that can be used to make database upgrade
scripts to go from one Evergreen version to another. The code is mostly
cribbed from the script that makes the release tarballs.
It's meant to be used in an Evergreen git repository and could be used
like so to generate an upgrade script to go from 3.7.2 to 3.9.0 assuming
that you have checked out the origin/tags/rel_3_9_0 branch:
make-db-upgrade -f origin/tags/rel_3_7_2
It will put the db upgrade script in the
Open-ILS/src/sql/Pg/version-upgrade directory along side the other
existing db upgrades.
On 6/2/22 22:24, Jason Boyer via Evergreen-dev wrote:
Hi Jeff, looking at the logs in your gist the locale column doesn't
exist on the actor.usr table. This is causing the cstore call to fail
which returns a 500 error to the auth service which just returns a
generic login failure to you. This column is added in the
3.8.0-3.9.0 upgrade script which I believe failed because the
3.7.1-3.8.0 script likely also failed.
I noticed you mentioned upgrading from 3.7.2 to 3.9.0 and running the
3.7.1-3.8.0 and 3.8.0-3.9.0 scripts to perform the upgrade. Unless you
edited it, the 3.7.1-3.8.0 script will have failed because 12 of the
changes between 3.7.1 and 3.8.0 were already been applied during the
3.7.1-3.7.2 upgrade. Upgrade scripts 1266, 1268, 1269, 1270, 1272, 1273,
1279, 1282, 1283, 1294, 1302, and 1303 were already applied in the
3.7.1-3.7.2 upgrade script and are also applied in the 3.7.1-3.8.0
upgrade script. You can finish the 3.7.2-3.8.0 upgrade by manually
applying the 1260, 1267, 1271, 1274, 1275, 1276, 1277, 1278, 1280, 1281,
1284, 1285, 1286, 1287, 1288, 1289, 1290, 1291, 1292, 1293, 1295, 1296,
1297, 1298, 1299, 1300, 1301, 1304, 1305, and 1306 scripts from the
Open-ILS/src/sql/Pg/upgrade/ directory. You'll also need to define the
eg_version psql variable when applying them, like so:
psql -v "eg_version='3.8.0'" -f xxxx.....sql
Once those scripts have been applied the 3.8.0-3.9.0 script can be run
again and this time it should succeed.
What likely happened is that the 3.8.0-3.9.0 script depended on
something existing that was added in the failed 3.7.1-3.8.0 script and
when that was missing the whole upgrade script failed because it all
takes place in 1 big transaction.
Jason
On Jun 2, 2022, at 8:50 PM, Jeffrey G via Evergreen-dev
<[email protected]
<mailto:[email protected]>> wrote:
I upgraded from 3.7.2 to 3.9.0 today.
I stopped all services, followed the install instructions for 3.9.0,
then ran the 3.7.1-3.8.0-upgrade-db.sql and 3.8.0-3.9.0-upgrade-db.sql
scripts, then restarted all services.
I tried to login through srfsh, which failed, so I rebooted and tried
again; it still continues to fail with:
Received Data: {
"ilsevent":1000,
"textcode":"LOGIN_FAILED",
"desc":"User login failed",
"pid":7392,
"stacktrace":"oils_auth.c:733"
}
Web logins are failing as well.
The results from settings-tester.pl appear OK to me.
I've created a GitHub gist some more output, both .conf files, and the
log files here:
https://gist.github.com/jdgoettsch/cf20ed49ddca577564b5153a688c7983
<https://gist.github.com/jdgoettsch/cf20ed49ddca577564b5153a688c7983>
Any ideas where things went wrong? Any help is appreciated.
--
Jeff Goettsch
Agricultural and Resource Economics
530-752-2219
https://are.ucdavis.edu/ <https://are.ucdavis.edu/>
_______________________________________________
Evergreen-dev mailing list
[email protected]
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev
_______________________________________________
Evergreen-dev mailing list
[email protected]
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev
_______________________________________________
Evergreen-dev mailing list
[email protected]
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev
