<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000066">
Hi List,<br>
<br>
I am using sssd (F17) with AD and what I observed is that sssd
frequently marks my AD server working and then "not working".
Symptoms:<br>
<br>
(Mon May 21 13:58:43 2012) [sssd[be[default]]]
[sdap_id_op_connect_step] (0x4000): beginning to connect<br>
(Mon May 21 13:58:43 2012) [sssd[be[default]]]
[fo_resolve_service_send] (0x0100): Trying to resolve service 'LDAP'<br>
(Mon May 21 13:58:43 2012) [sssd[be[default]]] [get_server_status]
(0x1000): Status of server 'dcpra1.XXX' is 'working'<br>
(Mon May 21 13:58:43 2012) [sssd[be[default]]] [get_port_status]
(0x1000): Port status of port 389 for server 'dcpra1.XXX' is 'not
working'<br>
(Mon May 21 13:58:43 2012) [sssd[be[default]]]
[fo_resolve_service_send] (0x0020): No available servers for service
'LDAP'<br>
<br>
Sometimes sssd does manage to connect, sometimes not.<br>
I know there is a problem with the AD controller cutting the
connection after some timeout that we can not (yet) handle
correctly, but this also happens shortly after sssd restart.<br>
<br>
Is there any explanation to this?<br>
Thanks,<br>
Ondrej<br>
<br>
</body>
</html>