Chapter 22. Troubleshooting IdM replica installation The following sections describe the process for gathering information about a failing IdM replica installation, and how to resolve some common installation issues. 22.1. IdM replica installation error log files When you install an Identity Management (IdM) replica, debugging information is appended to the following log files on the replica : /var/log/ipareplica-install.log /var/log/ipareplica-conncheck.log /var/log/ipaclient-install.log /var/log/httpd/error_log /var/log/dirsrv/slapd- INSTANCE-NAME /access /var/log/dirsrv/slapd- INSTANCE-NAME /errors /var/log/ipaserver-install.log The replica installation process also appends debugging information to the following log files on the IdM server the replica is contacting: /var/log/httpd/error_log /var/log/dirsrv/slapd- INSTANCE-NAME /access /var/log/dirsrv/slapd- INSTANCE-NAME /errors The last line of each log file reports success or failure, and ERROR and DEBUG entries provide additional context. Additional resources Reviewing IdM replica installation errors 22.2. Reviewing IdM replica installation errors To troubleshoot a failing IdM replica installation, review the errors at the end of the installation error log files on the new replica and the server, and use this information to resolve any corresponding issues. Prerequisites You must have root privileges to display the contents of IdM log files. Procedure Use the tail command to display the latest errors from the primary log file /var/log/ipareplica-install.log . The following example displays the last 10 lines. To review the log file interactively, open the end of the log file using the less utility and use the ^ and v arrow keys to navigate. Optional: While /var/log/ipareplica-install.log is the primary log file for a replica installation, you can gather additional troubleshooting information by repeating this review process with additional files on the replica and the server. On the replica: On the server: Additional resources IdM replica installation error log files If you are unable to resolve a failing replica installation, and you have a Red Hat Technical Support subscription, open a Technical Support case at the Red Hat Customer Portal and provide an sosreport of the replica and an sosreport of the server. The sosreport utility collects configuration details, logs and system information from a RHEL system. For more information about the sosreport utility, see the Red Hat Knowledgebase solution What is an sosreport and how to create one in Red Hat Enterprise Linux? . 22.3. IdM CA installation error log files Installing the Certificate Authority (CA) service on an Identity Management (IdM) replica appends debugging information to several locations on the replica and the IdM server the replica communicates with. Table 22.1. On the replica (in order of recommended priority): Location Description /var/log/pki/pki-ca-spawn. USDTIME_OF_INSTALLATION .log High-level issues and Python traces for the pkispawn installation process journalctl -u pki-tomcatd@pki-tomcat output Errors from the pki-tomcatd@pki-tomcat service /var/log/pki/pki-tomcat/ca/debug. USDDATE .log Large JAVA stacktraces of activity in the core of the Public Key Infrastructure (PKI) product /var/log/pki/pki-tomcat/ca/signedAudit/ca_audit Audit log of the PKI product /var/log/pki/pki-tomcat/ca/system /var/log/pki/pki-tomcat/ca/transactions /var/log/pki/pki-tomcat/catalina. USDDATE .log Low-level debug data of certificate operations for service principals, hosts, and other entities that use certificates On the server contacted by the replica: /var/log/httpd/error_log log file Installing the CA service on an existing IdM replica also writes debugging information to the following log file: /var/log/ipareplica-ca-install.log log file Note If a full IdM replica installation fails while installing the optional CA component, no details about the CA are logged; a message is logged in the /var/log/ipareplica-install.log file indicating that the overall installation process failed. Review the log files listed above for details specific to the CA installation failure. The only exception to this behavior is when you are installing the CA service and the root CA is an external CA. If there is an issue with the certificate from the external CA, errors are logged in /var/log/ipareplica-install.log . Additional resources Reviewing IdM CA installation errors 22.4. Reviewing IdM CA installation errors To troubleshoot a failing IdM CA installation, review the errors at the end of the CA installation error log files and use this information to resolve any corresponding issues. Prerequisites You must have root privileges to display the contents of IdM log files. Procedure To review a log file interactively, open the end of the log file using the less utility and use the ^ and v arrow keys to navigate, while searching for ScriptError entries. The following example opens /var/log/pki/pki-ca-spawn. USDTIME_OF_INSTALLATION .log . Gather additional troubleshooting information by repeating this review process with all the CA installation error log files. Additional resources IdM CA installation error log files If you are unable to resolve a failing IdM server installation, and you have a Red Hat Technical Support subscription, open a Technical Support case at the Red Hat Customer Portal and provide an sosreport of the server. The sosreport utility collects configuration details, logs and system information from a RHEL system. For more information about the sosreport utility, see the Red Hat Knowledgebase solution What is an sosreport and how to create one in Red Hat Enterprise Linux? . 22.5. Removing a partial IdM replica installation If an IdM replica installation fails, some configuration files might be left behind. Additional attempts to install the IdM replica can fail and the installation script reports that IPA is already configured: Example system with existing partial IdM configuration To resolve this issue, uninstall IdM software from the replica, remove the replica from the IdM topology, and retry the installation process. Prerequisites You must have root privileges. Procedure Uninstall the IdM server software on the host you are trying to configure as an IdM replica. On all other servers in the topology, use the ipa server-del command to delete any references to the replica that did not install properly. Attempt installing the replica. If you continue to experience difficulty installing an IdM replica because of repeated failed installations, reinstall the operating system. One of the requirements for installing an IdM replica is a clean system without any customization. Failed installations may have compromised the integrity of the host by unexpectedly modifying system files. Additional resources For additional details on uninstalling an IdM replica, see Uninstalling an IdM replica . If installation attempts fail after repeated uninstallation attempts, and you have a Red Hat Technical Support subscription, open a Technical Support case at the Red Hat Customer Portal and provide an sosreport of the replica and an sosreport of the server. The sosreport utility collects configuration details, logs and system information from a RHEL system. For more information about the sosreport utility, see the Red Hat Knowledgebase solution What is an sosreport and how to create one in Red Hat Enterprise Linux? . 22.6. Resolving invalid credential errors If an IdM replica installation fails with an Invalid credentials error, the system clocks on the hosts might be out of sync with each other: If you use the --no-ntp or -N options to attempt the replica installation while clocks are out of sync, the installation fails because services are unable to authenticate with Kerberos. To resolve this issue, synchronize the clocks on both hosts and retry the installation process. Prerequisites You must have root privileges to change system time. Procedure Synchronize the system clocks manually or with chronyd . Synchronizing manually Display the system time on the server and set the replica's time to match. Synchronizing with chronyd : See Using the Chrony suite to configure NTP to configure and set system time with chrony tools. Attempt the IdM replica installation again. Additional resources If you are unable to resolve a failing replica installation, and you have a Red Hat Technical Support subscription, open a Technical Support case at the Red Hat Customer Portal and provide an sosreport of the replica and an sosreport of the server. The sosreport utility collects configuration details, logs and system information from a RHEL system. For more information about the sosreport utility, see the Red Hat Knowledgebase solution What is an sosreport and how to create one in Red Hat Enterprise Linux? . 22.7. Additional resources Troubleshooting the first IdM server installation Troubleshooting IdM client installation Backing up and restoring IdM

