On 9/28/2010 at 04:11 PM, Yan Gao <[email protected]> wrote:
> On 09/28/10 01:25, Phil Armstrong wrote:
> > I'm running pacemaker-1.1.2-0.6.1 on sles11sp1. I was only able to
> > successfully login to the crm_gui from one of my nodes in spite of the
> > fact that the login parameters appeared to be identical. I traced the
> > problem to a zero length /etc/pam.d/hbmgmt file on the node that
> > exhibited the login failure. This file is part of
> > pacemaker-mgmt-2.0.0-0.3.10, which I have installed on both nodes.
> >
> > I had no previous knowledge of this file and so I am quite sure it
> > wasn't anything I did consciously to zero out the file, or to
> > consciously populate it with the contents of the working node:
> >
> > #%PAM-1.0
> > auth include common-auth
> > account include common-account
> >
> >
> > Can anyone tell me how this file is created or modified ?
> The file is extracted from pacemaker-mgmt on package installation.
> The back-end of the GUI (mgmtd) reads it for user authentication.
> No one is supposed or needs to modify the file for any reason.
>
> So that's strange it was zeroed out. You might need to check the
> modification time to recall what was happening.
Wild guess - was your system STONITH'd or otherwise forcibly reset,
immediately after installing pacemaker-mgmt, and are you using XFS
for your root filesystem?
Regards,
Tim
The scenario you present is very plausible. I can't say for sure how soon after
installation the machine was reset, but it could very well have happened that
way. I should know better than to reset with sync'ing.
Thanks, Phil
--
Phil Armstrong [email protected]
Phone: 651-683-5561 VNET 233-5561
_______________________________________________
Pacemaker mailing list: [email protected]
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
