socket call resulted in error (98): no message

[Cantor, Scott]

> What port should I be looking at - I believe I can use netstat to see if it is
> active.

It's a file, it's a Unix domain socket.

See the Listener documentation in the wiki. Should be a relative file name that eventually ends up in /var/run/shibboleth. In a newer configuration it's entirely defaulted.

I checked the header files on Red Hat, 98 is "address in use". I can't think of any reason -f wouldn't clear the socket, so I don't know what its problem is. Other than clearing /var/run/shibboleth, I'd probably try an strace around running shibd to see what it's trying to create.

I'd still check SELinux and make sure it's off.

-- Scott