Commands:
[user@replica ~]USD sudo tail -n 10 /var/log/ipareplica-install.log [sudo] password for user: func(installer) File "/usr/lib/python3.6/site-packages/ipaserver/install/server/replicainstall.py", line 424, in decorated func(installer) File "/usr/lib/python3.6/site-packages/ipaserver/install/server/replicainstall.py", line 785, in promote_check ensure_enrolled(installer) File "/usr/lib/python3.6/site-packages/ipaserver/install/server/replicainstall.py", line 740, in ensure_enrolled raise ScriptError("Configuration of client side components failed!") 2020-05-28T18:24:51Z DEBUG The ipa-replica-install command failed, exception: ScriptError: Configuration of client side components failed! 2020-05-28T18:24:51Z ERROR Configuration of client side components failed! 2020-05-28T18:24:51Z ERROR The ipa-replica-install command failed. See /var/log/ipareplica-install.log for more information
[user@replica ~]USD sudo less -N +G /var/log/ipareplica-install.log
[user@replica ~]USD sudo less -N +G /var/log/ipareplica-conncheck.log [user@replica ~]USD sudo less -N +G /var/log/ipaclient-install.log [user@replica ~]USD sudo less -N +G /var/log/httpd/error_log [user@replica ~]USD sudo less -N +G /var/log/dirsrv/slapd- INSTANCE-NAME /access [user@replica ~]USD sudo less -N +G /var/log/dirsrv/slapd- INSTANCE-NAME /errors [user@replica ~]USD sudo less -N +G /var/log/ipaserver-install.log
[user@server ~]USD sudo less -N +G /var/log/httpd/error_log [user@server ~]USD sudo less -N +G /var/log/dirsrv/slapd- INSTANCE-NAME /access [user@server ~]USD sudo less -N +G /var/log/dirsrv/slapd- INSTANCE-NAME /errors
[user@server ~]USD sudo less -N +G /var/log/pki/pki-ca-spawn. 20200527185902 .log
ipa-replica-install Your system may be partly configured. Run /usr/sbin/ipa-server-install --uninstall to clean up. IPA server is already configured on this system. If you want to reinstall the IPA server, please uninstall it first using 'ipa-server-install --uninstall'. The ipa-replica-install command failed. See /var/log/ipareplica-install.log for more information
ipa-server-install --uninstall
ipa server-del replica.idm.example.com
[27/40]: setting up initial replication Starting replication, please wait until this has completed. Update in progress, 15 seconds elapsed [ldap://server.example.com:389] reports: Update failed! Status: [49 - LDAP error: Invalid credentials] [error] RuntimeError: Failed to start replication Your system may be partly configured. Run /usr/sbin/ipa-server-install --uninstall to clean up. ipa.ipapython.install.cli.install_tool(CompatServerReplicaInstall): ERROR Failed to start replication ipa.ipapython.install.cli.install_tool(CompatServerReplicaInstall): ERROR The ipa-replica-install command failed. See /var/log/ipareplica-install.log for more information
[user@server ~]USD date Thu May 28 21:03:57 EDT 2020 [user@replica ~]USD sudo timedatectl set-time '2020-05-28 21:04:00'