Thank you for your excellent assistance, Francois!
Today I was able to try the upgrade, and followed that with your two recommended Calls to cleanup the JS cache. GeoNetwork took a minute or so to respond, which I guess because it was busy, but then everything loaded and ran fine. I did not need to use the "?debug" suffix.
The minor error message I reported when manually migrating the database was because there is no "editable" column in the settings database table when manually migrating at the v407 step; the column appears later when GeoNetwork is run. When the migration is done automatically, it probably works slightly differently.
I find the new splash screen quite inviting. The searches seem much faster - and entering even a few characters in a word reveals relevant records. The team has done a great job with this release, IMHO.
-- terry
-------- Forwarded Message --------
Subject: Re: [GeoNetwork-users] Problem updating from GN4.0.6 to GN4.2.2
Date: Thu, 4 May 2023 07:56:53 +0200
From: Francois Prunayre <fx.prunayre@anonymised.com>
To: Terry <terry.curran@anonymised.com>
Indeed, no issue in the log. SQL migration sounds to have completed successfully (version was updated in settings table).
H2 databases are only used for caches.
I would try to startup. Call
http://domain.org/geonetwork/static/wroAPI/reloadModel
http://domain.org/geonetwork/static/wroAPI/reloadCache
to force a cleanup of JS cache
and then load the home page and check any error in the log.
To increase log level, you can update the settings and change log4j2.xml by log4j2-dev.xml
HTH
Francois
Le mer. 3 mai 2023 à 20:10, Terry <terry.curran@anonymised.com> a écrit :
<!-- SNIP -->
On 2023-05-02 11:28 p.m., Francois Prunayre wrote:
Hi Terry,
I would
* check the following in the settings table
UPDATE Settings SET editable = 'y' WHERE editable IS NULL;
to be sure that the value is properly set and there is no null
(which should not be possible).* About H2, check
https://geonetwork-opensource.org/manuals/4.0.x/en/overview/change-log/version-4.2.0.html#migration-instructions* Any errors in the logs ?
Cheers.
FrancoisLe mer. 3 mai 2023 à 05:37, Terry via GeoNetwork-users
<geonetwork-users@lists.sourceforge.net> a écrit :We are trying to avoid a full metadata dump and reload.
We have a RHEL8 VM with an Apache Reverse Proxy ahead of a Jetty
webserver hosting GN4.0.6, GS and ERDDAP.We also have a PostGIS
database, and a remote gn_dir.Startup and linkages are by a Jetty
daemon.Everything seemed to be working for more than a year.To upgrade to GN4.2.2, as usual we downloaded the war,
unzipped it, and
made changes to three files: config-node/srv.xml to point
exclusively at
config-db/jndi.xml, jetty-environment.xml to contain the database
credentials (name, port, user, pw, and gnDatabaseDialect [to
POSTGRESQL]) and config-db/jndi.xml to contain the usual PostGIS
parameters.On some attempts we also set the jdbc.properties to
the same,
but usually just kept the defaults.Upon reboot with the modified GN, the database got migrated to
4.2.2,
with two we think insignificant errors from v407 migration:gndb422=# UPDATE Settings SET editable = 'n' WHERE name =
'system/userFeedback/lastNotificationDate';
ERROR: column "editable" of relation "settings" does not exist
LINE 1: UPDATE Settings SET editable = 'n' WHERE name =
'system/user...
^
gndb422=# UPDATE Settings SET editable = 'n' WHERE name =
'system/security/passwordEnforcement/pattern';
ERROR: column "editable" of relation "settings" does not exist
LINE 1: UPDATE Settings SET editable = 'n' WHERE name =
'system/secu...We got the title on the GN splash screen from the settings, but
otherwise blank screen.We noticed the log had many h2 errors
regarding
the gn-wro4j disk-cache, and related h2 errors, but also said
that
geonetwork was available.Stopped jetty, deleted the
wro4j-cache.mv.db in
remote gn_dir folder, because we knew it would get rebuilt on
restart.Rebooted computer and thus jetty, and no "gn-wro4j disk-cache"
errors.
Got the same header and blank screen.However, appending
“?debug” allowed
login and we could then see the data.Cleared the “JS & CSS
cache” and
rebooted.Things looked okay.Tried reindexing and got a 502 Proxy
Error.Metadata could no longer be seen.Any thoughts about next step, and/or what we are doing wrong?
Terry
Pacific Salmon Foundation
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork