Red Hat Enterprise 6 and libcurl

[Cantor, Scott]

On Sep 13, 2013, at 1:21 PM, "Brian Reindel" <brian at reindel.com> wrote:

> SELinux is not enabled. I saw that on the Nabble archives and Google
> and checked.

Ok. That is the most likely cause. Failing that, there's no way shibd is running, so you have to have some kind of log output to diagnose it. To run the -t option as a check, set the library path as in the sysconfig file if you want to see what it does without the libcurl issue.

> When Shibboleth uses curl to connect to grab the metadata from the IdP
> it is hitting Apache via SSL.

I didn't understand you to be talking about the IdP Apache there.

Either way that would never prevent shibd from running.

> If Apache were misconfigured so that the
> cipher suite doesn't match with the cipher that curl is using then
> that might be the reason for the error I'm seeing from shibd -t.

It's not, that is the libcurl issue.  Nor will it prevent startup and cause the listener error.

>  I'm really trying to confirm if this is an
> installation issue or a configuration issue.

No way to know, but likely config.

> On RHE6 should I have to
> change anything by default to get shibd to use the alternative libcurl
> included in /opt/shibboleth/lib64?

No, not via init script. Yes, if via command line.

> As far as the log files are concerned, do you have any insights into
> why I would not see any?

If it was never started.

> For Linux isn't /var/log/shibboleth where
> they should be printing out in a default install?

The shibd log, yes.
> 


-- Scott