You have the freeipa server package installed, and the systemd
service
enabled, but the server is not configured. If you want it to run on
this machine, configure the server as suggested right there in the log
messages, if not, either remove the package, or disable the systemd
service.
On 10/5/19 1:09 am, lejeczek via FreeIPA-users wrote:
> hi guys
>
> I have no ipa configured, not even a client set up and yet I see
> something constantly wants IPA:
>
> May 09 16:06:19 swir.private. systemd[1]: ipa.service: main process
> exited, code=exited, status=6/NOTCONFIGURED
> May 09 16:06:19 swir.private. systemd[1]: Failed to start Identity,
> Policy, Audit.
> May 09 16:06:19 swir.private. systemd[1]: Unit ipa.service entered
> failed state.
> May 09 16:06:19 swir.private. systemd[1]: ipa.service failed.
> ^[May 09 16:06:49 swir.private. systemd[1]: Starting Identity, Policy,
> Audit...
> May 09 16:06:49 swir.private. ipactl[42053]: IPA is not configured (see
> man pages of ipa-server-install for help)
> May 09 16:06:49 swir.private. systemd[1]: ipa.service: main process
> exited, code=exited, status=6/NOTCONFIGURED
> May 09 16:06:49 swir.private. systemd[1]: Failed to start Identity,
> Policy, Audit.
> May 09 16:06:49 swir.private. systemd[1]: Unit ipa.service entered
> failed state.
> May 09 16:06:49 swir.private. systemd[1]: ipa.service failed.
> May 09 16:07:20 swir.private. systemd[1]: Starting Identity, Policy,
> Audit...
> May 09 16:07:20 swir.private. ipactl[42275]: IPA is not configured (see
> man pages of ipa-server-install for help)
> May 09 16:07:20 swir.private. systemd[1]: ipa.service: main process
> exited, code=exited, status=6/NOTCONFIGURED
> May 09 16:07:20 swir.private. systemd[1]: Failed to start Identity,
> Policy, Audit.
> May 09 16:07:20 swir.private. systemd[1]: Unit ipa.service entered
> failed state.
> May 09 16:07:20 swir.private. systemd[1]: ipa.service failed.
> May 09 16:07:51 swir.private. systemd[1]: Starting Identity, Policy,
> Audit...
> May 09 16:07:51 swir.private. ipactl[42503]: IPA is not configured (see
> man pages of ipa-server-install for help)
> May 09 16:07:51 swir.private. systemd[1]: ipa.service: main process
> exited, code=exited, status=6/NOTCONFIGURED
> May 09 16:07:51 swir.private. systemd[1]: Failed to start Identity,
> Policy, Audit.
> May 09 16:07:51 swir.private. systemd[1]: Unit ipa.service entered
> failed state.
> May 09 16:07:51 swir.private. systemd[1]: ipa.service failed.
>
> Is that normal and if not then what can be the problem?
>
> many thanks, L.
>
>
> _______________________________________________
> FreeIPA-users mailing list -- freeipa-users(a)lists.fedorahosted.org
> To unsubscribe send an email to freeipa-users-leave(a)lists.fedorahosted.org
> Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html
> List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedorahosted.org/archives/list/freeipa-users@lists.fedoraho...
_______________________________________________
FreeIPA-users mailing list -- freeipa-users(a)lists.fedorahosted.org
To unsubscribe send an email to freeipa-users-leave(a)lists.fedorahosted.org
Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedorahosted.org/archives/list/freeipa-users@lists.fedoraho...
to include a possible clue so other might use if come across similar
problem - I thought it was something from IPA's suite, some related
component, but instead it was my own radius server which I told to
after+wants from/via systemd but also Restart=on-failure
This was messing IPA to such extent, not 100% sure but almost, that it
was screwing up a replica installation process at the point of dirsrv
update, whose ldap Radius needed in order to start.
Replica's failure:
Upgrading IPA:. Estimated time: 1 minute 30 seconds
[1/10]: stopping directory server
[2/10]: saving configuration
[3/10]: disabling listeners
[4/10]: enabling DS global lock
[5/10]: disabling Schema Compat
[6/10]: starting directory server
[7/10]: upgrading server
ipaserver.install.upgradeinstance: ERROR Upgrade failed with cannot
connect to 'ldapi://%2Fvar%2Frun%2Fslapd-PRIVATE.socket':
[error] RuntimeError: cannot connect to
'ldapi://%2Fvar%2Frun%2Fslapd-PRIVATE.socket':
[cleanup]: stopping directory server
[cleanup]: restoring configuration
Your system may be partly configured.
Run /usr/sbin/ipa-server-install --uninstall to clean up.
ipapython.admintool: ERROR Update failed: cannot connect to
'ldapi://%2Fvar%2Frun%2Fslapd-PRIVATE.socket':
ipapython.admintool: ERROR The ipa-replica-install command failed.
See /var/log/ipareplica-install.log for more information