Topic
2 replies Latest Post - ‏2012-02-13T09:53:29Z by xf00657
xf00657
xf00657
92 Posts
ACCEPTED ANSWER

Pinned topic 2602 - 346 RMC could not be refreshed.

‏2012-02-09T12:12:53Z |
Hello,
preparing a new Linux Cluster I always get the message after preprpnode ... command:

RMC could not be refreshed.

I ran /usr/sbin/rsct/install/bin/recfgct (and also with -s option), but withou success.
No idea how I could solve this.
Could you help?
Regards
Rüdiger
Updated on 2012-02-13T09:53:29Z at 2012-02-13T09:53:29Z by xf00657
  • Enrico_Joedecke
    Enrico_Joedecke
    92 Posts
    ACCEPTED ANSWER

    Re: 2602 - 346 RMC could not be refreshed.

    ‏2012-02-09T17:21:57Z  in response to xf00657
    Hello Ruediger,

    according to the message reference of RSCT, there should be an additional 'code', that explains the problem in more detail:

    > 2602-346 RMC could not be refreshed.
    > Explanation: The RMC refresh to configure the latest
    > access control changes was not successful. The
    > updates are not in effect.
    > User response: Fix the error indicated by code and
    > run the command again.

    If this does not provide further informatin, please check the file /var/ct/cfg/ctrmc.acls - this is where the nodes specified with 'preprpnode' are inserted to. If the file is healthy and the node information is included, use 'refresh -s ctrmc' to refresh the RMC.

    Enrico
    • xf00657
      xf00657
      92 Posts
      ACCEPTED ANSWER

      Re: 2602 - 346 RMC could not be refreshed.

      ‏2012-02-13T09:53:29Z  in response to Enrico_Joedecke
      Hello Enrico,

      its seems that the file is correct. It also seems that we have problems using Perl and / or security on this for lpars. This could be the reason for the error messages. Issuing directly under "root" runs withot errors.
      Thanks!

      Rüdiger