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 Rotation failing in SDDC Manager after manually updating the vRealize Log Insight passwords. (67380)

Last Updated: 3/22/2019Categories: TroubleshootingTotal Views: 3858Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

Password Rotation is failing with the error: FAILED - SsoRotatorTask

The certificate in use for vRealize Log Insight contains the fully qualified domain name for the cluster address but not the IP address.

You see messages similar to the following in the /home/vrack/vrm/logs/vrack-vrm.log file on the SDDC Manager Controller VM:

2019-01-18 11:14:15.345 [pool-2-thread-10] INFO  [com.vmware.vrack.vrm.core.util.HttpClientService] Initializing Http client hosted with 1 threads.

2019-01-18 11:14:15.772 [pool-2-thread-10] INFO  [com.vmware.vrack.vrm.cms.updaters.LogInsightSsoUpdater] vRLI logging is disabled, updating only management vCenter in vRLI

2019-01-18 11:14:15.790 [pool-2-thread-10] INFO  [com.vmware.vrack.vrm.core.util.HttpClientService] Initializing Http client hosted with 1 threads.

2019-01-18 11:14:16.059 [pool-2-thread-10] ERROR [com.vmware.vrack.vrm.cms.updaters.LogInsightApiClient] LogInsight login API failed after 6 retries

2019-01-18 11:14:16.060 [pool-2-thread-10] ERROR [com.vmware.vrack.vrm.cms.workflows.rotators.SsoRotatorTask] 59dffe00-2675-49d0-bb4a-aa70aea8bbe9: SsoRotatorTask:192.168.160.23: failed java.lang.IllegalStateException: could not get credential

at com.vmware.vrack.vrm.cms.updaters.LogInsightApiClient.getCredential(LogInsightApiClient.java:76)

at com.vmware.vrack.vrm.cms.updaters.LogInsightSsoUpdater.test(LogInsightSsoUpdater.java:87)

at com.vmware.vrack.vrm.cms.workflows.rotators.AbstractRotatorTask.doUpdatersTest(AbstractRotatorTask.java:311)

at com.vmware.vrack.vrm.cms.workflows.rotators.AbstractRotatorTask.run(AbstractRotatorTask.java:229)

at com.vmware.vrack.vrm.core.engine.SimpleWorkflowEngine.executeTask(SimpleWorkflowEngine.java:550)

at com.vmware.vrack.vrm.core.engine.SimpleWorkflowEngine.runSingleTask(SimpleWorkflowEngine.java:501)

at com.vmware.vrack.vrm.core.engine.SimpleWorkflowEngine.access$1000(SimpleWorkflowEngine.java:47)

at com.vmware.vrack.vrm.core.engine.SimpleWorkflowEngine$2.run(SimpleWorkflowEngine.java:311)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

at java.lang.Thread.run(Thread.java:748)

Caused by: java.lang.IllegalStateException: could not get sessionId

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

In SDDC Manager, both the Fully Qualified Domain Name and the IP address are required in the Subject Alternative Name for the vRealize Log Insight certificate.

Resolution

Update the SSL certificate for vRealize Log Insight to include both the IP address and the fully qualified domain name in the Subject Alternative Name.

Workaround

You can work around this issue by implementing the following steps.

Note: Take a snapshot of the SDDC Manager Controller VM prior to making any changes.

SSH to the SDDC Manager Controller VM.

Issue the following command to display the relevant Log Insight data in the Cassandra database:

/opt/vmware/cassandra/apache-cassandra-2.2.4/bin/cqlsh -e "select id,hostname,ipaddress,name,vipaddress,vipfqdn from vrmkeyspace.loginsight"

Note: You will see output similar to the following:

id                                   | hostname                         | ipaddress   | name            | vipaddress  | vipfqdn
--------------------------------------+----------------------------------+-------------+-----------------+-------------+-------------------------------------
b4b2fc01-3af8-11e9-af8f-fde4f87f9cdd | loginsight-vm-3.vcf.vxrack.local | 192.30.0.27 | loginsight-vm-3 |        null |                                null
b4b2d4f0-3af8-11e9-af8f-fde4f87f9cdd | loginsight-vm-1.vcf.vxrack.local | 192.30.0.25 | loginsight-vm-1 | 192.30.0.28 | loginsight-cluster.vcf.vxrack.local
b4b2fc00-3af8-11e9-af8f-fde4f87f9cdd | loginsight-vm-2.vcf.vxrack.local | 192.30.0.26 | loginsight-vm-2 |        null |                                null

Note: Make a note of the id, vipaddress and vipfqdn values for the entry where the vipfqdn value is populated. In this example, the id value is b4b2d4f0-3af8-11e9-af8f-fde4f87f9cdd, the vipaddress is 192.30.0.25 and vipfqdn value is loginsight-cluster.vcf.vxrack.local.

Issue a command similar to the following to temporarily change the vipaddress value in the vrmkeyspace.loginsight table to the fully qualified domain name instead of the IP address:

/opt/vmware/cassandra/apache-cassandra-2.2.4/bin/cqlsh -e "update vrmkeyspace.loginsight set vipaddress='loginsight-cluster.vcf.vxrack.local' where id=b4b2d4f0-3af8-11e9-af8f-fde4f87f9cdd"

Note: Replace loginsight-cluster.vcf.vxrack.local and b4b2d4f0-3af8-11e9-af8f-fde4f87f9cdd with the values noted for vipfqdn and id (respectively) in Step 2.

Run the password rotation again.

Issue a command similar to the following to change the vipaddress value in the vrmkeyspace.loginsight table back to the original IP address:

/opt/vmware/cassandra/apache-cassandra-2.2.4/bin/cqlsh -e "update vrmkeyspace.loginsight set vipaddress='192.30.0.26' where id=b4b2d4f0-3af8-11e9-af8f-fde4f87f9cdd"

Note: Replace 192.30.0.26 and b4b2d4f0-3af8-11e9-af8f-fde4f87f9cdd with the values noted for vipaddress and id (respectively) in Step 2.

Note: The snapshot taken at the beginning of this process can be removed.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

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:

VMware Cloud Foundation 2.x

Take Our Survey

Support Assistant