Dear all,
The log file of our Geoserver is currently flooding with warnings of type
WARN [wms.capabilities] - Error writing metadata; skipping layer: finnsmia_absoluteValue
java.lang.RuntimeException: Error while committing XML elements; specific element was: Start(Layer, org.xml.sax.helpers.AttributesImpl@anonymised.com)
at org.geotools.xml.transform.TransformerBase$TranslatorSupport.commit(TransformerBase.java:697)
at org.geoserver.wms.capabilities.Capabilities_1_3_0_Transformer$Capabilities_1_3_0_Translator.doHandleLayer(Capabilities_1_3_0_Transformer.java:937)
. . .
Near the end of the long error message there is a line
Caused by: java.io.IOException: Broken pipe
which makes me wonder, if this is an issue with insufficient rights in some folder or something. Where exactly is Geoserver trying to write something in this case? I did try to look at the code a bit, but it didn’t seem clear.
Some details: We use daily updating image mosaics with time dimension. The catalog for the rasters is in a PostgreSQL database and we use a JNDI-connection with SELECT-rights. It seems to me that the capabilities file on the WMS interface (by GetCapabilities-request) is up-to-date and contains the correct TIME-dimension values, so whatever this problem is, it doesn’t affect the service itself a whole lot.
Thanks for any tips,
Sam
If you turn logging up to developer you should see the underlying exception, it could be permissions or a bad XML name for a layer possibly.
Ian
···
Ian Turton
Have a look at the log file for your app container eg Tomcat or similar and check if there is a broken pipe message there.
I run Geoserver in Tomcat and occasionally have a problem where Tomcat reports a broken pipe
···
From: Neuvonen Samuli samuli.neuvonen@anonymised.com
Sent: Thursday, 17 February 2022 1:24 AM
To: geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] Error writing metadata / Capabilities_1_3_0_Transformer.java
Dear all,
The log file of our Geoserver is currently flooding with warnings of type
WARN [wms.capabilities] - Error writing metadata; skipping layer: finnsmia_absoluteValue
java.lang.RuntimeException: Error while committing XML elements; specific element was: Start(Layer, org.xml.sax.helpers.AttributesImpl@anonymised.com)
at org.geotools.xml.transform.TransformerBase$TranslatorSupport.commit(TransformerBase.java:697)
at org.geoserver.wms.capabilities.Capabilities_1_3_0_Transformer$Capabilities_1_3_0_Translator.doHandleLayer(Capabilities_1_3_0_Transformer.java:937)
. . .
Near the end of the long error message there is a line
Caused by: java.io.IOException: Broken pipe
which makes me wonder, if this is an issue with insufficient rights in some folder or something. Where exactly is Geoserver trying to write something in this case? I did try to look at the code a bit, but it didn’t seem clear.
Some details: We use daily updating image mosaics with time dimension. The catalog for the rasters is in a PostgreSQL database and we use a JNDI-connection with SELECT-rights. It seems to me that the capabilities file on the WMS interface (by GetCapabilities-request) is up-to-date and contains the correct TIME-dimension values, so whatever this problem is, it doesn’t affect the service itself a whole lot.
Thanks for any tips,
Sam
A broken pipe normally just means the client decided to shut the HTTP connection
in GeoServer’s face before it could complete sending the response over.
Nothing to worry about.
Cheers
Andrea
···
Regards,
Andrea Aime
==
GeoServer Professional Services from the experts!
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions Group
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928
https://www.geosolutionsgroup.com/
http://twitter.com/geosolutions_it
Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail
Dear list,
We are using an external Geofence-installation to handle authorization of requests to GeoServer. However, we are unable to create users that have admin rights to only certain workspaces: whenever a user is set as admin in Geofence, it gets full admin rights to GeoServer, regardless of any other rules set in Geofence or GeoServer. Users given limited admin rights (i.e. admin rights to some workspace) only in GeoServer web UI (and not Geofence) do not get any (admin) access.
A similar use case was mentioned in at least two messages
https://sourceforge.net/p/geoserver/mailman/message/37125364
https://sourceforge.net/p/geoserver/mailman/message/37045161/
but with no replies. Should I interpret this so that no solution exists? Or that it is so obvious that no-one can be bothered to reply?
We have a solution with a cluster of “worker GeoServers” and a “chief GeoServer” intended to be used only for administration and not accessible from the internet. Would it be possible to remove GeoFence from the chief and manage the admin users and workspaces from there? Or would that somehow corrupt the data directory which is common to all the GeoServer instances or something?
Many thanks for any help,
Samuli Neuvonen