issue starting up IdP after server crash
Michael A Weyandt
maw120 at zips.uakron.edu
Wed Oct 11 11:28:05 EDT 2017
Ended up finding out what was wrong once I started looking into the fail fast, and took a look at the metadata I had. Turns out most of the http backed metadata was half filled in due to the storage issues I had earlier. So after clearing those, and restarting the IdP it fetched the full versions.
Thanks for the help.
On Oct 11, 2017, 10:52 AM -0400, Cantor, Scott <cantor.2 at osu.edu>, wrote:
> > So far I’ve rolled back the changes that were made on the 4th with no luck. Not sure where to look next.
> Well, it's telling you there's a metadata source that's broken, but if it's not logging which one (that seems odd) you'd have to check them all. The fundamental issue is you left the metadata fail-fast, which is your decision, but getting it to start up isn't going to make the systems in the failing metadata source work. Some people prefer "everything or nothing works" and some don't, which is why the fail-fast behavior is up to the deployer.
> -- Scott
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users