Re: [Geoserver-users] Lost ability to serve WMS

[Terry C. <tc...@ps...>]

Don't exactly know what I did, but GS is working again.
In the log I found and corrected some obsolete http: references that were throwing errors. I found I had omitted the netCDF input module during an update. I don't think any of this was the root problem, and I must have done something else.

Eventually I rebooted the server (I had done this many times previously), and things seem fine and the log is quiet.

-- terry


Date: Mon, 13 May 2024 23:56:56 -0700
From: Terry Curran<tc...@ps...>
To:geo...@li...
Subject: [Geoserver-users] Lost ability to serve WMS
Message-ID:<c31...@ps...>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

We have RHEL8 server, Jetty webserver and GeoServer v2.22.4. There is an
Apache proxy.? We have the data folder external to the GeoServer
application.? It has been running through various upgrades for many
years.? Until recently, GeoNetwork has restricted upgrades to Java8
compatibility (hence GS v2.22.4).

I think a month or so ago, I did something to the setup (cannot recall
what).? All layers continued to work with Open Layers, which is how I
normally check operation.? Very recently, it was brought to my attention
that WMS and WMTS could not be accessed via GIS applications. However
WFS and WCS layers are accessible.

Using the WMS GetCapabilities query in the GeoServer Demo package, I get
a timeout after a minute or so, and the message "This XML file does not
appear to have any style information associated with it. The document
tree is shown below" (file attached - looks okay to me).

The default data folder is still with the GeoServer installation and, if
I point at it, the WMS requests are accessible via GIS systems,
suggesting the GS installation is fine - there is something wrong with
our external data store.? File permissions and ownership are the same as
the default data store.

I have tried augmenting the default data store with
workspace/store/styles from our external store, but get error messages.

If all else fails, is there a way of rescuing the
workspace/store/250+layers/style information?? Or is there something
simple that fixes our problem?

Terry Curran

Pacific Salmon Foundation