shibd hangs partway through startup - no visible errors

[Scott, Benjamin]

Hi Scott, thanks for the quick response. I dug around a bit more and found something interesting. when I start the shibd container, the last log entry it provides is the final attribute from the attribute map, e.g

2019-01-16 15:28:55 INFO Shibboleth.AttributeExtractor.XML : creating mapping for Attribute urn:oasis:names:tc:SAML:2.0:nameid-format:persistent

and I get no more logging or events. However, when I get a shell into the container running shibd and issue a "kill" command to the shibd process, it generates more log lines that are timestamped from the last log line, but don't show up in the logs until I kill shibd:

2019-01-16 15:28:55 INFO Shibboleth.Application : building AttributeFilter of type XML...
2019-01-16 15:28:55 INFO Shibboleth.AttributeFilter : loaded XML resource (/etc/shibboleth/attribute-policy.xml)
2019-01-16 15:28:55 INFO Shibboleth.Application : building AttributeResolver of type Query...
2019-01-16 15:28:55 INFO Shibboleth.Application : building CredentialResolver of type File...
2019-01-16 15:28:55 INFO XMLTooling.SecurityHelper : loading private key from file (/opt/app-root/etc/shibboleth/redacted.key)
2019-01-16 15:28:55 INFO XMLTooling.SecurityHelper : loading certificate(s) from file (/opt/app-root/etc/shibboleth/redacted.crt)
2019-01-16 15:28:55 INFO Shibboleth.Listener : listener service starting

and then log lines indicating it is shutting down (note the gap in time):

2019-01-16 19:17:46 INFO Shibboleth.Listener : listener service shutting down
2019-01-16 19:17:46 INFO Shibboleth.Config : shibboleth 3.0.3 library shutting down
2019-01-16 19:17:46 INFO XMLTooling.StorageService : cleanup thread finished
2019-01-16 19:17:46 INFO XMLTooling.Config : xmltooling 3.0.3 library shutdown complete

Any idea why the logs would be buffered/not flushed until I kill shibd? Those delayed log lines indicate that the listener is starting but I am still unable to connect to the listener. Thanks again for your thoughts.

Ben
________________________________________
From: users <users-bounces at shibboleth.net> on behalf of Cantor, Scott <cantor.2 at osu.edu>
Sent: Wednesday, January 16, 2019 9:45 AM
To: Shib Users
Subject: Re: shibd hangs partway through startup - no visible errors

Whatever it is is environmental, but strace is usually a good way to tell what something's doing if it's hung on a system call and then it's on to gdb and debugging it outright.

Offhand, the most typical "this makes no sense" explanation on RHEL is always SELinux.

-- Scott


--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net