#5292 Installing ipa-server package breaks httpd
Closed: Fixed Opened by pvoborni.

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

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

Description of problem:
After installing ipa-server package, service httpd fails to start.
Version-Release number of selected component (if applicable):
ipa-server-4.2.0-5.el7.x86_64
httpd-2.4.6-38.el7.x86_64
How reproducible:
always
Steps to Reproduce:
1. install clean server
2. yum install httpd ipa-server -y
3. service httpd start
Actual results:
# service httpd start
Redirecting to /bin/systemctl start  httpd.service
Job for httpd.service failed because the control process exited with error
code. See "systemctl status httpd.service" and "journalctl -xe" for details.
Journal:
Sep 10 11:09:30 vm-167.abc.idm.lab.eng.brq.redhat.com systemd[1]: Starting The Apache HTTP Server...
-- Subject: Unit httpd.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit httpd.service has begun starting up.
Sep 10 11:09:32 vm-167.abc.idm.lab.eng.brq.redhat.com ipa-httpd-kdcproxy[29231]: ipa         : ERROR    Unknown error while retrieving setting from ldap://localhost:389: Timeout exceeded
Sep 10 11:09:32 vm-167.abc.idm.lab.eng.brq.redhat.com ipa-httpd-kdcproxy[29231]: Traceback (most recent call last):
Sep 10 11:09:32 vm-167.abc.idm.lab.eng.brq.redhat.com ipa-httpd-kdcproxy[29231]: File "/usr/libexec/ipa/ipa-httpd-kdcproxy", line 83, in _ldap_con
Sep 10 11:09:32 vm-167.abc.idm.lab.eng.brq.redhat.com ipa-httpd-kdcproxy[29231]: self.con.do_bind(timeout=self.time_limit)
Sep 10 11:09:32 vm-167.abc.idm.lab.eng.brq.redhat.com ipa-httpd-kdcproxy[29231]: File "/usr/lib/python2.7/site-packages/ipapython/ipaldap.py", line 1617, in do_bind
Sep 10 11:09:32 vm-167.abc.idm.lab.eng.brq.redhat.com ipa-httpd-kdcproxy[29231]: self.do_external_bind(pw_name, timeout=timeout)
Sep 10 11:09:32 vm-167.abc.idm.lab.eng.brq.redhat.com ipa-httpd-kdcproxy[29231]: File "/usr/lib/python2.7/site-packages/ipapython/ipaldap.py", line 1607, in do_external_bind
Sep 10 11:09:32 vm-167.abc.idm.lab.eng.brq.redhat.com ipa-httpd-kdcproxy[29231]: self.__bind_with_wait(self.external_bind, timeout, user_name)
Sep 10 11:09:32 vm-167.abc.idm.lab.eng.brq.redhat.com ipa-httpd-kdcproxy[29231]: File "/usr/lib/python2.7/site-packages/ipapython/ipaldap.py", line 1596, in __bind_with_wait
Sep 10 11:09:32 vm-167.abc.idm.lab.eng.brq.redhat.com ipa-httpd-kdcproxy[29231]: self.__wait_for_connection(timeout)
Sep 10 11:09:32 vm-167.abc.idm.lab.eng.brq.redhat.com ipa-httpd-kdcproxy[29231]: File "/usr/lib/python2.7/site-packages/ipapython/ipaldap.py", line 1582, in __wait_for_connection
Sep 10 11:09:32 vm-167.abc.idm.lab.eng.brq.redhat.com ipa-httpd-kdcproxy[29231]: wait_for_open_ports(host, int(port), timeout)
Sep 10 11:09:32 vm-167.abc.idm.lab.eng.brq.redhat.com ipa-httpd-kdcproxy[29231]: File "/usr/lib/python2.7/site-packages/ipapython/ipautil.py", line 1180, in wait_for_open_ports
Sep 10 11:09:32 vm-167.abc.idm.lab.eng.brq.redhat.com ipa-httpd-kdcproxy[29231]: raise socket.timeout("Timeout exceeded")
Sep 10 11:09:32 vm-167.abc.idm.lab.eng.brq.redhat.com ipa-httpd-kdcproxy[29231]: timeout: Timeout exceeded
Sep 10 11:09:32 vm-167.abc.idm.lab.eng.brq.redhat.com ipa-httpd-kdcproxy[29231]: ipa         : ERROR    Unknown error while retrieving setting from ldap://localhost:389: Timeout exceeded
Sep 10 11:09:32 vm-167.abc.idm.lab.eng.brq.redhat.com systemd[1]: httpd.service: control process exited, code=exited status=1
Sep 10 11:09:32 vm-167.abc.idm.lab.eng.brq.redhat.com systemd[1]: Failed to start The Apache HTTP Server.
Expected results:
httpd service starts normally

I've posted a patch on the mailing list.

I'm a bit puzzled because I tested the same scenario when I was working on the feature. I'm like 90% sure I had the problem covered.

master:

  • a3d077443fc7f15c005f86aeed40443d0a0843a1 Handle timeout error in ipa-httpd-kdcproxy

ipa-4-2:

  • 1464437ca2a1bb18fd6468e673ae7589e4d4216f Handle timeout error in ipa-httpd-kdcproxy

Metadata Update from @pvoborni:
- Issue assigned to cheimes
- Issue set to the milestone: FreeIPA 4.2.2

Metadata