[Freeipa-users] Re: freeipa failing to start after update
Glad to know this will be fixed! ___ FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org To unsubscribe send an email to freeipa-users-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/freeipa-users@lists.fedorahosted.org
[Freeipa-users] Re: freeipa failing to start after update
Andrew Meyer via FreeIPA-users writes: > [andrew.meyer@freeipa01 ~]$ sudo ipactl --ignore-service-failures start ... > Starting smb Service > Failed to start smb Service > Forced start, ignoring smb Service, continuing normal operation > Starting winbind Service > Failed to start winbind Service > Forced start, ignoring winbind Service, continuing normal operation > Starting ipa-otpd Service > Starting ipa-dnskeysyncd Service > ipa: INFO: The ipactl command was successful That seems to be a bug - see: https://bugs.centos.org/view.php?id=16929 Jochen -- This space is intentionally left blank. ___ FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org To unsubscribe send an email to freeipa-users-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/freeipa-users@lists.fedorahosted.org
[Freeipa-users] Re: freeipa failing to start after update
[andrew.meyer@freeipa01 ~]$ sudo ipactl --ignore-service-failures start Existing service file detected! Assuming stale, cleaning and proceeding Starting Directory Service Starting krb5kdc Service Starting kadmin Service Starting named Service Starting httpd Service Starting ipa-custodia Service Starting pki-tomcatd Service Starting smb Service Failed to start smb Service Forced start, ignoring smb Service, continuing normal operation Starting winbind Service Failed to start winbind Service Forced start, ignoring winbind Service, continuing normal operation Starting ipa-otpd Service Starting ipa-dnskeysyncd Service ipa: INFO: The ipactl command was successful [andrew.meyer@freeipa01 ~]$ ___ FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org To unsubscribe send an email to freeipa-users-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/freeipa-users@lists.fedorahosted.org
[Freeipa-users] Re: freeipa failing to start after update
Andrew Meyer via FreeIPA-users wrote: > I am running CentOS 8.x and have updated to the latest version of IPA and > CentOS 8. I rebooted after updating and am now getting the following: > > Jan 20 12:55:29 freeipa01 server[7889]: arguments used: stop > Jan 20 12:55:30 freeipa01 systemd[1]: Stopping 389 Directory Server > ZONE1-EXAMPLE-NET > Jan 20 12:55:30 freeipa01 ns-slapd[7385]: [20/Jan/2020:12:55:30.169315691 > -0600] - INFO - op_thread_cleanup - slapd shutting down - signaling operation > threads - op stack size 2 max work q size 2 max work q stack size 2 [snip] Not really enough context. I'm guessing ipactl failed to start things, it would then move to shut them down. Does ipactl start work on the cli? rob ___ FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org To unsubscribe send an email to freeipa-users-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/freeipa-users@lists.fedorahosted.org
