#4291 CA not start during ipa server install in pure IPv6 env
Closed: Fixed None Opened 9 years ago by mkosek.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1081561

Description of problem:
ipa server install ended with "CA did not start in 300s" in pure IPv6 env

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.In /etc/hosts
Remove : localhost localhost.localdomain localhost4
Add         : <ipv6> <hostname> <shortname> (IP FQDN shortname)
2.delete ipv4 address
3.stop ip6tables

Actual results:
install is not finished with
'CA did not start in 300s'

Expected results:
install is successfull

Additional info:
[root@70ms ~]# cat /etc/hosts
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
2620:52:0:1040:9e8e:99ff:fe4c:1320 70ms.testrelm.com 70ms
[root@70ms ~]# ip addr del dev lo
Warning: Executing wildcard deletion to stay compatible with old scripts.
Explicitly specify the prefix length ( to avoid this warning.
This special behaviour is likely to disappear in further releases,
fix your scripts!

[root@70ms ~]# ip -4 addr del dev eno1
Warning: Executing wildcard deletion to stay compatible with old scripts.
Explicitly specify the prefix length ( to avoid this warning.
This special behaviour is likely to disappear in further releases,
fix your scripts!

If master is getting disconnected after deleting ipv4 addr,
try to ssh -6 with ipv6 addr from replica:

[root@70replica ~]# ssh -6 2620:52:0:1040:9e8e:99ff:fe4c:1320
The authenticity of host '2620:52:0:1040:9e8e:99ff:fe4c:1320
(2620:52:0:1040:9e8e:99ff:fe4c:1320)' can't be established.
ECDSA key fingerprint is cc:95:6b:33:b0:95:31:7f:16:b2:86:42:71:1c:95:52.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '2620:52:0:1040:9e8e:99ff:fe4c:1320' (ECDSA) to the
list of known hosts.
Last login: Thu Mar 27 09:03:41 2014 from
** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** **
This System is reserved by xdong@redhat.com.

To return this system early. You can run the command: return2beaker.sh
Ensure you have your logs off the system before returning to Beaker

To extend your reservation time. You can run the command:
This is an interactive script. You will be prompted for how many
hours you would like to extend the reservation.

You should verify the watchdog was updated succesfully after
you extend your reservation.

For ssh, kvm, serial and power control operations please look here:

For the default root password, see:

Beaker Test information:

Job Whiteboard: IPV6 test env -- master 3

Recipe Whiteboard: IPA MASTER
** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** **
[root@70ms ~]# ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: mtu 1500 qdisc mq state UP qlen 1000
link/ether 9c:8e:99:4c:13:20 brd ff:ff:ff:ff:ff:ff
inet6 2620:52:0:1040:9e8e:99ff:fe4c:1320/64 scope global dynamic
valid_lft 2592000sec preferred_lft 604800sec
inet6 fec0:0:a10:4000:9e8e:99ff:fe4c:1320/64 scope site dynamic
valid_lft 2592000sec preferred_lft 604800sec
inet6 fe80::9e8e:99ff:fe4c:1320/64 scope link
valid_lft forever preferred_lft forever
3: eno2: mtu 1500 qdisc mq state DOWN qlen 1000
link/ether 9c:8e:99:4c:13:21 brd ff:ff:ff:ff:ff:ff
4: eno3: mtu 1500 qdisc mq state DOWN qlen 1000
link/ether 9c:8e:99:4c:13:22 brd ff:ff:ff:ff:ff:ff
5: eno4: mtu 1500 qdisc mq state DOWN qlen 1000
link/ether 9c:8e:99:4c:13:23 brd ff:ff:ff:ff:ff:ff

[root@70ms ~]# ipa-server-install --setup-dns --no-forwarder -a Secret123 -p

The log file for this installation can be found in
This program will set up the IPA Server.

This includes:
* Configure a stand-alone CA (dogtag) for certificate management
* Configure the Network Time Daemon (ntpd)
* Create and configure an instance of Directory Server
* Create and configure a Kerberos Key Distribution Center (KDC)
* Configure Apache (httpd)
* Configure DNS (bind)

To accept the default shown in brackets, press the Enter key.

WARNING: conflicting time&date synchronization service 'chronyd' will be
in favor of ntpd

Existing BIND configuration detected, overwrite? [no]: y
Enter the fully qualified domain name of the computer
on which you're setting up server software. Using the form
Example: master.example.com.

Server host name [70ms.testrelm.com]:

Warning: skipping DNS resolution of host 70ms.testrelm.com
The domain name has been determined based on the host name.

Please confirm the domain name [testrelm.com]:

The kerberos protocol requires a Realm name to be defined.
This is typically the domain name converted to uppercase.

Please provide a realm name [TESTRELM.COM]:
Do you want to configure the reverse zone? [yes]:
Please specify the reverse zone name
Using reverse zone

The IPA Master Server will be configured with:
Hostname: 70ms.testrelm.com
IP address: 2620:52:0:1040:9e8e:99ff:fe4c:1320
Domain name: testrelm.com
Realm name: TESTRELM.COM

BIND DNS server will be configured to serve IPA domain with:
Forwarders: No forwarders
Reverse zone:

Continue to configure the system with these values? [no]: y
The following operations may take some minutes to complete.
Please wait until the prompt is returned.

Configuring NTP daemon (ntpd)
[1/4]: stopping ntpd
[2/4]: writing configuration
[3/4]: configuring ntpd to start on boot
[4/4]: starting ntpd
Done configuring NTP daemon (ntpd).
Configuring directory server (dirsrv): Estimated time 1 minute
[1/38]: creating directory server user
[2/38]: creating directory server instance
[3/38]: adding default schema
[4/38]: enabling memberof plugin

[5/38]: enabling winsync plugin
[6/38]: configuring replication version plugin
[7/38]: enabling IPA enrollment plugin
[8/38]: enabling ldapi
[9/38]: configuring uniqueness plugin
[10/38]: configuring uuid plugin
[11/38]: configuring modrdn plugin
[12/38]: configuring DNS plugin
[13/38]: enabling entryUSN plugin
[14/38]: configuring lockout plugin
[15/38]: creating indices
[16/38]: enabling referential integrity plugin
[17/38]: configuring certmap.conf
[18/38]: configure autobind for root
[19/38]: configure new location for managed entries
[20/38]: configure dirsrv ccache
[21/38]: enable SASL mapping fallback
[22/38]: restarting directory server
[23/38]: adding default layout
[24/38]: adding delegation layout
[25/38]: creating container for managed entries
[26/38]: configuring user private groups
[27/38]: configuring netgroups from hostgroups
[28/38]: creating default Sudo bind user
[29/38]: creating default Auto Member layout
[30/38]: adding range check plugin
[31/38]: creating default HBAC rule allow_all
[32/38]: initializing group membership
[33/38]: adding master entry
[34/38]: configuring Posix uid/gid generation
[35/38]: adding replication acis
[36/38]: enabling compatibility plugin
[37/38]: tuning directory server
[38/38]: configuring directory to start on boot
Done configuring directory server (dirsrv).
Configuring certificate server (pki-tomcatd): Estimated time 3 minutes 30
[1/22]: creating certificate server user
[2/22]: configuring certificate server instance
[3/22]: stopping certificate server instance to update CS.cfg
[4/22]: disabling nonces
[5/22]: set up CRL publishing
[6/22]: starting certificate server instance
[7/22]: creating RA agent certificate database
[8/22]: importing CA chain to RA certificate database
[9/22]: fixing RA database permissions
[10/22]: setting up signing cert profile
[11/22]: set certificate subject base
[12/22]: enabling Subject Key Identifier
[13/22]: enabling CRL and OCSP extensions for certificates
[14/22]: setting audit signing renewal to 2 years
[15/22]: configuring certificate server to start on boot
[16/22]: restarting certificate server
[17/22]: requesting RA certificate from CA
[18/22]: issuing RA agent certificate
[19/22]: adding RA agent as a trusted user
[20/22]: configure certificate renewals
[21/22]: configure Server-Cert certificate renewal
[22/22]: Configure HTTP to proxy connections
Done configuring certificate server (pki-tomcatd).
Configuring Kerberos KDC (krb5kdc): Estimated time 30 seconds
[1/10]: adding sasl mappings to the directory
[2/10]: adding kerberos container to the directory
[3/10]: configuring KDC
[4/10]: initialize kerberos container
[5/10]: adding default ACIs
[6/10]: creating a keytab for the directory
[7/10]: creating a keytab for the machine
[8/10]: adding the password extension to the directory
[9/10]: starting the KDC
[10/10]: configuring KDC to start on boot
Done configuring Kerberos KDC (krb5kdc).
Configuring kadmin
[1/2]: starting kadmin
[2/2]: configuring kadmin to start on boot
Done configuring kadmin.
Configuring ipa_memcached
[1/2]: starting ipa_memcached
[2/2]: configuring ipa_memcached to start on boot
Done configuring ipa_memcached.
Configuring ipa-otpd
[1/2]: starting ipa-otpd
[2/2]: configuring ipa-otpd to start on boot
Done configuring ipa-otpd.
Configuring the web interface (httpd): Estimated time 1 minute
[1/14]: setting mod_nss port to 443
[2/14]: setting mod_nss password file
[3/14]: enabling mod_nss renegotiate
[4/14]: adding URL rewriting rules
[5/14]: configuring httpd
[6/14]: setting up ssl
[7/14]: setting up browser autoconfig
[8/14]: publish CA cert
[9/14]: creating a keytab for httpd
[10/14]: clean up any existing httpd ccache
[11/14]: configuring SELinux for httpd
[12/14]: configure httpd ccache
[13/14]: restarting httpd
[14/14]: configuring httpd to start on boot
Done configuring the web interface (httpd).
Applying LDAP updates
Restarting the directory server
Restarting the KDC
Restarting the certificate server
CA did not start in 300s

Hacky workaround is to modify /usr/share/ipa/ipa-pki-proxy.conf to use instead of localhost as confirmed by dgilmore in #freeipa. That will at least complete the install and ipa cert-show 1 works. Whether everything else works is unknown.

During processing of remaining tickets in 4.2 Backlog, this ticket was found as suitable to be fixed in the nearest bugfixing branch - which is 4.2.x.

FreeIPA 4.2.1 was released, moving to 4.2.x.

Adjusting, according to recent fix in pki.

According to https://bugzilla.redhat.com/show_bug.cgi?id=1082663#c10 the only thing to add is to add


so probably (not sure) in cainstance.py:

config.set("Tomcat", "pki_ajp_host", "::1")


  • fa3b319 Fix ipa-server-install in pure IPv6 environment

Metadata Update from @mkosek:
- Issue assigned to tkrizek
- Issue set to the milestone: FreeIPA 4.4.1

7 years ago

Login to comment on this ticket.