"time synchronization problem with your system" error

[hubloko]

I saw the other thread about time synchronization but I'm having trouble to solve this problem. I'm posting the asterisk -r output:

Connected to Asterisk 1.4.39-2-vici currently running on linux-gzf1 (pid = 2614)
verbosity is at least 21

versions (the current versions):

OpenSuSE v.11.3 32-bit w/ PAE and 64-bit
Asterisk v.1.4.39.2-vici
DAHDI v.2.4.1.2
LibPRI v.1.4.11.5
Sangoma Wanpipe v.3.5.20
Sangoma VoiceTime v.1.0.11
MFCR2 via OpenR2 v.1.3.0
VTiger CRM v.5.1.0
ViciDial v.2.2.1
ViciDial SVN Trunk v.2.4-334a build 110831-2038
Amfletec VoiceSync v.1.2.3
Multi-Server installation capable
Simplified "Preload" ISO and express installer option
ZoiperWeb v.2.4.0

[williamconley]

Please post the name of the .iso disk from which you installed (this will include the .iso installer version ...).

Also: You seem to have a bit of a contradiction here:

ViciDial v.2.2.1
ViciDial SVN Trunk v.2.4-334a build 110831-2038

You cannot have two versions of Vicidial. It is possible you copied one from the web page you downloaded from, and the rest from your actual server ... if so, ONLY use the Vicidial version from your live machine.

As a rule, time sync errors occur for two basic reasons: The first reason is "dropping packets". Your agent screens run on a workstation that must have NO packets dropping to the vicidial server. If you drop packets, vicidial will toss this error constantly until you fix your network connections. The second is that you have a multi-server setup and they are not time-synced.

Also, from time to time, we get issues with time settings within the server (playing with time settings is a bad idea!). php.ini must agree with the server's OS. If you have played with the time settings at all, it can be simpler to reinstall and 'keep your fingers out of the cookie jar'. After your Vicidial server is online, certified, running smoothly ... then make cool change and tweaks. Until then ... flat install with no changes to avoid complications caused by manager error.

[GaD]

This has also happened to me when I've had to change server IP. I remember I had to run the script that updates the server IP in the database but still was not enough. I removed and recreated the extensions and all was fine after that.....