Not digging too far into this yet, but:
(Wed Sep 20 15:48:08 2023) [sssd[be[default]]]
[dp_get_account_info_handler] (0x0200): Got request for
[0x1][BE_REQ_USER][name=pms1@default]
...
(Wed Sep 20 15:48:08 2023) [sssd[be[default]]] [sdap_print_server]
(0x2000): Searching 144.167.6.61:1389
...
(Wed Sep 20 15:48:14 2023) [sssd[be[default]]]
[generic_ext_search_handler] (0x0040): sdap_get_generic_ext_recv failed
[110]: Connection timed out
...
(Wed Sep 20 15:48:14 2023) [sssd[be[default]]] [fo_resolve_service_send]
(0x0020): No available servers for service 'LDAP'
(Wed Sep 20 15:48:14 2023) [sssd[be[default]]] [be_resolve_server_done]
(0x1000): Server resolution failed: [5]: Input/output error
(Wed Sep 20 15:48:14 2023) [sssd[be[default]]] [sdap_id_op_connect_done]
(0x0020): Failed to connect, going offline (5 [Input/output error])
(Wed Sep 20 15:48:14 2023) [sssd[be[default]]] [be_mark_offline]
(0x2000): Going offline!
It looks like you might have some LDAP servers which aren't responding
to requests, Are non-working LDAP servers still listed in your DNS? Check:
# dig -t srv
_ldap._tcp.net.ualr.edu
The IP Address which isn't responding to requests seems to be tied to
the host
opendj2a.net.ualr.edu.
On 9/20/23 16:56, Johnnie W Adams wrote:
> I've attached a tar file of the /var/log/sssd directory, which I hope
> will carry over. The logon delay is >10 seconds.