NGupta201110141
Contributor
Contributor

Failed to connect to the Serengeti Management Server

Jump to solution

I am building a test setup for BDE and now I am stuck with a problem.

Issue: Failed to connect to the Serengeti Management Server using BDE plugin in Web Client. After selecting the Serengeti Management Server, when I click on OK, I get a "Connection Failed!" error message. Screen shot of the error is attached.

Things that I have tried so far:

1. I have tried using IE, Firefox, but I get same error.

2. Uninstalled the BDE plugin, Re-installed it, but still same problem

3. DNS resolution is working absolutely fine.

4. I am able to ping to/from all possible directions

5. The vApp was deployed with the Initialize Resources box checked. Also, SSO registration was performed

6. Have deployed a brand new vApp couple of times, but still same problem.

7. When vApp is deployed without SSO registration, I can connect using Serengeti CLI, but from Web Client, I still get same issue. Strangely, witth SSO registration enabled, I cannot to Serengeti CLI as well.

8. As per the other posts, ran <EnableSSOAuth> command and restarted the Tomcat services. Still same issue.

9. Have rebooted SSO, VC, vAPP, but no luck.

Snippet of Serengeti server logs is below:

[root@bigdata ~]# tail -f /opt/serengeti/logs/serengeti.log

at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
        at java.lang.Thread.run(Thread.java:636)
2013 Aug 05 21:01:11,245+0000 INFO  http-8080-3| com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor: Request message has expired. Server message: ns0:MessageExpired: Request has expired
2013 Aug 05 21:01:11,245+0000 INFO  http-8080-3| com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor: Server returned 'request expired' less than 0 seconds after request was issued, but it shouldn't have expired for at least 600 seconds.
2013 Aug 05 21:01:11,245+0000 ERROR http-8080-3| com.vmware.bdd.security.sso.utils.SecurityUtils: Cannot validate the token by sso: Server returned 'request expired' less than 0 seconds after request was issued, but it shouldn't have expired for at least 600 seconds.

[root@bigdata ~]# tail -f /opt/serengeti/logs/vhm.log

[root@bigdata ~]# tail -f /opt/serengeti/logs/vhm.log

2013 Aug 05 21:22:19.878 [ClusterSCL_Poll_Thread-VcVlsi] No found clusters for hadoop UUID SERENGETI-vApp-BDEvApp

2013 Aug 05 21:22:19.878 [ClusterSCL_Poll_Thread-ChangeListener] Temporarily lost connection to VC...

2013 Aug 05 21:22:24.988 [ClusterSCL_Poll_Thread-VcVlsi] No found clusters for hadoop UUID SERENGETI-vApp-BDEvApp

2013 Aug 05 21:22:24.988 [ClusterSCL_Poll_Thread-ChangeListener] Temporarily lost connection to VC...

2013 Aug 05 21:22:30.98 [ClusterSCL_Poll_Thread-VcVlsi] No found clusters for hadoop UUID SERENGETI-vApp-BDEvApp

2013 Aug 05 21:22:30.99 [ClusterSCL_Poll_Thread-ChangeListener] Temporarily lost connection to VC...

Has anyone seen this problem?

Regards,

Nitin Gupta


0 Kudos
1 Solution

Accepted Solutions
JunW
Enthusiast
Enthusiast

I saw the log said " com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor: Server returned 'request expired' less than 0 seconds after request was issued, but it shouldn't have expired for at least 600 seconds." for these login request. According to KB at http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=203808...

You may need to update the locale time of vc server. Please have a try according to this KB, and see if it works.

Thanks,

Jun

View solution in original post

0 Kudos
2 Replies
JunW
Enthusiast
Enthusiast

I saw the log said " com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor: Server returned 'request expired' less than 0 seconds after request was issued, but it shouldn't have expired for at least 600 seconds." for these login request. According to KB at http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=203808...

You may need to update the locale time of vc server. Please have a try according to this KB, and see if it works.

Thanks,

Jun

0 Kudos
NGupta201110141
Contributor
Contributor

Thanks for your reply Jun. That did guide me in the right direction. VC, SSO, DC all had US as its location. But, the ESXi servers in the cluster were not in time sync. Changing the time on the host to match the time of VC fixed the problem.

Thanks again for your help.

Regards,

Nitin Gupta cde4

0 Kudos