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.neuvo...@syke.fi> 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@43a3c239<mailto:org.xml.sax.helpers.AttributesImpl@43a3c239>) 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 ________________________________ CONFIDENTIALITY NOTICE AND DISCLAIMER The information in this transmission may be confidential and/or protected by legal professional privilege, and is intended only for the person or persons to whom it is addressed. If you are not such a person, you are warned that any disclosure, copying or dissemination of the information is unauthorised. If you have received the transmission in error, please immediately contact this office by telephone, fax or email, to inform us of the error and to enable arrangements to be made for the destruction of the transmission, or its return at our cost. No liability is accepted for any unauthorised use of the information contained in this transmission.
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
