URL: https://github.com/SSSD/sssd/pull/112
Author: justin-stephenson
Title: #112: FAILOVER: Improve port status log messages
Action: opened
PR body:
"""
This PR is created to ensure administrators do not follow the wrong path
troubleshooting issues, especially with messages such as:
`Port status of port 636 for server 'server' is 'not working'`
This patch should help to clarify that there is no direct relationship between
port status and actual networking status.
"""
To pull the PR as Git branch:
git remote add ghsssd https://github.com/SSSD/sssd
git fetch ghsssd pull/112/head:pr112
git checkout pr112
From 945efeff38fc0e2a39cc4465caf9420f658889f1 Mon Sep 17 00:00:00 2001
From: Justin Stephenson <jstep...@redhat.com>
Date: Mon, 19 Dec 2016 16:49:17 -0500
Subject: [PATCH] FAILOVER: Improve port status log messages
It should be more clear to users that SSSD port status does not
correlate with networking port status.
---
src/providers/fail_over.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/src/providers/fail_over.c b/src/providers/fail_over.c
index 7708409..4c27af6 100644
--- a/src/providers/fail_over.c
+++ b/src/providers/fail_over.c
@@ -372,6 +372,11 @@ get_port_status(struct fo_server *server)
struct timeval tv;
time_t timeout;
+ DEBUG(SSSDBG_CONF_SETTINGS,
+ "Port status is used for internal SSSD state handling only, "
+ "there is no link between SSSD internal state and system "
+ "networking state.");
+
DEBUG(SSSDBG_TRACE_LIBS,
"Port status of port %d for server '%s' is '%s'\n", server->port,
SERVER_NAME(server), str_port_status(server->port_status));
_______________________________________________
sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org
To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org
