No MetadataProvider available
John Westwood
john.westwood at port.ac.uk
Thu Jun 6 10:01:44 EDT 2013
Thanks for all the help. Simply restarting Shibboleth fixed the problem. I
guess the network was awry when Shibboleth was originally restarted after
the hardware fault. I should have tried that first, since it is the number
one way to fix things on a computer!
On 5 June 2013 17:22, Cantor, Scott <cantor.2 at osu.edu> wrote:
> On 6/5/13 10:18 AM, "John Westwood" <john.westwood at port.ac.uk> wrote:
> >
> >We are running Shibboleth SP 2.4.3 in SLES 11 . Shibboleth was working
> >fine until we had a hardware fault. This was fixed and the server was
> >restarted, but now when trying to authenticate the following error occurs:
>
> The reason is that you're on an out of date version, and you were bitten
> by a bug. The SLES system sweeps /var/run between reboots, so your backup
> metadata got thrown away. You've most likely been using it for a while and
> it's not been connecting for new metadata. Once the backup was lost, it
> failed. If you have an unusual network environment with a proxy, you
> really need to either monitor logs for errors, or consider not using a
> backup file, since that will just hide the problem from you.
>
> The supported version, 2.5, uses /var/cache to store off the metadata
> files so that they don't get swept away across reboots.
>
> Of course, I can't speak to why your network problem exists. Perhaps they
> moved the proxy or something.
>
> -- Scott
>
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20130606/8c0c465e/attachment.html
More information about the users
mailing list