Shibd complains that its socket is being used or can't connect to that socket
This happens when shibd was not terminated properly and its socket is locked.
Start shibd with
-f option to force it reclaim the lock
If you are running SELinux (on redhat variants etc), then you need to turn it off or change it to permissive.
to top