Hi Jan,
In the GeoNode project, they make a call to the REST API to check if the
GeoNode workspace is available:
https://github.com/GeoNode/geonode/blob/3e59b936b3ce938f6b6ba4ccfb9ff3a95c068a78/docker-compose.yml#L90
Alexandre
Le ven. 17 déc. 2021 à 08:32, Jan Hoskens via Geoserver-users <
So what resource should we use if we are running the Geoserver in a
dockerized environment and need Liveness/Readiness probes to see if
everything is up and running as it should?
Kind Regards,
Jan
Op do 16 dec. 2021 om 16:39 schreef Ian Turton :
> I'd guess there is something missing from
Hi everyone,
I have a "problem" consuming a WMS service via Cascade. I'll describe
what's happening below:
GeoServer 01: is the instance where the layers are configured
GeoServer 02: is the instance where GeoServer 01 layers are being consumed
through WMS Cascade.
What happens?
Basically, when
Thanks for answering
Even inserting the path dir in the service execution file, it doesn't work.
Are there any more config files I could be looking at? - I think I've
exhausted my options...
Maurício Vieira Cardoso Filho
Gerente TI Infra
Tel: +556137995051
email : mcard...@topocart.com.br;
I'd guess there is something missing from the JSON serializer code that
skips or doesn't know about those attributes (but to be honest they are
pretty much hard coded as true in the module lookup code so I wouldn't
worry about them in general)
Ian
On Thu, 16 Dec 2021 at 15:25, Jan Hoskens via
Hi,
When using the REST api as described on
https://docs.geoserver.org/latest/en/api/#1.0.0/manifests.yaml , I expect
to see a status for each module (isAvailable/isEnabled). But I do not
receive the suggested response on the page.
I should get:
{"about": {
"status": [
{
Our official statement covers both vulnerabilities, please read:
http://geoserver.org/announcements/2021/12/13/logj4-rce-statement.html
Cheers
Andrea
On Thu, Dec 16, 2021 at 2:28 PM Ron Lindhoudt via Geoserver-users <
geoserver-users@lists.sourceforge.net> wrote:
> I understand that the
I understand that the GeoTools/Geoserver community has made a fix to address
the JMSAppender vulnerability:
log4j-1.2.17.norce.jarhttps://repo.osgeo.org/repository/geotools-releases/log4j/log4j/1.2.17.norce/log4j-1.2.17.norce.jar
But there also an older vulnerability
Hi,
please be aware that also log4j 1.x might be affected when using the
JMSAppender in the configuration!
From the log4j project website:
Log4j 1.x does not have Lookups so the risk is lower. Applications using Log4j
1.x are only vulnerable to this attack when they use JNDI in their
I am coming to this late but have you checked the tomcat.service file in
/usr/lib/systemd/system
Is there a line something like;
ReadWritePaths=/data/
for wherever your data directory is?
Russ
> On 16 Dec 2021, at 11:30, Mauricio Vieira Cardoso Filho
> wrote:
>
> Hi, A good day to all.
>
Hi, A good day to all.
Problem with connection to the bank is solved. Simply reconnected.
However, when I direct the geoserver to read the specific data directory
(/dados/geoserverv), it cannot load the data from this directory, giving an
error 404.
But if you leave the default path
11 matches
Mail list logo
