<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 06/09/2014 09:07 AM, Gianluca Cecchi
wrote:<br>
</div>
<blockquote
cite="mid:CAG2kNCx-SsQB9aqrW1euKVhmomiZ6qsz57YtX+nAU77sBFRkgA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Mon, Jun 9, 2014 at 3:11 PM, Vu
Pham <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:vu@sivell.com" target="_blank">vu@sivell.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
System: RHEL 6.5<br>
<br>
Although I can log in to non-root users via ssh, I cannot
su to any users, root or non-root. When using su, after
typing in the user name, the su command just hangs there
without the password prompt.<br>
<br>
When trying to login from the console, the password prompt
never shows, and after a few minutes, the screen is
cleared and the login prompt shows again.<br>
I cannot log in to root via ssh, because it is disabled by
the sshd config file.<br>
<br>
<br>
top shows dbus-daemon get %100 CPU.<br>
<br>
Any help is greatly appreciated.<br>
<br>
Thanks,<br>
Vu<br>
<br>
</blockquote>
<div><br>
</div>
<div>Do you have ldap configured on your system perhaps?</div>
<div>In that case you could have a problem with it causing
the problem...</div>
<div>because messagebus runs as dbus local user</div>
<div><br>
</div>
<div>In that case, if not already there, you could put
inside /etc/nslcd.conf a line to ignore group membership
lookups for dbus</div>
<div><br>
</div>
<div>nss_initgroups_ignoreusers root,ldap,named,.....,dbus</div>
<div><br>
</div>
<div>the "...." above is to be substituted with a comma
seprated list of other local users you want not to make
lookup for.</div>
<div><br>
</div>
<div>if you can make that change you can start in single
user mode and change from there.</div>
<div>Also, during boot you could have problems with
messagebus service to start and proceed the boot because
of this.</div>
<div>There are other parameters to tune config files in case
of problems with ldap.... if this is the problem</div>
<div><br>
</div>
<div>HIH,</div>
<div>Gianluca</div>
<div> <br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Gianluca, <br>
<br>
Thank you for your reply. <br>
No, I do not use ldap on this server. This server just uses the
default login with the default settings of pam.d.<br>
<br>
Vu<br>
</body>
</html>