<html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div><span></span></div><div class="qtdSeparateBR"><br><br></div><div class="yahoo_quoted" id="yui_3_16_0_ym19_1_1460001886615_31614" style="display: block;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yui_3_16_0_ym19_1_1460001886615_31613"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yui_3_16_0_ym19_1_1460001886615_31612"> <div dir="ltr" id="yui_3_16_0_ym19_1_1460001886615_31622"> <font size="2" face="Arial" id="yui_3_16_0_ym19_1_1460001886615_31621"> <hr size="1"> <b><span style="font-weight:bold;">From:</span></b> Petr Vobornik <pvoborni@redhat.com><br> <b><span style="font-weight: bold;">To:</span></b> John Williams <john.1209@yahoo.com>; "Freeipa-users@redhat.com" <Freeipa-users@redhat.com> <br> <b><span style="font-weight: bold;">Sent:</span></b> Thursday, April 7, 2016 8:01 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [Freeipa-users] CentOS 7 replica installation failing<br> </font> </div> <div class="y_msg_container" id="yui_3_16_0_ym19_1_1460001886615_31611" dir="ltr"><br>On 04/07/2016 01:34 PM, John Williams wrote:<br clear="none">> <br clear="none">> <br clear="none">> --------------------------------------------------------------------------------<br clear="none">> *From:* Petr Vobornik <<a shape="rect" ymailto="mailto:pvoborni@redhat.com" href="mailto:pvoborni@redhat.com">pvoborni@redhat.com</a>><br clear="none">> *To:* John Williams <<a shape="rect" ymailto="mailto:john.1209@yahoo.com" href="mailto:john.1209@yahoo.com">john.1209@yahoo.com</a>>; "<a shape="rect" ymailto="mailto:Freeipa-users@redhat.com" href="mailto:Freeipa-users@redhat.com">Freeipa-users@redhat.com</a>" <br clear="none">> <<a shape="rect" ymailto="mailto:Freeipa-users@redhat.com" href="mailto:Freeipa-users@redhat.com">Freeipa-users@redhat.com</a>><br clear="none">> *Sent:* Thursday, April 7, 2016 7:11 AM<br clear="none">> *Subject:* Re: [Freeipa-users] CentOS 7 replica installation failing<br clear="none">> <br clear="none">> On 04/07/2016 06:12 AM, John Williams wrote:<br clear="none">> > I've setup an initial FreeIPA instance on a CentOS 7 host. The install went<br clear="none">> > without a hitch. I can login to the GUI with no problems. However, I am not<br clear="none">> > able to install the replica on another CentOS 7 host. I get the following <br clear="none">> errors:<br clear="none">> ><br clear="none">> > [<a shape="rect" ymailto="mailto:root@ipa2" href="mailto:root@ipa2">root@ipa2</a> <mailto:<a shape="rect" ymailto="mailto:root@ipa2" href="mailto:root@ipa2">root@ipa2</a>> ~]# ipa-replica-install --setup-ca --setup-dns <br clear="none">> --no-forwarders<br clear="none">> > /var/lib/ipa/replica-info-ipa2.nrln.us.gpg --skip-conncheck<br clear="none">> <br clear="none">> It was run with '--skip-conncheck'. Is there a reason? If you remove it,<br clear="none">> what does it complain about?<br clear="none">> <br clear="none">> In general, using --skip-conncheck should be avoided because it may hide<br clear="none">> errors.<br clear="none">> <br clear="none">> You could also check master server<br clear="none">> /var/log/dirsrv/slapd-your-instance/access and errors logs if there is<br clear="none">> some connection attempt from the replica visible.<br clear="none">> <br clear="none">> And maybe /var/log/ipareplica-install.log contains more info.<br clear="none">> <br clear="none">> I ran the skip connections, because when I ran it initially without the skip <br clear="none">> connections, I got the following messages:<br clear="none">> <br clear="none">> The following UDP ports could not be verified as open: 88, 464<br clear="none">> This can happen if they are already bound to an application<br clear="none">> and ipa-replica-conncheck cannot attach own UDP responder.<br clear="none">> <br clear="none">> Remote master check failed with following error message(s):<br clear="none">> Warning: Permanently added 'ipa1.nrln.us,192.168.1.38' (ECDSA) to the list of <br clear="none">> known hosts.<br clear="none">> Could not chdir to home directory /home/admin: No such file or directory<br clear="none">> Port check failed! Inaccessible port(s): 389 (TCP), 636 (TCP), 88 (TCP), 464 <br clear="none">> (TCP), 80 (TCP), 443 (TCP)<br clear="none">> <br clear="none">> ipa.ipapython.install.cli.install_tool(Replica): ERROR Connection check failed!<br clear="none">> Please fix your network settings according to error messages above.<br clear="none">> If the check results are not valid it can be skipped with --skip-conncheck <br clear="none">> parameter.<br clear="none">> <br clear="none">> There is nothing blocking the connections, and the initial IPA server seems to <br clear="none">> be working fine.<br clear="none">> <br clear="none">> Here are some snippets from the log:<br clear="none">> <br clear="none">> <br clear="none">> File <br clear="none">> "/usr/lib/python2.7/site-packages/ipaserver/install/server/replicainstall.py", <br clear="none">> line 525, in install_check<br clear="none">> options.setup_ca, config.ca_ds_port, options.admin_password)<br clear="none">> File "/usr/lib/python2.7/site-packages/ipaserver/install/replication.py", <br clear="none">> line 91, in replica_conn_check<br clear="none">> "\nIf the check results are not valid it can be skipped with <br clear="none">> --skip-conncheck parameter.")<br clear="none">> <br clear="none">> 2016-04-07T11:30:06Z DEBUG The ipa-replica-install command failed, exception: <br clear="none">> SystemExit: Connection check failed!<br clear="none">> Please fix your network settings according to error messages above.<br clear="none">> If the check results are not valid it can be skipped with --skip-conncheck <br clear="none">> parameter.<br clear="none">> 2016-04-07T11:30:06Z ERROR Connection check failed!<br clear="none">> Please fix your network settings according to error messages above.<br clear="none">> If the check results are not valid it can be skipped with --skip-conncheck <br clear="none">> parameter.<br clear="none">> <br clear="none">> Here are some more logs:<br clear="none">> <br clear="none">> [<a shape="rect" ymailto="mailto:root@ipa2" href="mailto:root@ipa2">root@ipa2</a> ~]# tail -30 /var/log/ipareplica-conncheck.log<br clear="none">> Could not chdir to home directory /home/admin: No such file or directory<br clear="none">> debug1: client_input_channel_req: channel 0 rtype exit-status reply 0<br clear="none">> debug1: client_input_channel_req: channel 0 rtype <a shape="rect" ymailto="mailto:eow@openssh.com" href="mailto:eow@openssh.com">eow@openssh.com</a> reply 0<br clear="none">> debug1: channel 0: free: client-session, nchannels 1<br clear="none">> debug1: fd 1 clearing O_NONBLOCK<br clear="none">> debug1: fd 2 clearing O_NONBLOCK<br clear="none">> Transferred: sent 3032, received 2584 bytes, in 0.0 seconds<br clear="none">> Bytes per second: sent 131062.5, received 111697.1<br clear="none">> debug1: Exit status 0<br clear="none">> <br clear="none">> 2016-04-07T11:30:02Z DEBUG Starting external process<br clear="none">> 2016-04-07T11:30:02Z DEBUG args='/bin/ssh' '-o StrictHostKeychecking=no' '-o <br clear="none">> UserKnownHostsFile=/tmp/tmpCbCb50' '<a shape="rect" ymailto="mailto:admin@ipa1.nrln.us" href="mailto:admin@ipa1.nrln.us">admin@ipa1.nrln.us</a>' <br clear="none">> '/usr/sbin/ipa-replica-conncheck --replica ipa2.nrln.us'<br clear="none">> 2016-04-07T11:30:05Z DEBUG Process finished, return code=1<br clear="none">> 2016-04-07T11:30:05Z DEBUG stdout=Check connection from master to remote replica <br clear="none">> 'ipa2.nrln.us':<br clear="none">> Directory Service: Unsecure port (389): FAILED<br clear="none">> Directory Service: Secure port (636): FAILED<br clear="none">> Kerberos KDC: TCP (88): FAILED<br clear="none">> Kerberos KDC: UDP (88): WARNING<br clear="none">> Kerberos Kpasswd: TCP (464): FAILED<br clear="none">> Kerberos Kpasswd: UDP (464): WARNING<br clear="none">> HTTP Server: Unsecure port (80): FAILED<br clear="none">> HTTP Server: Secure port (443): FAILED<br clear="none">> The following UDP ports could not be verified as open: 88, 464<br clear="none">> This can happen if they are already bound to an application<br clear="none">> and ipa-replica-conncheck cannot attach own UDP responder.<br clear="none">> <br clear="none">> 2016-04-07T11:30:05Z DEBUG stderr=Warning: Permanently added <br clear="none">> 'ipa1.nrln.us,192.168.1.38' (ECDSA) to the list of known hosts.<br clear="none">> Could not chdir to home directory /home/admin: No such file or directory<br clear="none">> Port check failed! Inaccessible port(s): 389 (TCP), 636 (TCP), 88 (TCP), 464 <br clear="none">> (TCP), 80 (TCP), 443 (TCP)<br clear="none">> <br clear="none">> These two hosts are on the same subnet, nor firewall, or IPTables running. <br clear="none">> That's why the error message confusing.<br clear="none">> <br clear="none">> Any suggestions?<br clear="none"><br clear="none">The error suggest that master is not able to contact replica on any port.<br clear="none"><br clear="none">Is DNS ok?<br clear="none"><br clear="none">What does `nmap ipa2.nrln.us` return?<br clear="none"><br>OMG. The firewall was on the replica. Thanks so much!!<br><br clear="none">> <br clear="none">> > WARNING: conflicting time&date synchronization service 'chronyd' will<br clear="none">> > be disabled in favor of ntpd<br clear="none">> ><br clear="none">> > Directory Manager (existing master) password:<br clear="none">> ><br clear="none">> > Existing BIND configuration detected, overwrite? [no]: yes<br clear="none">> > Using reverse zone(s) 1.168.192.in-addr.arpa.<br clear="none">> > Configuring NTP daemon (ntpd)<br clear="none">> > [1/4]: stopping ntpd<br clear="none">> > [2/4]: writing configuration<br clear="none">> > [3/4]: configuring ntpd to start on boot<br clear="none">> > [4/4]: starting ntpd<br clear="none">> > Done configuring NTP daemon (ntpd).<br clear="none">> > Configuring directory server (dirsrv). Estimated time: 1 minute<br clear="none">> > [1/38]: creating directory server user<br clear="none">> > [2/38]: creating directory server instance<br clear="none">> > [3/38]: adding default schema<br clear="none">> > [4/38]: enabling memberof plugin<br clear="none">> > [5/38]: enabling winsync plugin<br clear="none">> > [6/38]: configuring replication version plugin<br clear="none">> > [7/38]: enabling IPA enrollment plugin<br clear="none">> > [8/38]: enabling ldapi<br clear="none">> > [9/38]: configuring uniqueness plugin<br clear="none">> > [10/38]: configuring uuid plugin<br clear="none">> > [11/38]: configuring modrdn plugin<br clear="none">> > [12/38]: configuring DNS plugin<br clear="none">> > [13/38]: enabling entryUSN plugin<br clear="none">> > [14/38]: configuring lockout plugin<br clear="none">> > [15/38]: creating indices<br clear="none">> > [16/38]: enabling referential integrity plugin<br clear="none">> > [17/38]: configuring ssl for ds instance<br clear="none">> > [18/38]: configuring certmap.conf<br clear="none">> > [19/38]: configure autobind for root<br clear="none">> > [20/38]: configure new location for managed entries<br clear="none">> > [21/38]: configure dirsrv ccache<br clear="none">> > [22/38]: enable SASL mapping fallback<br clear="none">> > [23/38]: restarting directory server<br clear="none">> > [24/38]: setting up initial replication<br clear="none">> > Starting replication, please wait until this has completed.<br clear="none">> ><br clear="none">> > [ipa1.nrln.us] reports: Update failed! Status: [-1 - LDAP error: Can't contact<br clear="none">> > LDAP server]<br clear="none">> ><br clear="none">> > [error] RuntimeError: Failed to start replication<br clear="none">> > Your system may be partly configured.<br clear="none">> > Run /usr/sbin/ipa-server-install --uninstall to clean up.<br clear="none">> ><br clear="none">> > ipa.ipapython.install.cli.install_tool(Replica): ERROR Failed to start<br clear="none">> > replication<br clear="none">> ><br clear="none">> ><br clear="none">> > The error message is misleading. The two hosts sit on the same subnet. All<br clear="none">> > firewalls are off. Selinux is disabled. Here is an nmap port scan from the<br clear="none">> > replica to the master:<br clear="none">> ><br clear="none">> ><br clear="none">> > [<a shape="rect" ymailto="mailto:root@ipa2" href="mailto:root@ipa2">root@ipa2</a> <mailto:<a shape="rect" ymailto="mailto:root@ipa2" href="mailto:root@ipa2">root@ipa2</a>> ~]# nmap ipa1<br clear="none">> ><br clear="none">> > Starting Nmap 6.40 ( <a shape="rect" href="http://nmap.org/" target="_blank">http://nmap.org </a><<a shape="rect" href="http://nmap.org/" target="_blank">http://nmap.org/</a>>) at 2016-04-07 00:12 EDT<br clear="none">> > Nmap scan report for ipa1 (192.168.1.38)<br clear="none">> > Host is up (0.000086s latency).<br clear="none">> > rDNS record for 192.168.1.38: ipa1.nrln.us<br clear="none">> > Not shown: 990 closed ports<br clear="none">> > PORT STATE SERVICE<br clear="none">> > 22/tcp open ssh<br clear="none">> > 80/tcp open http<br clear="none">> > 88/tcp open kerberos-sec<br clear="none">> > 389/tcp open ldap<br clear="none">> > 443/tcp open https<br clear="none">> > 464/tcp open kpasswd5<br clear="none">> > 636/tcp open ldapssl<br clear="none">> > 749/tcp open kerberos-adm<br clear="none">> > 8080/tcp open http-proxy<br clear="none">> > 8443/tcp open https-alt<br clear="none">> > MAC Address: 52:54:00:33:34:F0 (QEMU Virtual NIC)<br clear="none">> ><br clear="none">> > Nmap done: 1 IP address (1 host up) scanned in 0.14 seconds<br clear="none">> > [<a shape="rect" ymailto="mailto:root@ipa2" href="mailto:root@ipa2">root@ipa2</a> <mailto:<a shape="rect" ymailto="mailto:root@ipa2" href="mailto:root@ipa2">root@ipa2</a>> ~]#<div class="yqt7709176886" id="yqtfd45913"><br clear="none">> ><br clear="none">> ><br clear="none">> > Why do I get this message?<br clear="none">> ><br clear="none"><br clear="none"><br clear="none">-- <br clear="none">Petr Vobornik<br clear="none"></div><br><br></div> </div> </div> </div></div></body></html>