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

Add Cluster or Host fails with error 504 Gateway Time-out in VMware Cloud Foundation on Vxrail (74526)

Last Updated: 4/14/2020Categories: TroubleshootingTotal Views: 5467Language:
English

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

Symptoms

Adding a Cluster or Esxi host(s) fails with a 504 Gateway Time-out in the SDDC Manager UI.

Attempting to log in to the SDDC Manager UI, reports :  Bad gateway, nginx/1.15.

Purpose

Increase the timeout value for nginx and SDDC manager UI in the VCF on VxRail deployment prior to VCF version 3.9.1.

Cause

In large scale VMware Cloud Foundation on VxRail deployments, the discovery of the Cluster or ESXi hosts takes more than the default time-out value for the "nginx" and "SDDC Manager UI services.

Nginx  gateway  default timeout  value is 1 minute.

SDDC Manager UI server default timeout value is 2 minute.

Resolution

This is a known issue affecting the mentioned versions, this will be fixed in future release. Please see the below section to workaround this issue.

Workaround

Take a snapshot of SDDC manager Controller VM.

Download the extract  vxrail-scale-fixitup-v2.2.py script attached to the KB.

Use a file transfer utility to upload the vxrail-scale-fixitup-v2.2.py script to the /tmp/ directory on the SDDC Manager Controller VM.

SSH to the SDDC Manager Controller VM as the vcf user.

Issue the following command to switch to the root user account:

# su

Run the following command to check the health state of nginx.

# nginx -t

Example:

root@sddc-manager [ ~ ]# nginx -t

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

Note: Do not run the vxrail-scale-fixitup-v2.2.py script if nginx.conf  is not in a healthy state.

Run the following command to confirm the sddc-manager-ui-app service is up.

# curl localhost/sddc-manager-ui-app/about | json_pp

Example:
root@sddc-manager [ ~ ]# curl localhost/sddc-manager-ui-app/about | json_pp
{
"author" : "VMware",
"version" : "3.8.0-RELEASE-14212073",
"dbSchemaVersion" : 1,
"builtBy" : "mts",
"createdBy" : "Apache Maven 3.5.0",
"buildDate" : "2019-07-22T03:13:24Z",
"id" : "c091bdb5-6558-40e6-9011-2794e9fc61de",
"name" : "SDDC-MANAGER-UI-APP"

Navigate to path /tmp/ directory.

Run the following command to execute the script to increase the nginx and SDDC_MANAGER_UI time out.

# python vxrail-scale-fixitup-v2.2.py

Note: The script will backup the following files at their original locations before modifying them:

-  /opt/vmware/vcf/sddc-manager-ui-app/server/src/servers/sddcManagerServer/www.js file.
- /etc/nginx/nginx.conf file.

Re-run the commands in steps 6 and 7 to verify the status of nginx and sddc-manager-ui-app  after running the vxrail-scale-fixitup-v2.2.py script.

Note:

If nginx  and sddc-manager-ui-app are not in healthy state after running the script and and the SDDC Manager UI is not loading, please restore the www.js and  the nginx.conf files from their backups or revert the SDDC Manager to the snapshot that was taken before running the script.

The  vxrail-scale-fixitup-v2.2.py script should only be run once on a system, running  it twice  without restoring  www.js and nginx.conf files from their backup files or reverting the snapshot will cause nginx  service to not startup.

The VCF upgrade to any version prior to VCF 3.9.1 will overwrite the www.js and  nginx.conf files and revert the Time-out value back to default. So the vxrail-scale-fixitup-v2.2.py script will need to be re-run again after upgrading to any VCF version prior to 3.9.1.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

vxrail-scale-fixitup-v2.2.py

Additional Resources

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

KB
•
Download and Install VMware Fusion (2014097)

KB
•
My Workspace ONE 週刊ナレッジベース ダイジェストの廃止 (74652)

KB
•
Workspace ONE Notebook 1.4 for Android リリースのお知らせ (79156)

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 Cloud Foundation on VxRail

VMware Cloud Foundation

Related Versions:

VMware Cloud Foundation on VxRail 3.8.x

VMware Cloud Foundation on VxRail 3.7.x

VMware Cloud Foundation 3.9.x

Take Our Survey

Support Assistant