<div dir="ltr">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!<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 5 June 2013 17:22, Cantor, Scott <span dir="ltr"><<a href="mailto:cantor.2@osu.edu" target="_blank">cantor.2@osu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 6/5/13 10:18 AM, "John Westwood" <<a href="mailto:john.westwood@port.ac.uk">john.westwood@port.ac.uk</a>> wrote:<br>
><br>
>We are running Shibboleth SP 2.4.3 in SLES 11 . Shibboleth was working<br>
>fine until we had a hardware fault. This was fixed and the server was<br>
>restarted, but now when trying to authenticate the following error occurs:<br>
<br>
</div>The reason is that you're on an out of date version, and you were bitten<br>
by a bug. The SLES system sweeps /var/run between reboots, so your backup<br>
metadata got thrown away. You've most likely been using it for a while and<br>
it's not been connecting for new metadata. Once the backup was lost, it<br>
failed. If you have an unusual network environment with a proxy, you<br>
really need to either monitor logs for errors, or consider not using a<br>
backup file, since that will just hide the problem from you.<br>
<br>
The supported version, 2.5, uses /var/cache to store off the metadata<br>
files so that they don't get swept away across reboots.<br>
<br>
Of course, I can't speak to why your network problem exists. Perhaps they<br>
moved the proxy or something.<br>
<span class="HOEnZb"><font color="#888888"><br>
-- Scott<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
--<br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a><br>
</div></div></blockquote></div><br></div>