time synchronization issue

[adoman22]

Hello everyone. Before I begin here is my system information for you.

Vicibox 7 install
Opensuse 42.1
asterisk 11.22

This week i started getting an issue that is popping up periodic on agent screen " Time synchronization error" So with that it is not allowing to make calls at all. I have had this issue before so there was a few things that i checked first.

I ran # Date -- to make sure the system date for some reason has not changed. The date was correct.

All of the agent computers matched to the date as well. Now i have been using this install for the last 5 or 6 months. Nothing on the system has changed so it has got me baffled.

I then checked asterisk to see if something was wrong there. I could not log into asterisk using #asterisk -rvvvvvv-- i then checked the status of asterisk and it stated [dead]. I then restarted asterisk and it showed it as [running].

This issue has happened 1-2 times / day over the last 5 days. The only thing that seems to fix the issue is rebooting the whole server. As you can see restarting a dialing server 1-2 times per day is becoming a hastle and should not be happening.

What could be causing asterisk to stop all of sudden and for the time sync error?

[adoman22]

Another update.

The issue just happened again. And i went in to look at asterisk. i typed # asterisk -r (which actually allowed me to login this time,), but still when i typed # service asterisk status (it says it is dead, but still allows me to login. I am confused)

[williamconley]

1) Welcome to the Party!

2) As you are obviously new here, I have some suggestions to help us all help you:

When you post, please post your entire configuration including (but not limited to) your installation method (7.X.X?) and vicidial version with build (VERSION: 2.X-XXXx ... BUILD: #####-####).

This IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "manual/from scratch" you must post your operating system with version (and the .iso version from which you installed your original operating system) plus a link to the installation instructions you used. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

3) NEVER respond to your own post. If there have been no comments by anyone else, just edit the original. Otherwise you are considered to have "answered" the post by being the first commenter. This causes you to disappear from the "Unanswered" list and you could experience a significant delay in gettng a response. IE: We all thought someone else answered you. But it was just you talking to yourself. lol

4) You did try to post your specs, but you did NOT post your Vicidial Version with Build. Tsk.

5) Asterisk is not being run as a service. If it did, the "console" would be invisible, and there is only one "true console" which has perl scripting errors on it. Thus, Vicidial starts a "screen" and then inside that screen it runs asterisk. This allow catching those perl errors, among other things. screen -list will show you all the screens running in a Vicidial server.

6) Vicidial Time Synchronization errors have hundreds of posts on this forum. Use google to search, you'll find lots of discussion on the topic. In a single server system it's usually dropping packets, but could also be a crashed table or crashed asterisk server. In rare cases it's misconfigured time on the server and in clusters it can happen if time between servers is off by too much.