shibboleth samld process going down with open SAML v 3.3.1

[Kannan, Satheesh (ELS-CON)]

Hi,

We have recently migrated to open SAML v 3.3.1. seeing intermittent down time with shibd port going down.
Could you please suggest finding cause of shibd going down with amazon Linux2.
Even, This sandbox environment doesn't receive any traffic as well.

Seeing couple of WARN and cRIT erros  from OpenSAML.MetadataProvider module.
It could be any reason open saml module error contribute to shibd port going down.


15:38:59.094(06/02) WARN  Shibboleth.DEPRECATION : MetadataGenerator handler

15:38:59.085(06/02) CRIT  OpenSAML.MetadataProvider.Chaining : failure initializing MetadataProvider: Metadata instance was invalid at time of acquisition.


I noticed below warn/CRIT  messages in shar.log file

15:38:40.351(06/02) ERROR OpenSAML.MetadataProvider.XML : error while loading resource (http://shibcontent.com/htdocs/ federation-metadata.xml): XML er
ror(s) during parsing, check log for specifics
15:38:40.353(06/02) WARN  OpenSAML.MetadataProvider.XML : adjusted reload interval to 600 seconds
15:38:40.353(06/02) WARN  OpenSAML.MetadataProvider.XML : trying backup file, exception loading remote resource: XML error(s) during parsing, check log for specifics
15:38:40.353(06/02) INFO  OpenSAML.MetadataProvider.XML : using local backup of remote resource
15:38:40.361(06/02) INFO  OpenSAML.MetadataProvider.XML : loaded XML resource (/elsnfs/shibUpdate/feds/matadata.xml)
15:38:40.361(06/02) DEBUG OpenSAML.MetadataProvider.XML : reload thread started...running every 600 seconds
15:38:40.362(06/02) CRIT  OpenSAML.MetadataProvider.Chaining : failure initializing MetadataProvider: Invalid child element: md:AttributeService
15:38:40.362(06/02) DEBUG OpenSAML.MetadataProvider.XML : loading configuration from external resource...
15:38:40.364(06/02) INFO  OpenSAML.MetadataProvider.XML : loaded XML resource (/elsnfs/shibUpdate/feds/CERTNX_IDP3/idp-metadata.xml)
15:38:40.365(06/02) DEBUG OpenSAML.MetadataProvider.XML : remote metadata resource will be backed up to (/elsnfs/shibUpdate/feds/urn_mace_incommon/InCommon-metadata-idp-only.xml.0
a3d)
15:38:40.365(06/02) DEBUG OpenSAML.MetadataProvider.XML : loading configuration from external resource...
15:38:40.365(06/02) DEBUG OpenSAML.MetadataProvider.XML : reload thread started...running when signaled
15:38:40.365(06/02) DEBUG OpenSAML.MetadataProvider.XML : writing to backing file: /elsnfs/shibUpdate/feds/urn_mace_metadata-idp-only.xml.0a3d
15:38:45.320(06/02) INFO  OpenSAML.MetadataProvider.XML : loaded XML resource (http://www.test.com/metadata-idp-only.xml)
15:38:50.231(06/02) ERROR OpenSAML.MetadataProvider.XML : metadata instance was invalid at time of acquisition
15:38:51.301(06/02) WARN  OpenSAML.MetadataProvider.XML : adjusted reload interval to 600 seconds
15:38:51.301(06/02) WARN  OpenSAML.MetadataProvider.XML : trying backup file, exception loading remote resource: Metadata instance was invalid at time of acquisition.
15:38:51.301(06/02) INFO  OpenSAML.MetadataProvider.XML : using local backup of remote resource
15:38:53.455(06/02) INFO  OpenSAML.MetadataProvider.XML : loaded XML resource (/elsnfs/shibUpdate/feds/ss-metadata-idp-only.xml)
15:38:58.137(06/02) ERROR OpenSAML.MetadataProvider.XML : metadata instance was invalid at time of acquisition
15:38:59.085(06/02) DEBUG OpenSAML.MetadataProvider.XML : reload thread started...running every 600 seconds

15:38:59.085(06/02) CRIT  OpenSAML.MetadataProvider.Chaining : failure initializing MetadataProvider: Metadata instance was invalid at time of acquisition.
15:38:59.094(06/02) WARN  Shibboleth.DEPRECATION : MetadataGenerator handler
15:38:59.096(06/02) INFO  Shibboleth.Listener : listener service starting
15:39:26.530(06/02) INFO  Shibboleth.Listener : detected socket closure, shutting down worker thread
15:39:26.537(06/02) INFO  Shibboleth.Listener : detected socket closure, shutting down worker thread
15:39:26.556(06/02) INFO  Shibboleth.Listener : detected socket closure, shutting down worker thread
15:39:56.540(06/02) INFO  Shibboleth.Listener : detected socket closure, shutting down worker thread

Regards,
Satheesh

________________________________

Elsevier B.V. Registered Office: Radarweg 29, 1043 NX Amsterdam, The Netherlands, Registration No. 33158992, Registered in The Netherlands.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20250602/b3c1fd6f/attachment.htm>