error while fetching metadata (using shibd -t)

[Timo Tunturi]

On 9/21/12 1:44 PM, Martin Haase wrote:
> Hi Guys,
>
> not just a real problem, however, wanted to share this. shibd -t outputs
> this:
>
> 2012-09-21 12:17:11 ERROR XMLTooling.libcurl.InputStream : error while
> fetching https://metadata-server/metadata.xml: (59) Unknown cipher in
> list: ALL:!aNULL:!LOW:!EXPORT:!SSLv2
> 2012-09-21 12:17:11 ERROR XMLTooling.ParserPool : fatal error on line 0,
> column 0, message: internal error in NetAccessor
> 2012-09-21 12:17:11 ERROR OpenSAML.MetadataProvider.XML : error while
> loading resource (https://metadata-server/metadata.xml): XML error(s)
> during parsing, check log for specifics
> 2012-09-21 12:17:11 WARN OpenSAML.MetadataProvider.XML : adjusted reload
> interval to 600 seconds
> 2012-09-21 12:17:11 WARN OpenSAML.MetadataProvider.XML : trying backup
> file, exception loading remote resource: XML error(s) during parsing,
> check log for specifics
> overall configuration is loadable, check console for non-fatal problems
>
> The funny thing is, from shibd.log, the SP is very well able to fetch
> the metadata, and tell if they have changed, etc. The SP is 2.5.0, both
> systems run RHEL 6.3, libcurl-openssl is installed on the SP, and the
> metadata server has a real certificate.
>
> FWIW, the Apache SSLCipherSuite directive on the metadata server looks
> totally unrelated to what the error message says about those unknown
> ciphers.

Linker probably doesn't link to the proper curl-library. In the standard 
shibd init script there is a kind of a fix for that, but when you invoke 
the shibd binary directly, things work a bit differently.

---clip---
export LD_LIBRARY_PATH=/opt/shibboleth/lib64:$LD_LIBRARY_PATH
---clip---

> Cheers,
> Martin
>
>
>
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
>


-- 
Timo Tunturi, Aalto University IT