In both EucalyptusNC/services.xml and EucalyptusCC/services.xml there's no ClockSkewBuffer (nor TimeToLive nor PrecisionInMilliseconds), therefore messages "from the future" (from the webservice's point of view) won't be accepted, even if the difference in time is minimal.
This happens on a default Ubuntu 11.04 x64 cloud server installation, after a full upgrade (apt-get update && apt-get dist-upgrade) and a reboot.
Eucalyptus' package version is 2.0.1+bzr1256-0ubuntu4.1
In both EucalyptusNC/ services. xml and EucalyptusCC/ services. xml there's no ClockSkewBuffer (nor TimeToLive nor PrecisionInMill iseconds) , therefore messages "from the future" (from the webservice's point of view) won't be accepted, even if the difference in time is minimal.
This happens on a default Ubuntu 11.04 x64 cloud server installation, after a full upgrade (apt-get update && apt-get dist-upgrade) and a reboot.
Eucalyptus' package version is 2.0.1+bzr1256- 0ubuntu4. 1
For a more detailed description on this issue, see a question I asked in ServerFault: http:// serverfault. com/questions/ 313200/ ubuntu- enterprise- cloud-ncs- down-and- time-synchroniz ation