A tool to help an administer control an IPA environment.
IPA glues several discrete services together to work in concert and the order that these services are started and stopped is important. ipactl ensures that they are started and stopped in the correct order.
IPA stores the available masters and the services configured on each one. The first thing ipactl does is start (if it is not already running) the IPA 389-ds instance to query what services it controls. The hostname used in the query needs to match the hostname of the value stored in LDAP. This can be controlled with the host option in /etc/ipa/default.conf. This should be a fully-qualified hostname.
Start all of the services that make up IPA
Stop all of the services that make up IPA
Stop then start all of the services that make up IPA
Provides status of all the services that make up IPA
- -d, --debug
Display debugging information
Skip version check
If any service start fails, do not rollback the services, continue with the operation
- -f, --force
Force IPA to start. Combine options --skip-version-check and --ignore-service-failures
All actions except status:
1 a generic error occurred
2 unknown or invalid argument(s)
4 user has insufficient privilege
6 IPA server is not configured
For the status action:
0 service is running
3 service is not running
4 service status is unknown (or unconfigured)
If not executed as root then the status action will return 4 for insufficient privileges.
Some services are socket activated and may show as STOPPED by the status action. These services include ipa-ods-exporter and ipa-otpd.