Hi,<div><br></div><div>By upgrading to liblog4shib1-1.0.4, it has resolved the issue.</div><div><br></div><div>We will not have to open an issue in Jira after all.</div><div><br></div><div>Thanks for your help</div><div><br>
</div><div>Yannick<br><br><div class="gmail_quote">On Tue, Jul 10, 2012 at 8:12 AM, Yannick Béot <span dir="ltr"><<a href="mailto:yannick.beot@gmail.com" target="_blank">yannick.beot@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<div><br></div><div>Indeed, by putting a
ERROR level in shibd.logger, the LogoutRequest is correctly decoded and I get an "expiration" error.<div>I'm using log4shib-1.0.3-2.1.<br><br>Nothing fancy in the dependencies:</div><div><div><font face="courier new, monospace"># rpm -qR log4shib-1.0.3-2.1</font></div>
<div><font face="courier new, monospace">/sbin/ldconfig</font></div><div><font face="courier new, monospace">/sbin/ldconfig</font></div><div><font face="courier new, monospace">libc.so.6()(64bit)</font></div><div><font face="courier new, monospace">libc.so.6(GLIBC_2.2.5)(64bit)</font></div>
<div><font face="courier new, monospace">libc.so.6(GLIBC_2.4)(64bit)</font></div><div><font face="courier new, monospace">libgcc_s.so.1()(64bit)</font></div><div><font face="courier new, monospace">libgcc_s.so.1(GCC_3.0)(64bit)</font></div>
<div><font face="courier new, monospace">liblog4shib.so.1()(64bit)</font></div><div><font face="courier new, monospace">libm.so.6()(64bit)</font></div><div><font face="courier new, monospace">libnsl.so.1()(64bit)</font></div>
<div><font face="courier new, monospace">libstdc++.so.6()(64bit)</font></div><div><font face="courier new, monospace">libstdc++.so.6(CXXABI_1.3)(64bit)</font></div><div><font face="courier new, monospace">libstdc++.so.6(CXXABI_1.3.1)(64bit)</font></div>
<div><font face="courier new, monospace">libstdc++.so.6(GLIBCXX_3.4)(64bit)</font></div><div><font face="courier new, monospace">rpmlib(CompressedFileNames) <= 3.0.4-1</font></div><div><font face="courier new, monospace">rpmlib(PayloadFilesHavePrefix) <= 4.0-1</font></div>
<div><font face="courier new, monospace">rtld(GNU_HASH)</font></div><div><br></div>Regards,</div><div><br></div><div>Yannick<div><div class="h5"><br><br><div class="gmail_quote">On Mon, Jul 9, 2012 at 11:41 PM, 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>On 7/9/12 5:36 PM, "Yannick Béot" <<a href="mailto:yannick.beot@gmail.com" target="_blank">yannick.beot@gmail.com</a>> wrote:<br>
<br>
>I reproduced the problem with the exact same request catch from apache<br>
>access logs during the previous crash.<br>
<br>
</div>Hmm, ok. That's puzzling since it would have to have expired there also,<br>
so that means it did fail in the decoding step.<br>
<br>
Logging comes to mind, but you're on RHEL5, and that shouldn't have any<br>
issues with broken logging code by now.<br>
<br>
Nevertheless, if you're logging protocol messages in the SP, turn down<br>
logging and try it again.<br>
<span><font color="#888888"><br>
-- Scott<br>
<br>
</font></span></blockquote></div><br></div></div></div></div>
</blockquote></div><br></div>