CIM monitoring applications fail to authenticate to an ESXi host after several days of use
search cancel

CIM monitoring applications fail to authenticate to an ESXi host after several days of use

book

Article ID: 341986

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • Monitoring applications that connect directly to the ESXi Common Information Model (CIM) system work initially, but begin to receive authentication errors after a few days
  • The ESXi host does not allow connections from monitoring tools
  • In the \var\log\syslog.log file, you see entries similar to:

    01-12T10:48:32Z openwsmand: pam_per_user: create_subrequest_handle(): creating new subrequest (user="<application_user_name>", service="system-auth-generic")
    01-12T10:48:32Z openwsmand: PAM unable to dlopen(/lib/security/$ISA/pam_unix.so): libcrypt.so.1: cannot map zero-fill pages: No space left on device
    01-12T10:48:32Z openwsmand: PAM adding faulty module: /lib/security/$ISA/pam_unix.so
    01-12T10:48:33Z openwsmand: pam_per_user: create_subrequest_handle(): doing map lookup for user "<application_user_name>"
    01-12T10:48:33Z openwsmand: pam_per_user: create_subrequest_handle(): creating new subrequest (user="<application_user_name>", service="system-auth-generic")
    01-12T10:48:33Z openwsmand: PAM unable to dlopen(/lib/security/$ISA/pam_unix.so): libcrypt.so.1: failed to map segment from shared object: No space left on device
    01-12T10:48:33Z openwsmand: PAM adding faulty module: /lib/security/$ISA/pam_unix.so

    Note: application_user_name in the log output is the username which this software is configured to authenticate.

  • The consumed memory of the resource group host/vim/vmvisor/wsman is approaching its limit.

    To view the current consumed memory for this resource group:
    1. Log in to the host directly using the vSphere Client.
    2. Select the Performance tab.
    3. Select Advanced View and click Chart Options.
    4. Select System > Real Time and select host/vim/vmvisor/wsman.
    5. Under the Counters option, select Resource Memory.
    6. Click OK.
Note: The default allocation for this resource group is 20MB. If the consumed memory is approaching this limit, this article may apply.


Environment

VMware vSphere ESXi 5.1
VMware ESXi 4.1.x Embedded
VMware vSphere ESXi 5.0
VMware ESXi 4.1.x Installable

Resolution

This is a known issue affecting VMware ESXi 5.0.x and 5.1.x.

This issue is resolved in:

To work around this issue, restart the wsman service using the command:

#/etc/init.d/wsman restart







Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box

VMware ESXi 5.1, Patch Release ESXi510-201307001
VMware ESXi 5.0, Patch Release ESXi500-201308001

Powered by Wolken Software