socket call resulted in error (98): no message

[Stapleton, Steven]

> You should always use /etc/init.d/shibd to start the service. Whether that's the problem I don't know, but in the
> future that will be critical for various reasons.

> Ordinarily I'd say SELinux is the problem, but that normally affects Apache talking to the socket, not the
> initialization. So I'd say more likely the socket is in use and there's a stale socket file. Using -f would clear it, which
> is I believe the default behavior of the init script.
>
> -- Scott

jstaplet at xpe10gt-cs-1 (2) 12:36:40 ~ > sudo /etc/init.d/shibd start
Starting shibd: listener failed to initialize


Looking at the init.d script, it does have the -f flag:
daemon --user $SHIBD_USER $shibd -p $pidfile -f -w 30

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

Thanks,
-Jim Stapleton