''s profileKT' Cheung's Space 【 张智波...PhotosBlogListsMore Tools Help

Blog


    March 24

    建立快照后导致存储空间不足而提示需要redo log error问题

    ESX上的VM由于建立了快照后,长期不对该VM进行监测而导致整个LUN空间被占满,
    VI Client中出现错误提示:No more space for the redo log error when attempting to start a virtual machine.
     
    解决方案, VMware KB:1002103
     
    另外, 假如想将虚拟机的快照文件保存到其他LUN中去, 可以采用以下解决方案:
     
    FYI.
     
    ~.~
    March 16

    Defunct cimservera processes seen on VMware ESX 3.5 running hardware management agents

    Details

    Note: This issue is not specific to certain management agents.
     
    This issue was observed to happen on idling VMware ESX hosts with hardware management agents installed and discovered by their corresponding management application. A high number of the defunct processes could result in various symptoms resulting from the VMware ESX service console failing to spawn new processes.
     
    Symptoms include:
    • Unable to log in through SSH to the ESX host.
    • Unable to log in on the local service console.
    • HA errors.
    If you are able to log in to the service console, you can verify this issue using the following command, which might show from a few up to thousands of cimservera defunct processes:
     
    # ps -ef 
    root 6232 0.0 0.0 0 0 ? Z Sep24 0:00 [cimservera <defunct>]
    root 6377 0.0 0.0 0 0 ? Z Sep24 0:00 [cimservera <defunct>]
    root 6496 0.0 0.0 0 0 ? Z Sep24 0:00 [cimservera <defunct>]
     
     
    In addition, /var/log/messages shows the failed logins:

    Nov 17 18:29:32 blr-cpd-018 cimservera[505]: user "root" failed to authenticate
    Nov 17 18:29:34 blr-cpd-018 cimservera[506]: user "root" failed to authenticate
    Nov 17 18:29:36 blr-cpd-018 cimservera[507]: user "root" failed to authenticate
    Nov 17 18:29:39 blr-cpd-018 cimservera[508]: user "root" failed to authenticate

    Solution
     
    If the failed login attempts are the result of misconfigured credentials in the management application, correct this problem first before proceeding to prevent further degradation.
     
    Restart the pegasus process to clear the defunct cimservera processes. Use the following command at the service console:

    # service pegasus restart
     
    If you are unable to log in to the service console as a result of this problem, there are two alternatives:
    • Re-try logging in. Subsequent login attempts might succeed.
    • Shut down all virtual machines running on that host through the guest operating system's remote desktop or equivalent facility, and then hard reset the ESX host.
    Note: This issue is fixed in VMware ESX 3.5, Patch ESX350-200901407-BG: Updates Pegasus (KB 1006657).