diff options
| author | Justin Stephenson <jstephen@redhat.com> | 2016-12-19 16:49:17 -0500 |
|---|---|---|
| committer | Jakub Hrozek <jhrozek@redhat.com> | 2017-02-06 16:17:29 +0100 |
| commit | 1c7f9a676088ecee4c14df14b8688b391fb32a05 (patch) | |
| tree | 11ab2580f7e0b3845680357a2b31824197ce46be | |
| parent | cb831fbbcb0dac8b6202037d4cd1a0d82db54f54 (diff) | |
| download | sssd-1c7f9a676088ecee4c14df14b8688b391fb32a05.tar.gz sssd-1c7f9a676088ecee4c14df14b8688b391fb32a05.tar.xz sssd-1c7f9a676088ecee4c14df14b8688b391fb32a05.zip | |
FAILOVER: Improve port status log messages
It should be more clear to administrators that when SSSD internal
port status is set as PORT_NOT_WORKING, this does not directly relate
to an assumed network port-related issue.
Reviewed-by: Jakub Hrozek <jhrozek@redhat.com>
| -rw-r--r-- | src/providers/fail_over.c | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/src/providers/fail_over.c b/src/providers/fail_over.c index 5d3c26d4a..168e59d6f 100644 --- a/src/providers/fail_over.c +++ b/src/providers/fail_over.c @@ -376,12 +376,18 @@ get_port_status(struct fo_server *server) "Port status of port %d for server '%s' is '%s'\n", server->port, SERVER_NAME(server), str_port_status(server->port_status)); + if (server->port_status == PORT_NOT_WORKING) { + DEBUG(SSSDBG_MINOR_FAILURE, "SSSD is unable to complete the full " + "connection request, this internal status does not necessarily " + "indicate network port issues.\n"); + } + timeout = server->service->ctx->opts->retry_timeout; if (timeout != 0 && server->port_status == PORT_NOT_WORKING) { gettimeofday(&tv, NULL); if (STATUS_DIFF(server, tv) > timeout) { DEBUG(SSSDBG_CONF_SETTINGS, - "Reseting the status of port %d for server '%s'\n", + "Resetting the status of port %d for server '%s'\n", server->port, SERVER_NAME(server)); server->port_status = PORT_NEUTRAL; server->last_status_change.tv_sec = tv.tv_sec; |