Shibboleth SP on RHEL7- issues between shibd <-> systemd?

[Cantor, Scott]

On 6/1/15, 9:19 AM, "users on behalf of Mark Cairney" <users-bounces at shibboleth.net on behalf of Mark.Cairney at ed.ac.uk> wrote:
>
># /etc/init.d/shibd start
>Starting shibd (via systemctl):  Job for shibd.service failed. See
>'systemctl status shibd.service' and 'journalctl -xn' for details.
>                                                           [FAILED]
>However the process starts (this PID matches the one in
>/var/run/shibboleth/shibd.pid):

It's simply taking too long to start, more than 30 seconds. You can change the -w param in the script, or just live with it. Has nothing to do with systemd.

>If I run the status command I see:

That's probably it reporting the original failure to start fast enough and reporting the PID of the original process before it forked.

>Similarly if I stop the service I see:
>
># /etc/init.d/shibd stop
>Stopping shibd (via systemctl):                            [  OK  ]
>
>However shibd is still running.

I've not seen any such behavior, but I'll look at ours, it certainly should be slow to start up, enough to trigger this if it's actually happening.

I know enough to probably throw a systemd script together at this point.

-- Scott