Cisco Bug: CSCsz99868 - Implement gradual time synchronization
Feb 22, 2014
- Cisco Unified MeetingPlace
Known Affected Releases
Symptom: System cannot update if time difference is greater than 30 seconds. Conditions: We're still seeing systems in the field with the server clock out of sync by more than 30 seconds and therefore unable to sync up the time, which leads to broken recordings. Usually, the workaround in this case is to restart web services, at which point web server clock can synch with the NTP source even when there is a larger offset than 30 seconds. However, in some cases (particularly on machines that belong to a domain), the restart of web services does not synch clock immediately, and a subsequent restart is required. The problem can be reproduced on some machines in a domain, by doing the following: 1. Stop the MeetingPlace services. 2. Move system time on the web-server for two minutes ahead of current time. 3. Start the MeetingPlace services.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases