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

VMware Cloud Foundation for Service Providers 2.3 SOS utility crashes while collecting logs for ESXi hosts (52383)

Last Updated: 7/3/2018Categories: InformationalTotal Views: 2871Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The SOS log collection tool is not completing successfully.

The SOS  process is terminated with an error message  similar  to

./sos: line 13: 31845 Killed $path $CURRENT_PATH/sos.pyc $@

Cause

This issue occurred when the SOS tool is not able to connect to one of the  VMware Cloud Foundation for Service Providers components (PSC, NSX, vCenter, Esxi,..), due to a network  issue, or the SDDC Manager  isn't able to ssh nor  to run API calls to one of the components.

The SOS  tool will keep trying to connect to the unreachable  components, and won't timeout until the SOS process gets killed by the Linux Kernel to prevent the  SDDC Manager VM from running out of memory.

The kernel will begin killing processes to free up RAM when a linux machine runs low on memory.This is called the OOM Killer.(OOM stands for out of memory).

Example:

The several ESXi Host are showing as unreachable when running the ./sos --Health-Check

---- -+---------------------------+--------------------------+------------------------
| SL# | Area                        | Title                        | State                    |
+-----+---------------------------+--------------------------+------------------------
| 1     | ESXI : 10.63.17.18  | Connectivity status | UNREACHABLE |
| 2    | ESXI : 10.63.8.109   | Connectivity status | UNREACHABLE |
| 3     | ESXI : 10.63.8.99    | Connectivity status | UNREACHABLE |

Not able to SHH to the hosts due to:

SSH service is disable on the hosts.

Network is down.

The Esxi Host root password was change outside of the SDDC Manager.

Resolution

This is currently a known issue affecting VMware Cloud Foundation for Service Providers. This issue is resolved in in VMware Cloud Foundation Service Provider 2.4.

Workaround

****Please Note: This Workaround is only valid for VMware Cloud Foundation Service Providers version 2.3****

Workaround for  customers  on VMware Cloud Foundation for Service Providers 2.3 and are unable to update to  2.4

To workaround this issue we need to recreate the progressreporter.pyc  file  located on the SDDC Manager  VM  Path: /opt/vmware/sddc-support/utils/progressreporter.pyc ) using the progressreporter.py file  which is attached to this KB.

The new progressreporter.pyc file  will contain the compiled code that prevents the kernel from killing sos utility. The fix  will cause the sos process to timeout and bypath the unreachable component, instead of getting terminated by the  Linux Kernel.

Steps to recreate the progressreporter.pyc file:

Run command cp -rp /opt/vmware/sddc-support /tmp    to backup of sddc-support to /tmp

Go to /tmp/sddc-support/utils     cd /tmp/sddc-support/utils

a. Run rm progressreporter.pyc   to remove the progressreporter.pyc file
b. Run vi progressreporter.py  this will open a new file.
c. Click ( i ) to insert the text .
d. Open attached progressreporter.py file on this KB, and copy the content to the new progressreporter.py file.
e. To save the change  press ( ESC ), then type    (   :wq   )

Run SOS log collection from  tmp directory   /tmp/sddc-support/sos  to test the SOS log collection process.

After first SOS run  the new progressreporter.pyc will be created with the latest compiled code.

Remove /tmp/sddc-support/utils/progressreporter.py  by running  rm /tmp/sddc-support/utils/progressreporter.py

If the SOS log completed successfully,  then  run mv /opt/vmware/sddc-support /opt/vmware/sddc-support-golden-copy to preserve the copy of code which came with build.

Run  mv /tmp/sddc-support /opt/vmware   to move the SDDC-Support from the tmp directory to its original location,

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

progressreporter.py

Additional Resources

KB
•
将 VMware Cloud Foundation 升级到版本 2.3 后，“VDI 工作流：配置 Horizon View Cloud Pod 架构”的任务挂起 (52397)

KB
•
如何从 VMware Cloud Foundation LCM 清单中移除对 ESXi 6.5 EP5 的引用 (52402)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Foundation

Related Versions:

Take Our Survey

Support Assistant