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

Password/Credentials rotate operation in VMware SDDC Manager fails with 504 gateway timed out (78862)

Last Updated: 6/29/2020Categories: TroubleshootingTotal Views: 4704Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

SDDC Manager UI shows "504 gateway timed out" error.

The workflows fails in a large scale environment or an old deployments with large amount of historical credentials/password rotate operations.

Attempting to retry the workflow also shows "504 gateway timed out."

Cause

The backend services take more than 60 seconds to fetch details of the FAILED task to provide RETRY option but since UI gateway at nginx is configured to wait only for 60 seconds so it sends back a timeout error message to the UI.

Resolution

To fix the issue in existing environments it's advised to increase the gateway timeout from 60 seconds to 900 seconds. This will allow the SDDC Manager UI to wait longer to complete the operation.
In the unlikely event the timeout error is still observed after making the below changes, the timeout value can be increased to an even larger value, for example 1200 seconds.

Please find below the workaround needed to be applied to nginx.conf file where we increase the timeout for credentials API's.

Steps to update nginx.conf File:

Open a SSH session to the SDDC Manager VM and switch to the root user:

su -

Using a text editior, open the nginx.conf file at following location /etc/nginx/nginx.conf.

Search for the string "credentials" where the line matches the following:

location  ~ ^/v1/(hosts|license-keys|credentials|certificate-authorities|skyline)":

Modify the line from the following:

# operationsmanager v1 public APIs

location ~ ^/v1/(hosts|license-keys|credentials|certificate-authorities|skyline)(.*) {

proxy_pass http://127.0.0.1:7300/operationsmanager/v1/$1$2$is_args$args;

}

Replacing with:

# operationsmanager v1 public APIs
location ~ ^/v1/(hosts|license-keys|credentials|certificate-authorities|skyline)(.*) {
proxy_read_timeout 900;
proxy_connect_timeout 900;
proxy_send_timeout 900;
proxy_pass http://127.0.0.1:7300/operationsmanager/v1/$1$2$is_args$args;
}

For requests coming from the UI, re-configure the nginx.conf file specifically for UI server request.
Please find below steps:

Search for the string ""location ~ /ui/.* {"" where the line matches the following.

Add the entry to reflect the same as below:

location ^~ /ui/api/v1/credentials {
proxy_read_timeout 900;
proxy_connect_timeout 900;
proxy_send_timeout 900;

# UI server handles auth via PSC/SSO
proxy_pass http://127.0.0.1:7500;
}

Restart the nginx servce:

systemctl restart nginx.service

The timeout setting on the nodejs server service will also need to be increased from the default of 2 minutes.

Open a SSH session to the SDDC Manager VM and switch to the root user:

su -

Stop SDDC Manager UI service

systemctl stop sddc-manager-ui-app

Update UI server connection timeout value by editing /opt/vmware/vcf/sddc-manager-ui-app/server/src/servers/sddcManagerServer/www.js file

Search for the string "server.listen" in the file and Add line "server.timeout = 900000; " below.

Save and exit the file.

Start SDDC Manager UI service

systemctl start sddc-manager-ui-app

Allow some time of the service to start, check the status by running:

systemctl status sddc-manager-ui-app

At this time, the password workflow can be started.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
确定 vRealize Automation 7.x 置备失败的根本原因 (79611)

Result 1 of 1

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