https://bugzilla.novell.com/show_bug.cgi?id=336020 Summary: resmgrd graps 100% cpu, no local login fails (remote via ssh still works) Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: SLES 10 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: lauffer@ph-freiburg.de QAContact: qa@suse.de Found By: Beta-Customer Hello! Note: This is a sles-10-sp1, not opensuse-10.3 bugreport... The system: ----------- We've set up a sles10-sp1 and customized its nss with nss_ldap support. We don't need nss_ldap for logins into the system but (only) to grant some access to samba shares with the "valid user" option there. We use local accounts (in /etc/passwd...shadow...group) for the few sysadmins. We don't need the nss_ldap setup for login, ssh... we just use/need them for setting samba access... The problem: ------------ Now we recognized that we've no chance to login into the system via console. The system checks successfully for right or wrong password and if pw ok it prints the welcome message but no bash will be started. Instead the resmgrd graps 100% cpu for some seconds and during this period the login "hangs"... and than suddenly resmgrd is idle again and the login timed out. Well, waht I guess is that resmgrd-and-no-local-login problem is in conjunction with the nss_ldap environment here. F.e. it takes a very long time to resolve...: time id lauffer uid=201(lauffer) gid=100(users) groups=100(users), 16(dialout), 33(video), 206(webadmins) real 2m31.601s user 2m19.289s sys 0m1.672s What works: ----------- Login into the system via ssh... So what's todo? My question is how can I customize the system that I can login again into the system from console? Can't we prepare the sles that it will grant the access even nss_ldap (or whatever is resonsible for the problem?) fails or timed out? Thank you very much for your help! -- 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.