Menu

#1655 an error occured when using moncfg rmcmon

2.6
closed
Monitoring (33)
5
2014-08-16
2011-01-17
Bin Li
No

an error occured when using moncfg on mn on AIX 71B:
bash-3.2# moncfg rmcmon hv32s38p04
ERROR::::5::mc_start_session::2::/usr/bin/lsrsrc-api: 2612-022 A session could not be established with the RMC daemon on "local_node".

   The RSCT daemon has got a core dump, and so other rmc commands are also invalid:  
bash-3.2# lscondition
/usr/sbin/rsct/bin/lsrsrc-api: 2612-022 A session could not be established with the RMC daemon on "local_node".

And in phil's suggestion,we have to restart rsct and run/usr/sbin/rsct/install/bin/recfgct to solove the problem.

Discussion

  • Ling

    Ling - 2011-01-17

    /var is full on your mn. Please add more file system spaces and reinstall RSCT.

     
  • Bin Li

    Bin Li - 2011-01-18

    Ling,
    I think maybe the file system space in /var is not the root reason. I met the issue in another 71B mn where the space in /var has 73M left, and other file systems on this mn also have free spaces.

     
  • Guang Cheng Li

    Guang Cheng Li - 2011-01-18

    Li Bin,

    The error indicates that the RMC daemon is not started on your MN. Please do some further debug and post additional useful information in the bug. I have no idea on what is going on only according to the error messages above....

    If the /var is not big enough, we can see various strange erros. A good practice is to increase the default partitions size before you install xCAT.

    If you could recreate this problem on a system that file systems are no full, please provide login information to me and I can login and take a look.

     
  • Airong Zheng

    Airong Zheng - 2011-04-01

    I can't recreate the issue in my environment with latest xCAT build. I don't know if the problem has been elimitnated in the lastest version or I am missing some part of the config, Could you try it again? And if the problem still exists, I can investigate on your node.

     
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 28 days (the time period specified by
    the administrator of this Tracker).

     
MongoDB Logo MongoDB