Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Vxrail Hosts going into not responding state due to perccli vibs (71380)

Last Updated: 1/24/2021Categories: TroubleshootingTotal Views: 13347Language:
Chinese (Simplified)English

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Symptoms

Hosts going into not responding state randomly in a Vxrail environment. SSH , esxcli commands would not run.  Hosts running on 6.7 update 1 Build 11675023

Any commands run on affected hosts was giving errors -:

"cannot open shared object file Error 24ps: error while loading shared libraries: libz.so.1: cannot open shared object file : Error 24"

OSError : [Errno 24] Too many open files: '/lib64/python3.5/site-packages/vmsupport/encryption.pyc

The "esxcli "commands returns following errors -:

Got no data from process: python /usr/lib/vmware/vsan/esxcli/esxcli_vsan_debug.pyc sync.summary

The vmkernel logs filled with -:

Open file limit 65536 exceeded

A large number of "percli" processes running as per uwstats and ps commands.

#uwstats | grep -i perccli
58802654         perccli.64201508    4      w   7   8  256   0   0       2   2  4096
58802683         perccli.64201550    4      w   7   8  256   0   0       2   2  4096
58802772         perccli.64201664    4      w   7   8  256   0   0       2   2  4096
58802806         perccli.64201716    4      w   7   8  256   0   0       2   2  4096
58802896         perccli.64201827    4      w   7   8  256   0   0       2   2  4096
58802966         perccli.64201912    4      w   7   8  256   0   0       2   2  4096
58803099         perccli.64202075    4      w   7   8  256   0   0       2   2  4096
58803469         perccli.64202518    4      w   7   8  256   0   0       2   2  4096
58803557         perccli.64202629    4      w   7   8  256   0   0       2   2  4096

vsanmgmt.log was filled with following errors -:

2019-08-14T02:42:56Z VSANMGMTSVC: ERROR vsanperfsvc[38a43808-be3d-11e9] [VsanEsxHclUtil::__init__] Failed to run tool perccli: Running storcli failed: b'/opt/lsi/perccli/perccli: error while loading shared libraries: libm.so.6: cannot open shared object file: Error 24\n'
2019-08-14T02:44:01Z VSANMGMTSVC: INFO vsanperfsvc[5f5097e2-be3d-11e9] [VsanStorcli::_runStorcli] Running: /opt/lsi/perccli/wrapperperccli ++group=host/vim/tmp /call show J
2019-08-14T02:44:01Z VSANMGMTSVC: ERROR vsanperfsvc[5f5097e2-be3d-11e9] [VsanEsxHclUtil::__init__] Failed to run tool perccli: Running storcli failed: b'/opt/lsi/perccli/perccli: error while loading shared libraries: libm.so.6: cannot open shared object file: Error 24\n'
2019-08-14T02:46:12Z VSANMGMTSVC: INFO vsanperfsvc[ad4a8080-be3d-11e9] [VsanStorcli::_runStorcli] Running: /opt/lsi/perccli/wrapperperccli ++group=host/vim/tmp /call show J

2019-08-14T02:46:32Z VSANMGMTSVC: ERROR vsanperfsvc[ad4a8080-be3d-11e9] [VsanEsxHclUtil::__init__] Failed to run tool perccli: Exception 'RunCommandError' occured running command '['/opt/lsi/perccli/wrapperperccli', '++group=host/vim/tmp', '/call', 'show', 'J']'
2019-08-14T02:47:17Z VSANMGMTSVC: INFO vsanperfsvc[d42a7ffe-be3d-11e9] [VsanStorcli::_runStorcli] Running: /opt/lsi/perccli/wrapperperccli ++group=host/vim/tmp /call show J
2019-08-14T02:52:43Z VSANMGMTSVC: INFO vsanperfsvc[9685f45a-be3e-11e9] [VsanStorcli::_runStorcli] Running: /opt/lsi/perccli/wrapperperccli ++group=host/vim/tmp /call show J
2019-08-14T02:52:43Z VSANMGMTSVC: ERROR vsanperfsvc[9685f45a-be3e-11e9] [VsanEsxHclUtil::__init__] Failed to run tool perccli: Running storcli failed: b'/opt/lsi/perccli/perccli: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: Error 24\n'
2019-08-14T02:54:54Z VSANMGMTSVC: INFO vsanperfsvc[e41310fe-be3e-11e9] [VsanStorcli::_runStorcli] Running: /opt/lsi/perccli/wrapperperccli ++group=host/vim/tmp /call show J
2019-08-14T02:54:54Z VSANMGMTSVC: ERROR vsanperfsvc[e41310fe-be3e-11e9] [VsanEsxHclUtil::__init__] Failed to run tool perccli: Running storcli failed: b'/opt/lsi/perccli/perccli: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: Error 24\n'

Cause

Incompatible perccli vibs running on ESXi hosts in the Vxrail vsan cluster.
The hosts were running on 330mini adapter which does not need the perccli vib.
Incompatible Vxrail version .

Impact / Risks

Hosts randomly going into not responding state may impact production (CPU, memory, and storage) and cause DU (Data Unavailability) situation.

Resolution

The issue is resolved in the VxRail version 4.7.211 and later ( confirmed by DELL-EMC )

Workaround

Uninstall perccli vibs from all the ESXi hosts in the Vxrail vsan cluster.

# esxcli software vib remove -n vmware-perccli-007.0529.0000.0000
Removal Result
Message: Operation finished successfully.
Reboot Required: false
VIBs Installed:
VIBs Removed: LSI_bootbank_vmware-perccli-007.0529.0000.0000_007.0529.0000.0000-01
VIBs Skipped:

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
vCenter Server を 6.7 P02 にアップグレードした後、Skyline Health オンライン チェックの実行が停止する (79457)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
NSX-T DFW가 Challenge ACK를 올바르게 처리하지 않음 (84299)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSAN

Related Versions:

Take Our Survey

Support Assistant