VMware {code} Community
SreeSindhuSruth
Enthusiast
Enthusiast
‎06-19-2017 03:17 AM

virgo localhost for sdk 6.5 gives time sync error in logs

Hi,

 

To configure virgo server with any vCenter did the following:

For windows copied the webclient.properties, ds, store,jks in vsphere-client/cfg as in the documentation of 6.5

for VCSA followed the fully automated part of the documentation and webclientproperties got genereated in vsphere-clent/cfg.

started the server by running startup.bat in html-clientsdk/vpshere-client/server/bin/startup.bat

Checked the logs -it has the error:

<code>c.vmware.vise.vim.connections.SiteAffinityServerEndpointProvider  CDC is misconfigured. Will not use CDC. java.lang.UnsatisfiedLinkError: no libcdcjni in java.library.path

at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1886)

at java.lang.Runtime.loadLibrary0(Runtime.java:849)

at java.lang.System.loadLibrary(System.java:1088)

at com.vmware.identity.cdc.CdcAdapter.<clinit>(CdcAdapter.java:18)

at com.vmware.identity.cdc.CdcSession.<init>(CdcSession.java:37)

at com.vmware.identity.cdc.CdcFactory.createCdcSessionViaIPC(CdcFactory.java:39)

at com.vmware.vise.vim.connections.SiteAffinityServerEndpointProvider.getCdcData(SiteAffinityServerEndpointProvider.java:201)

at com.vmware.vise.vim.security.sso.impl.SsoCmLocatorImpl.getCdcDataNoException(SsoCmLocatorImpl.java:111)

[ERROR] cm-catalog-manager-pool-5     com.vmware.vim.sso.client.impl.SoapBindingImpl                    SOAP fault javax.xml.ws.soap.SOAPFaultException: The time now Mon Jun 19 13:35:22 IST 2017 does not fall in the request lifetime interval extended with clock tolerance of 600000 ms: [ Mon Jun 19 03:28:08 IST 2017; Mon Jun 19 03:58:08 IST 2017). This might be due to a clock skew problem.

at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178)

at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:117)

at com.sun.xml.internal.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:184)

at com.sun.xml.internal.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:203)

at com.vmware.vim.sso.client.impl.SoapBindingImpl.sendMessage(SoapBindingImpl.java:161)

at com.vmware.vim.sso.client.impl.SoapBindingImpl.sendMessage(SoapBindingImpl.java:114)

at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.sendRequest(SecurityTokenServiceImpl.java:784)

at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.executeRoundtrip(SecurityTokenServiceImpl.java:714)

at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl.acquireTokenByCertificate(SecurityTokenServiceImpl.java:473)

 

 

 

 

 

[ERROR] cm-catalog-manager-pool-5     com.vmware.vise.vim.security.sso.impl.SsoUtilInternal             Time sync error: VC Server and local machine's clocks are out of sync by more than the accepted tolerance. 

[2017-06-18T15:08:09.233-07:00] [ERROR] cm-catalog-manager-pool-5     com.vmware.vise.vim.security.sso.impl.NgcSolutionUser             Solution user login failed. com.vmware.vim.sso.client.exception.TimeSynchronizationException: Server returned 'request expired' less than 0 seconds after request was issued, but it shouldn't have expired for at least 600 seconds.

at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.checkTimeSyncronization(SecurityTokenServiceImpl.java:758)

at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.executeRoundtrip(SecurityTokenServiceImpl.java:716)

at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl.acquireTokenByCertificate(SecurityTokenServiceImpl.java:473)

at com.vmware.vise.vim.security.sso.impl.SsoUtilInternal.acquireTokenByCertificate(SsoUtilInternal.java:716)

at com.vmware.vise.vim.security.sso.impl.NgcSolutionUser.login(NgcSolutionUser.java:229)

 

</code>

