AnsweredAssumed Answered

NODE_ALARM_MAPRUSER_MISMATCH after change of user

Question asked by webtransactor on Jun 27, 2013
Latest reply on Jul 14, 2013 by webtransactor
I changed the user to root as described in the documentation because login to the MCS did not work with other users than mapr (PAM restrictions for non root users). But I cannot get rid of the NODE_ALARM_MAPRUSER_MISMATCH Alarms. In the logging I can see:
<pre>
2013-06-28 10:58:32,899 WARN Alarms [HB-4]: Alarm raised: NODE_ALARM_MAPRUSER_MISMATCH; Cluster: my.cluster.com; Node: mapr-node1.abg.fsc.net; Message: FileServers are configured to run as 500-200, the FileServer on this node is running as a different user.
2013-06-28 10:58:33,015 WARN Alarms [HB-3]: Alarm raised: NODE_ALARM_MAPRUSER_MISMATCH; Cluster: my.cluster.com; Node: mapr-node2.abg.fsc.net; Message: FileServers are configured to run as 500-200, the FileServer on this node is running as a different user.
</pre>
500 was the id of the mapr user the processes where running before I changed it. If I look on the system, no processes are running with this user id anymore.

Outcomes