shibd hangs partway through startup - no visible errors

[Scott, Benjamin]

Just to close the loop on this, I used strace to confirm that the listener was successfully starting, then found that there was an openshift network policy within the shibd namespace that was blocking connections from the other applications. I removed that and everything is starting and connecting correctly. Thank you again for your help.

Ben

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

> Any idea why the logs would be buffered/not flushed until I kill shibd?

I don't believe that's happening, so no. I think it probably is hung up somewhere and killing it frees it up to finish starting up and then it notices the shutdown signal queued up and stops.

> Those delayed log lines indicate that the listener is starting

That would be very surprising to me. Check the port state (or I guess the socket path if it's a domain socket) if you really want to. If it's open/present, ok. If it's not, then it's not.

If the issue is reproducible based on a specific attribute map that isn't also used somewhere that isn't hanging then I would file a bug. If not, it's environmental and the only way I know to learn anything else is strace or gdb.

-- 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