socket call resulted in error (98): no message

[Stapleton, Steven]

>  I had similar problems with 2.4.3 on CentOS 5.5 when I started shibd without the init scripts. Once started, shibd
> would not let go of its socket even with -f or manual kills of the processes. I tried "shibd stop",
> "shibd -f stop", "shibd -f start", and finally tried "kill" and eventually "kill -9". The kills terminated the process
> but the socket remained.
>
> I didn't have time to chase it farther and since this was a throwaway test system, I resorted to the easiest thing
> that WOULD clean out the socket, a reboot. SELinux was set to permissive.
>
> Once I started using the init.d scripts or the "service shibd start" command, the problem went away.

Thanks, looks like the restart fixed it. It started without error, and the log file has no errors, but plenty of entries for the startup time.

Thanks,
-Jim Stapleton