ipactl started to be noise and print a bunch of httplib errors to stderr. This errors are harmless and just confusing for users. ipactl polls Dogtag until the HTTP interface is up and ready to serve.
# ipactl restart Starting Directory Service Restarting krb5kdc Service Restarting kadmin Service Restarting named Service Restarting httpd Service Restarting ipa-custodia Service Restarting ntpd Service Restarting pki-tomcatd Service ipa: ERROR: httplib request failed: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ipapython/dogtag.py", line 204, in _httplib_request conn.request(method, uri, body=request_body, headers=headers) File "/usr/lib64/python2.7/httplib.py", line 1042, in request self._send_request(method, url, body, headers) File "/usr/lib64/python2.7/httplib.py", line 1082, in _send_request self.endheaders(body) File "/usr/lib64/python2.7/httplib.py", line 1038, in endheaders self._send_output(message_body) File "/usr/lib64/python2.7/httplib.py", line 882, in _send_output self.send(msg) File "/usr/lib64/python2.7/httplib.py", line 844, in send self.connect() File "/usr/lib64/python2.7/httplib.py", line 821, in connect self.timeout, self.source_address) File "/usr/lib64/python2.7/socket.py", line 575, in create_connection raise err error: [Errno 111] Connection refused ipa: ERROR: httplib request failed: ...
master:
Leaving opened in NEEDS_TRIAGE to decide if this should be backported or not. If not this can be closed as fixed and moved to 4.5.
The same issue is present on 4.4.x ?
Metadata Update from @cheimes: - Issue assigned to mbasti - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Most likely yes
Metadata Update from @mbasti: - Issue close_status updated to: None
Actually not, because in 4.4 there is no logging for that :)
Metadata Update from @mbasti: - Issue close_status updated to: fixed - Issue set to the milestone: FreeIPA 4.5 (was: 0.0 NEEDS_TRIAGE) - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.