SP starts up and runs but systemd things it timed out

Herron, Joel D herronj at uww.edu
Fri Sep 10 13:57:53 UTC 2021

It starts and stays running via "./sbin/shibd start" from the command line. 

I don’t see any difference in the log output from starting manually vs from the service, outside of the service just constantly restarting the process.

While running everything is work as expected; users can login, sessions are created, users are passed to the application and server vars are correctly passed. 

I've made a workaround I installed the included init.d  script for suse and just made a forking unit service file that references the init.d script and that is working so I'll call that good enough.

For ref incase someone's interested

Description=Shibboleth Service Provider Daemon

ExecStart=/etc/init.d/shibd start
ExecStop=/etc/init.d/shibd stop
ExecReload=/etc/init.d/shibd restart



On 9/10/21, 4:14 AM, "users on behalf of Peter Schober" <users-bounces at shibboleth.net on behalf of peter.schober at univie.ac.at> wrote:


    * Herron, Joel D <herronj at uww.edu> [2021-09-09 21:21]:
    > So something is afoot then, I'm not loading any aggregates at all
    > just my local IDP metadata file which is maybe 5kb.

    Does the SP start properly (and quickly) if you run the start command
    interactively on the command line?

    And yes, of course check your logs.

    For Consortium Member technical support, see https://shibboleth.atlassian.net/wiki/x/ZYEpPw
    To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net

More information about the users mailing list