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

[Cantor, Scott]

On 6/1/15, 9:59 AM, "users on behalf of Mark Cairney" <users-bounces at shibboleth.net on behalf of Mark.Cairney at ed.ac.uk> wrote:

>Thanks, looking at the times in shibd.log it was taking over 30 seconds
>from start to finish. I've now upped the -w parameter and it's starting
>and stopping as expected!
>I'm slightly surprised it takes as long as it does to start as it's a
>relatively simple config but that' by-the-by.

From your domain, I'm assuming you're loading UK fed metadata. That alone will take upwards of 15-20 seconds just to download in some cases.

>Fully systemd-ing it would be good for future-proofing but now it's
>behaving I'm happy enough to go with this tweaked config.

Well, if stopping doesn't work without that change, that's still new information to me, I wasn't aware. That, I guess, suggests it's not actually running the init script to stop it, it must be tracking the PID inside that abomination and only stopping the forked process it records.

That's not a bug I can really fix other than setting the warn value. Setting it higher by default is bad because it changes the hang time for everybody. I suppose I could just provide a separate script to do the kill if the OS is going to refuse to run it.

The fix is to stop using metadata batches, basically.

-- Scott