https://bugzilla.novell.com/show_bug.cgi?id=414955 Summary: syslog-ng and LDAP (slapd) cause system-locks Product: openSUSE 11.0 Version: Final Platform: i386 OS/Version: openSUSE 11.0 Status: NEW Severity: Critical Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: michael@neuweiler.biz QAContact: qa@suse.de Found By: Other Installed opensuse 11.0 in text mode server. Installed DHCP, DNS, NFS, TFTP, SAMBA, NTP, LDAP and Kerberos server. Where possible, the services use the local LDAP to store the configuration. When logrotate is called by crond.daily, the syslog and ldap seem to lock eachother: syslog-ng wants to access ldap but ldap wants to write to syslog before responding. The result is that every service that wants to write to syslog stops responding - even "su -" or "sudo" is not possible anymore. Unless you already have a shell as root open, there's no other way than to hard-reboot the server. Usually the last entry in /var/log/messages is "syslog-ng [xxx] : SIGHUP received, restarting syslog-ng". Sometimes the slapd process starts to use up all CPU cycles (but not always). The cause seems to be related with what is described in http://lists.opensuse.org/opensuse-de/2005-11/msg00129.html (german). During the installation/configuration of one of the above mentioned services, the file /etc/nssswitch.conf is modified (and a nssswitch.confbak is created). I suspect it might help if I change the line passwd_compat : ldap to passwd_compat : files ldap -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.