Ina code base far far away ... or maybe not.
... deep in the bowels of out HTTP connection backend routines ... it so
happens that we are throwing away an exception.
So here is an almost one-liner that cheered me up as it unveiled the
mystery of a client failing to join a replica.
Simo Sorce * Red Hat, Inc * New York
>From ea4b3db0054d02672fed9af5b1d0f537fb4c5076 Mon Sep 17 00:00:00 2001
From: Simo Sorce <s...@redhat.com>
Date: Tue, 18 Dec 2012 17:14:41 -0500
Subject: [PATCH] Log info on failure to connect
When multiple servers are avilable we were simply suppressing information on
why a connection failed.
Log it as 'info' so that it is possible to diagnose issues more easily.
ipalib/rpc.py | 2 ++
1 file changed, 2 insertions(+)
diff --git a/ipalib/rpc.py b/ipalib/rpc.py
index a5c5de5579903a413217afa10a7ef2dad4f1b4c4..749c0537ac736d97226a5a3d274bf96dc1afe0f2 100644
@@ -665,6 +665,8 @@ class xmlclient(Connectible):
except Exception, e:
if not fallback:
+ self.log.info('Connection to %s failed with %s' % (url, e))
serverproxy = None
if serverproxy is None:
Freeipa-devel mailing list