dustymabe added a new comment to an issue you are following: `` actually I don't think it shut itself down now. looks like the gssproxy service fails to come up and has to time out before other things can continue during boot:
``` -bash-4.3# systemctl status gssproxy.service ● gssproxy.service - GSSAPI Proxy Daemon Loaded: loaded (/usr/lib/systemd/system/gssproxy.service; disabled; vendor preset: disabled) Active: failed (Result: timeout) since Tue 2016-10-25 14:58:00 UTC; 9min ago Process: 1460 ExecStart=/usr/sbin/gssproxy -D (code=killed, signal=TERM) Oct 25 14:56:30 localhost.localdomain systemd[1]: Starting GSSAPI Proxy Daemon... Oct 25 14:58:00 host-172-17-1-6 systemd[1]: gssproxy.service: Start operation timed out. Terminating. Oct 25 14:58:00 host-172-17-1-6 systemd[1]: Failed to start GSSAPI Proxy Daemon. Oct 25 14:58:00 host-172-17-1-6 systemd[1]: gssproxy.service: Unit entered failed state. Oct 25 14:58:00 host-172-17-1-6 systemd[1]: gssproxy.service: Failed with result 'timeout'. ``` `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/175 _______________________________________________ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
