Is your unreclaimable SLAB usage on CentOS 8 growing when running the Check_MK
agent on it? See Werk#10070
We have seen cases in which the parameter “KillMode=process” of the unit file
“check_mk@.service” causes a memory leak. […]
To fix this, the parameter “KillMode=process” was changed to “Type=forking”.
Playing with FreeIPA? Recreating the CA? Firefox complaining about
SEC_ERROR_REUSED_ISSUER_AND_SERIAL? Can’t find the certificate via Preferences
/ Privacy & Security / Certificates?
Migrating from MySQL to MariaDB on Ubuntu? MariaDB not starting? There may be an
old AppArmor Profile in the way. Or mysql.service and mariadb.service may both
be enabled.
While Active Directory permits SASL binds to be performed on an SSL/TLS-protected connection, it does not permit the use of SASL-layer encryption/integrity verification mechanisms on such a connection.
Also passing -O "maxssf=0,minssf=0" to ldapsearch works for me.
Trying to use -Y GSSAPI when ldapsearching Active Directory and getting:
SASL/GSSAPI authentication started
ldap_sasl_interactive_bind_s: Local error (-2)
additional info: SASL(-1): generic failure: GSSAPI Error: An invalid name was supplied (Success)
Does the host’s IP address you try to connect to not resolve back to it’s
name, for example:
ldapsearch -H ldap://gc.local/
gc.local has address 192.168.0.1
1.0.168.192.in-addr.arpa domain name pointer foo.local.
foo.local has address 192.168.0.1
Try using the other name: ldapsearch -H ldap://foo.local/