ldap_result() failed: Can't contact LDAP server
Package: nslcd I have upgraded from Debian 11 to Debian 12. The problem is that I keep getting the below errors in the syslog... 893:2024-02-29T16:30:13.055665+00:00 hostname-shaheena nslcd[7712]: [d062c2] ldap_start_tls_s() failed (uri=ldap:// 127.0.0.1:389/): Can't contact LDAP server: Transport endpoint is not connected 894:2024-02-29T16:30:13.055747+00:00 hostname-shaheena nslcd[7712]: [d062c2] failed to bind to LDAP server ldap:// 127.0.0.1:389/: Can't contact LDAP server: Transport endpoint is not connected 1423:2024-03-01T09:08:08.473189+00:00 hostname-shaheena nslcd[24301]: [8b4567] ldap_start_tls_s() failed (uri=ldap:// 127.0.0.1:389/): Can't contact LDAP server: Transport endpoint is not connected 1424:2024-03-01T09:08:08.473204+00:00 hostname-shaheena nslcd[24301]: [8b4567] failed to bind to LDAP server ldap:// 127.0.0.1:389/: Can't contact LDAP server: Transport endpoint is not connected 1648:2024-03-01T09:09:08.556456+00:00 hostname-shaheena nslcd[36935]: [8b4567] ldap_start_tls_s() failed (uri=ldap:// 127.0.0.1:389/): Can't contact LDAP server: Transport endpoint is not connected 1649:2024-03-01T09:09:08.556475+00:00 hostname-shaheena nslcd[36935]: [8b4567] failed to bind to LDAP server ldap:// 127.0.0.1:389/: Can't contact LDAP server: Transport endpoint is not connected 1651:2024-03-01T09:09:08.668341+00:00 hostname-shaheena nslcd[36935]: [7b23c6] ldap_start_tls_s() failed (uri=ldap:// 127.0.0.1:389/): Can't contact LDAP server: Transport endpoint is not connected 1652:2024-03-01T09:09:08.668363+00:00 hostname-shaheena nslcd[36935]: [7b23c6] failed to bind to LDAP server ldap:// 127.0.0.1:389/: Can't contact LDAP server: Transport endpoint is not connected My nslcd.conf looks like below: # /etc/nslcd.conf # nslcd configuration file. See nslcd.conf(5) # for details. # The user and group nslcd should run as. uid nslcd gid nslcd uri ldap://127.0.0.1:389/ binddn cn=ldap_login,ou=people,dc=subdomain,dc=domain,dc=com bindpw xxx ldap_version 3 base ou=people,dc=subdomain,dc=domain,dc=com ssl start_tls tls_reqcert never cat /etc/nsswitch.conf # /etc/nsswitch.conf gshadow:files hosts: files dns networks: files protocols: db files services: db files ethers: db files rpc:db files passwd:compat ldap group: compat ldap shadow:compat ldap netgroup: nis ldap All the services are up and running fine. Only thing is I am not able to figure out what is causing these messages in the syslog. Can u guys help me understand this ?
Temporary failure in name resolution
Package: ntpsec Hello, we were using Bullseye and have upgraded to Bookworm. With Bookworm, we have ntpsec. The package is installed successfully and the service looks good. But the syslog is filled with below messages: 2024-03-06T14:58:11.724851+05:30 hostname-shaheena ntpd[35823]: DNS: dns_check: DNS error: -3, Temporary failure in name resolution 2024-03-06T14:58:11.724862+05:30 hostname-shaheena ntpd[35823]: DNS: dns_take_status: None=>temp, 3 2024-03-06T14:58:19.572547+05:30 hostname-shaheena ntpd[35823]: DNS: dns_probe: None, cast_flags:1, flags:20801 2024-03-06T14:58:19.588607+05:30 hostname-shaheena ntpd[35823]: DNS: dns_check: processing None, 1, 20801 In ntp.conf the server is always set to None. We keep it to None always. In bullseye it never gave any such messages in the syslog.. even though the server was None. But with Bookworm, it gives the above messages in syslog. When I change the server to the ntp server name in the ntp.conf file... I don't see these messages in the syslog. Am I missing any configurations or anything else.. How can get rid of these messages in syslog Any help will be appreciated. Thanks Regards, SK
OpenSSL 3.0 support for Debian11
Hello Team, We are using Debian 11 with OpenSSL 1.1.1n As OpenSSL 1.1.1 series is going EOL on 11th September 2023. We would like to know if Debian is planning to add OpenSSL 3.0 support on Debian 11 any time soon. Regards,
