[RFE] SSSD logs improvements: clarify which config option applies to each timeout in the logs

[ikerexxe]

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 8): Bug 1928648

Description of problem:
Reading SSSD logs it's not clear which config option applies to each timeout.
For better analysis of the logs it would be helpful if timeout parameter in man
pages are displayed in timeout error so that it would be easier to confirm the
parameter and customize the timeout value accordingly.

Examples:
----------------------------------------------------------------------------
(Thu Dec 31 05:47:42 2020) [sssd[be[idm.rccad.net]]] [sdap_op_timeout]
(0x1000): Issuing timeout for 5
(Thu Dec 31 05:47:42 2020) [sssd[be[idm.rccad.net]]] [sdap_op_destructor]
(0x1000): Abandoning operation 5
(Thu Dec 31 05:47:42 2020) [sssd[be[idm.rccad.net]]] [ipa_s2n_get_user_done]
(0x0040): s2n exop request failed.
(Thu Dec 31 05:47:42 2020) [sssd[be[idm.rccad.net]]] [sdap_id_op_done]
(0x0200): communication error on cached connection, moving to nex
t server
(Thu Dec 31 05:47:42 2020) [sssd[be[idm.rccad.net]]] [sdap_id_op_done]
(0x4000): too many communication failures, giving up...
(Thu Dec 31 05:47:42 2020) [sssd[be[idm.rccad.net]]] [sdap_id_op_done]
(0x4000): releasing operation connection
(Thu Dec 31 05:47:42 2020) [sssd[be[idm.rccad.net]]]
[sdap_id_release_conn_data] (0x4000): releasing unused connection
(Thu Dec 31 05:47:42 2020) [sssd[be[idm.rccad.net]]] [sdap_handle_release]
(0x2000): Trace: sh[0x55db61756160], connected[1], ops[(nil)]
, ldap[0x55db617632d0], destructor_lock[0], release_memory[0]
(Thu Dec 31 05:47:42 2020) [sssd[be[idm.rccad.net]]]
[remove_connection_callback] (0x4000): Successfully removed connection
callback.
(Thu Dec 31 05:47:42 2020) [sssd[be[idm.rccad.net]]]
[ipa_subdomain_account_done] (0x0040): ipa_get_*_acct request failed: [110]:
Connection timed out.
----------------------------------------------------------------------------

------------------------------------------------------------------------------
(Wed Dec 30 10:18:15 2020) [sssd[be[example.com]]] [sdap_process_message]
(0x4000): Message type: [LDAP_RES_EXTENDED]
(Wed Dec 30 10:18:15 2020) [sssd[be[example.com]]] [sdap_connect_done]
(0x0080): START TLS result: Server is unavailable(52), 00000000: LdapErr:
DSID-0C0912B3, comment: Error initializing SSL/TLS, data 0, v3839
(Wed Dec 30 10:18:15 2020) [sssd[be[example.com]]] [sdap_connect_done]
(0x0080): ldap_install_tls failed: [Timed out] [00000000: LdapErr:
DSID-0C0912B3, comment: Error initializing SSL/TLS, data 0, v3839]
(Wed Dec 30 10:18:15 2020) [sssd[be[example.com]]] [sdap_op_destructor]
(0x2000): Operation 1 finished
------------------------------------------------------------------------------

----------------------------------------------------------------------------
(Tue Dec 29 12:26:37 2020) [sssd[be[example.com]]]
[sssd_async_socket_init_send] (0x4000): Using file descriptor [28] for the
connection.
(Tue Dec 29 12:26:37 2020) [sssd[be[example.com]]]
[sssd_async_socket_init_send] (0x0400): Setting 6 seconds timeout for
connecting
----------------------------------------------------------------------------


Version-Release number of selected component (if applicable):
sssd-2.3.0-9.el8.x86_64


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
Timeout error does not display the corresponding timeout parameter which is
used for timeout.


Expected results:
It would be helpful if timeout parameter in man pages are displayed in timeout
error so that it would be easier to confirm the parameter and customize the
timeout value accordingly.


Additional info:

[pbrezina]

Pushed PR: #5576

• master
  • f55c41b - SSSD Log: log_timeout_parameter_display