c.vmware.vise.vim.connections.SiteAffinityServerEndpointProvider  CDC is misconfigured. Will not use CDC. java.lang.UnsatisfiedLinkError: no libcdcjni in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1886)
at java.lang.Runtime.loadLibrary0(Runtime.java:849)
at java.lang.System.loadLibrary(System.java:1088)
at com.vmware.identity.cdc.CdcAdapter.<clinit>(CdcAdapter.java:18)
at com.vmware.identity.cdc.CdcSession.<init>(CdcSession.java:37)
at com.vmware.identity.cdc.CdcFactory.createCdcSessionViaIPC(CdcFactory.java:39)
at com.vmware.vise.vim.connections.SiteAffinityServerEndpointProvider.getCdcData(SiteAffinityServerEndpointProvider.java:201)
at com.vmware.vise.vim.security.sso.impl.SsoCmLocatorImpl.getCdcDataNoException(SsoCmLocatorImpl.java:111)
[ERROR] cm-catalog-manager-pool-5     com.vmware.vim.sso.client.impl.SoapBindingImpl                    SOAP fault javax.xml.ws.soap.SOAPFaultException: The time now Mon Jun 19 13:35:22 IST 2017 does not fall in the request lifetime interval extended with clock tolerance of 600000 ms: [ Mon Jun 19 03:28:08 IST 2017; Mon Jun 19 03:58:08 IST 2017). This might be due to a clock skew problem.
at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178)
at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:117)
at com.sun.xml.internal.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:184)
at com.sun.xml.internal.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:203)
at com.vmware.vim.sso.client.impl.SoapBindingImpl.sendMessage(SoapBindingImpl.java:161)
at com.vmware.vim.sso.client.impl.SoapBindingImpl.sendMessage(SoapBindingImpl.java:114)
at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.sendRequest(SecurityTokenServiceImpl.java:784)
at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.executeRoundtrip(SecurityTokenServiceImpl.java:714)
at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl.acquireTokenByCertificate(SecurityTokenServiceImpl.java:473)
 
 
 
 
 
[ERROR] cm-catalog-manager-pool-5     com.vmware.vise.vim.security.sso.impl.SsoUtilInternal             Time sync error: VC Server and local machine's clocks are out of sync by more than the accepted tolerance. 
[2017-06-18T15:08:09.233-07:00] [ERROR] cm-catalog-manager-pool-5     com.vmware.vise.vim.security.sso.impl.NgcSolutionUser             Solution user login failed. com.vmware.vim.sso.client.exception.TimeSynchronizationException: Server returned 'request expired' less than 0 seconds after request was issued, but it shouldn't have expired for at least 600 seconds.
at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.checkTimeSyncronization(SecurityTokenServiceImpl.java:758)
at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.executeRoundtrip(SecurityTokenServiceImpl.java:716)
at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl.acquireTokenByCertificate(SecurityTokenServiceImpl.java:473)
at com.vmware.vise.vim.security.sso.impl.SsoUtilInternal.acquireTokenByCertificate(SsoUtilInternal.java:716)
at com.vmware.vise.vim.security.sso.impl.NgcSolutionUser.login(NgcSolutionUser.java:229)
Reply
0 Kudos
4 Replies
Plam_Dimitrov
VMware Employee
VMware Employee
‎06-23-2017 06:27 AM

Hello,

These kinds of errors happen when the clock of your local machine and that of the vCenter differ by more than the accepted amount (which is currently 10 minutes). At least one of those machines should have their clock set to the wrong time - make sure to adjust it to the correct time and the issue should be fixed.

Reply
0 Kudos
_vladi_
VMware Employee
VMware Employee
‎06-28-2017 02:38 PM

Not really. It is not about timezones but clock synchronization. You need to synchronize the machine that has the wrong time set:

 - If that is your local machine see this article.

 - If it is your vCenter (you can check the timestamps in the logs for correctness) see this article.

Cheers,

Vladi

Reply
0 Kudos
SreeSindhuSruth
Enthusiast
Enthusiast
‎07-12-2017 03:06 AM

_vladi_​

From the below error, is the synchronization issue is with the dev machine or vCenter.

I use dev (which is VM) and restarted the vm such that vm tools run during power of//on.

vCenter has been restarted as well.

[2017-07-12T05:14:07.300+05:30] [INFO ] http-bio-9443-exec-2         
70000021 100001 ###### c.v.v.s.c.impl.SecurityTokenServiceImpl$RequestResponseProcessor  
Request message has expired. Server message: ns0:MessageExpired
: The time now Wed Jul 12 23:43:46 IST 2017 does not fall in the request lifetime interval extended with clock tolerance of 600000 ms:
[ Wed Jul 12 05:04:07 IST 2017; Wed Jul 12 05:34:07 IST 2017). This might be due to a clock skew problem.
Reply
0 Kudos
_vladi_
VMware Employee
VMware Employee
‎07-12-2017 03:47 AM

Hi,

Just restarting the machines will not fix this problem

Your logs specify that the current time of your dev machine is 23:43:46 while the current time of your vCenter is 05:14:07. So the difference in time is more than 18 hours which is a lot higher than the request timeout (=10 min) + the clock tolerance of 600000ms (=10 min).

As I don't know when you have been testing this and generating this log I am not sure which one is correct. Just try it again and see which of the above times is actually correct.

The wrong one needs to be updated using the commands you can find in the respective links I provided earlier for both possibilities.

Cheers,

Vladi

Reply
0 Kudos