Hi Matthew,
Unfortunately I get the same error as originally reported when using the lp1921494-test patches for SSSD.
# apt-cache policy sssd | grep Installed
Installed: 2.2.3-3ubuntu0.7+lp1921494v20211011b2
systemctl stop sssd
rm -rf /var/lib/sss/db/*
systemctl start sssd
systemctl status sssd - Could not start TLS encryption. (unknown error code)
Attached is also a washed debug level 4 sssd.log from the startup of sssd with the patchset applied.
Something I see is that my logs complains about connecting to port 389, whereas Snakekicks recent log tries connecting to port 636 "marking port 636 to server x as not working".
Hi Matthew, 7+lp1921494v202 11011b2
Unfortunately I get the same error as originally reported when using the lp1921494-test patches for SSSD.
# apt-cache policy sssd | grep Installed
Installed: 2.2.3-3ubuntu0.
systemctl stop sssd
rm -rf /var/lib/sss/db/*
systemctl start sssd
systemctl status sssd - Could not start TLS encryption. (unknown error code)
Attached is also a washed debug level 4 sssd.log from the startup of sssd with the patchset applied.
Something I see is that my logs complains about connecting to port 389, whereas Snakekicks recent log tries connecting to port 636 "marking port 636 to server x as not working".